Merriott Lyle Distribution - Proposal
Documentfinal Merriott Lyle Distribution · proposal · final · 17 Aug 2026
Proposal dated 17 Aug 2026 for one expansion line on the existing Enterprise subscription: £10k annual price, £4,548 total order value, co-termed to 27 Feb 2027. Conditioned on an adoption review and closing open tickets. It is a proposal, not executed paper.
What it says
What this says
As at Fri 9 Oct 2026Proposal dated 17 Aug 2026 for one expansion line on the existing Enterprise subscription: £10k annual price, £4,548 total order value, co-termed to 27 Feb 2027. Conditioned on an adoption review and closing open tickets. It is a proposal, not executed paper.
What it is: a version 1 proposal from Lewis Kerr, filed as final, for an expansion of the Enterprise subscription. It states the current subscription carries "an annual recurring value of £128k" and a licence for 200 users, running to 27 Feb 2027.
Commits: nothing is binding yet. The order form is to follow "once the points in section 4 are agreed". Invoicing is a "Single invoice on acceptance", with payment terms "As per your current order form".
Unusual: the proposal names its own risks and attaches conditions: a named owner, an adoption review, open tickets resolved first and a usage checkpoint before renewal. It says active use has fallen by about a quarter and three tickets arrived in the last month.
Not settled: the document does not say what the expansion consists of, nor why £4,548 differs from £10k beyond calling it the order total. It does not show who at the customer receives it or whether it was accepted.
As found in this document
As at Fri 9 Oct 2026- Date end27 Feb 2027Source: the AI read of this record
- Date renewal27 Feb 2027Source: the AI read of this record
- Price£10,000Source: the AI read of this record
- Annual price of the expansion£10,000Source: the AI read of this record
- Total value of this order£4,548Source: the AI read of this record
- TermCo-termed, ending 27 Feb 2027Source: the AI read of this record
- InvoicingSingle invoice on acceptanceSource: the AI read of this record
- Payment termsAs per your current order formSource: the AI read of this record
- Price validityHeld until you have reviewed the adoption points aboveSource: the AI read of this record
- VATNot included in any figure shownSource: the AI read of this record
The document
Body
Merriott Lyle Distribution - Proposal
Prepared by: Lewis Kerr, Account Executive, BG-Demo Customer success manager: Daniel Okafor Date: 17 Aug 2026 Version: 1 (final) Deal type: Expansion of the existing Enterprise subscription
1. Context
Merriott Lyle Distribution has been a BG-Demo customer since 28 Feb 2025 and runs B-Glass on the Enterprise tier. The brain gives branch, key-account and credit-control teams one view of each trade account: orders, disputes, calls and invoices together, inside your own Snowflake account.
The current subscription carries an annual recurring value of £128k and a licence for 200 users. It runs to 27 Feb 2027, and everything in this proposal is co-termed to your renewal so that you have one date to manage, not two.
This proposal sets out one expansion. It is written to be practical rather than ambitious, because the recent picture on your account calls for care, and I would rather you buy what the usage supports.
2. Where the account stands today
I have looked at the account before putting a price in front of you. In plain terms:
Read the whole document (5,375 characters)
- Active use is lower than it was. The number of people using the brain each day has fallen by about a quarter against the previous quarter, and it sits well below the 200 users you are licensed for.
- Support has been busier than usual. There have been three tickets in the last month, two of them high priority. Daniel is following those up with your team, and I would like them closed to your satisfaction before anything new is switched on.
- Payments are in order. There are no overdue invoices, so I read this as a question of adoption and value, not a commercial dispute.
The fall in activity matters more to me than the licence count. Headroom on licensed users means there is no need to buy more seats. It does mean the case for any expansion has to rest on a clear use that your teams will adopt.
3. What we propose
One expansion line, added to the existing Enterprise order form under the current MSA:
| Item | Detail |
|---|---|
| Subscription tier | Enterprise (unchanged) |
| Deal type | Expansion |
| Annual price of the expansion | £10k |
| Total value of this order | £4,548 |
| Alignment | Co-termed to your renewal on 27 Feb 2027 |
| Licensed users | 200 (unchanged) |
All prices are shown excluding VAT, which is added at the prevailing rate on the invoice.
To be clear about the two figures: £10k is the annual price of the expansion once it is running for a full year. £4,548 is the total value of this order, which is what you would be invoiced under this proposal. I have kept them apart on purpose so that nobody mistakes one for the other when it reaches your finance team.
4. How we would keep it grounded in usage
I do not want to sell you something that sits unused. So I suggest the following conditions are agreed with us before the order is signed.
- A named owner on your side. One person in the branch, key-account or credit-control group who is accountable for the expansion being used.
- A short adoption review. Daniel will sit with your team to look at who is asking questions of the brain and who is not, and to agree what would make it more useful to the quieter teams.
- Open tickets resolved first. The high priority items are closed, and your team confirms the connectors are loading as expected.
- A usage checkpoint before renewal. We review the same measures together ahead of your renewal conversation, so that the renewal is based on what you have actually used.
5. What is not changing
- Your Enterprise service levels, including availability, first response times and data freshness credits, stay as they are in the executed order form.
- Your existing connectors, users and single sign-on arrangements are untouched.
- Nothing in this proposal alters the annual recurring value or the term of the current contract.
6. Commercial terms
| Term | Position |
|---|---|
| Governing agreement | Existing MSA and executed Enterprise order form |
| Term | Co-termed, ending 27 Feb 2027 |
| Invoicing | Single invoice on acceptance |
| Payment terms | As per your current order form |
| Price validity | Held until you have reviewed the adoption points above |
| VAT | Not included in any figure shown |
7. Risks we are naming openly
- Adoption risk. If the fall in active users continues, an expansion will add cost without adding value. This is why the checkpoint in section 4 exists.
- Key-person risk. If a small number of people ask most of the questions, the brain depends on them. Daniel will check this in the adoption review.
- Renewal risk. A weak usage picture going into 27 Feb 2027 would make the renewal harder for everyone. Doing the adoption work now is the best protection for both of us.
8. Next steps
- You review this proposal with your finance team and the teams that would use the expansion.
- Daniel arranges the adoption review and closes out the open tickets.
- I send over the order form for signature once the points in section 4 are agreed.
- We hold the usage checkpoint ahead of your renewal.
If anything here does not match how you see the account, tell me and I will change it. I would rather get the quote right than get it signed quickly.
Kind regards,
Lewis Kerr Account Executive, BG-Demo
Unusual terms
As at Fri 9 Oct 2026- Expansion conditional on adoption review
- Open high priority tickets to close first
- Usage checkpoint before renewal
- Order value differs from annual price