Matteo Ricci

Hollowmere Care Group / B-Brain – Demo

Callcompleted

Hollowmere Care Group: documents logo Hollowmere Care Group: documents · 2026-02-23 14:00

Demo to Natasha Pryor and Josh Fairburn. Josh's concerns were access, source-system changes and the clunky incident export. Natasha accepted next-morning freshness for commissioner reporting. A proposal is the next step.

What was said

What this says

Current to 11 Oct 26

Demo to Natasha Pryor and Josh Fairburn. Josh's concerns were access, source-system changes and the clunky incident export. Natasha accepted next-morning freshness for commissioner reporting. A proposal is the next step.

What happened: Hannah Lowe answered Josh's questions on connectors, freshness and what breaks when a source changes. She showed the connector status page and promised a written note on the incident export.

Customer view: Natasha put the commissioner-facing incident data first and said next-morning refresh is enough. Josh will check the export interface with the supplier.

Commercial: Matteo Ricci named the proposal as the next step. Staged go-live starts with contact and invoice data, with incidents following.

Watch: The incident export is a manual report run by Josh, so it is the likely delay. Natasha also wants a load-level evidence trail for board questions.

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

Themes

Current to 9 Oct 26
Theme
Connector design and freshness
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

B-Brain

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Matteo to send the proposal with Hannah's written notes on the incident export.
  • Josh to ask the supplier about an export interface and report back.

Risks

Current to 9 Oct 26
  • The incident export is a manual report and may delay the incident side that commissioners rely on.
  • Source-system changes can stop a connector loading, and Josh said systems change constantly.

Opportunities

Current to 9 Oct 26
  • A staged go-live starting with contact and invoice data gives early visible value.

Transcript

Not yet analysedThe transcript has not been written yet.

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