Stourleigh Logistics / BB-Demo – Demo
Callcompleted
Stourleigh Logistics: documents · 2026-05-05 14:15
On 5 May 2026 Neil Ashby and Kirsty Hollis saw a demo on Stourleigh test CRM and despatch data. They liked it; BB-Demo will send architecture documents and a pricing proposal. Dashboards were described as included on Starter.
What was said
What this says
Current to 11 Oct 26On 5 May 2026 Neil Ashby and Kirsty Hollis saw a demo on Stourleigh test CRM and despatch data. They liked it; BB-Demo will send architecture documents and a pricing proposal. Dashboards were described as included on Starter.
What happened: Sophie Ling and Theo Gallagher demoed on-time delivery by customer from Salesforce and despatch data. Neil Ashby, Head of Revenue Operations, and Kirsty Hollis, Sales Manager, asked about scripting, dashboards, extra systems and support.
Customer view: Neil said delivery reporting is pulled manually and takes ages. He closed with approval and Kirsty said she could see how the team would use it.
Commercial: Sophie framed Starter with four connectors, two left after Salesforce and despatch, and a four business hour response target. Theo said the brain includes a dashboard builder, yet Starter covers pages, chat and search.
Watch: Correct the dashboard expectation in the proposal, or the customer may assume it is in scope.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Sophie Ling to send the architecture documentation and a pricing proposal.
- Sophie Ling to set up a follow-up call with Neil Ashby to talk terms.
Risks
Current to 9 Oct 26- Dashboards were described as included while the Starter tier covers pages, chat and search, so expectations may need correcting.
- The finance connector was described as taking a couple of weeks, which could slip against customer expectations.
Opportunities
Current to 9 Oct 26- A finance system as a later connector would use one of the two spare Starter slots.
- Interest in a live daily delivery dashboard could support a Growth conversation.
Transcript
Sophie Ling NoneAfternoon everyone, thanks for joining. Neil, Kirsty, good to see you. Theo and I have prepared a quick demo of how the brain works. Theo, shall we kick off?
Theo Gallagher NoneThanks Sophie. Hi Neil, Kirsty. What we've done is load some of your test CRM and despatch data so you can see a real example. Neil, what would be most valuable to see today?
Neil Ashby NoneWe're keen to see if it can help us understand delivery performance by customer and region. That's something we pull manually right now and it takes ages.- Theo Gallagher NonePerfect. So I'll ask the brain a natural question and show you what it returns. Let me type: 'Show me on-time delivery rate by customer, last month.'
- Theo Gallagher NoneSo it's processed that and come back with a table. You've got customer names, number of deliveries, on-time count, and the percentage. This is from your Salesforce CRM and despatch system, pulled together in seconds.
Kirsty Hollis NoneThat's useful. Can I ask it things like 'which customers had the most delays' or do we have to script these questions?- Theo Gallagher NoneNo scripting needed. You just ask. Watch...'Which five customers had the most late deliveries in recent activity?' And there you are.
- Sophie Ling NoneAnd the data refreshes nightly, so if a delivery is marked complete in the despatch system today, it's in the brain by tomorrow morning.
- Neil Ashby NoneHow does this compare to just pulling reports from Salesforce?
- Theo Gallagher NoneThe short answer is speed and scope. In Salesforce you build a report, and you're working with just that system. Here, you're asking across all your data, CRM, despatch, finance, calls, in one go. The longer answer is: you don't need to know SQL or report-building syntax. You just ask a question.
- Kirsty Hollis NoneCould we build dashboards? Like a live view of daily delivery performance?
- Theo Gallagher NoneYes. The brain includes a dashboard builder. You'd design a dashboard: maybe showing on-time percentage, number of orders, top delays, and it refreshes nightly. No code required.
- Neil Ashby NoneWhat if we want to add another system later, like our finance software?
- Theo Gallagher NoneYou'd tell us, we'd scope the connector: usually takes a couple of weeks: and once it's built and tested, it'd be live and feeding data. Finance, HR, whatever you need.
- Sophie Ling NoneAnd Starter includes four connectors. You're starting with Salesforce and despatch, so you'd have two slots left for later.
- Kirsty Hollis NoneHow do we get support if something goes wrong?
- Theo Gallagher NoneYou'd have a support channel with us. On Starter, the response target is four business hours. So if a connector stops syncing or you spot bad data, you'd log a ticket and we'd get back to you within four hours during business days.
- Neil Ashby NoneLooks good to me. Anything else, Kirsty?
- Kirsty Hollis NoneI think that covers it. I can see how the team would use this.
- Sophie Ling NoneGreat. So next step is we'll send you some documentation on the architecture and a pricing proposal. You have a look, let us know if you have questions, and we'll set up a follow-up call to talk terms.
- Neil Ashby NoneSounds good. Thanks both.