Ardenmore Pension Administration - Renewal Proposal v1
Documentdraft Ardenmore Pension Administration · renewal_proposal · draft · 2025-06-20
Internal draft renewal proposal for a like-for-like Starter renewal at £23k a year, 25 users, billed annually in advance on 30-day terms. Not shared with the customer. The fee and the decision maker are unconfirmed.
What it says
What this says
Current to 14 Oct 26Internal draft renewal proposal for a like-for-like Starter renewal at £23k a year, 25 users, billed annually in advance on 30-day terms. Not shared with the customer. The fee and the decision maker are unconfirmed.
What it is: a draft by Tom Ashdown dated 20 Jun 2025, marked "Not yet shared with the customer". It proposes one further annual term for the Starter tier when the term ending 29 Aug 2025 closes.
Commits: nothing binds either party. The proposed terms are an annual fee of £23k, 25 users and billing "Annually in advance, 30-day terms, as today".
Unusual: the fee is the current contracted figure, so no v2 uplift is shown. The text says usage is "a fraction of the licensed total", and a user reduction is floated.
Not settled: the fee still needs Tom's confirmation, the customer decision maker is unknown, and the user count is undecided. The document does not show whether a renewal was ever agreed, and it is an open draft, not executed paper.
As found in this document
Current to 9 Oct 26- Date end29 Aug 2025Source: object_read:doc_159_017
- Date renewal29 Aug 2025Source: object_read:doc_159_017
- Price£23,000Source: object_read:doc_159_017
- Annual fee£23,000, the current contracted annual recurring revenue, to be confirmed by Tom before this goes to the customer£23,000, the current contracted annual recurring revenue, to be confirmed by Tom before this goes to the customer · Source: object_read:doc_159_017
- BillingAnnually in advance, 30-day terms, as todayAnnually in advance, 30-day terms, as today · Source: object_read:doc_159_017
- TermOne further annual term, starting when the current term endsOne further annual term, starting when the current term ends · Source: object_read:doc_159_017
- Users25, as todaySource: object_read:doc_159_017
The document
Body
Ardenmore Pension Administration - Renewal Proposal v1
Draft. Prepared by Tom Ashdown, Account Executive, BB-Demo, on 20 Jun 2025. Not yet shared with the customer. Open points are listed at the end.
1. Purpose
This proposal sets out how Ardenmore Pension Administration could renew its BB-Demo subscription for a further annual term, keeping the current scope. Ardenmore has been a customer since 30 Aug 2023, and the current term ends on 29 Aug 2025.
2. Where things stand
| Item | Current position |
|---|---|
| Organisation | Ardenmore Pension Administration, Birmingham |
| Tier | Starter |
| Licensed users | 25 |
| Annual recurring revenue (contracted) | £23k |
| Customer since | 30 Aug 2023 |
| Current term ends | 29 Aug 2025 |
| Account owner | Tom Ashdown |
| Customer success manager | Marcus Bell |
Ardenmore uses the brain mainly in its client-relationship team, which supports the schemes the firm administers for Midlands employers. Usage has been steady and has edged up against the prior quarter. There are no open support tickets and no overdue invoices, so there is nothing on the account that needs clearing before a renewal conversation.
Read the whole document (3,304 characters)
3. Proposed renewal
| Element | Proposal |
|---|---|
| Deal type | Renewal |
| Tier | Starter, unchanged |
| Term | One further annual term, starting when the current term ends |
| Users | 25, as today |
| Connectors | As configured today, within the Starter allowance |
| Annual fee | £23k, the current contracted annual recurring revenue, to be confirmed by Tom before this goes to the customer |
| Billing | Annually in advance, 30-day terms, as today |
No change of scope is proposed in this version. The aim is a clean like-for-like renewal that does not disturb a team that is already getting steady use from the brain.
4. What Ardenmore keeps
- Pages, chat and search across the connected sources.
- The Starter service levels, including the nightly refresh on business days.
- The six-monthly check-in with the customer success manager.
- The data and configuration already built inside its own Snowflake account.
5. Possible conversation points
These are options to raise, not part of the proposal:
- Whether the client-relationship team has colleagues elsewhere in the firm who would benefit from access, which would be a question about the Growth tier.
- Whether the number of users is still right, given that usage is a fraction of the licensed total.
- Whether the team wants a short value review before the renewal date, so the benefit is easy to explain internally.
6. Next steps
| Step | Owner | Timing |
|---|---|---|
| Confirm renewal price and terms internally | Tom Ashdown | Before the draft goes out |
| Review usage and value points with the customer success manager | Marcus Bell | Next week |
| Share the proposal with the Ardenmore contact | Tom Ashdown | After internal confirmation |
| Agree dates for a renewal call | Tom Ashdown | As soon as the proposal is shared |
7. Open points
- The annual fee is shown at the current contracted level and needs Tom's confirmation.
- The Ardenmore decision maker for the renewal is still to be confirmed.
- Whether to suggest a reduction in licensed users is undecided and needs a view from the customer success manager.
Unusual terms
Current to 9 Oct 26- Draft, not shared with customer
- Fee shown at current level, unconfirmed
- Possible user reduction undecided