Fenmoor Specialty Underwriting: documents logo

Fenmoor Specialty Underwriting - QBR

Documentfinal

Fenmoor Specialty Underwriting: documents logo Fenmoor Specialty Underwriting: documents · qbr_deck · final · 2026-08-16

Final quarterly review deck for an Enterprise customer, term to 30 Jun 2027. Usage is steady: around fifteen active users against a full licence. Five tickets in the last month, four high priority. No overdue invoices.

What it says

What this says

Current to 11 Oct 26

Final quarterly review deck for an Enterprise customer, term to 30 Jun 2027. Usage is steady: around fifteen active users against a full licence. Five tickets in the last month, four high priority. No overdue invoices.

What it is: a customer-facing QBR prepared by Daniel Okafor, Customer Success Manager, dated 16 Aug 2026 and marked Final. It names Priya Raman as account owner.

What it says: "only around fifteen people were active in the brain over the last month", well short of the Enterprise allowance. Support had "five tickets in the last month, and four of them were high priority".

Commits: no service figures, prices or dates beyond the term end. It promises a ticket review, an adoption session and an early renewal conversation, with no dates.

Not settled: ticket causes and response times against the Enterprise commitment are not given. The heaviest askers are not identified, and the user count and subscription amount are described, not stated.

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

As found in this document

Current to 9 Oct 26
  • Date end30 Jun 2027Source: object_read:doc_001_027
  • Date start1 Jul 2024Source: object_read:doc_001_027

The document

Body

Fenmoor Specialty Underwriting - QBR

Quarterly business review, prepared 16 Aug 2026 Prepared by Daniel Okafor, Customer Success Manager, B-Brain Account owner: Priya Raman Status: Final


Where we are

Fenmoor has been a B-Brain customer since 1 Jul 2024 on the Enterprise tier. The current term runs to 30 Jun 2027, so we have a full year of the contract ahead of us. This review looks at how the brain is being used, what has gone wrong lately, and what we would like to do together over the coming quarter.

I want to be straightforward about the tone of this review. The picture is steady rather than strong, and the ticket queue over the last month has been busier than either of us would like.

MeasurePosition
TierEnterprise
Contracted subscriptionThe Enterprise annual subscription, in line with the executed order form
Licensed usersThe full Enterprise user allowance
Typical active users, last monthAround fifteen
Change against the prior quarterA small rise
Overdue invoicesNone

Usage

Read the whole document (4,579 characters)

On average, only around fifteen people were active in the brain over the last month. That is a small step up on the previous quarter, and I am glad to see the direction, but it is a long way short of the number of people the Enterprise licence covers.

What I read from this:

  • The brain is clearly valued by a core group, most likely underwriting operations, who use it to answer capacity providers' oversight questions.
  • The wider licensed population has not yet picked it up. That is headroom in one sense, but it is also a risk when we come to talk about renewal and about what the brain is worth to the business.
  • I would like us to know who the heaviest askers are, because a small group carrying most of the questions is a key-person exposure for Fenmoor as much as for us.

Support and service

There were five tickets in the last month, and four of them were high priority. For a customer of this size and tier that is a noticeable concentration, and I do not want to gloss over it.

Points worth stating plainly:

  • High priority tickets on the Enterprise tier carry the fastest first-response commitment we offer. I will go through the timestamps of each of the four with our support team before this review is discussed, so we are looking at what actually happened and not at how the tickets were worded.
  • Availability and data freshness are separate things. A brain that answers on stale data was still available, and on the Enterprise tier both are covered by service credits. We should be clear with each other which of the two any given ticket is about.
  • I will report back on the cause of each ticket in the same terms, by category: connector sync, data freshness, or how-to.

Commercial position

There are no overdue invoices, and payment has been on time. That tells me the concern here is about value and adoption, not about money or goodwill. It is exactly the situation where a clear value case matters more than a discount conversation.

Risks to keep an eye on

RiskWhy it mattersWhat we do
Low adoption against the licensed usersHard to defend the renewal on value if most seats are idleTargeted enablement for the teams not yet using the brain
Cluster of high priority ticketsErodes confidence among the people who do use itReview each ticket with support and share the findings
Reliance on a small group of askersKey-person risk if one of them moves onWiden the group of regular users and admins

Proposed plan for the coming quarter

  • Ticket review. Daniel to walk Fenmoor through each of the four high priority tickets: cause, response time against the Enterprise commitment, and any fix.
  • Adoption push. A short enablement session for underwriting and claims teams who are licensed but not yet asking questions. An on-site training day is available as an add-on if that would help.
  • Value case. Agree with Priya Raman and the Fenmoor sponsor which two or three questions the brain should be answering reliably for capacity providers, and measure those.
  • Renewal readiness. Start the renewal conversation early enough that nobody is surprised, well ahead of the end of the term.

Next steps

Just to close the loop: I will come back to you with the ticket findings shortly, and I would welcome thirty minutes with the Fenmoor team to agree the adoption plan. How is the team finding it day to day? That is the question I would most like answered in the room.

Best wishes, Daniel

Documentsmade from

Unusual terms

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

B-Brain is a fictional company; every organisation and person here is invented. 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
Organisations75
People at customers290
B-Brain staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

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.

B-Brain is a fictional company: every organisation, person and figure here is invented for this demonstration.

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.

Ask B

Ask B

B-Brain · read-only