Kadewerk Software / BG-Demo – Demo
Callcompleted
Kadewerk Software · 8 May 2025 12:45
Sanne de Wit and Yara El Idrissi saw the brain run on support-ticket data and asked about connectors, build time and data access. A proposal and a mid-June follow-up call were agreed. No decision was made.
What was said
What this says
As at Fri 9 Oct 2026Sanne de Wit and Yara El Idrissi saw the brain run on support-ticket data and asked about connectors, build time and data access. A proposal and a mid-June follow-up call were agreed. No decision was made.
What happened: Hannah Lowe showed a search over tickets and usage data. Yara said her team currently exports tickets to a spreadsheet and counts by hand.
Customer view: Sanne called the result quite good and asked about exports, the crew-scheduling system and data access. Yara asked what happens beyond four connectors.
Commercial: Lewis Kerr quoted 25,500 all-in for four weeks of implementation and a year on Starter, with four connectors. Extra connectors would be an add-on.
Watch: No decision was made and no finance voice was on the call. The follow-up is for mid-June, after Lewis sends the proposal.
Themes
As at Fri 9 Oct 2026Theme
Starter demo, ticket analytics
Importance
neutral
Sentiment
positive
Voice
decision-maker
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- Lewis Kerr to send the proposal with pricing and timeline by the end of that week.
- Lewis Kerr to hold the follow-up call with Sanne and Yara in mid-June.
Risks
As at Fri 9 Oct 2026- The four-connector Starter limit is already fully used by the planned sources, so any extra source costs more.
- No decision was made and no finance voice was present, so the budget route is unknown.
Opportunities
As at Fri 9 Oct 2026- Extra connectors as an add-on, or a move to Growth, if Kadewerk wants more sources.
- Hours saved on manual ticket counts give a clear value case for Yara's team.
Transcript
Lewis KerrRight, good afternoon. Thanks for taking the time. Hannah here is our Solutions Engineer, she's done a lot of crew-scheduling integrations for other customers, so she'll be walking you through the demo. Sanne, Yara, anything you need to know beforehand?
Sanne de WitNo, we're ready. Let's see what it can do.
Hannah LoweGreat. So, the short answer is, we'll walk through the brain running on your actual support-ticket data and some dummy crew-scheduling data. The longer answer is: what we really want to show you is how you can ask one question and get answers from tickets, usage data, and anything else you plug in, all at once. Does that sound like what you wanted to see?
Yara El IdrissiYeah. Right now we export tickets to a spreadsheet and do manual counts. So if I want to know, say, how many technical complaints are coming from customers who haven't logged in in three weeks, that's, I don't know, an hour of work.- Hannah LoweOkay. So that's actually a perfect example. In the brain, that's a one-line question. Let me show you. So here, this is our search interface. I'm going to type a query.
- Hannah LoweI'm typing: 'Technical complaints from customers inactive for three weeks.' And I'm going to hit search.
- Hannah LoweRight, so in about two seconds: see, the brain's come back with seven tickets that match that, with the customer names, the dates, the complaint text, all of it. If this was live with your data, this would be real. And you could drill into any of these, read the full ticket, see the usage history for that customer, all from one place.
- Sanne de WitThat's quite good, actually. What if we wanted to export that?
- Hannah LoweYou can export as CSV, send it to Slack, or just screenshot it. Whatever works for you.
- Lewis KerrThe idea is, it saves Yara hours. She can run that search in seconds, any time.
- Yara El IdrissiRight. And what data do you need from us to make this work?
- Hannah LoweYour support-ticket system, Zendesk, I think? and your product usage data. We'd also want your feature-request or bug-report tool if you've got one separate. That's four connectors: and on Starter, your limit is four, which is perfect for you.
- Sanne de WitWhat about the crew-scheduling system? That's our main product. Can you read that?
- Hannah LoweYes. That would be one of the four. So you'd have Zendesk for support, your usage data, your crew-scheduling system, and one more: maybe your CRM, or your feedback tool. It's your choice.
- Yara El IdrissiAnd how long until we'd see data in the system?
- Hannah LoweFor Starter, the implementation is four weeks. We'd start the day after you sign. First two weeks, we're building the connectors, testing them with your data: live data, in your Snowflake account, nobody else sees it. Weeks three and four, we do any tweaks, you run your own tests, and we hand it over ready to go.
- Lewis KerrAnd the cost for all of that is 25,500, all-in. Four weeks, the four connectors, all the support during the build, and then a year of the brain on Starter.
- Sanne de WitOkay. And it runs in our Snowflake, so you don't have access to the data?
- Hannah LoweRight. It's inside your Snowflake account. We can see logs and some metadata to support you, but we never see the actual tickets or the usage data. It's all yours.
- Yara El IdrissiGood. And if we need more than four connectors later, what happens?
- Lewis KerrYou can add more connectors as an add-on. We'd build them in, same way, few days' work usually. But for now, four should get you going.
- Hannah LoweAny other questions about how it works?
- Sanne de WitI think that's clear. What happens next?
- Lewis KerrI'll send you a proposal with the pricing, the timeline, and everything we've talked about. Have a read, chat it through internally, and let's set up a follow-up call for mid-June. That way you've got a few weeks to have a think about it.
- Sanne de WitSounds good.
- Lewis KerrGreat. I'll get that over by end of week. Cheers, both.
Callsmade from