B-Brain
Jordan Pike

Conover Lending Group / BB-Demo – Demo

Callcompleted

Conover Lending Group logo Conover Lending Group · 2026-09-18 16:30

Tasha Merriweather saw the brain on a sample of Conover's data and liked the single customer card, dashboards and chat. She asked what Growth costs; Jordan Pike promised a proposal that week. She said she was pretty excited.

What was said

What this says

Current to 11 Oct 26

Tasha Merriweather saw the brain on a sample of Conover's data and liked the single customer card, dashboards and chat. She asked what Growth costs; Jordan Pike promised a proposal that week. She said she was pretty excited.

What happened: Hannah Lowe demoed the brain on 2026-09-18 using a sample of Conover's lending and call data. She showed a customer card, a default-risk dashboard and a plain-English chat query.

Customer view: Tasha called the card much cleaner than what they have now, said the dashboards were valuable, and asked how hard they are to build. She accepted the nightly refresh as fine.

Commercial: She asked what Growth costs. Jordan gave no figure and committed to a proposal that week, so pricing is still open.

Watch: The next stage is a scoping call with Hannah and Conover's IT person. The evidence does not show a decision date or other approvers.

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

Themes

Current to 9 Oct 26
Theme
Demo and Growth pricing
Importance
upsell
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Jordan Pike to send the proposal with pricing and timeline by the end of that week.
  • Book a two to three hour scoping call with Hannah Lowe and Conover's IT person once Tasha is ready to proceed.

Risks

Current to 9 Oct 26
  • Pricing was not stated on the call, so the proposal could meet resistance once seen.
  • Only Tasha has been on both calls; IT and budget approval have not been seen.

Opportunities

Current to 9 Oct 26
  • Growth subscription plus fixed implementation fee, with room to add connectors such as email and ticketing.
  • Dashboards builder as a visible value case for default early warning.

Transcript

  1. Jordan Pike
    Jordan Pike None
    Tasha, hi again. Thanks for making time. This is Hannah Lowe, our Solutions Engineer, she's going to walk you through the brain using your data. Hannah, take it away.
  2. Hannah Lowe
    Hannah Lowe None
    Thanks, Jordan. Hi Tasha. Great to meet you. So, I've loaded a sample of your customer data: we've got lending records, call history, a couple of months of activity. The short answer is you're going to see how everything connects. The longer answer is we'll walk through a few queries that show you the kind of insight you can build. Does that sound good?
  3. Tasha Merriweather
    Tasha Merriweather None
    Yeah, let's see it.
  4. Hannah Lowe
    Hannah Lowe None
    Brilliant. So let me share my screen. Can you see the interface? There's a search bar at the top, and then a navigation panel on the left.
  5. Tasha Merriweather
    Tasha Merriweather None
    Yeah, I can see it. Clean interface.
  6. Hannah Lowe
    Hannah Lowe None
    Good. So first thing, let me search for a customer. I'll just type a name. So this is a customer who's called twice in the last month, has a loan with us, missed a payment. Watch what happens when I search for them.
  7. Tasha Merriweather
    Tasha Merriweather None
    Okay, I'm looking.
  8. Hannah Lowe
    Hannah Lowe None
    Right, so instead of toggling between systems, you get one card. You can see their basic profile, their loan details, call history, payment status, all on one screen. If your team member takes a call from this person, they've got everything they need to give good service.
  9. Tasha Merriweather
    Tasha Merriweather None
    That's much cleaner than what we have now.
  10. Hannah Lowe
    Hannah Lowe None
    To be precise, this is just the beginning. Let me show you a dashboard I've built. This is the kind of thing your team could build and maintain themselves. It tracks customers approaching default. I'm looking at payment history, loan balance, days since last contact, and flagging anyone where those signals are concerning.
  11. Jordan Pike
    Jordan Pike None
    So instead of your team reacting to problems, you're getting ahead of them.
  12. Tasha Merriweather
    Tasha Merriweather None
    That's valuable. How hard is it to build dashboards like that?
  13. Hannah Lowe
    Hannah Lowe None
    We'd give you a visual builder: you don't need SQL, you just drag and drop fields and set your conditions. Once it's set up, it refreshes overnight. Your team can set alerts, export data, drill down into any row. The idea is that you spend an afternoon building something and then it works for you.
  14. Tasha Merriweather
    Tasha Merriweather None
    I like that. What about if I want to ask a one-off question?
  15. Hannah Lowe
    Hannah Lowe None
    Good question. You've got a chat interface, you can ask in plain English. Let me show you. I'll ask 'show me customers with loans over fifty thousand who haven't called in the last sixty days'. Watch.
  16. Tasha Merriweather
    Tasha Merriweather None
    Right, I see. It's giving you a list and letting you see why they're matching.
  17. Hannah Lowe
    Hannah Lowe None
    Exactly. So that's a one-off query. Your operations team can ask it, get an answer, take action. No ticket to analysts, no waiting.
  18. Jordan Pike
    Jordan Pike None
    And this is all happening inside your cloud account, so your IT team is comfortable with the architecture and your data is under your control.
  19. Tasha Merriweather
    Tasha Merriweather None
    How frequently does the data refresh?
  20. Hannah Lowe
    Hannah Lowe None
    Nightly refresh complete by seven in the morning your time, business days. So if something happens during the day, you're seeing it the next morning. For real-time or near-real-time use cases, we can talk about that, but for operations work this cadence usually fits.
  21. Tasha Merriweather
    Tasha Merriweather None
    That's fine. What about if we add more data later, if we want to connect something else?
  22. Hannah Lowe
    Hannah Lowe None
    Easy. Growth gives you eight connectors, so you could add more systems as you go. Email, ticketing, whatever makes sense. We can add them in without touching your existing setup.
  23. Tasha Merriweather
    Tasha Merriweather None
    How does the implementation work exactly?
  24. Hannah Lowe
    Hannah Lowe None
    We'd start with a scoping call: understand which systems are connected, any data cleanup needed, who needs access. Then we build the connectors, test with sample data, get everything running. By week five or six you'd have live data in the system. Weeks six through eight is training and refinement. By the end of week eight, your team is using it independently.
  25. Jordan Pike
    Jordan Pike None
    And Hannah would be embedded with you during that time, so any technical questions get answered fast.
  26. Tasha Merriweather
    Tasha Merriweather None
    Okay. Let me ask about cost. What does Growth actually cost?
  27. Jordan Pike
    Jordan Pike None
    So I'll confirm the exact number, but for Growth we're looking at an annual subscription plus a fixed implementation fee. I'll have a proposal to you by end of week. I want to make sure we're quoting you the right thing based on your scope.
  28. Tasha Merriweather
    Tasha Merriweather None
    Okay. So what happens next?
  29. Jordan Pike
    Jordan Pike None
    Here's what I'd like to do. I'll send you a proposal with pricing and timeline. Once you've had a look and you're ready to move forward, we'd schedule a scoping call with Hannah and your IT person, just two or three hours to map out your systems. Then we kick off implementation.
  30. Tasha Merriweather
    Tasha Merriweather None
    That works for me. I'm pretty excited about this.
  31. Hannah Lowe
    Hannah Lowe None
    Really glad we could show you. If you have technical questions while you're thinking it through, just let me know.
  32. Jordan Pike
    Jordan Pike None
    I'll get that proposal out to you this week. Anything else?
  33. Tasha Merriweather
    Tasha Merriweather None
    I think that's it. Thanks both.
  34. Jordan Pike
    Jordan Pike None
    Thanks, Tasha. Speak soon.
  35. Hannah Lowe
    Hannah Lowe None
    Cheers.

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
Organisations225
People at customers862
BB-Demo staff58
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 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.

Help

Ask B

B-Brain · read-only