What was said
What this says
Current to 11 Oct 26Claire Chevalier, Head of Client Services, saw a demo on her own data patterns and said she was ready to move ahead. Tom Ashdown is aiming for a mid-July signature and an eight-week implementation, with the proposal as the next step.
What happened: Hannah Lowe demoed cross-channel sales queries, dashboards and customer service lookups over POS, e-commerce, inventory and CRM data. Claire asked about security, adding a loyalty platform later and the time commitment.
Customer view: Claire said "I think we're interested" and later asked for everything to be sent so it could be sorted. September go-live suits her because it leaves time to stabilise before the autumn trading season.
Commercial: The evidence does not show a tier, price or user count. Eight weeks matches the Growth implementation length in the offering map, but the call does not name a tier.
Watch: Claire is the only customer voice on the call, and nobody from finance or IT was present. The call does not show who signs.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Tom Ashdown sends the proposal and moves to the order form aiming for mid-July signature.
- Hannah Lowe sends the written summary with architecture diagram and connector specs.
Risks
Current to 9 Oct 26- No finance or IT participant was on the call, so the signing route is not visible.
- The mid-July signature target depends on Claire's review of the proposal.
Opportunities
Current to 9 Oct 26- Customer service order-history lookups give a second team a clear use beyond leadership reporting.
- A future loyalty platform would be an additional connector.
Transcript
- Tom Ashdown NoneClaire, great to see you again. Hannah's our Solutions Engineer, she's built a demo using your data patterns, so you can see exactly how this works.
- Hannah Lowe NoneHi Claire. I've modelled your POS, e-commerce, inventory, and CRM. Let me show you how the brain pulls from all of it.
- Claire Chevalier NonePerfect. I'm curious to see it in action.
- Hannah Lowe NoneRight. So every night at ten p.m., we refresh. We pull sales data from your POS and e-commerce, we pull inventory levels, we pull customer data from your CRM. All of that gets indexed and lives in your Snowflake. By ten-thirty, everything is current and searchable.
- Claire Chevalier NoneAnd then people can query it?
- Hannah Lowe NoneExactly. So here's the interface. I've got a query here: 'What were my top five products by sales value in the last seven days across all channels?' The brain runs that against your POS and e-commerce data and gives you the answer instantly. See? Top to bottom, stores and online combined.
- Claire Chevalier NoneThat's, that's powerful. How long would that normally take?
- Hannah Lowe NoneToday, probably an hour or more, pulling from two systems and stitching it together. Here, ten seconds.
- Tom Ashdown NoneAnd you can drill down. If you want to see that data by store, by region, by product category, all just filters on the same query.
- Hannah Lowe NoneRight. And then there's the dashboards. If you ask the same question every morning, you build a dashboard. It runs at ten p.m. refresh and you've got your answer ready for the morning leadership meeting.
- Claire Chevalier NoneCan customer service use it too?
- Hannah Lowe NoneAbsolutely. A customer calls, says 'What did I order last time?' Your person asks the brain 'Show me this customer's order history across online and stores.' It pulls from the CRM and both transaction systems. They answer the customer without putting them on hold.
- Claire Chevalier NoneAnd the data is secure?
- Hannah Lowe NoneAll of it's encrypted at rest and in transit. Only people you authorize can access the brain. You control the permissions: so customer service might see customer and order data, but not inventory cost data.
- Claire Chevalier NoneGood. What if we want to add another system later? Like if we bring on a new loyalty platform?
- Hannah Lowe NoneWe build a new connector. Your existing queries keep working because they're built on your data model. The new system just plugs in.
- Tom Ashdown NoneAnd during implementation, what does that look like?
- Hannah Lowe NoneEight weeks. I work with you week by week: we configure each connector, we review your data architecture, we make sure the queries work how you expect them to. By week eight, you're trained and live.
- Claire Chevalier NoneHow many hours a week are we talking?
- Hannah Lowe NoneTwo or three from your IT person for connectivity. Maybe an hour a week from your operations or customer service team to help us understand your business. Not a huge commitment.
- Claire Chevalier NoneOkay. And Tom, when could we go live?
- Tom Ashdown NoneIf you sign by mid-July, we kick off right after, eight weeks puts you at September. That works?
- Claire Chevalier NoneSeptember works. That gives us the time to stabilise before the autumn trading season kicks in. I think we're interested.
- Tom Ashdown NoneBrilliant. So next is the proposal. You review it, any questions, let me know. If you're happy, we move to the order form and we're aiming for mid-July signature.
- Hannah Lowe NoneI'll also put together a written summary: architecture diagram, connector specs, all the technical detail your IT team will need.
- Claire Chevalier NoneThat'll be helpful. All right, I think we're ready to move ahead. Send me everything and we'll get this sorted.
- Tom Ashdown NoneWill do. Cheers, Claire. Really looking forward to this.