B-Brain - Board Pack - quarter to 30 Sep 2023

Documentfinal

board_pack · final · 2023-10-17

Final board pack issued 17 Oct 2023 by CEO Nell Ashcombe. It reports contracted ARR of £56,550 across three customers and a headcount of seven, and says plainly what it does not show: cash, pipeline and usage.

What it says

What this says

Current to 11 Oct 26

Final board pack issued 17 Oct 2023 by CEO Nell Ashcombe. It reports contracted ARR of £56,550 across three customers and a headcount of seven, and says plainly what it does not show: cash, pipeline and usage.

What it is: an internal board pack for the quarter ending 30 Sep 2023, issued on 17 Oct 2023 by Nell Ashcombe. The status is Final in both the header and the text.

Claims: "Annual recurring revenue (contracted)" is £56,550, taken from executed order forms and excluding one-off implementation fees. It rests on three customers, so the pack says "each renewal matters a great deal".

Risks named: concentration, capacity with seven people, value evidence and data freshness. Priorities include naming an owner for each of the three accounts and writing down the value each customer gets.

Not settled: the pack carries no cash or runway view, no pipeline and no usage statistics. It is a point-in-time record from 2023, so it is not a current view of the company.

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

As found in this document

Not yet analysedThe read found no dated or priced terms.

The document

Body

B-Brain - Board Pack - quarter to 30 Sep 2023

Status: Final Prepared by: Nell Ashcombe, Chief Executive Officer and Co-founder Date of pack: 17 Oct 2023 Period covered: the quarter ending 30 Sep 2023

Headline numbers

MeasurePosition at 30 Sep 2023
Annual recurring revenue (contracted)nineteen and a half thousand pounds
Customersone
Headcountseven

These are the three numbers I would ask the board to hold in mind. Everything else in this pack is commentary on them.

How to read this pack

We are a young company and the numbers are small, so I have kept the pack short and plain. Where I give a figure for revenue it is the contracted annual figure, taken from the signed order form. I have not used pipeline, hopes or verbal agreements. If a number cannot be traced to a signed document, it is not in here.

Revenue

We have one paying customer, and the contracted annual subscription for that customer is the nineteen and a half thousand pounds shown above. That is where we are, and I would rather say it plainly than dress it up.

Two points on how that figure is built:

Read the whole document (4,661 characters)
  • It is the annual subscription only. The one-off implementation fee is a separate matter and is not counted in recurring revenue.
  • It is contracted, not invoiced. Invoicing follows the order form, and the two should agree. I will bring an invoicing check to the board as soon as there is more than one customer to check.

With one customer, our revenue and our concentration risk are the same thing. I do not think that is a surprise to anyone on the board, but it is worth writing down.

Customers

One customer is live on the brain, running inside their own Snowflake account. Because there is only one, the most useful thing we can do is learn from them in detail rather than generalise.

What I am watching, in order:

  • Whether their teams are asking the brain questions as part of their normal week, not only during demonstrations.
  • Whether the data feeding the brain is fresh each morning.
  • Whether the person who championed us still has the time and the standing to keep it going.

I would like to be able to say what the brain changed for them, and how we know. At the moment I can say some of that and not all of it. That is a gap in our evidence, not a complaint about the customer.

People

Headcount is seven. We have been careful about hiring ahead of revenue, and the team is small enough that everyone knows every account and every open issue.

Commentary:

  • The team covers building, delivering and selling. There is not yet a dedicated function for adoption or renewals; at the moment that sits with whoever knows the customer best.
  • I do not propose to change that this quarter. I do expect to bring a proposal once we have a second customer and can see what the two have in common.

What went well

  • We signed a customer and have kept that customer.
  • The product works inside a customer's own Snowflake account, which is the thing we said we would do.
  • The team has stayed together and stayed focused.

What did not go as well

  • One customer is not a business. We are early, and the pipeline is thinner than I would like.
  • We have not yet written down a repeatable way of measuring value for a customer. That one is on us.
  • Our reporting is by hand. It is accurate, but it will not scale past a handful of accounts.

Risks

RiskWhy it mattersWhat we are doing
Customer concentrationAll recurring revenue sits with one customerPrioritise new customers; keep the existing relationship close
Key-person dependenceA small team holds most of the knowledgeWrite things down; share account knowledge across the team
Evidence of valueRenewal depends on being able to show what the brain is worthAgree a simple set of usage measures with the customer

Priorities for the next quarter

  • Win a second customer.
  • Agree with our existing customer how we will both judge whether the brain is working, using usage rather than opinion.
  • Put a simple, repeatable monthly reporting routine in place so this pack gets easier to write and easier to trust.

Asks of the board

  • Note the position at 30 Sep 2023.
  • Challenge the priorities above, in particular whether a second customer should come before anything else.
  • Tell me what you would want to see in this pack that is not here.

Closing note

The contracted annual recurring revenue is the nineteen and a half thousand pounds stated above. It is the figure in the signed order form, and I will keep it that way: say what happened, say how we know.

Best, Nell

Documentsmade from

Unusual terms

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

B-Brain is a fictional company; every organisation and person here is invented. 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
Organisations75
People at customers290
B-Brain staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

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.

B-Brain is a fictional company: every organisation, person and figure here is invented for this demonstration.

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.

Ask B

Ask B

B-Brain · read-only