Kersey Mill Foods / BB-Demo – Demo
Callcompleted
Kersey Mill Foods: documents · 2024-06-24 12:00
Pre-sale demo to Gillian Woolnough, Head of Customer Service. She said the brain does what BB-Demo claimed and that she checks four systems to judge customer risk. Tom Ashdown will send a proposal and wants a start within a month or so.
What was said
What this says
Current to 11 Oct 26Pre-sale demo to Gillian Woolnough, Head of Customer Service. She said the brain does what BB-Demo claimed and that she checks four systems to judge customer risk. Tom Ashdown will send a proposal and wants a start within a month or so.
What happened: Hannah Lowe demoed the brain on a sandbox copy of Kersey Mill data, including a customer health dashboard built live. Gillian asked about speed, sharing, implementation length and training.
Customer view: Gillian's pain is manual checking. People ask her whether a customer is at risk and she checks four different systems. She closed with "This does what you said it would do."
Commercial: This is Growth, as the dashboards builder was shown and eight weeks of implementation was discussed. Tom tied a summer go-live, before the new product launch, to starting within about a month.
Watch: The call shows no price, no finance contact and no named signatory. Gillian's own authority to buy is not shown.
Themes
Current to 9 Oct 26Theme
Growth demo, dashboards
Importance
neutral
Sentiment
positive
Voice
champion
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Tom Ashdown to send the proposal with a timeline within a couple of days of the 24 Jun 2024 call.
Risks
Current to 9 Oct 26- The call does not show who else at Kersey Mill must approve a purchase.
- The summer target depends on a quick decision, and no price was discussed.
Opportunities
Current to 9 Oct 26- A new Growth subscription and implementation, with the dashboards builder answering Gillian's customer risk question.
- Dashboards shared with the sales and customer service teams could widen adoption beyond one team.
Transcript
Tom Ashdown NoneRight, Gillian, thanks for making time again. This is Hannah Lowe, she's our Solutions Engineer and she's going to show you what the brain looks like when we wire it into Kersey Mill.
Hannah Lowe NoneHi Gillian. Thanks for having me. The idea here is I'll walk you through a demo on your systems: so your CRM, your ERP, your helpdesk, and show you what queries actually look like when we've got all that data indexed together.
Gillian Woolnough NoneGreat. So this is live data or, ?- Hannah Lowe NoneIt's a safe copy of your data that we've pulled and indexed. Production-grade what-ifs don't happen in demo, so everything you see is real Kersey Mill data but in a sandbox. Right, can you see the screen?
- Gillian Woolnough NoneYep.
- Hannah Lowe NoneOkay, so on the left here are your data sources. We've connected your CRM, the ERP for inventory and production, the helpdesk, and we've indexed a few sample calls. In the middle is the query interface, the chat. Let me show you what you can actually do. Say Gillian wanted to know: which customers are complaining most, and are they also having delivery issues? Watch.
- Hannah Lowe NoneSo I type the question in natural language. The brain understands your schema, finds customers who raised complaints in the helpdesk, cross-references that with the ERP to see if they've also got delayed orders, and boom, answer in seconds.
- Gillian Woolnough NoneThat's, yeah, that's useful. Is it always that fast?
- Hannah Lowe NoneIn practice, yes. There can be pauses if the query is really complex or the dataset is huge, but for most operational questions: risk scoring, order status, customer health, you're looking at seconds to maybe ten seconds.
- Tom Ashdown NoneAnd this means Gillian's not writing SQL or asking IT for reports. She can just ask.
- Hannah Lowe NoneExactly. Gillian can ask it herself, anytime. No bottleneck. But Growth also includes the dashboards builder, so you can pin metrics that matter to you. Let me show you. I'm going to build a simple dashboard for customer health. Drag in customer name, drag in complaint count, drag in open orders, colour-code by risk level. Done. And now this updates every night when we refresh your data.
- Gillian Woolnough NoneCan other people see it?
- Hannah Lowe NoneYeah, you can share it with whoever you want. Publish it to a URL, embed it in your internal portal, you could give your sales team and customer service team the same view so everyone's working from the same numbers.
- Gillian Woolnough NoneThat would solve a lot of, people are always asking me 'is this customer at risk' and I'm checking four different systems.
- Hannah Lowe NoneYeah, dashboard fixes that. So to be precise, the brain indexes your data every night. By seven in the morning your local time, everything is fresh. So that customer health dashboard is always current.
- Tom Ashdown NoneAnd your data, everything stays in your Snowflake account.
- Hannah Lowe NoneRight. You own it, you control it, we don't see it. SOC 2 controls around our connectors, and we've got solid security documentation if your IT team wants to dive in.
- Gillian Woolnough NoneOkay. So the implementation, you said eight weeks?
- Hannah Lowe NoneRoughly. First two weeks we sit down with your team, understand your schema: which tables, which fields matter most, and design the connectors. Then we build them, test them, do a data health review with you. Third four weeks we're tuning, you're building dashboards, we're running training.
- Gillian Woolnough NoneWhat kind of training?
- Hannah Lowe NoneWe run through the interface: how to ask questions, how to build dashboards, best practices for queries that perform. We'll work with a small group from your team: customer service, maybe ops, and then they cascade it to anyone else who needs it.
- Tom Ashdown NoneAnd after we go live, we do quarterly check-ins to make sure you're getting value and to spot any new use cases.
- Gillian Woolnough NoneAll right. I think I've got what I need. This does what you said it would do.
- Tom Ashdown NoneBrilliant. So I'll write up a proposal with a timeline. If you want to hit summer, before the new product launch, we'd need to start in the next month or so. I'll send that over and we can talk numbers.
- Gillian Woolnough NonePerfect.
- Tom Ashdown NoneCheers. I'll be in touch within a couple of days.
Callsmade from