Matteo Ricci

Hollowmere Care Group / BB-Demo – 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

BB-Demo

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

  1. Matteo Ricci
    Matteo Ricci None
    Afternoon, both. Natasha, Josh. Hannah has joined me, she is our solutions engineer for connectors.
  2. Hannah Lowe
    Hannah Lowe None
    Afternoon. Thanks, Matteo. Before I share anything, can I ask what you most need to know today? I'd rather answer your questions than walk through slides.
  3. Natasha Pryor
    Natasha Pryor None
    Straight to it, good. Josh will be the one living with this day to day, so I'd say his questions come first.
  4. Josh Fairburn
    Josh Fairburn None
    Right, okay. Thanks. So, mine are: what do we have to connect, who has to give us access, and what breaks if one of the source systems changes.
  5. Hannah Lowe
    Hannah Lowe None
    The short answer is, you connect what you already have, and nothing needs replacing. The longer answer is that each source gets a connector, and each connector has an owner on your side, someone who can approve access. For your case I'd expect the CRM, the helpdesk, the accounting system, the call recorder, your incident records and the shared mailbox.
  6. Josh Fairburn
    Josh Fairburn None
    The incident records are the awkward one. They're in a care management system and the export is, to be honest, a bit clunky.
  7. Hannah Lowe
    Hannah Lowe None
    That's useful to know. Do you get a scheduled export, or is it somebody running a report?
  8. Josh Fairburn
    Josh Fairburn None
    It's somebody running a report. Well, me, mostly.
  9. Hannah Lowe
    Hannah Lowe None
    Then to be precise, that is the one I would design first. If it's a file drop, we can pick it up from a shared location on a schedule. If the system has an interface we can use, even better. I'll put that in writing so you can check it with the supplier.
  10. Natasha Pryor
    Natasha Pryor None
    Which would be quicker to get live? I don't want the whole project waiting on one export.
  11. Hannah Lowe
    Hannah Lowe None
    The CRM and the accounting system will be quickest, they're standard. Incidents, I'd say, takes longest because of the design work. So we would go live in stages, and the first thing your people see is the contact and invoice side.
  12. Matteo Ricci
    Matteo Ricci None
    Which fits what Natasha said last week, start with the homes that shout loudest. Contact and invoices will show you those quite quickly.
  13. Natasha Pryor
    Natasha Pryor None
    It does. Just as long as the incident side follows. That's what the commissioners lean on.
  14. Josh Fairburn
    Josh Fairburn None
    What about freshness? If a home manager logs an incident at four in the afternoon, when does that appear?
  15. Hannah Lowe
    Hannah Lowe None
    The nightly refresh finishes by 07:00 on business days. So that incident would be there the next morning. It isn't live in the minute. If you needed that, we should talk about it separately, rather than me promising something loosely.
  16. Natasha Pryor
    Natasha Pryor None
    Next morning is fine for commissioner reporting. Not for a safeguarding alert, but that's not what we're buying this for.
  17. Hannah Lowe
    Hannah Lowe None
    Good, I'm glad you said that, it's important. The brain is for reporting and questions, not an alerting system.
  18. Josh Fairburn
    Josh Fairburn None
    And what do I have to do when someone changes a system? Because they do, constantly.
  19. Hannah Lowe
    Hannah Lowe None
    Tell us, ideally before. If a source changes its fields, the connector may stop loading. You would see the record count go flat, and we monitor for that as well, but a heads-up from you saves everyone a few days. Let me show you the connector status page, so you know what it looks like when it's healthy.
  20. Josh Fairburn
    Josh Fairburn None
    Oh, that's clear. So green is loading, and this one amber is stale?
  21. Hannah Lowe
    Hannah Lowe None
    Exactly, amber is no new records beyond what you expect. You'd get it before anyone complains.
  22. Natasha Pryor
    Natasha Pryor None
    What's the evidence trail for the connector itself? If the board asks me where a number came from, I want to say which system, which load, which time.
  23. Hannah Lowe
    Hannah Lowe None
    Every load is logged with source, time and record count. I can export that for you as a table. We can evidence it.
  24. Matteo Ricci
    Matteo Ricci None
    Let me confirm that in writing as well, with Hannah's notes on the incident export. Natasha, the next step on our side is the proposal, which I will talk you through shortly. Anything else for today?
  25. Natasha Pryor
    Natasha Pryor None
    No, that was what I needed. Josh?
  26. Josh Fairburn
    Josh Fairburn None
    I'm happy. I'll find out about that export interface from the supplier and come back.
  27. Hannah Lowe
    Hannah Lowe None
    Perfect. Thank you both.
  28. Matteo Ricci
    Matteo Ricci None
    Thank you. Best regards, and speak soon.

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
Organisations75
People at customers290
BB-Demo 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.

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.

Ask B

Ask B

B-Brain · read-only