Brenneck Pay - Proposal
Documentfinal Brenneck Pay: documents · proposal · final · 2025-11-25
Final version one proposal dated 25 Nov 2025 for the Growth tier, with EU data residency. Annual subscription £50k, billed in advance; deal total £62k including the one-off implementation fee. It is a proposal, not an executed order form.
What it says
What this says
Current to 11 Oct 26Final version one proposal dated 25 Nov 2025 for the Growth tier, with EU data residency. Annual subscription £50k, billed in advance; deal total £62k including the one-off implementation fee. It is a proposal, not an executed order form.
What it is: a proposal from Sophie Ling, Account Executive, for merchant account management and merchant risk to share one view of each merchant. It states "Status: Final, version one" but is not signed paper.
Commits: it states "£50k is the annual subscription price" and "£62k is the total value of the deal". Payment is "the standard thirty days from invoice", with quarterly billing on request.
Unusual: service levels are described only as the standard Growth levels, with no figures. Connector delivery days are not given, and the order form is to fix them.
Not settled: no signature, start date or renewal date appears. The evidence does not show whether an order form followed, so the proposal is an open item.
As found in this document
Current to 9 Oct 26- Price£50,000Source: object_read:doc_078_003
- Growth subscription£50,000 annual, billed in advance£50,000 annual, billed in advance · Source: object_read:doc_078_003
- Deal total£62,000 (subscription plus one-off implementation fee)£62,000 (subscription plus one-off implementation fee) · Source: object_read:doc_078_003
- Payment termsthe standard thirty days from invoicethe standard thirty days from invoice · Source: object_read:doc_078_003
- BillingQuarterly billing is available on requestQuarterly billing is available on request · Source: object_read:doc_078_003
- ConnectorsConnectors named in the order form will carry a commitment to be live within an agreed number of daysConnectors named in the order form will carry a commitment to be live within an agreed number of days · Source: object_read:doc_078_003
- Data locationHeld in an EU region, inside your Snowflake accountHeld in an EU region, inside your Snowflake account · Source: object_read:doc_078_003
The document
Body
Brenneck Pay - Proposal
Prepared for: Brenneck Pay, Frankfurt Prepared by: Sophie Ling, Account Executive, BB-Demo Account owner: Matteo Ricci Customer success manager: Elena Novak Date: 25 Nov 2025 Status: Final, version one
Context
Brenneck Pay is a Frankfurt payment institution supervised by BaFin. It processes card and account-to-account payments for German online retailers. Over our conversations with the team, one theme came up repeatedly: merchant account managers and the merchant risk team each hold part of the picture of a merchant, in different systems, and reconciling the two by hand takes time and invites disagreement.
This proposal sets out how BB-Demo would give both teams a single, queryable view of each merchant, built and run inside Brenneck Pay's own Snowflake account, with the data kept in an EU region.
What you told us you need
Read the whole document (5,826 characters)
- One view of each merchant that account managers and merchant risk can both trust, so that neither team has to rebuild it from exports.
- The ability to ask plain-language questions across the merchant relationship, covering the CRM, support conversations, calls, emails and finance data, and get an answer that points back to its source.
- Data held in an EU region, consistent with your obligations as a supervised institution.
- A rollout that starts with the teams who feel the problem most, rather than the whole company at once.
What we propose
We propose the Growth tier of the BB-Demo company brain. Growth is designed for several teams working from the same data, which fits two groups with different questions about the same merchant.
Scope
| Area | What is included |
|---|---|
| Tier | Growth |
| Teams in scope | Merchant account management and merchant risk |
| Core capability | Pages, chat and search across connected sources |
| Dashboards | The Growth dashboards builder, so each team can build its own merchant views |
| Users | The Growth user allowance |
| Connectors | The Growth connector allowance, to be agreed source by source in the order form |
| Data location | Held in an EU region, inside your Snowflake account |
| Customer success | Quarterly business reviews with your customer success manager |
| Implementation | The standard Growth implementation, delivered as a fixed-fee, one-off engagement |
How the brain would be used
Account managers would ask questions such as which merchants have gone quiet, what was agreed on the last call, and which have open support issues. Merchant risk would ask which merchants show a change in pattern, and what the commercial context is behind it. Both teams would be reading from the same underlying records, so a conversation between them starts from the same facts.
Implementation approach
Implementation is a fixed-fee engagement with a clear sequence. The timetable is the standard Growth implementation timetable.
- Discovery and access: agree the sources, the owners of each system and the access needed inside your Snowflake account.
- Connect and index: bring the agreed sources into the brain, check that records are loading and confirm the nightly refresh completes before the working day begins.
- Build and review: set up the first pages and dashboards with each team and review the answers against records your people already know well.
- Go live and handover: train the two teams, confirm the support route and hand over to Elena Novak for adoption and the first quarterly review.
Connectors named in the order form will carry a commitment to be live within an agreed number of days.
Service levels
Growth carries the standard Growth service levels, which are written into the order form:
- Availability at the Growth service level, with service credits if it is missed.
- Priority one issues receive a first response within the Growth response time, measured in business hours.
- The nightly refresh completes before the start of the working day on business days.
We would be glad to walk your security and compliance colleagues through how the brain runs inside your own environment, so that your review has the detail it needs.
Commercials
| Item | Amount |
|---|---|
| Growth subscription, annual, billed in advance | £50k |
| One-off implementation fee | Included in the deal total below |
| Deal total (subscription plus one-off implementation fee) | £62k |
To be clear about the two figures: £50k is the annual subscription price. £62k is the total value of the deal, which includes the one-off implementation fee. The implementation fee is paid once and does not recur at renewal.
Payment terms are the standard thirty days from invoice. Quarterly billing is available on request.
Assumptions
- Your team will nominate a named owner for each connected system and give us access inside your Snowflake account.
- Merchant account management and merchant risk will each provide a lead to review answers during build.
- Additional teams, users or connectors beyond the Growth allowances can be added later through the order form.
Next steps
- Brenneck Pay reviews this proposal with the account management and merchant risk leads.
- Your security and compliance colleagues raise any questions with Sophie Ling, who will route them to the right person at BB-Demo.
- On agreement, BB-Demo issues the order form under the master services agreement for signature.
- Matteo Ricci and Elena Novak then confirm a kick-off with your teams.
Contacts
| Role | Name |
|---|---|
| Account Executive | Sophie Ling |
| Account owner | Matteo Ricci |
| Customer success manager | Elena Novak |
Thank you for the time your team has given us. We think the case for a single view of each merchant is a strong one, and we would be pleased to build it with you.
Unusual terms
Current to 9 Oct 26- EU region data residency inside customer Snowflake account