Brimscombe Energy - Renewal Proposal v1
Documentdraft Brimscombe Energy · renewal_proposal · draft · 2026-10-02
Internal draft renewal proposal dated 2 Oct 2026 for the Enterprise subscription ending 9 Jan 2027. It proposes £131k for one year, billed annually in advance, against £120k current contracted annual recurring revenue. It is not issued or executed.
What it says
What this says
Current to 13 Oct 26Internal draft renewal proposal dated 2 Oct 2026 for the Enterprise subscription ending 9 Jan 2027. It proposes £131k for one year, billed annually in advance, against £120k current contracted annual recurring revenue. It is not issued or executed.
What it is: a first draft by Tom Ashdown for internal review, stating it is "not an offer capable of acceptance until it is issued as a final version with a renewal order form". It covers a one-year renewal from the day after the term ends on 9 Jan 2027, on the same scope.
Commits: nothing binding yet. It proposes £131k for 180 licensed users with SSO and SCIM and an executive sponsor, and keeps the Enterprise service levels as in the current order form, including the 07:00 nightly refresh.
Unusual: the proposed price is above the £120k current figure and the draft says internally how to explain that change is still open. No availability percentage or P1 time is stated.
Not settled: how the high priority ticket was resolved, whether to raise add-ons, and who signs for Brimscombe Energy. Customer success review is pending.
As found in this document
Current to 9 Oct 26- Date end9 Jan 2027Source: object_read:doc_154_022
- Date renewal9 Jan 2027Source: object_read:doc_154_022
- Price£130,750Source: object_read:doc_154_022
- Annual price£130,750Source: object_read:doc_154_022
- BillingBilled annually in advanceSource: object_read:doc_154_022
- Nightly refreshNightly refresh complete by 07:00 customer local time on business days.Nightly refresh complete by 07:00 customer local time on business days. · Source: object_read:doc_154_022
- Service creditsService credits for availability and for data freshness, which is an Enterprise-only protection.Service credits for availability and for data freshness, which is an Enterprise-only protection. · Source: object_read:doc_154_022
- Renewal order formBefore 9 Jan 2027Source: object_read:doc_154_022
The document
Body
Brimscombe Energy - Renewal Proposal v1
Status: Draft for internal review before it goes to Brimscombe Energy.
| Prepared for | Brimscombe Energy, Gloucester |
| Prepared by | Tom Ashdown, Account Executive, BB-Demo |
| Customer success manager | Daniel Okafor, BB-Demo |
| Document date | 2 Oct 2026 |
| Subscription | Enterprise |
| Current term ends | 9 Jan 2027 |
1. Purpose of this proposal
Brimscombe Energy has been a BB-Demo customer since 10 Jan 2025. The current Enterprise subscription ends on 9 Jan 2027. This proposal sets out how we would like to renew it for a further year, what Brimscombe Energy has built on the company brain so far, and what we suggest the next term should focus on.
This is a first draft. Anything marked as an open point in section 8 needs agreeing internally, or with Brimscombe Energy, before the proposal is final.
2. Where we are today
Read the whole document (5,800 characters)
Brimscombe Energy supplies business gas and electricity to SME and corporate sites and is licensed by Ofgem. You chose Enterprise so that the key-account, collections and complaints teams can see each business customer's sites, contracts, calls and bills together, rather than reconciling them by hand across systems.
| Item | Current position |
|---|---|
| Tier | Enterprise |
| Contracted annual recurring revenue | £120k |
| Licensed users | 180 |
| Customer since | 10 Jan 2025 |
| Account owner | Tom Ashdown |
| Customer success manager | Daniel Okafor |
| Invoices overdue | None |
The account is in good standing. Invoices have been paid on time and nothing is outstanding.
3. Usage and value in the current term
Usage has moved in the right direction. The average number of active users over the last thirty days is up on the prior quarter, which suggests more people in the three teams are reaching for the brain as part of their normal day.
At the same time, the number of people active in a typical month is still well below the 180 licensed users. We read that as headroom rather than a problem: there is room to bring more of each team onto the brain without any change to the subscription.
Support has been quiet. There was one ticket in the last thirty days, and it was the one high priority ticket in that period. We will confirm its resolution with Daniel before this proposal is shared, so that we describe it accurately.
4. What we propose
We propose to renew the Enterprise subscription for one year from the day after the current term ends on 9 Jan 2027, on the same scope as today.
| Line | Detail | Annual price |
|---|---|---|
| Enterprise subscription | Company-wide use, 180 licensed users, Enterprise connector allowance, SSO and SCIM, executive sponsor | £131k |
| Total annual price | Billed annually in advance | £131k |
The renewal price of £131k compares with the current contracted annual recurring revenue of £120k. There is no implementation fee on a renewal, so the whole figure is the subscription for the year.
Tom will confirm the final commercial terms in writing before anything is signed, and nothing in this draft changes the executed order form until a renewal order form is agreed.
5. Service levels
The renewal keeps the Enterprise service levels exactly as they stand in the current order form:
- Availability at the Enterprise level.
- First response on a P1 ticket at the Enterprise level, the fastest we offer.
- Nightly refresh complete by 07:00 customer local time on business days.
- Service credits for availability and for data freshness, which is an Enterprise-only protection.
If a service level in the executed order form differs from the standard Enterprise terms, the executed order form applies and the renewal will follow it.
6. Suggested focus for the next term
We would like the next year to be about depth of use rather than new scope. Three areas for discussion:
- Adoption across the three teams. Work with each team lead on who is not yet using the brain and why, using the licensed users already paid for.
- Complaints and collections. Agree two or three questions each team should be able to answer from the brain every week, so value is easy to point to at the next review.
- Reviewing connectors. Check that every source Brimscombe Energy relies on is loading and that records indexed are still growing.
Daniel will own the adoption plan and the quarterly reviews. Tom will own the commercial paperwork.
7. Timetable
| Step | Owner | Timing |
|---|---|---|
| Internal review of this draft | Tom Ashdown | This week |
| Check on the high priority ticket and usage picture | Daniel Okafor | Before the proposal is shared |
| Proposal shared with Brimscombe Energy | Tom Ashdown | Once the review is done |
| Renewal conversation with Brimscombe Energy | Tom Ashdown and Daniel Okafor | Well ahead of the end of the term |
| Renewal order form signed | Brimscombe Energy and BB-Demo | Before 9 Jan 2027 |
8. Open points
- Confirm with Daniel how the high priority ticket was resolved and whether Brimscombe Energy was satisfied.
- Agree internally how we explain the change from the current contracted annual recurring revenue to the renewal price.
- Decide whether to raise any add-ons, such as Premium support or the Sandbox, at the renewal meeting or leave them for later.
- Identify the right sponsor at Brimscombe Energy to sign the renewal order form.
9. Approvals
| Role | Organisation | Status |
|---|---|---|
| Account Executive | BB-Demo | Author of this draft |
| Customer Success Manager | BB-Demo | Review pending |
| Authorised signatory | Brimscombe Energy | Not yet issued |
This document is a draft proposal and is not an offer capable of acceptance until it is issued as a final version with a renewal order form.
Unusual terms
Current to 9 Oct 26- Proposed price above current contracted figure
- Draft not capable of acceptance