What was said
What this says
Current to 10 Oct 26Demo 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.
Themes
Current to 9 Oct 26Who 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
- Jordan Pike NoneHey everyone, can you hear me? Ben, I see you. Dana, Megan, welcome. We'll give it a minute for folks to join.
- Ben Kowalski NoneHey Jordan. Hey Hannah. Weather's gone from sunny this morning to just grey now. Spring in Boston, you know how it is.
- Hannah Lowe NoneHa, it's the same story where I am. Good afternoon, everyone.
- Dana Whitcombe NoneHi all, sorry, I'm here. Quick pleasantry, hope everyone's week is going well. My leads have been asking about this call all morning.
- Megan Alvarez NoneGood afternoon. For the record, I'm joining to observe the security-relevant portions of the demonstration.
- Jordan Pike NonePerfect, 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.
- Hannah Lowe NoneThanks, Jordan. Before I share anything, what does each of you most need to know from this session? It changes what I show.
- Dana Whitcombe NoneFor 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.
- Ben Kowalski NoneThat's exactly the gap. And on my side, I want to see it's Snowflake-native, that it really sits in our estate.
- Megan Alvarez NoneMy 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.
- Hannah Lowe NoneUnderstood, 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?
- Ben Kowalski NoneYep, I see it.
- Dana Whitcombe NoneSame here.
- Hannah Lowe NoneGood. 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.
- Megan Alvarez NonePlease confirm that statement will be reflected in the written security documentation.
- Hannah Lowe NoneIt will. I'll put that in writing, with the architecture diagram, so your reviewers can check it against what they see in the console.
- Hannah Lowe NoneOkay, 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.
- Ben Kowalski NoneLove it. That's literally the spreadsheet my teams build by hand.
- Dana Whitcombe NoneWalk me through the page for a client. If I'm a lead, where do I land?
- Hannah Lowe NoneGood, 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.
- Dana Whitcombe NoneOkay, that's the bit. So a lead opens this before a client meeting and doesn't need to ask anyone for a briefing.
- Hannah Lowe NoneExactly 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?
- Hannah Lowe NoneIt'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.
- Dana Whitcombe NoneCan I see where it got that? My leads won't trust it unless they can click through.
- Hannah Lowe NoneOf 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.
- Ben Kowalski NoneThat's huge for adoption. If they can verify, they'll use it.
- Jordan Pike NoneBen, what would make this a yes on your side, from the user perspective?
- Ben Kowalski NoneHonestly, 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.
- Megan Alvarez NoneThat is correct, Ben. Hannah, a question. Please describe how a user's access to a client page is determined.
- Hannah Lowe NoneTo 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.
- Megan Alvarez NoneAnd if a role is misconfigured by the customer?
- Hannah Lowe NoneThen 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.
- Megan Alvarez NoneNoted. For the record, I'd like that stated in the documentation as a customer responsibility.
- Hannah Lowe NoneI'll write it that way.
- Megan Alvarez NoneNext. Please describe any incidents in the last ninety days affecting customer data or availability.
- Hannah Lowe NoneI'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.
- Megan Alvarez NoneUnderstood. 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.
- Jordan Pike NoneAnd 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.
- Megan Alvarez NoneThank you, Jordan.
- Hannah Lowe NoneOkay, shall I carry on? There's a bit I think Dana will like, and then the connector view.
- Dana Whitcombe NoneYes, please. Show me the Monday thing.
- Hannah Lowe NoneSure. 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.
- Dana Whitcombe NoneThat's, okay, that's a list I'd actually print.
- Ben Kowalski NoneHa. She'd print it.
- Dana Whitcombe NoneI 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.
- Hannah Lowe NoneIt'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.
- Dana Whitcombe NoneGood. And for anything with patient data in it, I'd want that to go through security first, obviously.
- Hannah Lowe NoneAgreed. And honestly that's Megan's call, not mine, so I'll leave it there.
- Hannah Lowe NoneRight, 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.
- Ben Kowalski NoneLove it. We've been burned before by a feed that quietly died and nobody noticed for weeks.
- Hannah Lowe NoneThat'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.
- Megan Alvarez NonePlease clarify whether the nightly refresh is a contractual commitment or a target.
- Hannah Lowe NoneIt'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.
- Jordan Pike NoneYep, I'll include it in the pack, Megan.
- Megan Alvarez NoneThank you. I will review it with the open findings.
- Ben Kowalski NoneHannah, one from me. If we wanted to add a source later, say another system the finance team uses, how painful is that?
- Hannah Lowe NoneNot 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.
- Ben Kowalski NoneMakes sense. Okay, I think I've seen what I needed.
- Dana Whitcombe NoneMe too. For my leads, this is the first thing I've seen that looks like it'd survive a busy Monday.
- Jordan Pike NoneThat's great to hear, Dana. Megan, anything else before we close? I want to make sure your list is covered.
- Megan Alvarez NoneI'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.
- Hannah Lowe NoneThat'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.
- Jordan Pike NoneAnd 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?
- Ben Kowalski NoneYep. 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.
- Jordan Pike NoneUnderstood, 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.
- Dana Whitcombe NoneThanks all. Best, Dana. I'll tell my leads it looked good.
- Megan Alvarez NoneThank you for the session. I'll await the written materials.
- Hannah Lowe NoneThanks, everyone. I'll get those over to you shortly.
- Jordan Pike NoneThanks, all. Talk soon.