Jordan Pike

Quillmark Health / BB-Demo – Demo

Callcompleted

Quillmark Health: documents logo Quillmark Health: documents · 2026-04-16 15:30

Demo of the brain on sample data for Quillmark Health. Client services and data leads liked it. The CISO listed four open security items and gave no verbal approval, so security review gates any deal.

What was said

What this says

Current to 10 Oct 26

Demo of the brain on sample data for Quillmark Health. Client services and data leads liked it. The CISO listed four open security items and gave no verbal approval, so security review gates any deal.

What happened: Hannah Lowe demoed client pages, citations, the dashboards builder and the connector view on a Snowflake sample. Dana Whitcombe and Ben Kowalski were positive, and Megan Alvarez questioned residency, access, incidents and freshness.

Customer view: Dana said leads need click-through to sources and a printable Monday view. Ben tied his yes to Dana's leads using it, and said security and procurement own the rest.

Commercial: Megan restated four open items: written data residency, the access model, ninety days of incident history, and freshness wording in the order form. Jordan Pike gave 30 Jun 2026 as a planning close only.

Watch: the incident question was not answered on the call and Megan expects full disclosure. Any Enterprise sale depends on written answers landing cleanly.

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

Themes

Current to 9 Oct 26
Theme
Enterprise demo, security gating
Importance
praise
Sentiment
mixed
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Hannah Lowe to put residency, the access model and the incident history in writing after checking with the security lead.
  • Jordan Pike to send the pack, the freshness section of the order form and a recap.
  • Ben Kowalski to help line up the procurement conversation, with Tasha looped in.

Risks

Current to 9 Oct 26
  • The incident history for the last ninety days was not answered on the call and the CISO expects full disclosure.
  • No approval was given verbally, and procurement follows the security review, so timing is not in BB-Demo's hands.
  • Access depends on the customer's own Snowflake role design, which the CISO wants documented as a customer responsibility.

Opportunities

Current to 9 Oct 26
  • Client services leads see the client page and dashboards builder as a fit for their Monday routine on Enterprise.
  • Adding a finance source later would be a further connector, possibly an add-on beyond the tier limit.

Transcript

  1. Jordan Pike
    Jordan Pike None
    Hey everyone, can you hear me? Ben, I see you. Dana, Megan, welcome. We'll give it a minute for folks to join.
  2. Ben Kowalski
    Ben Kowalski None
    Hey Jordan. Hey Hannah. Weather's gone from sunny this morning to just grey now. Spring in Boston, you know how it is.
  3. Hannah Lowe
    Hannah Lowe None
    Ha, it's the same story where I am. Good afternoon, everyone.
  4. Dana Whitcombe
    Dana Whitcombe None
    Hi all, sorry, I'm here. Quick pleasantry, hope everyone's week is going well. My leads have been asking about this call all morning.
  5. Megan Alvarez
    Megan Alvarez None
    Good afternoon. For the record, I'm joining to observe the security-relevant portions of the demonstration.
  6. Jordan Pike
    Jordan Pike None
    Perfect, thanks Megan. One-line agenda and a time check. We've got just under an hour. Hannah will demo the brain running on a sample of your data, we'll take questions as we go, and I'll leave the last few minutes for next steps. Hannah, I'll hand you the floor.
  7. Hannah Lowe
    Hannah Lowe None
    Thanks, Jordan. Before I share anything, what does each of you most need to know from this session? It changes what I show.
  8. Dana Whitcombe
    Dana Whitcombe None
    For my leads, honestly, it's what does that look like day to day? Each hospital client has its own team, and on a Monday my lead wants to know where that client stands without opening six tabs.
  9. Ben Kowalski
    Ben Kowalski None
    That's exactly the gap. And on my side, I want to see it's Snowflake-native, that it really sits in our estate.
  10. Megan Alvarez
    Megan Alvarez None
    My needs are structured. One, where the data resides. Two, who can see what. Three, how access is logged. I'll raise questions as they arise, and I'd ask that they be answered precisely.
  11. Hannah Lowe
    Hannah Lowe None
    Understood, Megan. I'll be precise, and where I'm not certain I'll say so and put the answer in writing afterwards. Right, let me share my screen. Can everyone see a Snowflake console?
  12. Ben Kowalski
    Ben Kowalski None
    Yep, I see it.
  13. Dana Whitcombe
    Dana Whitcombe None
    Same here.
  14. Hannah Lowe
    Hannah Lowe None
    Good. So the short answer to where the brain lives is, inside the customer's own Snowflake account. The longer answer is that BB-Demo sets up its schemas and roles in your account, the connectors write there, and the questions are answered from there. There's no separate BB-Demo copy of your data to protect.
  15. Megan Alvarez
    Megan Alvarez None
    Please confirm that statement will be reflected in the written security documentation.
  16. Hannah Lowe
    Hannah Lowe None
    It will. I'll put that in writing, with the architecture diagram, so your reviewers can check it against what they see in the console.
  17. Hannah Lowe
    Hannah Lowe None
    Okay, here's the sample. This is one hospital client, a made-up group, but the structure is what you gave us. Each record comes from a different source. These rows are from the CRM, these are tickets from the helpdesk, these are call summaries from the recorder.
  18. Ben Kowalski
    Ben Kowalski None
    Love it. That's literally the spreadsheet my teams build by hand.
  19. Dana Whitcombe
    Dana Whitcombe None
    Walk me through the page for a client. If I'm a lead, where do I land?
  20. Hannah Lowe
    Hannah Lowe None
    Good, let me open it. This is a client page. At the top is the summary, who the contacts are, what's open, what's changed recently. Underneath, the timeline, so you can see a ticket, a call and an email in the order they happened rather than in three systems.
  21. Dana Whitcombe
    Dana Whitcombe None
    Okay, that's the bit. So a lead opens this before a client meeting and doesn't need to ask anyone for a briefing.
  22. Hannah Lowe
    Hannah Lowe None
    Exactly that. And if they want more, they ask. Let me try a question. What has this client raised in the last month, and is any of it still unresolved?
  23. Hannah Lowe
    Hannah Lowe None
    It's thinking. It looks across the helpdesk and the calls, and, there. It's listed two open items and pointed to the tickets they came from. Each answer links back to its source, so you can check it.
  24. Dana Whitcombe
    Dana Whitcombe None
    Can I see where it got that? My leads won't trust it unless they can click through.
  25. Hannah Lowe
    Hannah Lowe None
    Of course. If I click the citation, it opens the ticket itself. That's by design. The brain shouldn't ask anyone to just believe it.
  26. Ben Kowalski
    Ben Kowalski None
    That's huge for adoption. If they can verify, they'll use it.
  27. Jordan Pike
    Jordan Pike None
    Ben, what would make this a yes on your side, from the user perspective?
  28. Ben Kowalski
    Ben Kowalski None
    Honestly, if Dana's leads say they'd use it on a Monday, I'm there. The rest is process, and security and procurement own that, not me.
  29. Megan Alvarez
    Megan Alvarez None
    That is correct, Ben. Hannah, a question. Please describe how a user's access to a client page is determined.
  30. Hannah Lowe
    Hannah Lowe None
    To be precise, it follows the roles in your Snowflake account. The brain doesn't invent a second permissions model. If a role can't read a source table, the brain can't show that content to that person. On Enterprise there's also SSO and SCIM, so people are provisioned and removed from your identity provider.
  31. Megan Alvarez
    Megan Alvarez None
    And if a role is misconfigured by the customer?
  32. Hannah Lowe
    Hannah Lowe None
    Then the brain would reflect that misconfiguration, because it trusts the account's roles. That's a fair point and I won't dress it up. What we do is test roles during onboarding, and I'd recommend you review the role design before go-live.
  33. Megan Alvarez
    Megan Alvarez None
    Noted. For the record, I'd like that stated in the documentation as a customer responsibility.
  34. Hannah Lowe
    Hannah Lowe None
    I'll write it that way.
  35. Megan Alvarez
    Megan Alvarez None
    Next. Please describe any incidents in the last ninety days affecting customer data or availability.
  36. Hannah Lowe
    Hannah Lowe None
    I'm going to be careful here, Megan, because that's a question that should be answered from the incident record and not from my memory. I'll take it away, check it with our security lead, and send you a written answer. I'd rather give you the right answer slowly than a guess today.
  37. Megan Alvarez
    Megan Alvarez None
    Understood. I would expect that to be addressed in full, including anything minor. Our risk posture requires disclosure from the vendor before we find it ourselves.
  38. Jordan Pike
    Jordan Pike None
    And to be transparent, Megan, you'll get it all. If there's something we'd rather not say, that's exactly the thing you should hear. I'll make sure that goes in the pack.
  39. Megan Alvarez
    Megan Alvarez None
    Thank you, Jordan.
  40. Hannah Lowe
    Hannah Lowe None
    Okay, shall I carry on? There's a bit I think Dana will like, and then the connector view.
  41. Dana Whitcombe
    Dana Whitcombe None
    Yes, please. Show me the Monday thing.
  42. Hannah Lowe
    Hannah Lowe None
    Sure. This is the dashboards builder. It's one of the things that comes with the tier you're looking at. I'll build something quickly. A view of all hospital clients with open items, sorted by how long the oldest one has been waiting. Give me a moment, I'll drag in the fields.
  43. Dana Whitcombe
    Dana Whitcombe None
    That's, okay, that's a list I'd actually print.
  44. Ben Kowalski
    Ben Kowalski None
    Ha. She'd print it.
  45. Dana Whitcombe
    Dana Whitcombe None
    I would! But seriously, what does it take for one of my leads to build that themselves? Because I'm not going to ask IT every time.
  46. Hannah Lowe
    Hannah Lowe None
    It's drag and drop, the way I just did. Someone in your team would probably set up the first few and the leads would adjust them. We cover it in training during implementation, so it's not left to chance.
  47. Dana Whitcombe
    Dana Whitcombe None
    Good. And for anything with patient data in it, I'd want that to go through security first, obviously.
  48. Hannah Lowe
    Hannah Lowe None
    Agreed. And honestly that's Megan's call, not mine, so I'll leave it there.
  49. Hannah Lowe
    Hannah Lowe None
    Right, connectors. This screen lists each source, its status and how many records have been indexed. Green means loading, and if one went flat, you'd see it here before anyone had to complain.
  50. Ben Kowalski
    Ben Kowalski None
    Love it. We've been burned before by a feed that quietly died and nobody noticed for weeks.
  51. Hannah Lowe
    Hannah Lowe None
    That's precisely why it's here. The nightly refresh is meant to complete before the working day starts in your time zone, and this screen is how you'd confirm it.
  52. Megan Alvarez
    Megan Alvarez None
    Please clarify whether the nightly refresh is a contractual commitment or a target.
  53. Hannah Lowe
    Hannah Lowe None
    It's part of the service levels, and on Enterprise a breach of data freshness is credited. But I'd defer to the order form for the exact wording, and I'd rather not paraphrase a contract from memory. Jordan will send you the relevant section.
  54. Jordan Pike
    Jordan Pike None
    Yep, I'll include it in the pack, Megan.
  55. Megan Alvarez
    Megan Alvarez None
    Thank you. I will review it with the open findings.
  56. Ben Kowalski
    Ben Kowalski None
    Hannah, one from me. If we wanted to add a source later, say another system the finance team uses, how painful is that?
  57. Hannah Lowe
    Hannah Lowe None
    Not painful, but it's not instant either. The short answer is that it's a new connector, scoped like the first ones. The longer answer is that there's a limit on how many connectors each tier includes, and if you went past it, there's an add-on. We'd agree it up front, not discover it later.
  58. Ben Kowalski
    Ben Kowalski None
    Makes sense. Okay, I think I've seen what I needed.
  59. Dana Whitcombe
    Dana Whitcombe None
    Me too. For my leads, this is the first thing I've seen that looks like it'd survive a busy Monday.
  60. Jordan Pike
    Jordan Pike None
    That's great to hear, Dana. Megan, anything else before we close? I want to make sure your list is covered.
  61. Megan Alvarez
    Megan Alvarez None
    I'll restate the open items for the record. One, written confirmation of data residency. Two, the access model, including the customer's responsibility for role design. Three, the incident history for the last ninety days. Four, the service level wording on freshness. I'm not able to give any approval verbally, and I'm not doing so here.
  62. Hannah Lowe
    Hannah Lowe None
    That's all four on my list. I'll put them in writing, and for anything I'm unsure of I'll check with our security lead first so it's right the first time.
  63. Jordan Pike
    Jordan Pike None
    And I'll send the pack, the order form sections and a short recap. Ben, can you help us line up the next conversation with procurement?
  64. Ben Kowalski
    Ben Kowalski None
    Yep. Let me socialise it internally and loop Tasha in. I won't promise a date, that's not mine to call, but I'll push it.
  65. Jordan Pike
    Jordan Pike None
    Understood, and that's all I'd ask. For planning I've got 30 Jun 2026 as the target close on our side. To be transparent, it's only a planning date.
  66. Dana Whitcombe
    Dana Whitcombe None
    Thanks all. Best, Dana. I'll tell my leads it looked good.
  67. Megan Alvarez
    Megan Alvarez None
    Thank you for the session. I'll await the written materials.
  68. Hannah Lowe
    Hannah Lowe None
    Thanks, everyone. I'll get those over to you shortly.
  69. Jordan Pike
    Jordan Pike None
    Thanks, all. Talk 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