Kesselfeld Software / BG-Demo – Demo
Callcompleted
Kesselfeld Software · 4 Nov 2025 13:00
Matteo Ricci and Anya Petrova demoed the brain on anonymised data to Julia Hartmann and Tim Schröder. Julia was impressed. A proposal at £60k for the first year was promised the same day, subject to Florian signing off.
What was said
What this says
As at Fri 9 Oct 2026Matteo Ricci and Anya Petrova demoed the brain on anonymised data to Julia Hartmann and Tim Schröder. Julia was impressed. A proposal at £60k for the first year was promised the same day, subject to Florian signing off.
What happened: Anya ran live queries across Salesforce, helpdesk and call data. Julia and Tim asked about refresh timing, connector failures, support, training, accuracy and data security.
Customer view: Julia said she was quite impressed. Tim said data privacy matters because their own customers care about it.
Commercial: Matteo quoted £60k all-in for the first year including implementation, with eight weeks to live from order form signature. Florian must approve commercial terms, and a security review follows the proposal.
Watch: Anya mentioned four systems in the connector diagram but showed three in the demo, so connector scope needs confirming. The evidence does not show Florian's view.
Themes
As at Fri 9 Oct 2026Theme
Demo and proposal stage
Importance
neutral
Sentiment
positive
Voice
champion
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- Matteo Ricci to send the proposal on 4 Nov 2025 and follow up the week after.
- Anya Petrova to send the connector architecture diagram and demo FAQs.
- Matteo Ricci to confirm the connector scope, three systems shown against four in the diagram.
Risks
As at Fri 9 Oct 2026- Florian has not yet seen the commercial terms and must sign off before any order form.
- A security review with the customer's IT team sits between proposal and order form.
Opportunities
As at Fri 9 Oct 2026- Data stays in the customer's Snowflake account, which answers Tim's privacy concern.
- Julia asked about dashboards and training, which suggests interest in wider team adoption.
Transcript
Matteo RicciHi Julia, Tim, great to see you. I'm Matteo, and this is Anya, one of our solutions engineers. How are you both doing today?
Julia HartmannHi Matteo, hi Anya. Doing well, thanks. We're excited to see what this looks like on our data.
Tim SchröderYeah, same. I've been curious about how the connectors would work with our systems.
Anya PetrovaBrilliant. So what I've done is build a sandbox of the brain using some anonymised data you sent over, Salesforce customer records, helpdesk tickets, and call data. This is exactly what you'd see in production. Let me share my screen and walk you through it.- Anya PetrovaSo this is the brain interface. On the left you've got the chat, on the right a page builder where your team can save frequently-used queries. Let me show you the chat in action. 'Show me all customers with support tickets opened in the last week and their call volume.'
- Anya PetrovaAnd there we go. The brain's pulled all customers matching that criteria and given you a table. Customer name from Salesforce, number of open tickets from the helpdesk, and their call volume from the call system. All in one view.
- Julia HartmannWow. So that's pulling from three systems?
- Anya PetrovaExactly three. And you don't have to know SQL or anything, you just ask in English. Let me do another query. 'Of these customers, which ones haven't been on a call in two weeks?'
- Anya PetrovaThe brain understands the context and filters that list down. Now you've got five customers who have open tickets but zero calls in two weeks. That's probably a red flag.
- Tim SchröderCan you save that? Like, make it a dashboard or something?
- Anya PetrovaYeah, you can do it two ways. Create a custom dashboard: basically no code, just drag and drop. Or your team can ask that question every time. Most teams do a mix.
- Julia HartmannAnd the data refresh? How often does this update?
- Anya PetrovaEvery night. Anything that happened in your systems during the day: new tickets, calls, whatever, it all gets pulled in the nightly refresh and is live by 07:00 the next morning.
- Tim SchröderWhat if the helpdesk system goes down or the data doesn't sync properly?
- Anya PetrovaWe monitor all the connectors. If a sync fails, we'll let you know immediately and work to fix it. Typically it's a permissions issue or a system outage on their end.
- Julia HartmannAnd support, if we have questions about how to use it or something isn't working?
- Matteo RicciDuring implementation, our team is your main contact. Once you're live, you get a customer success manager. They do quarterly business reviews with you and if there's a technical issue, they escalate to us. First response time on Growth is within a business hour.
- Tim SchröderIs there training involved, or do you think the interface is intuitive enough?
- Anya PetrovaWe do training during implementation. Usually a couple of hours spread over a week, I'll walk your team through the interface, show them how to ask good questions. Most teams pick it up pretty quickly.
- Julia HartmannIs there risk of the brain making stuff up or getting confused?
- Anya PetrovaThe brain is built to search and summarise your actual data. It can't make anything up, it's only returning results from what's in your systems. If it doesn't understand a query, it'll say so.
- Matteo RicciThe key thing is your data never leaves your Snowflake account. We run inside your infrastructure. That's why there's no risk of data leakage, and security is tight.
- Tim SchröderYeah, that's actually really important for us. Our customers care about data privacy.
- Matteo RicciExactly. And if you've got specific compliance needs, GDPR, whatever, we can work around those. But the baseline is your data, your infrastructure, your control.
- Julia HartmannOkay, I'm quite impressed. So what happens next?
- Matteo RicciIf you'd like to move forward, we'd send you a proposal with the scope, timeline, and pricing. That comes to £59,500 all-in for the first year including implementation. You'd have a two-week window to review it, ask questions, and then we'd move into a security review with your IT team. Once that's cleared, we'd do an order form and we'd be off to the races.
- Julia HartmannOkay. And timeline, how quickly could we get live?
- Matteo RicciEight weeks from order form signature. So if you sign in mid-November, you'd be live just after the new year.
- Julia HartmannThat's tight but doable. Florian would need to sign off on the commercial terms, obviously.
- Matteo RicciOf course. I'll send the proposal today, just PDF, nothing fancy. Review it, get Florian's thoughts, and then we can schedule a call to talk through any questions.
- Tim SchröderYeah, that works for me.
- Matteo RicciBrilliant. I'll get that proposal over today and Anya can send some additional technical documentation, diagrams of how the connectors work, that sort of thing.
- Julia HartmannThat would be helpful, actually.
- Anya PetrovaWill do. I'll put together a connector architecture diagram showing how your four systems map into the brain, and some FAQs from the demo.
- Matteo RicciPerfect. So proposal today, technical docs from Anya, and then we'll follow up next week to check in. Sound good?
- Julia HartmannYep, sounds great. Thanks for the demo.
- Matteo RicciCheers, Julia. Thanks Tim, Anya. We'll talk soon.
Callsmade from