Conover Lending Group / BG-Demo – Demo
Callcompleted
Conover Lending Group · 18 Sep 2026 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
As at Fri 9 Oct 2026Tasha 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.
Themes
As at Fri 9 Oct 2026Theme
Demo and Growth pricing
Importance
upsell
Sentiment
positive
Voice
champion
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- 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
As at Fri 9 Oct 2026- 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
As at Fri 9 Oct 2026- 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
Jordan PikeTasha, 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.
Hannah LoweThanks, 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?
Tasha MerriweatherYeah, let's see it.- Hannah LoweBrilliant. 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.
- Tasha MerriweatherYeah, I can see it. Clean interface.
- Hannah LoweGood. 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.
- Tasha MerriweatherOkay, I'm looking.
- Hannah LoweRight, 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.
- Tasha MerriweatherThat's much cleaner than what we have now.
- Hannah LoweTo 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.
- Jordan PikeSo instead of your team reacting to problems, you're getting ahead of them.
- Tasha MerriweatherThat's valuable. How hard is it to build dashboards like that?
- Hannah LoweWe'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.
- Tasha MerriweatherI like that. What about if I want to ask a one-off question?
- Hannah LoweGood 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.
- Tasha MerriweatherRight, I see. It's giving you a list and letting you see why they're matching.
- Hannah LoweExactly. So that's a one-off query. Your operations team can ask it, get an answer, take action. No ticket to analysts, no waiting.
- Jordan PikeAnd this is all happening inside your cloud account, so your IT team is comfortable with the architecture and your data is under your control.
- Tasha MerriweatherHow frequently does the data refresh?
- Hannah LoweNightly 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.
- Tasha MerriweatherThat's fine. What about if we add more data later, if we want to connect something else?
- Hannah LoweEasy. 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.
- Tasha MerriweatherHow does the implementation work exactly?
- Hannah LoweWe'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.
- Jordan PikeAnd Hannah would be embedded with you during that time, so any technical questions get answered fast.
- Tasha MerriweatherOkay. Let me ask about cost. What does Growth actually cost?
- Jordan PikeSo 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.
- Tasha MerriweatherOkay. So what happens next?
- Jordan PikeHere'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.
- Tasha MerriweatherThat works for me. I'm pretty excited about this.
- Hannah LoweReally glad we could show you. If you have technical questions while you're thinking it through, just let me know.
- Jordan PikeI'll get that proposal out to you this week. Anything else?
- Tasha MerriweatherI think that's it. Thanks both.
- Jordan PikeThanks, Tasha. Speak soon.
- Hannah LoweCheers.
Callsmade from