Brenneck Pay - Proposal
Documentfinal Brenneck Pay: documents · proposal · final · 2026-07-23
A final version 1 proposal dated 23 Jul 2026 from Matteo Ricci to move Brenneck Pay from Growth to Enterprise at £125,000 annual price. It is an open proposal, not an order form. It states no availability or P1 response figures.
What it says
What this says
Current to 11 Oct 26A final version 1 proposal dated 23 Jul 2026 from Matteo Ricci to move Brenneck Pay from Growth to Enterprise at £125,000 annual price. It is an open proposal, not an order form. It states no availability or P1 response figures.
What it is: a BB-Demo proposal for an expansion from Growth to Enterprise. It says "The deal amount and the annual price are the same figure in this proposal."
Commits: it states a price and billing basis only. Billing is "annual in advance, with quarterly billing available on request, on standard payment terms", under an order form on the existing master agreement.
Unusual: the document says the current Growth term ends 2 Feb 2027, so the expansion sits close to that date. Service levels are described only as higher than Growth, with no figures.
Not settled: the order form, term, billing schedule and treatment of the Growth subscription are not yet issued. "Timings for each phase will be agreed with our engineering team before we put dates to them." User needs at full rollout are unconfirmed.
As found in this document
Current to 9 Oct 26- Date end2 Feb 2027Source: object_read:doc_078_014
- Price£125,000Source: object_read:doc_078_014
- Annual price£125,000 for the Enterprise tierSource: object_read:doc_078_014
- Billingannual in advance, with quarterly billing available on request, on standard payment termsannual in advance, with quarterly billing available on request, on standard payment terms · Source: object_read:doc_078_014
- Contract basisan order form under the existing master agreementan order form under the existing master agreement · Source: object_read:doc_078_014
The document
Body
Brenneck Pay - Proposal
Status: Final, version 1 Date: Thursday 23 July 2026 Prepared for: Brenneck Pay, Frankfurt Prepared by: Matteo Ricci, Account Executive, BB-Demo Customer success contact: Elena Novak, BB-Demo
1. Why we are writing
Brenneck Pay became a BB-Demo customer on Tuesday 3 February 2026 on the Growth tier. The purpose was clear from the start: merchant account managers and merchant risk should work from one view of each merchant, with the data held in an EU region.
Since then the brain has settled into daily use. Active use has risen sharply compared with the previous quarter, support demand has been light, and there are no overdue invoices. This proposal sets out what moving from Growth to Enterprise would mean for Brenneck Pay, what it would cost, and how we would run it.
I would rather you heard it plainly from me: this is an expansion, not a correction. Growth is working for the teams using it. Enterprise is for the point at which the brain becomes a company-wide, regulated layer rather than a tool for two functions.
2. Where Brenneck Pay is today
Read the whole document (6,707 characters)
| Item | Current position |
|---|---|
| Tier | Growth |
| Annual recurring revenue (contracted) | £50,000 |
| Licensed users | 40 |
| Contract end | 2 Feb 2027 |
| Data location | EU region, inside your own Snowflake account |
| Account owner | Matteo Ricci |
| Customer success manager | Elena Novak |
What the usage tells us
- Adoption is rising. The number of people using the brain each month has grown strongly quarter on quarter, which is the clearest sign that the merchant view is being relied on.
- Support is quiet. A single ticket was raised in the last month and none was high priority.
- Commercially healthy. No invoices are overdue.
We have not yet seen what the licensed user allowance looks like at full rollout, and we would rather confirm that with you than assume it.
3. What we propose
We propose that Brenneck Pay moves from Growth to Enterprise as an expansion of the existing relationship.
| Element | Proposal |
|---|---|
| Deal type | Expansion |
| Tier | Enterprise |
| Annual price | £125,000 |
| Deal amount | £125,000 |
| Contract end of current term | 2 Feb 2027 |
The deal amount and the annual price are the same figure in this proposal. The order form that follows will state the term, the billing schedule and how the existing Growth subscription is treated on moving across.
What Enterprise adds for Brenneck Pay
- Company-wide scope. The brain can serve every function, not only merchant account management and merchant risk. Compliance, finance, operations and leadership can ask questions of the same merchant record.
- Single sign-on and user provisioning. SSO and SCIM bring the brain under your identity controls, so joiners, movers and leavers are handled in one place.
- A larger allowance for users and connectors. The Enterprise allowances are well above the Growth allowance of 40 licensed users, which gives you room to roll out beyond the first teams without renegotiating each time.
- An executive sponsor. A named senior BB-Demo sponsor for Brenneck Pay, alongside your customer success manager.
- Stronger service levels. The Enterprise tier carries a higher availability commitment and a faster first response on the most urgent tickets than Growth. Enterprise is also the only tier credited for data freshness as well as availability.
- Security review support. Implementation for Enterprise includes support for your security review, which matters for a payment institution supervised by BaFin.
4. What your regulator will want to see
A question I ask every regulated buyer: what does your regulator need to see? For Brenneck Pay we expect the answer to centre on three things.
- Where the data sits. The brain is built and run inside your own Snowflake account, in an EU region. Your data does not leave your environment.
- Who can see what. SSO and SCIM give a clear, auditable record of access.
- How incidents are handled. If something goes wrong, your security team hears from us at once, with the facts as we know them. We do not hold things back.
We will support the security review with written answers, and I will confirm in writing anything that your team needs for its own records.
5. Implementation approach
The Growth deployment is already live, so the Enterprise move is an extension and not a fresh build. We would work in three phases.
| Phase | What happens | Owner |
|---|---|---|
| Review | Confirm scope, the functions to be added and the security questions your team needs answered | Matteo Ricci with Brenneck Pay |
| Extend | Add SSO and SCIM, bring further sources and teams onto the brain, and confirm the EU data location | BB-Demo delivery team |
| Embed | Train the new teams, name the executive sponsor and agree the review rhythm | Elena Novak |
Timings for each phase will be agreed with our engineering team before we put dates to them. I will not commit a date that engineering has not confirmed.
6. Commercial summary
- Annual price: £125,000 for the Enterprise tier.
- Deal type: expansion of the existing Growth relationship.
- Current contracted annual recurring revenue: £50,000.
- Current term ends: 2 Feb 2027.
- Billing: annual in advance, with quarterly billing available on request, on standard payment terms.
- Contract basis: an order form under the existing master agreement.
Any discount is a first-term matter only and would be shown on the order form itself.
7. Risks and how we would handle them
| Risk | Mitigation |
|---|---|
| Roll-out outpaces training | Embed phase led by Elena Novak, with training for each new team |
| Source systems change during the extension | Connector checks at each phase and a clear escalation route |
| Security review runs long | Early engagement with your security team and written answers prepared in advance |
| Value is hard to evidence to leadership | Quarterly reviews of questions asked, users and dashboards built, shared with your sponsor |
8. Next steps
- Brenneck Pay confirms which functions it wants on the brain beyond merchant account management and merchant risk.
- Your security team sends its questions, and we respond in writing.
- Matteo Ricci issues the Enterprise order form for review.
- Elena Novak agrees the extension plan with your operations lead, with dates confirmed by engineering.
Thank you for the trust you have placed in the brain so far. Please come back to me with any question, and I will answer it in writing.
Best regards, Matteo
Matteo Ricci Account Executive, BB-Demo
Unusual terms
Current to 9 Oct 26- Expansion proposed before current term ends 2 Feb 2027
- No phase dates committed until engineering confirms