Jordan Pike

Quarrington Care Network / BB-Demo – Demo

Callcompleted

Quarrington Care Network: documents logo Quarrington Care Network: documents · 2026-02-18 16:45

Demo to Danielle Okonkwo and Trent Nakamura. Trent found a referral count that did not tie to his report, and lineage pointed to duplicate logging. Growth is quoted at £62,000, with a liaison session and security answers still to come.

What was said

What this says

Current to 11 Oct 26

Demo to Danielle Okonkwo and Trent Nakamura. Trent found a referral count that did not tie to his report, and lineage pointed to duplicate logging. Growth is quoted at £62,000, with a liaison session and security answers still to come.

What happened: Trent opened by saying the sample count was lower than his own report. Hannah Lowe opened the lineage and showed four rows with the same referrer, date and branch collapsed into one.

Customer view: Trent called it consistent with double logging but will confirm against the intake log. Danielle said she was glad he found it and wants liaisons to try it first.

Commercial: Jordan Pike quoted £62,000 for Growth, the whole package and not a yearly figure. Danielle cannot commit budget, and a decision is aimed for 16 Apr 2026.

Watch: Trent is one person and carries the connector work. The business associate agreement is drafted, and the security answers are still owed in writing.

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

Themes

Current to 9 Oct 26
Theme
Data reconciliation and Growth quote
Importance
upsell
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Jordan Pike to send liaison session options today and the written breakdown of the total.
  • Hannah Lowe to send the written counting rule and the security responses available at this stage.
  • Trent Nakamura to send the liaison short list and intake extract, and reconcile the count.

Risks

Current to 9 Oct 26
  • Trent's referral count does not tie to the sample until he confirms the duplicates against the intake log.
  • Danielle cannot commit budget and needs liaison feedback, security answers and the number before she can push.
  • Trent is the only person on the customer side supporting the connector work.

Opportunities

Current to 9 Oct 26
  • Growth at £62,000 for the whole package, with a decision aimed for 16 Apr 2026.
  • Fewer hand-built referrer reports would give Trent a clear personal benefit.

Transcript

  1. Jordan Pike
    Jordan Pike None
    Hi everyone. Can you hear me okay? I'm getting a little echo on my side.
  2. Danielle Okonkwo
    Danielle Okonkwo None
    Hey Jordan, yes, loud and clear. Trent's just dialling in, he was stuck in a hallway.
  3. Trent Nakamura
    Trent Nakamura None
    Here, sorry. Had to find a room with a door. Can you see me? No? Hang on, camera's off.
  4. Hannah Lowe
    Hannah Lowe None
    Good afternoon, both. No rush at all, we're only just starting.
  5. Jordan Pike
    Jordan Pike None
    Great. So, quick agenda and a time check. We have just under an hour. Hannah will walk through the brain on a sample of your referral data, we'll leave plenty of room for questions, and in the last ten minutes or so we'll talk about where we are and what the next steps look like. Does that work?
  6. Danielle Okonkwo
    Danielle Okonkwo None
    That works. Can I start with a quick win from the field? Because it's the reason I'm pushing on this.
  7. Jordan Pike
    Jordan Pike None
    Please. I love a win.
  8. Danielle Okonkwo
    Danielle Okonkwo None
    One of my liaisons in Indiana walked into a hospital discharge office last week and the case manager said, you guys dropped the ball on that one family. And she had no idea. Nobody had told her. She called me from the parking lot. Ten minutes later we'd pieced it together from three different places. That is exactly what I never want to happen again. So she was fine in the end, but it took a scramble.
  9. Hannah Lowe
    Hannah Lowe None
    That's a helpful example, because it's precisely the kind of thing we'll try to reproduce today. One referrer, one view, with the calls, the tickets and the contract in the same place.
  10. Danielle Okonkwo
    Danielle Okonkwo None
    Right. Exactly.
  11. Trent Nakamura
    Trent Nakamura None
    Okay, can I jump in before we start? I'll be honest, I found a discrepancy when I looked at the sample extract you sent over.
  12. Jordan Pike
    Jordan Pike None
    Go for it. Better now than later.
  13. Trent Nakamura
    Trent Nakamura None
    So, one of the hospital systems. In my own referral report it shows a certain count for last quarter. In your sample it's lower. That doesn't tie to my numbers. And before anyone says it, I know it's a sample, but the gap is too big to be rounding.
  14. Hannah Lowe
    Hannah Lowe None
    Okay. Thank you for flagging it, and I'd rather deal with it than skip past it. To be precise, I don't yet know which side is right. The short answer is, it's probably a counting rule. The longer answer is that your report may count every referral event, and the brain, in the sample, counts one referral per referrer record after de-duplication. Is your report built from the intake log directly?
  15. Trent Nakamura
    Trent Nakamura None
    It is. Straight from intake, joined to the referrer table. So duplicates could be in there. We've had that before, when two branches log the same call.
  16. Hannah Lowe
    Hannah Lowe None
    Right. Then I'd suggest we do this. When I get to the referrer page, I'll open the source lineage for that hospital and we can see which records fed the count. If it's duplicates, we'll see them. If it's a missing connector or a filter, we'll see that too.
  17. Trent Nakamura
    Trent Nakamura None
    Okay. Which source wins, though, if they disagree? That's the question I always have.
  18. Hannah Lowe
    Hannah Lowe None
    Good question, and it's configurable. You decide the order of precedence per field, and the brain shows you which source it used. I'll show you where that setting lives.
  19. Trent Nakamura
    Trent Nakamura None
    Good. I'll reconcile it on my side as well, then we can compare.
  20. Jordan Pike
    Jordan Pike None
    Perfect. Hannah, over to you. Share your screen whenever you're ready.
  21. Hannah Lowe
    Hannah Lowe None
    Sharing now. Can you see the home page? Let me know if the text is too small.
  22. Danielle Okonkwo
    Danielle Okonkwo None
    Yes, I can see it. Bigger would be better, my eyes are not what they were.
  23. Hannah Lowe
    Hannah Lowe None
    No problem. Is that better? Good. So, this is the sample environment, loaded with the extract Trent sent. Nothing here is live and nothing leaves your control. In a real deployment the brain is built and run inside your own Snowflake account, so the data stays where your data already lives.
  24. Danielle Okonkwo
    Danielle Okonkwo None
    That's the part our compliance people will care about. Keep going, I want to see the referrer view.
  25. Hannah Lowe
    Hannah Lowe None
    Right, I'll search for the hospital system Trent mentioned. There. This is the referrer page. At the top you've got the organisation and its facilities. Underneath, a timeline: calls your liaisons logged, emails, helpdesk tickets from the patient services team, and the contract record.
  26. Danielle Okonkwo
    Danielle Okonkwo None
    Oh, that's nice. So a liaison opens this before she walks in.
  27. Hannah Lowe
    Hannah Lowe None
    Yes. And she doesn't need to know which system anything came from. Each item says where it came from, but she's not hunting through the CRM, then the helpdesk, then the call recorder.
  28. Danielle Okonkwo
    Danielle Okonkwo None
    What's the referral trend? Can it show that? Because the leadership team asks me that every single week.
  29. Hannah Lowe
    Hannah Lowe None
    Let's ask it. I'll type the question into the chat: what is the referral trend for this hospital system over the last two quarters, by facility. It takes a moment.
  30. Trent Nakamura
    Trent Nakamura None
    Come on, come on.
  31. Hannah Lowe
    Hannah Lowe None
    There we go. So it answers in plain sentences first, then gives you the table underneath. You'll see two facilities are up and one is down. And each line is clickable, so you can see the records behind the number.
  32. Danielle Okonkwo
    Danielle Okonkwo None
    The down one. Is that the one the liaison was complaining about?
  33. Trent Nakamura
    Trent Nakamura None
    It might be. Can you click into that one? That's the one that doesn't tie.
  34. Hannah Lowe
    Hannah Lowe None
    Of course. Opening the lineage. So here are the records counted. And, Trent, if you look at the second column, these four rows have the same referrer, the same date and the same branch. The brain has collapsed them into one.
  35. Trent Nakamura
    Trent Nakamura None
    Huh. Yeah. Okay. That's the double logging. I'd have to check, but that looks like exactly the problem I mentioned. So my report overstates.
  36. Hannah Lowe
    Hannah Lowe None
    Possibly, and I want to be careful here. I'd say it's consistent with duplicate logging. I wouldn't say your report is wrong until you've confirmed it against the intake log. I'll put that in writing, with the rule the brain applied, so you can test it.
  37. Trent Nakamura
    Trent Nakamura None
    Fair. That's all I ask. I never want to overstate what the data shows, either direction.
  38. Jordan Pike
    Jordan Pike None
    And to be transparent, this is why we do the demo on your data rather than ours. Slides never show you a mismatch like that.
  39. Danielle Okonkwo
    Danielle Okonkwo None
    Honestly, I'm glad Trent found it. Okay, next. Tickets. My patient services team gets calls from hospitals about a delayed start of care. Can a liaison see that?
  40. Hannah Lowe
    Hannah Lowe None
    Yes. Let me filter the timeline to tickets only. These are from the helpdesk connector. You can see the category, the status and who handled it. A liaison sees the open ones first, which is the thing she'd want before a visit.
  41. Danielle Okonkwo
    Danielle Okonkwo None
    Great. Now, one thing. Nobody puts patient information in an email, ever. Is any of that in here?
  42. Hannah Lowe
    Hannah Lowe None
    Good one to raise. The short answer is, the brain only holds what your connected systems hold and what you choose to connect. The longer answer is that we'd agree with you, field by field, what is brought in and what is excluded, and that goes in the design document. I won't claim more than that until I've confirmed the specifics with our security lead, and I'll put the answer in writing.
  43. Danielle Okonkwo
    Danielle Okonkwo None
    Good. That's what I wanted to hear. Not a promise, a process.
  44. Jordan Pike
    Jordan Pike None
    And the business associate agreement is part of the paperwork, so that's not something we skip. Here's where we are on that: it's drafted, and your legal team gets it alongside the proposal.
  45. Trent Nakamura
    Trent Nakamura None
    Can I ask about connectors? What's the effort on my side? Because I'm one person.
  46. Hannah Lowe
    Hannah Lowe None
    Sensible. For the Growth tier you have a limit on the number of connectors, so we'd pick the ones that matter most first. Probably the CRM, the helpdesk, the call recorder and your intake system. I'd do the design work with you. You'd need to provide credentials and someone who knows the schema, which is you.
  47. Trent Nakamura
    Trent Nakamura None
    Okay. So bullet points. One, I grant access. Two, I explain the intake schema. Three, I check the output against my reports. That I can do.
  48. Hannah Lowe
    Hannah Lowe None
    That's about right. And fewer one-off report requests afterwards, because the liaisons ask the brain instead of asking you.
  49. Trent Nakamura
    Trent Nakamura None
    That's the dream. Honestly, if I never build another referrer report by hand, I'll be happy.
  50. Danielle Okonkwo
    Danielle Okonkwo None
    Let's loop in the liaisons. Can we get a handful of them on a session before we sign anything? I want them to try it, and I want them to tell me what's useless.
  51. Jordan Pike
    Jordan Pike None
    Absolutely. What would make this a yes for you, Danielle? Is it the liaison feedback, the security answers, or the number?
  52. Danielle Okonkwo
    Danielle Okonkwo None
    All three, in that order. Liaisons first. If they like it, I can fight for it. And if Trent's reconciliation holds up, that helps a lot.
  53. Jordan Pike
    Jordan Pike None
    Understood. So on the number, to be transparent: the total deal value we're looking at is £62,000 for Growth. That's the whole package, not a yearly figure, and I'll send you the breakdown in writing so there's no confusion about what's one-off and what recurs.
  54. Danielle Okonkwo
    Danielle Okonkwo None
    Okay. I hear you. I can't commit budget on this call, you know that, I'd need to take it to our finance side. But I appreciate you saying it straight.
  55. Jordan Pike
    Jordan Pike None
    Completely fair. We're aiming for a decision around 16 Apr 2026, which gives you time for the liaison session, the security questions and legal.
  56. Danielle Okonkwo
    Danielle Okonkwo None
    That's workable. I need the liaison session set up by Friday, though, or it slips. Can you do that?
  57. Jordan Pike
    Jordan Pike None
    I'll send options today. Hannah, can you run it?
  58. Hannah Lowe
    Hannah Lowe None
    Yes. A hands-on session with a few liaisons, using their own referrers. I'll ask Trent for a short list first so I can prepare it properly.
  59. Trent Nakamura
    Trent Nakamura None
    I'll send the list, and the intake extract for the hospital system, without anything that identifies patients. And I'll reconcile that count and tell you what I find.
  60. Hannah Lowe
    Hannah Lowe None
    Thank you. I'll send the written answer on the counting rule, plus the security responses we can give at this stage.
  61. Danielle Okonkwo
    Danielle Okonkwo None
    Wonderful. Honestly, this was better than I expected. Okay, I've got another meeting.
  62. Jordan Pike
    Jordan Pike None
    Thanks, everyone. Talk soon.
  63. Trent Nakamura
    Trent Nakamura None
    Thanks all. Bye.

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