Ask
Lewis Kerr

Kadewerk Software / BB-Demo – Demo

Callcompleted

Kadewerk Software: documents logo Kadewerk Software: documents · 2025-05-08 12:45

Demo of the Starter tier to Kadewerk Software on 8 May 2025. Sanne de Wit wants helpdesk tickets and product usage in one layer, asked about Growth dashboards, and needs time to discuss with Maarten before signing.

What was said

What this says

Current to 11 Oct 26

Demo of the Starter tier to Kadewerk Software on 8 May 2025. Sanne de Wit wants helpdesk tickets and product usage in one layer, asked about Growth dashboards, and needs time to discuss with Maarten before signing.

What happened: Hannah Lowe and Lewis Kerr demoed the Starter tier to Sanne de Wit and Yara El Idrissi on 8 May 2025. Sanne's main ask was to see tickets and product usage together for one customer.

Customer view: Sanne said the search and query demo was exactly what they need. Yara raised architecture and encryption, then said she was satisfied.

Commercial: Sanne asked for custom dashboards, which are a Growth feature, and Yara asked whether an upgrade would be seamless. Sanne wants to be live before early July planning and needs time to discuss with Maarten, who was not on the call.

Watch: Hannah owes a written security summary, and the questionnaire runs during implementation. The evidence does not show an order form signed on this call.

AI · claude-sonnet-5-5 · 11 Oct 2026

Themes

Current to 9 Oct 26
Theme
Starter demo, tickets with usage
Importance
upsell
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Hannah Lowe to email the security summary on the evening of the call.
  • Lewis Kerr to send the order form for Sanne and Maarten to review.
  • Sanne de Wit to discuss with Maarten and come back with a timeline.

Risks

Current to 9 Oct 26
  • Maarten was not on the call and the decision waits on his review.
  • Sanne wants to be live before early July planning, so a late signature puts that date under pressure.
  • A written security summary is owed before Yara's satisfaction is on paper.

Opportunities

Current to 9 Oct 26
  • Sanne wants custom dashboards, which would move Kadewerk Software from Starter to Growth.
  • Four connectors are allowed on Starter, and Hannah suggested CRM and one more beyond helpdesk and product usage.

Transcript

  1. Hannah Lowe
    Hannah Lowe None
    Hi everyone, I'm Hannah, solutions engineer at BB-Demo. What I want to focus on today is how the brain would actually work for your team. Sanne, Yara, what would be most useful for me to show you?
  2. Sanne de Wit
    Sanne de Wit None
    Well, I'd like to see how you'd actually join our support tickets with usage data. Like, if someone logs a ticket, can we click on their account and see their usage history?
  3. Hannah Lowe
    Hannah Lowe None
    Yes, exactly that. So, to be precise, what we do is bring your helpdesk tickets and your product analytics into a single queryable layer. Once that's in place, you can search by customer name or ID and see their ticket history alongside their usage pattern: logins, features accessed, frequency, all of it. Let me walk through a concrete example.
  4. Hannah Lowe
    Hannah Lowe None
    Say a customer logs a ticket saying 'the scheduler is broken.' In the old way, you'd check your helpdesk, see the ticket, maybe email them some questions, wait for a reply. With the brain, you'd search their name, see the ticket, and instantly see: 'OK, they haven't logged in for three weeks, so they're probably not on the scheduler right now.' That changes the conversation.
  5. Yara El Idrissi
    Yara El Idrissi None
    And the data flows from our product directly? Like, you don't need us to export anything?
  6. Hannah Lowe
    Hannah Lowe None
    Correct. We set up a connector from your product's analytics API to the data warehouse. It syncs nightly, so the usage data is fresh every morning. And your helpdesk connector pulls your tickets the same way. Both run autonomously; you don't have to do anything.
  7. Yara El Idrissi
    Yara El Idrissi None
    OK. And in terms of architecture: is this all inside our network, or is data going out?
  8. Hannah Lowe
    Hannah Lowe None
    Good question. We set up a Snowflake account, that's a cloud data warehouse, that sits in your AWS region. Your data lives inside that account. We have read access to it so we can query your data and run the brain. You have full control and visibility. So no data's going out to some third-party service; it's all within your cloud footprint.
  9. Lewis Kerr
    Lewis Kerr None
    And from a security perspective, Yara, we go through a security review process with any new customer. We'd provide a questionnaire, evidence of our controls, and we can provide compliance documents. But for Starter, the review is streamlined, no months of back-and-forth.
  10. Hannah Lowe
    Hannah Lowe None
    Right. Now let me show you the actual interface. So when Sanne's team logs in, they see a search bar. They can type a customer name, and they get that customer's record: tickets, usage, all of it. Or they can ask bigger questions using our query tool. Like, 'show me all tickets from customers who dropped usage by more than fifty per cent in the last month.' And they get an answer back in seconds.
  11. Sanne de Wit
    Sanne de Wit None
    That's exactly what we need. And can we build custom dashboards? You mentioned that in the discovery.
  12. Hannah Lowe
    Hannah Lowe None
    Yes, but that's a Growth feature. Starter includes search and queries, but not the dashboard builder. Growth would let you and your team build and share dashboards, like 'top support drivers this month' or 'at-risk customers by usage trend.' That's something for later if you want to upgrade.
  13. Yara El Idrissi
    Yara El Idrissi None
    And if we upgrade, is it seamless?
  14. Hannah Lowe
    Hannah Lowe None
    Completely seamless. Your data and all your queries stay intact. You just get access to additional features.
  15. Lewis Kerr
    Lewis Kerr None
    And the upgrade itself is just a contract amendment. We'd handle it, and you'd have new features activated within a day.
  16. Sanne de Wit
    Sanne de Wit None
    OK. What about training? Will our team know how to use this, or do we need a lot of handholding?
  17. Hannah Lowe
    Hannah Lowe None
    During the four-week implementation, we do upfront training: we'd run through the interface with you, show you how to search, how to ask queries, common use cases. Then we're available for questions as your team gets comfortable. Most teams pick it up pretty quickly because it's just natural language, you're searching like you would Google, but for your data.
  18. Yara El Idrissi
    Yara El Idrissi None
    And what about ongoing: if we want to add connectors later, like email or something else?
  19. Hannah Lowe
    Hannah Lowe None
    You'd reach out to us, we'd discuss which connector you need and whether your tier includes it. Starter allows four connectors. You've got helpdesk and product usage; you could add CRM and one more. If you need more, that's an add-on, or you'd upgrade to Growth, which includes eight connectors.
  20. Sanne de Wit
    Sanne de Wit None
    Got it. I think this is really helpful. Lewis, what does the timeline look like if we move forward?
  21. Lewis Kerr
    Lewis Kerr None
    So we'd send you an order form, you'd sign, and we'd start the week after. Week one is setup and configuration, we're getting your connectors live, moving your data in. Weeks two and three, we're testing everything, training your team. Week four we're live and you're running with it. So four weeks end-to-end.
  22. Sanne de Wit
    Sanne de Wit None
    And you're confident in that timeline? Because we'd want to be live before our next quarterly planning cycle, which is early July.
  23. Hannah Lowe
    Hannah Lowe None
    Yes. If we start in early May, week four lands you right at the end of May. So you'd be live well before July, and you'd have time to shape your planning around what the brain tells you.
  24. Lewis Kerr
    Lewis Kerr None
    And I'll make sure we're available during those four weeks. Any questions from you, we're here.
  25. Yara El Idrissi
    Yara El Idrissi None
    I think that's good. One last thing, data security. You mentioned Snowflake, but what about encryption, access controls, that sort of thing?
  26. Hannah Lowe
    Hannah Lowe None
    Good question. Your data is encrypted in transit and at rest. Access is controlled by role, you define who can see what. We log all access for audit purposes. I'll put together a security summary and send it over, so you've got the details in writing. And we'll go through the questionnaire during implementation.
  27. Yara El Idrissi
    Yara El Idrissi None
    That's helpful. I'm satisfied.
  28. Lewis Kerr
    Lewis Kerr None
    Great. So next step: I'll send you the order form and the security summary Hannah mentioned. You review, sign, and let us know when you're ready to kick off. Sound good?
  29. Sanne de Wit
    Sanne de Wit None
    Yes. One question, what if we want to move ahead but need a bit of time to discuss with Maarten?
  30. Lewis Kerr
    Lewis Kerr None
    Totally fair. Take your time. I'd suggest getting it to him next week so we can kick off in early May if you're happy. But there's no pressure, let me know your timeline.
  31. Sanne de Wit
    Sanne de Wit None
    OK, I'll talk to him and we'll get back to you.
  32. Hannah Lowe
    Hannah Lowe None
    Perfect. Thanks, Sanne, Yara. I'll put that security summary in an email tonight, so you've got it to review.
  33. Lewis Kerr
    Lewis Kerr None
    And I'll follow up on the order form side. Cheers, everyone.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Brain · read-only