Fenmoor Specialty Underwriting - QBR
Documentfinal Fenmoor Specialty Underwriting: documents · qbr_deck · final · 2025-05-18
Quarterly business review dated 18 May 2025, prepared by Daniel Okafor. It reports a steady Growth account with a slight dip in active users and frames a like-for-like renewal before the term ended on 30 Jun 2025. It is now stale.
What it says
What this says
Current to 10 Oct 26Quarterly business review dated 18 May 2025, prepared by Daniel Okafor. It reports a steady Growth account with a slight dip in active users and frames a like-for-like renewal before the term ended on 30 Jun 2025. It is now stale.
What it is: A customer success QBR for the Growth tier, prepared by Daniel Okafor, Customer Success Manager, and marked Final. It is a status review, not a contract.
Reports: Use is "around nine active users", slightly down, with one ticket in the month and no overdue invoices. It names a small core group as a key-person risk.
Renewal: It calls the renewal "a like-for-like renewal" on the same Growth tier, users and connectors. Enterprise is offered only as a separate, no-obligation conversation.
Not settled: It states no subscription amount and does not show whether the renewal was signed. It names Priya Raman as account owner but does not show whether she is still in post, so check the executed order form, invoices and HR records.
As found in this document
Current to 9 Oct 26- Date end30 Jun 2025Source: object_read:doc_001_014
- Date renewal30 Jun 2025Source: object_read:doc_001_014
- Date start1 Jul 2024Source: object_read:doc_001_014
The document
Body
Fenmoor Specialty Underwriting - Quarterly Business Review
Prepared by: Daniel Okafor, Customer Success Manager, B-Brain Account owner: Priya Raman Review date: Sunday 18 May 2025 Status: Final
Where we are
- Fenmoor has been a B-Brain customer since 1 Jul 2024, on the Growth tier.
- The current contract term ends on 30 Jun 2025, so this review is also the natural moment to talk about what comes next.
- The brain runs inside Fenmoor's own Snowflake account and gives underwriting operations one view of submissions, bordereaux queries, claims tickets and CRM activity.
- The purpose is simple: to let the team answer capacity providers' oversight questions without reconciling systems by hand.
Contract snapshot
| Item | Position |
|---|---|
| Tier | Growth |
| Contract start | 1 Jul 2024 |
| Contract end | 30 Jun 2025 |
| Subscription | The contracted annual Growth subscription, billed annually in advance |
| Licensed users | The full Growth user allowance |
| Invoices | None overdue |
Usage this quarter
Read the whole document (4,414 characters)
- Daily use averages around nine active users over the last thirty days.
- That is slightly down on the previous quarter, a small dip rather than a collapse.
- Use sits comfortably inside the Growth user allowance, so there is plenty of headroom if more people want to join.
- The pattern looks like a core group of underwriting operations users who rely on the brain day to day, with a wider group dipping in occasionally.
What I would like to understand
- Whether the small dip reflects holidays and the usual spring workload, or a change in who is asking questions.
- Whether anyone in the wider underwriting and claims teams has not yet been shown what the brain can do for them.
Value delivered
- Underwriting operations can answer oversight questions from one place instead of chasing several systems.
- Bordereaux queries, claims tickets and CRM activity sit alongside submissions, so a question that once took a morning of cross-checking can be asked in plain English.
- The team has told us in earlier conversations that the single view is what they value most. I would like to capture a couple of specific examples before renewal so the value can be written down and not just remembered.
Support and service
| Measure | Last thirty days |
|---|---|
| Tickets raised | A single ticket |
| High priority tickets | None |
| Overdue invoices | None |
- One ticket in a month from a team of this size is a healthy sign. It points to a stable set of connectors and a brain that is doing its job quietly.
- The nightly refresh has been completing as expected, and nothing has been flagged on data freshness.
Risks and watch points
- Adoption breadth. A small core group carries most of the use. If one of them moved on, we would feel it. Widening the circle is the best protection.
- Slight fall in active users. Not alarming, but worth watching over the next quarter rather than assuming it will correct itself.
- Renewal timing. The term ends on 30 Jun 2025, so the conversation needs to start now and not at the last minute.
Plan for the next quarter
| Action | Owner | Timing |
|---|---|---|
| Run a short refresher session for underwriting operations and invite the wider team | Daniel Okafor | Over the next few weeks |
| Capture two or three concrete examples of questions the brain has answered for oversight reporting | Daniel Okafor with the Fenmoor team | Before the renewal conversation |
| Confirm renewal scope with Fenmoor | Priya Raman | Ahead of the term end |
| Review connector health and refresh timings | Daniel Okafor | Ongoing, reported at the next review |
Renewal outlook
- This month's renewal discussion is a like-for-like renewal: the same Growth tier, the same licensed users and the same connectors.
- If Fenmoor would like to explore more teams, more users or the additional features in the Enterprise tier, Priya can talk that through separately, with no obligation.
- Nothing in the data suggests a problem. The aim is to keep things steady and make the value easy to see.
Close the loop
Thank you to everyone at Fenmoor for your time this quarter. I will come back to you with the session dates and the renewal paperwork. In the meantime, how is the team finding it day to day? Do tell me if anything feels slower, harder or less useful than it should.
Best wishes, Daniel