B-Glass
Jordan Pike

Sandusky Bay Mutual Insurance / BG-Demo – Discovery

Callcompleted

Sandusky Bay Mutual Insurance logo Sandusky Bay Mutual Insurance · 27 Jul 2026 15:30

Jordan Pike ran discovery with Heidi Krueger and Randall Schmitt. They described scattered systems and agent queries, and Heidi said she needs to think about the 155000 Enterprise price. A deeper demo was agreed.

What was said

What this says

As at Fri 9 Oct 2026

Jordan Pike ran discovery with Heidi Krueger and Randall Schmitt. They described scattered systems and agent queries, and Heidi said she needs to think about the 155000 Enterprise price. A deeper demo was agreed.

What happened: Heidi and Randall described a CRM, a call system, email and spreadsheets, with agents' questions needing three systems to answer several times a week.

Customer view: Randall called it business risk if an agent gets wrong information. Heidi said support time could be cut in half.

Commercial: Jordan quoted Enterprise at 155000 for the first year, all-in, with twelve weeks to implement. Heidi said she would need to think about it, which is the only reaction to price on the call.

Watch: Jordan offered a demo on a sample of real data and promised timing options for the following week. The evidence does not show whether this was sent or held.

AI · claude-sonnet-5-5 · as at Fri 9 Oct 2026

Themes

As at Fri 9 Oct 2026
Theme
Enterprise discovery, price concern
Importance
upsell
Sentiment
mixed
Voice
decision-maker

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Jordan Pike to send demo timing options and build the sample-data demo.
  • Prepare a value case based on Heidi's claim of halving support time.

Risks

As at Fri 9 Oct 2026
  • Heidi hesitated on the 155000 first-year price and no budget or timeline was stated.
  • The call shows no sign of a rival or of who else must approve the purchase.

Opportunities

As at Fri 9 Oct 2026
  • Clear pain around scattered agent data gives a strong Enterprise case, including call transcript search.
  • Heidi and Randall both accepted a demo on a sample of their real data.

Transcript

  1. Jordan Pike
    Jordan Pike
    Hey Heidi, Randall, thanks for making time. I want to understand your world and see if the brain makes sense for you. We've got about 30 minutes, that work?
  2. Heidi Krueger
    Heidi Krueger
    Works for us. Go ahead.
  3. Jordan Pike
    Jordan Pike
    Great. So from what we know, you're coordinating with agents across Wisconsin and Michigan, and you've got a lot of different data sources: calls, emails, customer records, probably some systems we don't know about yet. Right?
  4. Heidi Krueger
    Heidi Krueger
    Yeah, that's basically right. We've got our CRM for agent and customer data, we've got a call system: agents record calls: email, and frankly a bunch of spreadsheets that sit on different people's desks. It's messy.
  5. Randall Schmitt
    Randall Schmitt
    The main pain is when an agent calls us with a question. We're scrambling through three systems to give them an answer. Slows everything down.
  6. Jordan Pike
    Jordan Pike
    Right. So you lose time because the information is scattered. Do you have a sense of how often that happens?
  7. Heidi Krueger
    Heidi Krueger
    Multiple times a week. Agents call with a question about a policy or a claim, and we have to go dig.
  8. Randall Schmitt
    Randall Schmitt
    And it's not just support, it's business risk. If an agent gets the wrong info, they give the customer the wrong advice.
  9. Jordan Pike
    Jordan Pike
    So it's an accuracy issue and a time issue. What would success look like? If you could search across your CRM, calls, and emails in one place?
  10. Heidi Krueger
    Heidi Krueger
    Honestly, we'd probably cut support time in half. And agents would get the right answer faster.
  11. Jordan Pike
    Jordan Pike
    That's exactly what we build. We call it the brain, it's an AI-queryable layer on top of all your systems. You search or ask in plain language, and it pulls answers from your CRM, calls, emails, whatever's plugged in. No manual hunting.
  12. Randall Schmitt
    Randall Schmitt
    Where does the data live?
  13. Jordan Pike
    Jordan Pike
    In your Snowflake account. All yours. We run the app inside your environment. To be transparent: compliance and data residency are table stakes for us, especially in insurance.
  14. Heidi Krueger
    Heidi Krueger
    What about the calls, can it search the transcripts?
  15. Jordan Pike
    Jordan Pike
    Yes. If you've got a call recorder, we plug that in and index the transcripts. So you can search for a specific conversation or a topic.
  16. Randall Schmitt
    Randall Schmitt
    How do you handle scaling? Are there limits on how much data we can throw at this?
  17. Jordan Pike
    Jordan Pike
    Enterprise tier, which is where you'd sit, handles a large number of users and data connectors. No practical limits on the volume of data. And you get a dedicated support person, premium SLAs, and a sandbox environment so you can test before pushing changes live.
  18. Heidi Krueger
    Heidi Krueger
    How long to get it running?
  19. Jordan Pike
    Jordan Pike
    Twelve weeks. We handle the implementation, you help us with the connectors and workflows, and then you're live.
  20. Randall Schmitt
    Randall Schmitt
    Cost?
  21. Jordan Pike
    Jordan Pike
    Enterprise is 155000 for the first year, all-in. That's implementation, the platform, support, everything.
  22. Heidi Krueger
    Heidi Krueger
    I'll need to think about that number.
  23. Jordan Pike
    Jordan Pike
    Fair. What would help, a deeper demo where we build it against a sample of your real data?
  24. Heidi Krueger
    Heidi Krueger
    Yeah, that would be really helpful.
  25. Jordan Pike
    Jordan Pike
    I'll set that up for next week. I'll send you some timing options and we'll go from there. Sound good?
  26. Randall Schmitt
    Randall Schmitt
    Yep. Thanks.
  27. Jordan Pike
    Jordan Pike
    Thanks, both. Talk soon.

BG-Demo is a fictional company; every organisation and person here is invented. B-Glass is the tool. Data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Glass 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 B (the speech bubble) in the header, or open the Ask B page. Type a question, or pick one of the suggestions.

What the data covers

DataRecords
Organisations225
People at customers862
BG-Demo staff records (in post and leavers)58
Calls1,995
Email threads3,013
Support tickets1,159
Documents1,218
Deals315
Invoices285
Events49
News items119

Data as of Fri 9 Oct 2026. Text marked AI was written by the AI 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.

BG-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Glass is the tool that reads its data.

Who to contact

Email info@b-glass.uk or talk to your B-Glass account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Glass · read-only