What it says
What this says
Current to 10 Oct 26Final quarterly business review for Fenmoor's Enterprise account, written by Daniel Okafor. It reports steady usage by a small core group, one ticket and no overdue invoices. It flags thin adoption and unclear sponsorship ahead of the 30 Jun 2027 contract end.
What it is: a customer-facing QBR deck by Daniel Okafor, dated 15 Sep 2026 and marked Final. It covers usage, value, service, risks, opportunities and a next-quarter plan.
Says: active users average "just under seventeen" over thirty days, with "a lot of headroom left". One ticket, none high priority, no overdue invoices.
Risks: "Most of the licensed seats are unused", and the deck notes data and analytics leadership "has been moving", so the current sponsor is unconfirmed.
Not settled: the deck gives no contracted ARR or licensed user number and defers to the executed order form. It also does not show which questions are asked or by whom. It commits B-Brain to no service terms.
As found in this document
Current to 9 Oct 26- Date end
- 30 Jun 2027
The document
Body
Fenmoor Specialty Underwriting - Quarterly Business Review
Prepared by Daniel Okafor, Customer Success Manager, B-Brain
Review date: Tuesday 15 September 2026
Status: Final
Where we are
| Item | Detail |
|---|---|
| Customer | Fenmoor Specialty Underwriting |
| Customer since | Monday 1 July 2024 |
| Tier | Enterprise |
| Contract end | 30 Jun 2027 |
| Account owner | Priya Raman |
| Customer Success Manager | Daniel Okafor |
Fenmoor has been on the brain since go-live on 1 Jul 2024. This review covers the last quarter: how the team is using the brain, what it is worth to Fenmoor's underwriting operations, what has gone wrong, and what we plan next.
Usage
- Active users average just under seventeen over the last thirty days, a little up on the prior quarter.
- That is a small share of the Enterprise user allowance, so there is a lot of headroom left. The brain is being used by a core group rather than across the whole business.
- Usage is steady rather than spiking, which suits a team answering regular oversight questions from capacity providers.
What the numbers do not show
Read the whole document (4,249 characters)
The headline usage tells us how many people are active, not which questions matter most. In the session I would like to hear from the team which questions they now ask the brain first, and which they still answer by hand.
Value
Fenmoor bought the brain so underwriting operations can answer capacity providers' oversight questions from one view of submissions, bordereaux queries, claims tickets and CRM activity.
- Submissions, bordereaux queries, claims tickets and CRM activity sit in one place inside Fenmoor's own Snowflake account.
- The team no longer has to reconcile those systems by hand before an oversight conversation.
- The value case is strongest where a capacity provider asks a question that would previously have meant pulling several people off their day jobs.
Just to close the loop on the commercial side: the contracted annual recurring revenue and the licensed user number are as set out in the executed order form, which remains the reference for price and terms.
Service and issues
| Measure | Last thirty days |
|---|---|
| Tickets raised | A single ticket |
| High priority tickets | None |
| Overdue invoices | None |
- Only one ticket came in during the period and none was high priority, so there is nothing to escalate.
- Invoices are up to date, so there is no billing question hanging over the account.
- Support has been quiet. With a small group of active users, quiet could mean things are working well, or it could mean the wider team has not yet tried the brain. We should find out which.
Risks and watch points
- Breadth of adoption. Most of the licensed seats are unused. If a few people drive most of the questions, the account depends on them.
- People change. Fenmoor's data and analytics leadership has been moving, so we should confirm who now sponsors the brain on the Fenmoor side and make sure they have seen what it does.
- Renewal. The contract runs to 30 Jun 2027. The renewal conversation is some months away, and the value case should be built well before then.
Opportunities
- Bring in further teams, for example claims and compliance, who already see the same data through the brain's pages, chat and search.
- Use the Enterprise features Fenmoor has not fully adopted, including SSO and SCIM and the executive sponsor relationship.
- Build more dashboards around the capacity provider oversight reporting, so the value is visible without anyone having to ask.
Plan for the next quarter
| Action | Owner | Timing |
|---|---|---|
| Confirm the current sponsor and their priorities | Daniel Okafor | Before the next review |
| Map which teams ask questions today and which do not | Daniel Okafor with Fenmoor's operations lead | Within the quarter |
| Agree two or three target use cases for wider adoption | Fenmoor team with Daniel Okafor | Within the quarter |
| Put together a short written value summary for the renewal | Daniel Okafor | Well ahead of the renewal |
Closing
Thank you to everyone at Fenmoor for their time. I'll come back to you with the adoption map once we have it. How is the team finding it?
Best wishes, Daniel