Jordan Pike

Quarrington Care Network / BB-Demo – Demo

Callcompleted

Quarrington Care Network: documents logo Quarrington Care Network: documents · 2026-02-06 17:30

Demo to Danielle Okonkwo and Brandon Ellison on Quarrington's own referral data. Interest is strong, but the Growth proposal at £62,000 faces open questions on patient data screening and single sign-on, which is Enterprise-only.

What was said

What this says

Current to 11 Oct 26

Demo to Danielle Okonkwo and Brandon Ellison on Quarrington's own referral data. Interest is strong, but the Growth proposal at £62,000 faces open questions on patient data screening and single sign-on, which is Enterprise-only.

What happened: Hannah Lowe showed referrer pages, chat and the dashboards builder on sample extracts. Danielle said it was the first time she had seen all four of those systems on one screen.

Customer view: Danielle wants one view per referrer and fast answers for leadership. Brandon's main worry is HIPAA exposure, and he said his team sometimes pastes details into tickets.

Commercial: Jordan Pike put the Growth deal at £62,000 all in, implementation included, not an annual figure. Danielle cannot commit budget and needs her finance lead and liaison sign-off, with a target close of Thu 16 Apr 2026.

Watch: Single sign-on and provisioning are Enterprise features, and Brandon thinks sign-in is a must for referrer contracts. Written answers on Growth sign-in, ticket screening and data exit are owed.

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

Themes

Current to 9 Oct 26
Theme
Growth demo, security and SSO
Importance
upsell
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Hannah Lowe to send the architecture diagram and written answers on Growth sign-in, ticket screening and data exit.
  • Jordan Pike to send the proposal with the breakdown of the total.
  • Brandon Ellison to check the sign-in policy with his IT lead, and Danielle Okonkwo to run a liaison session.

Risks

Current to 9 Oct 26
  • Single sign-on is an Enterprise feature and Brandon thinks it is a must for anything touching referrer contracts.
  • Brandon's team sometimes pastes patient details into tickets, and screening before indexing is unconfirmed.
  • Danielle cannot commit budget and needs her finance lead and liaison sign-off first.

Opportunities

Current to 9 Oct 26
  • Growth proposal at £62,000 for the whole deal, with a target close of Thu 16 Apr 2026.
  • If single sign-on is a hard requirement, the conversation may move to Enterprise.

Transcript

  1. Jordan Pike
    Jordan Pike None
    Hey Danielle, can you hear me okay?
  2. Danielle Okonkwo
    Danielle Okonkwo None
    I can, loud and clear. Happy Friday, Jordan. Is Hannah on?
  3. Hannah Lowe
    Hannah Lowe None
    I'm here, hello both. It's well past tea time for me, so apologies if I look slightly wilted.
  4. Danielle Okonkwo
    Danielle Okonkwo None
    Ha, no, we appreciate you staying on this late. Brandon's still wrapping up a call, he said he'd jump on in a couple of minutes.
  5. Jordan Pike
    Jordan Pike None
    No problem. Quick agenda while we wait. Here's where we are: this is the demo on your own referral data, then questions on security and access, then next steps. We have the full time until about ten past six, so I'll keep an eye on the clock.
  6. Danielle Okonkwo
    Danielle Okonkwo None
    Perfect. Can I start with a win from the field? Because it's exactly why I pushed for this.
  7. Jordan Pike
    Jordan Pike None
    Please. Love a win.
  8. Danielle Okonkwo
    Danielle Okonkwo None
    One of our liaisons in Indiana walked into a hospital discharge office on Wednesday. She had no idea the case manager there had been burned by a slow intake on our side last autumn. Nobody told her. She found out in the first thirty seconds, in the room, and spent the whole meeting digging out of it. That's the thing. She should have known before she walked in.
  9. Hannah Lowe
    Hannah Lowe None
    Right. And that history existed somewhere, I assume. A ticket, a call note, an email.
  10. Danielle Okonkwo
    Danielle Okonkwo None
    Oh, it existed in about four places. Nobody could see all four at once.
  11. Brandon Ellison
    Brandon Ellison None
    Sorry, sorry, I'm here. Brandon. Did I miss the intro?
  12. Jordan Pike
    Jordan Pike None
    Not at all, Brandon, welcome. We were just on Danielle's story from Indiana. Hannah, you wanted to ask them something first?
  13. Hannah Lowe
    Hannah Lowe None
    Yes. Before I share anything, what do the two of you most need to know by the end of today? I'd rather aim the demo at that than walk you through every screen.
  14. Danielle Okonkwo
    Danielle Okonkwo None
    For me, one view per referrer. Hospital, physician group, whoever. What's the referral trend, who have we talked to, what's open, what does the contract say. And I need leadership to get answers fast, not a week later.
  15. Brandon Ellison
    Brandon Ellison None
    Mine is a bit different. Patient services gets the complaints and the escalations that come back from referrers. I need to see those next to Danielle's side, but I need to be sure we're not exposing anything we shouldn't. Honestly that's my main worry. We're under HIPAA, and I'm the one who gets the call if something goes wrong.
  16. Hannah Lowe
    Hannah Lowe None
    That's a fair worry, and I'll come back to it properly. The short answer is the brain runs inside your own Snowflake account, so the data doesn't move to us. The longer answer is in access roles and the business associate agreement, and I'd like to show you both. Let me share my screen first.
  17. Danielle Okonkwo
    Danielle Okonkwo None
    Great.
  18. Hannah Lowe
    Hannah Lowe None
    Can you see it? A page with a referrer name at the top?
  19. Brandon Ellison
    Brandon Ellison None
    Yes, it's a bit small but I can read it.
  20. Hannah Lowe
    Hannah Lowe None
    I'll zoom in. So this is a referrer page. We built it from the sample extracts your team sent over, with no patient details in them, just organisation level records. Calls, tickets, contracts and emails, all joined on the referring hospital rather than on whichever system they happened to come from.
  21. Danielle Okonkwo
    Danielle Okonkwo None
    Mm. And that's one of ours? A real hospital?
  22. Hannah Lowe
    Hannah Lowe None
    It's one of the referrers in your extract, yes. Down the left you've got the timeline. Every touch, newest first. Here's a call with your liaison, here's a helpdesk ticket about a delayed start of care, and here, at the bottom, the agreement that covers them.
  23. Danielle Okonkwo
    Danielle Okonkwo None
    Okay, that is exactly what Indiana was missing. That ticket would have told her everything.
  24. Jordan Pike
    Jordan Pike None
    That's the point. Your liaison opens this the night before the visit, and she walks in prepared. Hannah, can you show the chat piece? That's where leadership gets their answers.
  25. Hannah Lowe
    Hannah Lowe None
    Of course. I'll type something Danielle might plausibly ask. Which referring hospitals in Indiana have gone quiet in the last quarter, and what was the last thing we heard from them.
  26. Brandon Ellison
    Brandon Ellison None
    It's thinking.
  27. Hannah Lowe
    Hannah Lowe None
    A few seconds, yes. And there. It gives you a short list, and each line has a source you can click, so you can check where it came from. To be precise, it's not guessing, it's reading the records and showing its working. If a source isn't there, it says so.
  28. Danielle Okonkwo
    Danielle Okonkwo None
    Can I ask it something now? Like live?
  29. Hannah Lowe
    Hannah Lowe None
    Please, tell me what to type.
  30. Danielle Okonkwo
    Danielle Okonkwo None
    What's the referral trend for the Illinois physician groups, and which of them have an open complaint?
  31. Hannah Lowe
    Hannah Lowe None
    Okay. Typing that as you said it.
  32. Hannah Lowe
    Hannah Lowe None
    There we are. A trend summary, then two groups with open items, and the ticket links under each. One thing I'd flag: it's only as good as what's been loaded, so the trend runs up to the last refresh. The nightly refresh finishes before seven in the morning on business days.
  33. Danielle Okonkwo
    Danielle Okonkwo None
    That works for us. Liaisons plan their day first thing. I need this by Friday for the leadership meeting, usually, so Thursday night refresh is fine.
  34. Brandon Ellison
    Brandon Ellison None
    Can I jump in on the complaints side? Say a referrer calls and complains. Does that show up here automatically, or does someone have to tag it?
  35. Hannah Lowe
    Hannah Lowe None
    It depends on where the complaint lands. If it comes in through your helpdesk, it's a ticket and it's joined to the referrer on the next refresh. If someone only mentions it on a recorded call, the brain can find it in the transcript, but I wouldn't promise it files it as a complaint unless the category is set up. We'd agree that with you in implementation.
  36. Brandon Ellison
    Brandon Ellison None
    Okay. That's honest at least. Our categories are a mess, to be fair.
  37. Jordan Pike
    Jordan Pike None
    To be transparent, most customers say that. Cleaning categories is usually a good side effect, not a blocker.
  38. Danielle Okonkwo
    Danielle Okonkwo None
    Right. Let's loop in the liaisons on that, they know how the complaints actually get described. Half of them never use the official categories anyway.
  39. Hannah Lowe
    Hannah Lowe None
    That would be ideal. Right, let me show you the dashboards builder quickly, because I think Danielle's leadership team will want a standing view rather than asking each time.
  40. Hannah Lowe
    Hannah Lowe None
    So this is a blank canvas. I'll drag in referral volume by month, split by state, and add a table of the top referrers with open tickets.
  41. Danielle Okonkwo
    Danielle Okonkwo None
    Oh, that's nice. So I could save that and send the link to the leadership team?
  42. Hannah Lowe
    Hannah Lowe None
    Yes, and it follows the same permissions as everything else. Anyone you share it with sees only what their role allows. Which brings me to your question, Brandon, because I think it's the right moment.
  43. Brandon Ellison
    Brandon Ellison None
    Please. Go on.
  44. Hannah Lowe
    Hannah Lowe None
    Three layers. First, where the data lives: in your Snowflake account, so your own controls and your own audit trail apply. Second, the agreement: you bought under a business associate agreement, so that's in place before anything is connected. Third, access inside the brain: roles, so patient services can see ticket and complaint content that referral relations doesn't, if you want it that way.
  45. Brandon Ellison
    Brandon Ellison None
    And if we don't load anything with patient names in it to begin with?
  46. Hannah Lowe
    Hannah Lowe None
    Then there's far less to protect, and I'd actively recommend that. We'd scope the connectors so that clinical systems aren't connected at all. The brain is for the relationship side: referrers, contracts, calls, tickets.
  47. Brandon Ellison
    Brandon Ellison None
    Good. Because my team does sometimes paste details into tickets when they shouldn't. I can't promise that stops.
  48. Hannah Lowe
    Hannah Lowe None
    Right, and I'd rather you tell me that now than find out later. Honestly, that's a real risk that no tool fully removes. What I can say is that if a ticket contains it, it would be in the helpdesk already, and the brain reads from there. Whether we could screen for it before indexing is a question I want to check with our security lead rather than answer off the cuff. I'll put that in writing.
  49. Jordan Pike
    Jordan Pike None
    And that's the right answer, Brandon. I'd rather you get it from the person who owns it than a sales guess. Your security team gets everything, including the parts that are not perfect.
  50. Brandon Ellison
    Brandon Ellison None
    Fine by me. Another one. Single sign-on. We'll need our staff to log in with our own identity provider. Is that there?
  51. Hannah Lowe
    Hannah Lowe None
    Single sign-on and automated user provisioning are part of the Enterprise tier, and you're looking at Growth. So the short answer is not as a standard feature. The longer answer is how sign-in works on Growth and whether that satisfies your policy, and I don't want to guess. I'll confirm in writing, and if it's a hard requirement, we should talk about it openly with Jordan.
  52. Jordan Pike
    Jordan Pike None
    Yes. Let's get that on the table early, Brandon. If it's a must-have, say so and we'll look at the right fit. No surprises later.
  53. Brandon Ellison
    Brandon Ellison None
    Okay, I'll check with our IT lead. I think it's a must for anything that touches referrer contracts, but I don't know what the policy says exactly.
  54. Danielle Okonkwo
    Danielle Okonkwo None
    Can we not hold this up on that, though? What's the realistic plan if we say yes? How long to get the liaisons using it?
  55. Hannah Lowe
    Hannah Lowe None
    Growth implementation is eight weeks, and I'd call that realistic, not padded. First two weeks connecting your sources and agreeing the referrer list, because that's the foundation. Then categories, pages, the dashboards, then training for the liaisons. If the connectors go smoothly, you'd have liaisons on real pages well before the end.
  56. Danielle Okonkwo
    Danielle Okonkwo None
    And who's on our side doing the work? I don't want my liaisons doing data entry.
  57. Hannah Lowe
    Hannah Lowe None
    You'd need one owner for each system, someone who can say yes to a connection and tell us when a field means something odd. And one person who decides what counts as a referrer, because that's where most of the arguments are. Your liaisons wouldn't enter data. They'd just use it and tell us when it's wrong.
  58. Danielle Okonkwo
    Danielle Okonkwo None
    That's me for the referrer list, and it'll be Brandon for the complaints side. IT, I'll find somebody.
  59. Brandon Ellison
    Brandon Ellison None
    Sure. I can be the owner for tickets. Just make sure the ask is written down so I can take it to my director.
  60. Jordan Pike
    Jordan Pike None
    Absolutely. Let me do the commercial piece now, so nobody's guessing. We're proposing Growth, and the total for the deal comes to £62,000 all in, implementation included. To be transparent, that's the whole figure for the deal, not an annual subscription number, and I'll break it out clearly in the proposal so your finance team can see the split.
  61. Danielle Okonkwo
    Danielle Okonkwo None
    Okay. I hear you. I can't commit budget on this call, you know that. It goes through our finance lead, and I'd want the liaisons' sign-off on the pilot pages first.
  62. Jordan Pike
    Jordan Pike None
    Understood, and I wouldn't ask you to. What would make this a yes for you and your finance lead? What do they need to see?
  63. Danielle Okonkwo
    Danielle Okonkwo None
    A clear line from the cost to referral volume. If I can say this keeps us from losing a hospital the way we nearly did in Indiana, that's the story. And a clean breakdown of the number, like you said.
  64. Jordan Pike
    Jordan Pike None
    Got it. Here's where we are on timing: we have pencilled in Thursday 16 April 2026 as the target to close. That's a plan, not a deadline you owe us. If the security answers take longer, we move it.
  65. Danielle Okonkwo
    Danielle Okonkwo None
    Fine. Thursday the sixteenth works as a target. I'll tell my finance lead it's coming.
  66. Brandon Ellison
    Brandon Ellison None
    One more from me, then I'll stop. If we ended up not wanting it after the first term, what happens to the data? Does it just sit there?
  67. Hannah Lowe
    Hannah Lowe None
    Because it's in your Snowflake account, it's yours. We'd remove our access and our own components, and what's in your account stays under your control. I'd want to write the exact wording with our contracts team, though, rather than paraphrase it.
  68. Brandon Ellison
    Brandon Ellison None
    That's a good answer. Please do put that in writing as well.
  69. Jordan Pike
    Jordan Pike None
    Will do. Okay, we've got a little time left. Let me recap what each person is taking away, and tell me if I've got it wrong.
  70. Jordan Pike
    Jordan Pike None
    Hannah sends three things: the architecture diagram, the written answers on Growth sign-in, and the answer on screening tickets for patient details before indexing, plus the data-exit wording. I send the proposal with the breakdown of the total. Danielle, you bring the liaisons in and talk to your finance lead. Brandon, you check the sign-in policy with your IT lead. Our customer success manager, Hollie Grieve, will reach out too, so you meet her before anything starts.
  71. Danielle Okonkwo
    Danielle Okonkwo None
    That's right. I'll set up thirty minutes with three liaisons next week so Hannah can show them the referrer page. I want their reaction before I take it upstairs.
  72. Hannah Lowe
    Hannah Lowe None
    Lovely. I'll bring a couple of their own referrers on the page, with the same organisation level data, so it feels real to them.
  73. Brandon Ellison
    Brandon Ellison None
    And I'll have an answer on sign-in by then, hopefully.
  74. Danielle Okonkwo
    Danielle Okonkwo None
    Great demo, you two. Really. That's the first time I've seen all four of those systems on one screen.
  75. Jordan Pike
    Jordan Pike None
    Thanks, Danielle, thanks Brandon. Appreciate your time on a Friday evening. Have a good weekend.
  76. Hannah Lowe
    Hannah Lowe None
    Thanks both. Speak next week.

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