Fenmoor Specialty Underwriting: documents logo

Fenmoor Specialty Underwriting - QBR

Documentfinal

Fenmoor Specialty Underwriting: documents logo Fenmoor Specialty Underwriting: documents · qbr_deck · final · 2026-02-12

Final QBR deck for Fenmoor's Growth tier, prepared by Daniel Okafor on 12 Feb 2026. Usage is steady and invoices are not overdue. The value case is undocumented and the term ends 30 Jun 2026. It states no price or service-level figures.

What it says

What this says

Current to 11 Oct 26

Final QBR deck for Fenmoor's Growth tier, prepared by Daniel Okafor on 12 Feb 2026. Usage is steady and invoices are not overdue. The value case is undocumented and the term ends 30 Jun 2026. It states no price or service-level figures.

What it is: a quarterly business review deck from BB-Demo's Customer Success Manager, Daniel Okafor, for Fenmoor. It says the account is on the Growth tier, with the current term ending 30 Jun 2026.

Usage: users are up "by a smaller step than last time" and questions are "broadly steady, with the same core group asking most of them". It names key-person risk and says the active people remain well below the Growth user allowance.

Commits: it sets owners for an adoption session, a value case and the renewal notice. Renewal pricing "will follow the current price book" and will be set out in writing. It states no price, availability or response-time figures.

Not settled: the deck does not state the contracted annual figure, saying only "As per your executed order form". It does not show finance's view of the renewal, and the renewal date is already past the as-of date, so the outcome is not shown here.

AI · claude-sonnet-5-5 · 11 Oct 2026

As found in this document

Current to 9 Oct 26
  • Date end30 Jun 2026Source: object_read:doc_001_022
  • Date renewal30 Jun 2026Source: object_read:doc_001_022
  • Renewal noticeDaniel will send the formal renewal notice in good timeDaniel will send the formal renewal notice in good time · Source: object_read:doc_001_022
  • Renewal pricingRenewal pricing will follow the current price book and we will set it out in writingRenewal pricing will follow the current price book and we will set it out in writing · Source: object_read:doc_001_022
  • Value summaryI'll come back to you by early next month with a draft value summary and options for the adoption session.I'll come back to you by early next month with a draft value summary and options for the adoption session. · Source: object_read:doc_001_022

The document

Body

Fenmoor Specialty Underwriting - QBR

Quarterly business review | Prepared by Daniel Okafor, Customer Success Manager, BB-Demo | 12 Feb 2026

Status: Final

Welcome and purpose

  • Thank you to everyone at Fenmoor for making time for this review.
  • We look at usage, value, service and the plan for the months ahead, with the renewal at the end of your current term in view.
  • Account owner at BB-Demo: Priya Raman. Customer Success Manager: Daniel Okafor.

Your contract at a glance

ItemPosition
TierGrowth
Customer since1 Jul 2024
Current term ends30 Jun 2026
Contracted annual recurring revenueAs per your executed order form
Licensed usersThe full Growth user allowance
Invoices overdueNone

The account is fully paid up, with nothing overdue.

Usage this quarter

Read the whole document (3,581 characters)
  • Active users: up again on the previous quarter, though by a smaller step than last time. We read that as a team settling into a steady pattern after a period of fast adoption.
  • Questions asked: broadly steady, with the same core group asking most of them. It would be healthy to widen that group a little.
  • Headroom: the number of active people remains well below the Growth user allowance, so there is room to grow within the current contract.
  • Records indexed: continuing to rise, so the brain is not going stale.

Value delivered

  • Underwriting operations can still answer capacity providers' oversight questions from one view of submissions, bordereaux queries, claims tickets and CRM activity.
  • The value is real but largely unwritten. Before the renewal conversation we would like to put it on paper, in a form your own finance and leadership colleagues can read without us in the room.
  • We would like to understand which oversight questions now take minutes rather than hours, and how often they come up.

Support and service

  • No support tickets were raised in the last month and none were high priority.
  • Nightly refresh and availability have both been on target for the period.
  • Quiet queues alongside steady usage look like a team that is getting what it needs. If that is not the whole story, please tell us.

Risks and open points

  • Usage is concentrated in a small group. If one of them moved on, a good share of the questions would go with them.
  • The value case is not yet documented, which matters because the term ends on 30 Jun 2026.
  • We have not yet heard from your finance side about the renewal, and would like to involve them early.

Plan for the coming months

  • Adoption: a short session for colleagues who have not yet logged in, aimed at the people who receive oversight questions. Owner: Daniel Okafor.
  • Value case: a one-page summary of time saved and questions answered, agreed with your operations lead. Owner: Daniel Okafor.
  • Renewal: Daniel will send the formal renewal notice in good time, and Priya Raman will talk through commercial terms with you. Renewal pricing will follow the current price book and we will set it out in writing, so there are no surprises.
  • Growth options: if more teams want to use the brain, we can look at the additional users or connectors that would fit, but only if there is a real need.

Summary

  • Usage is steady and still growing, if more gently.
  • Service has been quiet and on target.
  • The next job is to make the value visible and widen the user base ahead of the renewal.
  • I'll come back to you by early next month with a draft value summary and options for the adoption session.

Best wishes, Daniel

Documentsmade from

Unusual terms

Not yet analysedThe unusual terms of object_read:doc_001_022 are empty: the record found none.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

HelpAsk B

Ask B

B-Brain · read-only