What was said
What this says
Current to 13 Oct 26Demo on 30 Jan 2026 of the brain on Kaltenbrunn Medizintechnik's own sample data. The customer tested ticket-to-device matching, refresh and access. Decision is planned around 17 Apr 2026, with a £155k total deal value to be proposed.
What happened: On 30 Jan 2026 Hannah Lowe demoed the brain on a sample of Kaltenbrunn Medizintechnik's own data to Christina Möller and Kai Petersen. Kai's main concern was how device records and service tickets are joined.
Customer view: Hannah said plainly that older tickets without a serial were the weakest match. Christina called that honest, and the team asked for the list in writing.
Commercial: Matteo Ricci said the decision is planned around 17 Apr 2026 and that a written proposal with a total deal value of £155k would follow. That is a proposed total, not a contracted price.
Watch: The group access list, the EU region wording and the IT security questionnaire were all left open. Each could slow the path to April.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Hannah Lowe sends the list of unmatched and probable tickets and the written EU region confirmation.
- Kai Petersen sends the group access list to Hannah and copies Matteo Ricci.
- Matteo Ricci brings the written commercial proposal once the open items are answered.
Risks
Current to 9 Oct 26- Older tickets without a serial matched only on hospital and date, so they are weak evidence without a human check.
- The group access list is not yet walked through, so Enterprise SSO and SCIM coverage is unconfirmed.
- The security review and EU region confirmation could sit on the critical path to the April decision.
Opportunities
Current to 9 Oct 26- Enterprise fit looks strong: SSO, SCIM, EU residency and security review support all matched the customer's questions.
- Kai and Christina engaged closely with matching and refresh, which suggests a real use case in field service.
Transcript
- Hannah Lowe NoneHello, can you all hear me? Christina, Kai, good afternoon.
- Christina Möller NoneGood afternoon Hannah. Yes, I hear you. Kai is joining now, he had another meeting that ran over.
- Kai Petersen NoneHello, sorry, here I am. Is my microphone working? Good. Hello everyone.
- Matteo Ricci NoneGood afternoon, Kai, a pleasure to meet you properly. Christina has told us a lot about you. Let me restate the plan in one sentence: today is the demo on a sample of your own data, and the decision is planned around 17 April 2026, so this is the session where you can push hardest.
- Christina Möller NoneGood. My agenda is in the invitation. First the sample data and what Kai found, then the admin questions, then the hospital view with real devices.
- Hannah Lowe NoneThat works. Kai, can I start with you? What do you most need to know today, from the admin side?
- Kai Petersen NoneMainly how the sources are joined. Our device records and the service tickets use different identifiers, so I am curious how the brain decides that this ticket belongs to this device. That was always the manual work for me.
- Hannah Lowe NoneGood, that is the right place to look. Let me share the screen. This is the sample you sent us, loaded into a test area. I will show the matching rules first, and then the cases where it was not sure.
- Christina Möller NonePlease, which device, which hospital. I want to see a real case.
- Hannah Lowe NoneYes. Here is one device. You see the serial number from the device records, and the three tickets that were matched to it. Beside each match, the reason: same serial in the ticket text, or same hospital and same date, and so on.
- Kai Petersen NoneMm. And this one, it has a lower confidence, the second ticket. What does it do with those?
- Hannah Lowe NoneThe short answer is that it shows them separately, marked as probable. The longer answer is that you, as admin, can confirm or reject a match, and the brain remembers your decision for the next refresh.
- Kai Petersen NoneOkay, that is useful. So I would not need to fix it in the source.
- Hannah Lowe NoneNot for the brain, no. But I would still recommend fixing recurring patterns in the source, otherwise you keep confirming the same thing every week.
- Christina Möller NoneKai, I think this is the same as we discussed. Some of our older tickets have no serial at all.
- Kai Petersen NoneYes, quite a few. Those would be probable at best, I guess.
- Hannah Lowe NoneExactly. I would rather say that clearly now: in the sample, the older tickets without a serial were the weakest part. They matched on hospital and date only, so I would not treat them as evidence in a complaint without a human check.
- Christina Möller NoneThat is honest, thank you. What is the source of that statement, did you count them?
- Hannah Lowe NoneI did, and I will put the list in writing so Kai can check it against his own records. I do not want you to rely on my impression.
- Matteo Ricci NoneLet me confirm that in writing as well, Christina. Hannah sends the list of unmatched and probable tickets, and Kai tells us whether the pattern is what he expected.
- Kai Petersen NoneYes, I can do that. It would take me a few days.
- Hannah Lowe NoneGood. Now the second part, the refresh. The brain updates overnight, and for every tier the nightly refresh should be complete by 07:00 in your local time on business days. In the admin page you can see the last refresh per source.
- Kai Petersen NoneAnd if one source fails, for example the service system is down at night?
- Hannah Lowe NoneThen that source shows as stale, with the time of its last good load, and the answers that depend on it say so. The brain does not hide it. Everything else continues to refresh.
- Christina Möller NoneGood. For the engineers it must be visible. If the data is a day old, he must know.
- Hannah Lowe NoneIt is shown on the answer itself, next to the source tag, not just in the admin page.
- Kai Petersen NoneNow access. We have different groups, field service, key accounts, complaints. Not everyone should see the contract prices, for example.
- Hannah Lowe NoneEnterprise includes single sign-on and SCIM, so groups come from your identity system, and you set which group sees which sources and which page types. I can show the setting, but I will not claim it covers every case you might have until we have walked through your list.
- Christina Möller NoneWe will make a list. Kai, please write which group should see what. Then we agree it.
- Kai Petersen NoneWill do. I will send it to Hannah directly, if that is fine.
- Hannah Lowe NoneThat is fine. Send it to me and copy Matteo.
- Matteo Ricci NoneWhile we are on Enterprise, a word on the security review. It is part of the implementation support, so your IT and quality colleagues can send questionnaires and Hannah answers them. I would rather that started early, so it does not sit on the critical path to April.
- Christina Möller NoneYes. That is also what I thought. I will ask IT to send theirs before the next meeting.
- Kai Petersen NoneOne more thing, the EU region. Last time Christina mentioned residency. Is the sample I sent held anywhere outside the EU?
- Hannah Lowe NoneTo be precise, the test area is in the EU region we agreed for the demo. I will confirm that in the written follow-up so you have it for your records, and I will check the exact wording with my colleague before I send it.
- Christina Möller NoneGood. Let us agree the next step. What do you need from us, and when?
- Matteo Ricci NoneFrom you, the group list from Kai and the IT questionnaire. From us, the list of probable matches, the architecture note and the confirmation on region. And then I will bring the commercial proposal to you in writing, with the total deal value of £155,000 laid out, so your management can see what is in it.
- Christina Möller NoneYes. I will send the minutes tonight. Please check the actions. Thank you, Hannah, Matteo. Kai, thank you as well.
- Kai Petersen NoneThanks, that was helpful. Bye.
- Hannah Lowe NoneThanks, all. Goodbye.