B-Brain
Hartside Student Living logo

Hartside Student Living - QBR

Documentfinal

Hartside Student Living logo Hartside Student Living · qbr_deck · final · 2026-09-10

Final QBR deck prepared by Hollie Grieve on 10 Sep 2026 for a Growth customer with a contract running to 9 Apr 2027. It reports growing usage from a small core of users, three tickets in thirty days, and no overdue invoices. It is not a contract.

What it says

What this says

Current to 13 Oct 26

Final QBR deck prepared by Hollie Grieve on 10 Sep 2026 for a Growth customer with a contract running to 9 Apr 2027. It reports growing usage from a small core of users, three tickets in thirty days, and no overdue invoices. It is not a contract.

What it is: a customer QBR deck from BB-Demo's Customer Success Manager. It states "Contracted annual recurring revenue" of £45k, as the deck's own position table, and 40 licensed users.

What it says: active users are "a small core of the licensed users", so "there is no case for extra users at this stage". The value rests on a few people.

Not settled: the deck gives no connector picture ("We have not seen the connector picture in detail in this review"), no measure of time saved, and no team breakdown of users. The high-priority ticket is not shown as resolved.

Next: Lewis Kerr owns a commercial check-in on the term ending 9 Apr 2027, and Hollie owns the ticket review and the value measure.

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_010
  • Date start10 Apr 2026Source: object_read:doc_158_010

The document

Body

Hartside Student Living - QBR

Quarterly business review, Growth tier Prepared by Hollie Grieve, Customer Success Manager, BB-Demo Date: Thursday 10 September 2026 Status: Final

1. Where we are

ItemPosition
TierGrowth
Customer since10 Apr 2026
Contract end9 Apr 2027
Contracted annual recurring revenue£45k
Licensed users40
Account ownerLewis Kerr
Customer Success ManagerHollie Grieve

Hartside bought Growth so that university partnerships and resident services can see each university's nomination agreements, tickets and invoices together, across a portfolio in eight university cities.

2. Usage

  • Active users have grown well over a third compared with the prior quarter, which is a healthy direction.
  • The active group is still a small core of the licensed users. That leaves a lot of headroom inside the Growth allowance of forty users.
  • We would like to see which teams the current users sit in, so we can tell whether the growth is coming from university partnerships, resident services or both.

3. Value so far

Read the whole document (3,019 characters)
  • The brain is now the place where a university's agreements, tickets and invoices meet. That was the reason for buying, and the usage trend suggests it is being used for that.
  • We do not yet have a before-and-after measure of time saved on reconciling systems. This is worth agreeing together rather than us guessing at it.
  • The Growth dashboards builder is available and we would like to see whether the team wants a standing view per university.

4. Support and service

  • Three tickets were raised in the last thirty days, one of them high priority.
  • There are no overdue invoices on the account.
  • Nothing in the ticket picture suggests a pattern. We will keep the high-priority ticket under review with the team until they are happy it is closed out properly.

5. Opportunities

  • Adoption: invite the remaining licensed users, starting with the teams closest to nomination agreements and resident tickets.
  • Dashboards: build one shared view per university so the weekly conversation starts from the same page.
  • Headroom: with plenty of licensed users unused, there is no case for extra users at this stage. We would say so plainly.

6. Risks and watch points

  • A small core of active users means the value rests on a few people. If one of them moves on, usage could drop quickly.
  • We have not seen the connector picture in detail in this review. We will check that every connected source is still loading before the next QBR.

7. Next steps

ActionOwnerTiming
Review the high-priority ticket and confirm it is resolvedHollie GrieveBefore the next QBR
Agree which teams to bring on nextHollie Grieve with HartsideNext few weeks
Agree a simple measure of value for the brainHollie Grieve with HartsideNext few weeks
Commercial check-in on the term ending 9 Apr 2027Lewis KerrWell ahead of the contract end
Documentsmade from

Unusual terms

Not yet analysedThe unusual terms of object_read:doc_158_010 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