Brenneck Pay - Proposal v1
Documentdraft Brenneck Pay: documents · proposal · draft · 2025-11-20
Draft proposal dated 20 Nov 2025 for a Growth-tier company brain for Brenneck Pay, with EU data residency. Annual subscription £50k, total deal value £62k including the one-off implementation fee. Not an offer capable of acceptance.
What it says
What this says
Current to 11 Oct 26Draft proposal dated 20 Nov 2025 for a Growth-tier company brain for Brenneck Pay, with EU data residency. Annual subscription £50k, total deal value £62k including the one-off implementation fee. Not an offer capable of acceptance.
What it is: a working draft proposal from Sophie Ling, filed under Customers/Brenneck Pay/Proposals. It says "This is a working draft for discussion" and that scope and terms are open until an order form under the MSA is agreed.
Commits: nothing binding. It states an annual subscription of £50k, total deal value of £62k, billing "Subscription annually in advance", and no discount assumed. Any discount would apply to the first term only.
Unusual: service levels are described only as the standard Growth levels, with no figures. Connectors committed in the order form would carry a go-live commitment in days.
Not settled: the final connector list, add-ons, extra users or connectors, whether the price holds once scope is confirmed, and the Brenneck Pay signatories. The evidence does not show an executed order form, so this draft sets no contracted price.
As found in this document
Current to 9 Oct 26- Price£50,000Source: object_read:doc_078_002
- Annual subscription price£50,000Source: object_read:doc_078_002
- Total deal value including the one-off implementation fee£62,000Source: object_read:doc_078_002
- BillingSubscription annually in advanceSource: object_read:doc_078_002
- DiscountNo discount is assumed in this draft. Any discount would apply to the first term only.No discount is assumed in this draft. Any discount would apply to the first term only. · Source: object_read:doc_078_002
- Connector go-liveAny connector we commit to in the order form will carry a go-live commitment in days.Any connector we commit to in the order form will carry a go-live commitment in days. · Source: object_read:doc_078_002
The document
Body
Brenneck Pay - Proposal v1
Status: Draft
| Prepared for | Brenneck Pay, Frankfurt |
| Prepared by | Sophie Ling, Account Executive, BB-Demo |
| Account owner | Matteo Ricci |
| Customer success manager | Elena Novak |
| Date | Thursday 20 November 2025 |
| Tier proposed | Growth |
This is a working draft for discussion. Scope, connectors and commercial terms are open until they are confirmed in an order form under the MSA.
Context
Brenneck Pay is a Frankfurt payment institution supervised by BaFin. It processes card and account-to-account payments for German online retailers. Today, merchant account managers and the merchant risk team each work from their own systems and their own picture of a merchant. Questions that cross the two groups, such as whether a merchant's payment behaviour matches what the commercial team has been told, are answered by reconciling exports by hand.
You asked for one shared view of each merchant, held in an EU region, that both groups can query without waiting for an analyst.
What BB-Demo proposes
Read the whole document (5,883 characters)
BB-Demo would build the company brain for Brenneck Pay: one AI-queryable layer over the systems your teams already use, built and run inside your own Snowflake account. Merchant account managers and merchant risk would ask the same brain and see the same merchant, rather than two partial versions of it.
Why Growth
Growth is designed for several teams working from shared data. For Brenneck Pay it gives:
- pages, chat and search across the connected sources;
- the dashboards builder, so the risk and account teams can keep the views they rely on;
- quarterly business reviews with your customer success manager, to check that the brain is being used and that it is worth what you pay;
- the Growth user allowance and the Growth connector allowance, which we will map against the teams and systems agreed in discovery.
Scope
In scope
- One company brain in a Snowflake account controlled by Brenneck Pay.
- Connectors to the systems that hold merchant, account management and risk information, to be confirmed with your teams. Any connector we commit to in the order form will carry a go-live commitment in days.
- A merchant view that brings together what account managers know and what merchant risk sees.
- Data residency in an EU region, as you have asked.
- Training for the merchant account management and merchant risk teams.
Not yet decided
- The final list of source systems and who owns each connection on your side.
- Whether any additional users or connectors are needed beyond the Growth allowances.
- Whether a dedicated residency add-on or on-site training day is wanted on top of the base proposal.
Commercial summary
| Item | Value |
|---|---|
| Tier | Growth |
| Annual subscription price | £50k |
| Total deal value including the one-off implementation fee | £62k |
| Deal type | New customer |
| Billing | Subscription annually in advance |
The annual subscription is the recurring element, and it is what would renew each year. The total deal value is higher because it also includes the fixed-fee implementation, which is charged once when you join and does not recur. No discount is assumed in this draft. Any discount would apply to the first term only.
Service levels
Growth carries the standard Growth service levels for availability and priority incident response, with service credits for availability. The nightly refresh is completed before the start of your business day, so merchant teams begin each morning on current data. The exact levels will be written into the order form.
Security and regulatory considerations
Because Brenneck Pay is supervised by BaFin, we expect your security and compliance colleagues to want to review how the brain is built and where data sits. Two points matter most:
- The brain runs inside your Snowflake account, so your data stays under your own controls rather than moving to a BB-Demo environment.
- Data is kept in an EU region.
We will answer any security questionnaire your team sends and are glad to walk your colleagues through the architecture.
Delivery approach
| Phase | What happens | Owner |
|---|---|---|
| Discovery | Confirm teams, questions and source systems | Sophie Ling with your project lead |
| Build | Connect sources and load the first data into your Snowflake account | BB-Demo implementation team |
| Validate | Merchant account managers and merchant risk test the shared view on real merchants | Brenneck Pay teams |
| Launch | Training, go-live and first check-in | BB-Demo with Elena Novak |
Timings will be set out in the order form once scope is agreed.
Measuring value
We suggest agreeing early how you will judge success. Useful measures for a payment institution include how often account managers and risk analysts ask the brain questions, how much manual reconciliation falls away, and whether both teams reach the same answer about a merchant. Quarterly reviews will track these.
Next steps
- Review this draft with the merchant account management and merchant risk leads.
- Send us the list of systems you expect to connect, so scope and connectors can be confirmed.
- Share any security or compliance questions from your team ahead of a review session.
- Agree an outline timeline and a launch date that suits your teams.
- Customer success manager: Elena Novak will be your contact for adoption and reviews once you are live.
- Matteo Ricci and Sophie Ling will prepare the order form once the above is settled.
Open points in this draft
- Final connector list and any residency or training add-ons.
- Whether the proposed annual price holds once scope is confirmed.
- Named signatories on the Brenneck Pay side.
This proposal is a draft and is not an offer capable of acceptance until an order form has been agreed and signed.
Unusual terms
Current to 9 Oct 26- EU data residency requested
- Draft not capable of acceptance
- Service levels not quantified