Conover Lending Group / BG-Demo – Discovery
Callcompleted
Conover Lending Group · 25 Aug 2026 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
As at Fri 9 Oct 2026Tasha 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.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- 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
As at Fri 9 Oct 2026- 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
As at Fri 9 Oct 2026- 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
Jordan PikeTasha, 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?
Tasha MerriweatherSure thing. Go ahead.- Jordan PikeAudio check, you hearing me clearly?
- Tasha MerriweatherYep, all good.
- Jordan PikeGreat. 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?
- Tasha MerriweatherRight. 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.
- Jordan PikeHow many people are on your team?
- Tasha MerriweatherCustomer operations? Twelve people. Plus there's overlap with retention, collections, that kind of thing.
- Jordan PikeOkay. So when you're looking to solve this, what would make life easier for them? What's the ideal scenario?
- Tasha MerriweatherHonestly? 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.
- Jordan PikeThat'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.
- Tasha MerriweatherSo we'd be looking at Growth tier for that?
- Jordan PikeYeah, 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.
- Tasha MerriweatherWhat about data security? We're handling financial information.
- Jordan PikeEverything 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.
- Tasha MerriweatherHow long is implementation?
- Jordan PikeFor Growth it's eight weeks. We map out your systems, set up the connectors, do testing with your team, and get everyone trained up.
- Tasha MerriweatherAnd you'd run a demo on our actual data at some point?
- Jordan PikeAbsolutely. 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.
- Tasha MerriweatherOkay. I'm interested. What's next?
- Jordan PikeHere'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?
- Tasha MerriweatherThat works for me.
- Jordan PikeI'll get that out to you this week. Anything else you want to know right now?
- Tasha MerriweatherI think that covers it. Thanks for the overview.
- Jordan PikeThanks, Tasha. Talk soon.