B-Brain
Kaltenbrunn Medizintechnik logo

Kaltenbrunn Medizintechnik - Onboarding Plan

Documentfinal

Kaltenbrunn Medizintechnik logo Kaltenbrunn Medizintechnik · onboarding_plan · final · 2026-05-10

Final version 1 onboarding plan, dated 10 May 2026, for bringing the company brain live on the Enterprise tier with EU data. It states a subscription from 1 May 2026 to 30 Apr 2027, 150 licensed users and £125k contracted annual recurring revenue.

What it says

What this says

Current to 13 Oct 26

Final version 1 onboarding plan, dated 10 May 2026, for bringing the company brain live on the Enterprise tier with EU data. It states a subscription from 1 May 2026 to 30 Apr 2027, 150 licensed users and £125k contracted annual recurring revenue.

What it is: a five-phase plan prepared by Laura Penhaligon, covering kick-off, security review and connectors, validation, training and handover to customer success. It names Matteo Ricci as account owner and Elena Novak as customer success manager.

Commits: it sets no service levels or connector dates itself. It says "The executed order form remains the reference for price, connectors and service levels."

Unusual: the contract table gives "Annual recurring revenue (contracted)" of £125k, a figure the plan quotes from the order form and which cannot be checked here.

Not settled: the plan names no connectors, no go-live dates for each phase and no customer individuals. It flags that "only a small number of people are active at the start" against 150 licensed users.

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

As found in this document

Current to 9 Oct 26
  • Date end30 Apr 2027Source: object_read:doc_161_008
  • Date start1 May 2026Source: object_read:doc_161_008
  • Licensed users150Source: object_read:doc_161_008
  • Subscription start1 May 2026Source: object_read:doc_161_008
  • Subscription end30 Apr 2027Source: object_read:doc_161_008
  • Data regionEU regionSource: object_read:doc_161_008

The document

Body

Kaltenbrunn Medizintechnik - Onboarding Plan

Status: Final, version 1 Prepared by: Laura Penhaligon, Implementation Consultant, BB-Demo Date: 10 May 2026

Purpose

This plan sets out how BB-Demo and Kaltenbrunn Medizintechnik will bring the company brain live on the Enterprise tier. Kaltenbrunn makes patient-monitoring equipment for hospitals in Germany, Austria and the Nordics. The aim is that field service, key accounts and complaints see each hospital's devices, service tickets and contracts together, with the data held in an EU region.

Contract position

ItemDetail
TierEnterprise
Subscription start1 May 2026
Subscription end30 Apr 2027
Annual recurring revenue (contracted)£125k
Licensed users150
BB-Demo account ownerMatteo Ricci
BB-Demo customer success managerElena Novak
Implementation leadLaura Penhaligon

The executed order form remains the reference for price, connectors and service levels. If anything in this plan appears to differ from it, the order form decides.

Goals

Read the whole document (4,860 characters)
  • Connect the sources that hold device, service ticket and contract information so that one question can span all three.
  • Complete the customer's security review with BB-Demo's support.
  • Give field service, key accounts and complaints a working view they use in their daily routine.
  • Hand over to customer success with a clear picture of usage and next steps.

Phases and owners

Phase one: kick-off and access

ActivityOwner
Confirm project team and decision makers on both sidesLaura Penhaligon with the Kaltenbrunn project sponsor
Agree the working rhythm and a weekly check-inLaura Penhaligon
Confirm the EU data region and the Snowflake environmentKaltenbrunn IT lead with Laura Penhaligon
Grant access to the source systemsKaltenbrunn system owners

Milestone: access confirmed and the project team named.

Phase two: security review and connectors

ActivityOwner
Answer the security questionnaire and supply supporting evidenceLaura Penhaligon with Matteo Ricci
Review findings with Kaltenbrunn's information security contactKaltenbrunn information security
Configure the connectors named in the order form, in priority orderLaura Penhaligon
Confirm each connector is loading recordsLaura Penhaligon with Kaltenbrunn system owners

Milestone: security review closed and the agreed connectors loading on the nightly refresh.

Phase three: validation

ActivityOwner
Check a sample of hospitals, devices and contracts against the source systemsKaltenbrunn key accounts and field service leads
Resolve mismatches in account naming and contract referencesLaura Penhaligon
Agree the first set of pages and questions each team will useLaura Penhaligon with team leads

Milestone: the customer confirms the data is accurate enough to rely on.

Phase four: training and rollout

ActivityOwner
Run short sessions for field service, key accounts and complaintsLaura Penhaligon
Set up users, including single sign-on and provisioning with the customer's IT teamKaltenbrunn IT lead
Name an internal champion in each teamKaltenbrunn project sponsor

Milestone: each team has trained users asking real questions.

Phase five: handover

ActivityOwner
Review usage, open points and any connector requestsLaura Penhaligon with Elena Novak
Transfer ownership of the relationship to customer successElena Novak
Agree the first review date with KaltenbrunnElena Novak

Milestone: handover completed and the first review booked.

Risks and watch points

  • Adoption: only a small number of people are active at the start. The licensed allowance is far larger, so rollout to each team is the main measure of success.
  • Connector readiness: a source system changing during the project can stop a connector loading. System owners should tell Laura Penhaligon before any change.
  • Security review: delay in answers from either side moves every later phase.
  • Key person: each team should have more than one confident user so that value does not rest on a single champion.

Communication

  • A weekly check-in between Laura Penhaligon and the Kaltenbrunn project sponsor.
  • Matteo Ricci is the contact for any commercial question.
  • Elena Novak joins from the training phase so that the handover is not a surprise.

Success measures

  • Agreed connectors loading every business day.
  • Teams asking questions on their own, across more than one person in each team.
  • The security review closed without open items.
  • The customer able to say what the brain is worth to field service, key accounts and complaints.
Documentsmade from

Unusual terms

Current to 9 Oct 26
  • Contracted annual recurring revenue of £125,000 quoted in plan
  • Order form overrides plan on any difference

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
Organisations225
People at customers862
BB-Demo staff58
Calls1,995
Email threads3,013
Support tickets1,159
Documents1,218
Deals315
Invoices285
Events49
News items119

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