B-Brain
Kenmure Business Telecom logo

Kenmure Business Telecom - Onboarding Plan

Documentfinal

Kenmure Business Telecom logo Kenmure Business Telecom · onboarding_plan · final · 2025-08-30

Final onboarding plan prepared by Laura Penhaligon on 30 Aug 2025 for Kenmure Business Telecom's Enterprise tier. It sets four phases from mobilise to hand over, and quotes £104k contracted annual recurring revenue and 150 licensed users. It states no service levels.

What it says

What this says

Current to 13 Oct 26

Final onboarding plan prepared by Laura Penhaligon on 30 Aug 2025 for Kenmure Business Telecom's Enterprise tier. It sets four phases from mobilise to hand over, and quotes £104k contracted annual recurring revenue and 150 licensed users. It states no service levels.

What it is: a BB-Demo implementation plan for the Enterprise customer, covering mobilise, connect and load, adopt and hand over. It names Laura Penhaligon as implementation lead, Marcus Bell as customer success manager and Tom Ashdown as account owner.

Commits: the plan itself binds no one commercially. It says "The contracted terms are those in the executed order form. If anything in this plan differs from the order form, the order form wins."

Unusual: the snapshot gives a contract end of 27 Aug 2026, which is before the as-of date. The plan does not say whether a renewal followed, and it states no connector dates or service levels.

Not settled: the connector list, the executive sponsor and the first review date are left to be agreed. Adoption since 30 Aug 2025 is not shown here, and ownership may have changed since.

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

As found in this document

Current to 9 Oct 26
  • Date end27 Aug 2026Source: object_read:doc_156_008
  • Date start28 Aug 2025Source: object_read:doc_156_008
  • Price£104,500Source: object_read:doc_156_008
  • Licensed users150Source: object_read:doc_156_008
  • Contract end27 Aug 2026Source: object_read:doc_156_008
  • GovernanceLaura Penhaligon will give a short written update to the Kenmure project lead at the end of each phase.Laura Penhaligon will give a short written update to the Kenmure project lead at the end of each phase. · Source: object_read:doc_156_008

The document

Body

Onboarding Plan: Kenmure Business Telecom

Prepared by: Laura Penhaligon, Implementation Consultant, BB-Demo Date: 30 Aug 2025 Status: Final

Purpose

Kenmure Business Telecom joined BB-Demo on 28 Aug 2025 on the Enterprise tier. This plan sets out how we move from signature to a brain that the account management, provisioning and service desk teams use every day, so that each business customer's circuits, faults and bills can be seen together.

Contract snapshot

ItemDetail
CustomerKenmure Business Telecom, Glasgow
TierEnterprise
Licensed users150
Contracted annual recurring revenue£104k
Customer since28 Aug 2025
Contract end27 Aug 2026
Account ownerTom Ashdown
Customer success managerMarcus Bell
Implementation leadLaura Penhaligon

The contracted terms are those in the executed order form. If anything in this plan differs from the order form, the order form wins.

Starting position

Read the whole document (4,211 characters)

At the date of this plan only a couple of people are using the brain, which is expected at this stage. There are no open tickets and no overdue invoices. The aim of the plan is to grow from this small group to the wider teams the Enterprise licence covers.

Phases

Phase one: mobilise

ActivityOwnerOutcome
Kick-off with the Kenmure sponsor and project leadLaura PenhaligonShared view of goals, teams and success measures
Confirm access to the Customer's Snowflake accountCustomer IT leadEnvironment ready for the build
Agree the connector list and order of workLaura Penhaligon with Customer project leadPrioritised source systems
Start security review supportLaura PenhaligonQuestions answered and evidence shared

Phase two: connect and load

ActivityOwnerOutcome
Connect the first source systemsLaura PenhaligonRecords flowing into the brain
Check the nightly refreshLaura PenhaligonData fresh at the start of each business day
Validate records with the service desk and provisioning leadsCustomer team leadsConfirmation that circuits, faults and bills line up
Connect the remaining systemsLaura PenhaligonAll agreed connectors live

Phase three: adopt

ActivityOwnerOutcome
Train the account management teamLaura PenhaligonConfident everyday users
Train the provisioning and service desk teamsLaura PenhaligonQuestions asked in the brain, not by hand
Set up single sign-on and user provisioningCustomer IT lead with Laura PenhaligonControlled access for the wider user base
Build the first dashboardsCustomer project leadViews the teams ask for

Phase four: hand over

ActivityOwnerOutcome
Review usage against the licensed usersMarcus BellClear picture of adoption
Hand over from implementation to customer successLaura Penhaligon and Marcus BellOngoing support and review rhythm agreed
Confirm the executive sponsor and first review dateTom AshdownNamed sponsor and a date in the diary

Risks and dependencies

  • Source system access: connectors cannot go live until the Customer's IT team grants access. We will chase this early.
  • Changes to source systems: if Kenmure changes a system mid-project, a connector may need rework. Please tell us before it happens.
  • Key people: adoption depends on a named project lead and team leads being available for validation.
  • Security review: answers need a prompt turnaround from both sides to keep the build on track.

Success measures

  • All agreed connectors loading records and refreshing each night.
  • Growing numbers of active users across the three teams, working towards the licensed 150.
  • Questions asked in the brain by more than one team, not just the first few users.
  • No open priority issues at hand-over.

Governance

Laura Penhaligon will give a short written update to the Kenmure project lead at the end of each phase. Tom Ashdown remains the commercial contact, and Marcus Bell takes over day-to-day account care once implementation is complete.

Documentsmade from

Unusual terms

Current to 9 Oct 26
  • Contract end 27 Aug 2026 already passed
  • Order form prevails over the plan

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