B-Brain
Hartside Student Living logo

Hartside Student Living - Onboarding Plan

Documentfinal

Hartside Student Living logo Hartside Student Living · onboarding_plan · final · 2026-04-14

Final onboarding plan prepared 14 Apr 2026 by Hamza Akhtar. It covers a Growth tier subscription for 40 users, running 10 Apr 2026 to 9 Apr 2027, at £45k contracted annual recurring revenue, over an eight-week implementation.

What it says

What this says

Current to 13 Oct 26

Final onboarding plan prepared 14 Apr 2026 by Hamza Akhtar. It covers a Growth tier subscription for 40 users, running 10 Apr 2026 to 9 Apr 2027, at £45k contracted annual recurring revenue, over an eight-week implementation.

What it is: an implementation plan from BB-Demo to the customer, not a contract. It sets phases, owners and milestones from kick-off to handover in week eight.

Commits: Hamza Akhtar owns kick-off, connecting sources, validation and training. Hollie Grieve takes handover and runs quarterly business reviews, and Lewis Kerr stays the contact for changes to users or connectors.

Asks of the customer: a named project lead, "At least two administrators", timely access and early warning of system changes. The risk table flags single-person usage and inconsistent nomination agreement formats.

Not settled: no service levels, connector delivery dates or invoicing terms are stated. The £45k is the figure this plan gives, and the executed order form decides the contracted price. The first renewal falls on 9 Apr 2027.

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

As found in this document

Current to 9 Oct 26
  • Date end9 Apr 2027Source: object_read:doc_158_009
  • Date renewal9 Apr 2027Source: object_read:doc_158_009
  • Date start10 Apr 2026Source: object_read:doc_158_009
  • Price£45,000Source: object_read:doc_158_009
  • Licensed users40Source: object_read:doc_158_009
  • Subscription term10 Apr 2026 to 9 Apr 2027Source: object_read:doc_158_009
  • HandoverWeek eight: confirm the nightly refresh is running, hand over to customer successWeek eight: confirm the nightly refresh is running, hand over to customer success · Source: object_read:doc_158_009
  • Quarterly business reviewsHollie Grieve will run quarterly business reviews, which are part of GrowthHollie Grieve will run quarterly business reviews, which are part of Growth · Source: object_read:doc_158_009

The document

Body

Hartside Student Living - Onboarding Plan

Status: Final. Prepared 14 Apr 2026 by Hamza Akhtar, Implementation Consultant, BB-Demo.

Purpose

Hartside Student Living operates purpose-built student accommodation across eight university cities. The company has bought the Growth tier so that its university partnerships team and its resident services team can see each university's nomination agreements, tickets and invoices together, in one place, inside the company's own Snowflake account.

This plan sets out how we get from signature to a brain that both teams use every day.

Account summary

ItemDetail
CustomerHartside Student Living, Nottingham
TierGrowth
Licensed users40
Contracted annual recurring revenue£45k
Subscription start10 Apr 2026
Subscription end9 Apr 2027
BB-Demo account ownerLewis Kerr
BB-Demo implementation leadHamza Akhtar
BB-Demo customer success managerHollie Grieve

Goals

Read the whole document (4,060 characters)
  • Bring the customer's CRM, helpdesk and accounting data into the brain so each university can be viewed as one account.
  • Give the university partnerships team and the resident services team a shared view they trust.
  • Reach a point where people ask the brain questions instead of reconciling systems by hand.

Phases and owners

PhaseTimingWhat happensOwner
Kick-offWeek oneConfirm goals, name the customer's project lead and an administrator, agree the order in which sources are connectedHamza Akhtar
Access and securityWeek one to week twoThe customer's IT contact grants access inside the Snowflake account and approves each sourceCustomer IT contact, supported by Hamza Akhtar
Connect sourcesWeek two to week fiveConnect the CRM, the helpdesk and the accounting system first, then any remaining sources up to the Growth connector allowanceHamza Akhtar
Validate dataWeek five to week sixCheck that each university's nomination agreements, tickets and invoices line up, and correct mismatches with the customer's teamsHamza Akhtar with the customer project lead
Training and dashboardsWeek six to week sevenTrain both teams, build the first dashboards with the dashboards builderHamza Akhtar
HandoverWeek eightConfirm the nightly refresh is running, hand over to customer successHollie Grieve

The order of connectors may change if a source needs clean-up before it can be loaded.

Milestones

  • Kick-off held: project lead and administrator named.
  • First source live: the brain answers a question from real Hartside data.
  • All agreed sources live: the nomination, ticket and invoice views are available for every university city.
  • Teams trained: both teams have used the brain on their own questions.
  • Handover complete: customer success owns adoption from this point.

What we need from Hartside

  • A named project lead who can make decisions for both teams.
  • At least two administrators, so that adoption does not depend on one person.
  • Timely access to each source system, and early warning of any planned system changes.
  • A short list of the questions each team most wants answered, so the first dashboards reflect real work.

Risks to watch

RiskMitigation
A source changes shape part way through the projectAsk the IT contact to flag changes in advance, and re-run the affected load
Usage stays with a single personTrain both teams and name more than one administrator
Nomination agreements are held in inconsistent formatsAgree a common set of fields with the partnerships team during validation

After go-live

Hollie Grieve will run quarterly business reviews, which are part of Growth, and will track usage and questions asked. Lewis Kerr remains the contact for any change to users or connectors. The first renewal falls at the end of the subscription term on 9 Apr 2027, and the customer success manager will raise it well ahead of the notice period.

Documentsmade from

Unusual terms

Not yet analysedThe unusual terms of object_read:doc_158_009 are empty: the record found none.

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