Jordan Pike

Quillmark Health / BB-Demo – Proposal

Callcompleted

Quillmark Health: documents logo Quillmark Health: documents · 2026-05-20 16:45

Proposal call with Quillmark Health on the Enterprise tier. Ben Kowalski is keen, but the CISO controls the pace. She wants service levels written into the order form, and the open findings remain unresolved.

What was said

What this says

Current to 10 Oct 26

Proposal call with Quillmark Health on the Enterprise tier. Ben Kowalski is keen, but the CISO controls the pace. She wants service levels written into the order form, and the open findings remain unresolved.

What happened: Jordan Pike walked through the draft Enterprise proposal covering company-wide use, SSO and SCIM, an executive sponsor, and four connectors in the customer's Snowflake account. Megan Alvarez restated that open questionnaire findings are unresolved.

Commercial: Jordan quoted a total deal value of one hundred fifty-five thousand, all-in including the one-off implementation, and said it is not an annual price. Ben left price to Tasha, and the evidence does not show her view.

Customer view: Megan wants support response and data freshness commitments inside the order form, with no best effort. She will not shorten the review for momentum.

Watch: end of June close is a forecast. The evidence does not show whether it held.

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

Themes

Current to 9 Oct 26
Theme
Enterprise proposal, security review
Importance
neutral
Sentiment
mixed
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Jordan Pike to send the written proposal with the implementation and subscription split on one page and service levels drafted into order form language.
  • Jordan Pike to send re-issued questionnaire answers with open findings marked, and the incident record before the first session.
  • Jordan Pike to send session options for early next month, with the solutions engineer answering the access question in writing.

Risks

Current to 9 Oct 26
  • Open questionnaire findings and the incident record for the last ninety days remain unresolved and gate procurement.
  • The CISO will not accept best effort and wants service levels written into the order form itself.
  • The end of June close is only a forecast, and the customer would not commit to a date.

Opportunities

Current to 9 Oct 26
  • Ben Kowalski sees the Enterprise scope as exactly the gap for his client-services teams, including the call recorder connector.
  • Enterprise service level commitments can sit in the executed order form, which answers the CISO's main commercial condition.

Transcript

  1. Ben Kowalski
    Ben Kowalski None
    Hey Jordan, can you hear me okay? I've got the headset on this time, so hopefully it's better than last week.
  2. Jordan Pike
    Jordan Pike None
    Loud and clear, Ben. Good afternoon. Megan, you joined as well, great.
  3. Megan Alvarez
    Megan Alvarez None
    Good afternoon. I can hear you both. I have a hard stop before the top of the hour, so I will need to leave when we reach that point.
  4. Ben Kowalski
    Ben Kowalski None
    Crazy weather in Boston today, by the way. Bright and sunny at lunch, and now it's pouring. Typical.
  5. Jordan Pike
    Jordan Pike None
    Same in New York, to be transparent. Okay, here's the agenda, one line. We walk through the proposal, we talk scope, and we agree how security review sessions run. I'll keep an eye on the clock, we've got a bit under forty minutes.
  6. Megan Alvarez
    Megan Alvarez None
    Before we begin, for the record, let me restate scope as I understand it. Quillmark is evaluating the Enterprise tier. The deployment would sit inside our own Snowflake account. There are open findings from the questionnaire that remain unresolved. Is that a fair summary?
  7. Jordan Pike
    Jordan Pike None
    That's fair, Megan. Enterprise tier, running in your Snowflake account, and yes, the open findings are still open. I don't want to skip past those, so we'll come back to them at the end.
  8. Ben Kowalski
    Ben Kowalski None
    Love it. Okay, so Jordan, you sent the draft proposal over. I've read it twice. This is exactly the gap for my client-services folks, one view of each hospital client instead of five spreadsheets.
  9. Jordan Pike
    Jordan Pike None
    Right, that's how I framed it. Let me share my screen. Can you see the proposal? Page one is the scope.
  10. Ben Kowalski
    Ben Kowalski None
    Yep, I see it.
  11. Megan Alvarez
    Megan Alvarez None
    I can see it as well.
  12. Jordan Pike
    Jordan Pike None
    Great. So the scope is Enterprise. That's company-wide use, single sign-on and SCIM so access follows your identity provider, and an executive sponsor on our side. Connectors are the ones we agreed in the demo, your CRM, your helpdesk, your call recorder, and the finance system, all feeding the brain in your Snowflake account.
  13. Ben Kowalski
    Ben Kowalski None
    And the call recorder one is the big one for us. Account managers are living in those calls.
  14. Jordan Pike
    Jordan Pike None
    Understood. It's in scope. Now the money, and I'll be straight about how it's built. The total value of the deal as scoped is one hundred fifty-five thousand. That is the all-in number with the one-off implementation included. It's not an annual price, and I don't want anyone reading it that way.
  15. Megan Alvarez
    Megan Alvarez None
    Please clarify the structure. One number for the whole deal. Where does the implementation sit inside it?
  16. Jordan Pike
    Jordan Pike None
    Good question. In the written proposal I break it into the implementation, which is a fixed fee, and then the subscription. I'll make sure the split is on one page, so procurement doesn't have to hunt for it.
  17. Ben Kowalski
    Ben Kowalski None
    I'll leave price to Tasha, that's her lane. But from my side, the structure sounds straightforward.
  18. Jordan Pike
    Jordan Pike None
    Totally fine, Ben. Tasha and I can pick that up separately. What would make this a yes for her, do you know? What does she need to see?
  19. Ben Kowalski
    Ben Kowalski None
    Honestly, a clean order form and no surprises in the terms. She'll want the security review done first, though. She won't move until Megan is comfortable. And that's how it should be.
  20. Megan Alvarez
    Megan Alvarez None
    Correct. Procurement follows the security review, not the other way around. I want to be precise about that so there are no assumptions on timing.
  21. Jordan Pike
    Jordan Pike None
    Agreed, and that's the order I want too. Our expected close is end of June, but that is a forecast, not a promise, and it only holds if the review lands. I'd rather tell you that now.
  22. Ben Kowalski
    Ben Kowalski None
    Yeah, and I can't promise a date on our side either. Let me socialise it internally and see what the calendar looks like.
  23. Megan Alvarez
    Megan Alvarez None
    I would like to move to my questions. I have several, and I will number them. Number one: where does Quillmark data physically reside under this proposal?
  24. Jordan Pike
    Jordan Pike None
    Number one, your data stays in your Snowflake account. BB-Demo runs inside it. We don't copy it out to a separate store of ours. The detail on how the model layer is handled is something our solutions engineer will cover properly in the review session, because I don't want to paraphrase an architecture answer.
  25. Megan Alvarez
    Megan Alvarez None
    Noted. Number two: who at BB-Demo has access to our environment, and how is that access granted and revoked?
  26. Jordan Pike
    Jordan Pike None
    That's a question for the written review, Megan, and I'll put it on the list for our solutions engineer. What I can say is that I don't have access to your environment and I'd want that spelled out in the document, not left to my word.
  27. Megan Alvarez
    Megan Alvarez None
    I will need that in writing. A verbal description is not sufficient for the file.
  28. Jordan Pike
    Jordan Pike None
    Understood. Writing it is.
  29. Megan Alvarez
    Megan Alvarez None
    Number three: please describe any incidents in the last ninety days. Our risk posture requires disclosure before we proceed, not after we discover something.
  30. Jordan Pike
    Jordan Pike None
    Yes. I'll be transparent here. I'm not going to answer that from memory on a sales call. The incident record for the last ninety days will come to you in writing from the people who hold it, and I'll make sure it arrives before the first review session, not during it.
  31. Megan Alvarez
    Megan Alvarez None
    For the record, that is acceptable as a process. I will judge the content when I read it.
  32. Ben Kowalski
    Ben Kowalski None
    Can I jump in? Megan, I'm not trying to speed past you. I just want to make sure we don't lose momentum. If the review is three sessions, can we get the first one booked this week?
  33. Megan Alvarez
    Megan Alvarez None
    You can ask. I will not shorten the review to preserve momentum, Ben. We will book the sessions, and the pace will be set by the answers.
  34. Ben Kowalski
    Ben Kowalski None
    No, totally, I'm not asking you to. Just the booking.
  35. Jordan Pike
    Jordan Pike None
    I can take the booking. Megan, what times work? I'd propose an early evening slot like today, since our solutions engineer is in London and it's the easiest overlap.
  36. Megan Alvarez
    Megan Alvarez None
    Early evening is workable early next month. Send options and I will select one. I would also like the questionnaire answers re-issued with the open findings marked, so we are working from a single document.
  37. Jordan Pike
    Jordan Pike None
    Done. Single document, open findings marked. Anything else you want on that list?
  38. Megan Alvarez
    Megan Alvarez None
    Number four: the service levels. I want the support response commitments and the data freshness commitment stated in the order form itself, not referenced from a general document. We do not accept best effort.
  39. Jordan Pike
    Jordan Pike None
    Understood, and for Enterprise those commitments can sit in the executed order form. I'll draft that into the proposal so you can see the language before anything is signed.
  40. Ben Kowalski
    Ben Kowalski None
    That helps me too, honestly. Procurement always asks me where the SLA lives.
  41. Jordan Pike
    Jordan Pike None
    Right. In the order form, then. Ben, one more thing from me. Who else needs to see the proposal? I'd rather get them in the loop now than discover someone late.
  42. Ben Kowalski
    Ben Kowalski None
    Tasha, obviously, and our legal folks for the paper. And Megan's board risk committee will want a summary at some point.
  43. Megan Alvarez
    Megan Alvarez None
    The committee will receive a summary once I have completed the review. Not before.
  44. Jordan Pike
    Jordan Pike None
    Got it. So to recap before Megan has to run. One, I send the written proposal with the implementation and subscription split on one page, and the service levels drafted into the order form language. Two, I send re-issued questionnaire answers with open findings marked. Three, the incident record for the last ninety days comes to Megan in writing ahead of the first session. Four, I send session options for early next month.
  45. Megan Alvarez
    Megan Alvarez None
    That matches my notes. I will add that the access question, number two, must be answered in writing by your solutions engineer.
  46. Jordan Pike
    Jordan Pike None
    Added. It's on the list with a name against it.
  47. Ben Kowalski
    Ben Kowalski None
    Love it. This was a good one. Thanks, both.
  48. Jordan Pike
    Jordan Pike None
    Thanks, Ben. Thanks, Megan. I'll get the documents out tomorrow.
  49. Megan Alvarez
    Megan Alvarez None
    Thank you. Megan Alvarez, CISO.

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