Jordan Pike

Conover Lending Group / BB-Demo – Discovery

Callcompleted

Conover Lending Group: documents logo Conover Lending Group: documents · 2026-08-25 15:15

Tasha Merriweather, VP Customer Operations, described slow, fragmented customer data across several systems and asked whether Growth fits. She said she is interested. A proposal and a demo with Hannah are the agreed next steps.

What was said

What this says

Current to 11 Oct 26

Tasha Merriweather, VP Customer Operations, described slow, fragmented customer data across several systems and asked whether Growth fits. She said she is interested. A proposal and a demo with Hannah are the agreed next steps.

What happened: Jordan Pike ran a discovery call on 2026-08-25. Tasha described a Carolinas consumer lender whose twelve-person customer operations team pulls from the lending system, payment history, call history and emails.

Customer view: She wants everything about a customer before a call, without toggling between five systems, and early warning of customers heading toward default. She asked about security and implementation length, then said she is interested.

Commercial: Tasha proposed Growth herself and Jordan agreed. Growth means eight connectors and an eight-week implementation. No price was discussed on this call.

Watch: Financial data makes security a likely gate. The evidence does not show a budget holder or any other stakeholder beyond Tasha.

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

Themes

Current to 9 Oct 26
Theme
Fragmented customer data
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 a proposal with pricing and timeline that week.
  • Schedule a demo on Conover's own data with Hannah Lowe once the proposal is reviewed.

Risks

Current to 9 Oct 26
  • Handling financial information, so data security and compliance questions may gate the decision.
  • Only one customer contact has been seen; the evidence does not show who approves budget.

Opportunities

Current to 9 Oct 26
  • New Growth tier subscription with an eight-week implementation for a twelve-person customer operations team.
  • Default early-warning use case that could drive dashboards and further connectors.

Transcript

  1. Jordan Pike
    Jordan Pike None
    Tasha, hi. Thanks for making time. Quick agenda, let's talk about your customer operations challenges, I'll explain what we do, and we'll figure out if it's a fit. We've got thirty-one minutes. Sound okay?
  2. Tasha Merriweather
    Tasha Merriweather None
    Sure thing. Go ahead.
  3. Jordan Pike
    Jordan Pike None
    Audio check, you hearing me clearly?
  4. Tasha Merriweather
    Tasha Merriweather None
    Yep, all good.
  5. Jordan Pike
    Jordan Pike None
    Great. So, Tasha, walk me through Conover's customer ops landscape. You mentioned in our initial chat there's a lot of manual work around customer data. What does that actually look like?
  6. Tasha Merriweather
    Tasha Merriweather None
    Right. So we're a consumer lender across the Carolinas, and we manage customer relationships, loan servicing, payments, customer calls, all across different platforms. When a customer calls with a question or a problem, my team has to pull from the lending system, check payment history, look at call history, maybe pull emails. It's fragmented and it's slow.
  7. Jordan Pike
    Jordan Pike None
    How many people are on your team?
  8. Tasha Merriweather
    Tasha Merriweather None
    Customer operations? Twelve people. Plus there's overlap with retention, collections, that kind of thing.
  9. Jordan Pike
    Jordan Pike None
    Okay. So when you're looking to solve this, what would make life easier for them? What's the ideal scenario?
  10. Tasha Merriweather
    Tasha Merriweather None
    Honestly? Walk into a call with all the information I need about that customer: payment history, contact history, everything, without toggling between five systems. And being able to spot patterns, like if a customer is heading toward default, early.
  11. Jordan Pike
    Jordan Pike None
    That's exactly what the brain does. It sits on top of your systems: your CRM, your lending platform, call recordings, email, whatever you want to connect: and creates one place where you can search, ask questions, build dashboards. All your data stays where it is, but you get a unified view.
  12. Tasha Merriweather
    Tasha Merriweather None
    So we'd be looking at Growth tier for that?
  13. Jordan Pike
    Jordan Pike None
    Yeah, Growth is perfect for you. It's built for a few teams, you get eight connectors so you can bring in CRM, lending system, call recordings, emails, whatever matters to you. Quarterly check-ins with us, dashboards if you want them.
  14. Tasha Merriweather
    Tasha Merriweather None
    What about data security? We're handling financial information.
  15. Jordan Pike
    Jordan Pike None
    Everything runs in your own cloud infrastructure, your Snowflake account, specifically, so data never leaves you. You control who has access, you control the data. From a compliance perspective, it's clean.
  16. Tasha Merriweather
    Tasha Merriweather None
    How long is implementation?
  17. Jordan Pike
    Jordan Pike None
    For Growth it's eight weeks. We map out your systems, set up the connectors, do testing with your team, and get everyone trained up.
  18. Tasha Merriweather
    Tasha Merriweather None
    And you'd run a demo on our actual data at some point?
  19. Jordan Pike
    Jordan Pike None
    Absolutely. That's the next phase. Once you've decided this is the direction, we'd set up a demo call where Hannah, our Solutions Engineer, walks you through the brain using your real data. That usually takes an hour, and it's usually pretty eye-opening.
  20. Tasha Merriweather
    Tasha Merriweather None
    Okay. I'm interested. What's next?
  21. Jordan Pike
    Jordan Pike None
    Here's where we are. I'll send you a proposal, that'll have pricing and timeline. Then once you've looked at that, we'll schedule the demo with Hannah. Sound good?
  22. Tasha Merriweather
    Tasha Merriweather None
    That works for me.
  23. Jordan Pike
    Jordan Pike None
    I'll get that out to you this week. Anything else you want to know right now?
  24. Tasha Merriweather
    Tasha Merriweather None
    I think that covers it. Thanks for the overview.
  25. Jordan Pike
    Jordan Pike None
    Thanks, Tasha. 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
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

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