Matteo Ricci

Brenneck Pay / BB-Demo – Negotiation

Callcompleted

Brenneck Pay: documents logo Brenneck Pay: documents · 2026-10-05 13:30

Matthias Ebner, COO, will not close the Growth to Enterprise expansion on the expected Wednesday. Information security has not reviewed the pack, and the Growth term treatment and exit wording are open.

What was said

What this says

Current to 11 Oct 26

Matthias Ebner, COO, will not close the Growth to Enterprise expansion on the expected Wednesday. Information security has not reviewed the pack, and the Growth term treatment and exit wording are open.

What happened: Matteo Ricci and Owen Tallis negotiated the expansion with Matthias, Dennis Wolter and Henrik Lorenz on 5 Oct 2026. Matteo told the customer the CRM close date was not credible and said he would move it.

Customer view: Matthias wants everything in writing and will not sign until information security and procurement have each confirmed. His case for Enterprise is compliance and security rather than user count.

Commercial: Owen clarified that £125,000 is the total value of the deal, covering implementation and the first year of subscription, not an annual price. Treatment of the unused Growth term is a pricing exception that needs Owen's sign-off, and Dennis wants an answer that week.

Watch: The outsourcing register, which BaFin reviews, must be consistent before signing. Extras such as a named engineer or sandbox were deferred.

AI · claude-sonnet-5-5 · 11 Oct 2026

Themes

Current to 9 Oct 26
Theme
Enterprise expansion terms
Importance
upsell
Sentiment
mixed
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Owen sends Dennis the price split and a yes or no on the Growth term, with reasons, by the end of that week.
  • Matteo sends one numbered written summary and moves the CRM close date.
  • Henrik sends the register template and the information security contact within a day.

Risks

Current to 9 Oct 26
  • Information security has not returned the review pack, so the close date has slipped with no new date.
  • The unused Growth term is a pricing exception needing Owen Tallis's sign-off, and the exit wording is also open.
  • The outsourcing register entry must be consistent before anything is signed.

Opportunities

Current to 9 Oct 26
  • Enterprise company-wide, with the compliance function asking to be included and data staying in the EU region.
  • Quarterly payment was welcomed by Dennis, which could ease the commercial terms.
  • Named engineer and sandbox add-ons can be discussed separately once base terms are settled.

Transcript

  1. Matteo Ricci
    Matteo Ricci None
    Good afternoon, everyone. Can you hear me all right? I had to switch headsets, so tell me if I sound like I'm at the bottom of a well.
  2. Henrik Lorenz
    Henrik Lorenz None
    Clear from here. Afternoon, Matteo.
  3. Dennis Wolter
    Dennis Wolter None
    Yes, fine. Hello. I will have to leave a few minutes before the end, I have a close meeting at two o'clock, but I think we can manage.
  4. Owen Tallis
    Owen Tallis None
    Afternoon all. Owen here, I'm joining Matteo today because there is a pricing question on the table and it's better a senior name is on the call. Matthias, good to speak again.
  5. Matthias Ebner
    Matthias Ebner None
    Good afternoon, Owen. Good afternoon, everyone. Let me restate the decision needed today. We must decide whether the expansion from Growth to Enterprise goes forward, and on what written terms. I do not need a demonstration.
  6. Matteo Ricci
    Matteo Ricci None
    Thank you, Matthias, that is exactly how I would frame it. And the timeline, so we are all looking at the same page: the deal in our system carries an expected close of Wednesday this week. I would rather you heard from me early if I think that date is under pressure, so I will come back to it at the end.
  7. Owen Tallis
    Owen Tallis None
    Yes. So, where does it stand against Wednesday? That's my only question for now, and I'm happy to wait for the answer.
  8. Matteo Ricci
    Matteo Ricci None
    Commercially we are close. Scope is agreed in principle: Enterprise, company-wide, the data staying in the EU region as it is today. What is open is price presentation, the relationship with the existing Growth contract, and the security review. Those three.
  9. Henrik Lorenz
    Henrik Lorenz None
    Right. From procurement's side, I would add a fourth. The outsourcing register. If Enterprise changes the scope of what you do for us, the register entry changes, and that has to be consistent before anything is signed.
  10. Matthias Ebner
    Matthias Ebner None
    Correct. Please keep that in the list. I will not sign before information security and procurement have each confirmed in writing.
  11. Matteo Ricci
    Matteo Ricci None
    Understood, and we would not ask you to. Let me take them in order, if that works. Price first, because Dennis has to leave early.
  12. Dennis Wolter
    Dennis Wolter None
    Thank you. My question is simple. The paper I have shows a total of one hundred and twenty-five thousand pounds. What exactly is in that number?
  13. Owen Tallis
    Owen Tallis None
    Fair. The £125,000 is the total value of this deal, not an annual price. It includes the one-off implementation, which is a fixed fee for Enterprise, and it includes the first year of the subscription. I'd rather be precise than let you read it as a run rate.
  14. Dennis Wolter
    Dennis Wolter None
    So the implementation is inside it. Not a separate invoice later.
  15. Owen Tallis
    Owen Tallis None
    Inside the total, yes. I'll send you the split in writing so finance can book it properly. Subscription is annual in advance, quarterly if you ask for it, thirty-day terms.
  16. Dennis Wolter
    Dennis Wolter None
    Quarterly would help us. And the current contract? You currently invoice us fifty thousand a year for Growth, and that runs to the second of February next year. I do not want to pay for Growth and Enterprise at the same time.
  17. Matteo Ricci
    Matteo Ricci None
    No, that would not make sense, and nobody is proposing it. Let me confirm that in writing, but the intent is that Enterprise replaces Growth from the start of the new scope, and the existing order form is dealt with in the same document so there is no overlap.
  18. Owen Tallis
    Owen Tallis None
    Right, and that is the bit I need to take away, Dennis. How the unused part of the Growth term is treated is a pricing exception, so it needs my sign-off, not Matteo's. I'm not going to give you a number on a call.
  19. Dennis Wolter
    Dennis Wolter None
    Fine. But I would like an answer before the end of this week. If the answer is no credit, I need to know that too.
  20. Owen Tallis
    Owen Tallis None
    Fair enough. You'll have a yes or a no, with the reason, in writing. Not a maybe.
  21. Matthias Ebner
    Matthias Ebner None
    Dennis, anything else on cost?
  22. Dennis Wolter
    Dennis Wolter None
    Yes. Predictability. Matthias cares about this and so do I. What happens at the next renewal? The renewal date for the current agreement is the third of February 2027. Will the price move then?
  23. Owen Tallis
    Owen Tallis None
    Good question, and the honest answer is that it depends on what we write. Any discount applies to the first term only. I don't quote a discount beyond that, and I'd be doing you no favours if I implied otherwise. What I can do is put the subscription price for the following term in the order form so it is not a surprise.
  24. Matthias Ebner
    Matthias Ebner None
    That is what I would like. Please send it in writing.
  25. Owen Tallis
    Owen Tallis None
    Will do. Dated, with the figure and the unit.
  26. Henrik Lorenz
    Henrik Lorenz None
    Can I come in on that? From a procurement perspective we would also want a ceiling on any change during the term. Not just the renewal.
  27. Owen Tallis
    Owen Tallis None
    Mm. In the term, the order form is the price. It doesn't move unless you ask us to add something, more users or more connectors, and then you see the price before you agree.
  28. Henrik Lorenz
    Henrik Lorenz None
    Good. Then that is acceptable in principle. I still want to see the wording.
  29. Matteo Ricci
    Matteo Ricci None
    Of course. Let me move to scope, because I think it is worth saying aloud what Enterprise does and does not change for you. Today you are on forty licensed users and a limited set of connectors. Enterprise takes you to a hundred and fifty users and twenty connectors, and it adds single sign-on and SCIM, an executive sponsor on our side, and the higher service levels.
  30. Matthias Ebner
    Matthias Ebner None
    Which service levels, specifically? We are supervised. I need to be able to point to a document.
  31. Matteo Ricci
    Matteo Ricci None
    Availability moves up one step, the first response time on a priority incident is shorter, and the service credits then cover data freshness as well as availability, which Growth does not. The nightly refresh has the same commitment on every tier. I will put the exact wording in the order form schedule rather than paraphrase it from memory.
  32. Matthias Ebner
    Matthias Ebner None
    Please do. And what is the exit plan? If we leave, what happens to the data and the models you have built in our environment?
  33. Matteo Ricci
    Matteo Ricci None
    This is the part I like to answer plainly. The brain is built and run inside your own Snowflake account, so the data never leaves your environment. If the contract ended, the tables and the structures are already yours. What you would lose is our ongoing maintenance of the connectors and the interface layer.
  34. Matthias Ebner
    Matthias Ebner None
    That is good. I want that sentence in the contract, not only said on a call.
  35. Matteo Ricci
    Matteo Ricci None
    Yes. I'll draft it with our legal team and send it to Henrik first, so he can review the wording before it reaches you.
  36. Henrik Lorenz
    Henrik Lorenz None
    That works. Matteo, is the exit and transition support itself a chargeable item?
  37. Matteo Ricci
    Matteo Ricci None
    I do not want to say yes or no from memory. Let me confirm that in writing. I would rather give you a correct answer on Tuesday than a quick one now.
  38. Owen Tallis
    Owen Tallis None
    And to be clear, we won't hold you to a position because we ran out of time on a call. If it's not in the paper, it's not agreed.
  39. Matthias Ebner
    Matthias Ebner None
    That is the correct approach. An undocumented promise is of no use to me.
  40. Dennis Wolter
    Dennis Wolter None
    Sorry, one last thing before I drop off. The usage. Why are we expanding? I look at the invoice, I see forty users, and I am told usage is modest. Who is asking for this?
  41. Matthias Ebner
    Matthias Ebner None
    I can answer that, Dennis. Merchant risk and the account managers use it now, and the compliance function has asked to be included. That is the reason for the wider scope. It is not about the number of users in the first month.
  42. Matteo Ricci
    Matteo Ricci None
    And if I may add, usage has been growing quarter on quarter, from a small base. There have been no support tickets at all recently, which I read as people simply getting on with it. But I agree with Matthias, the case for Enterprise is the compliance and security side more than the user count.
  43. Dennis Wolter
    Dennis Wolter None
    Fine. That is a helpful answer. I have to go. Owen, please send me the split and the answer on the Growth term. Thank you all.
  44. Owen Tallis
    Owen Tallis None
    Will do, Dennis. Thanks for your time.
  45. Matteo Ricci
    Matteo Ricci None
    Thank you, Dennis.
  46. Henrik Lorenz
    Henrik Lorenz None
    Right. Now that Dennis has gone, can we talk about the security review? My understanding is that information security has not yet seen the full pack.
  47. Matteo Ricci
    Matteo Ricci None
    That is correct, and this is the point where I would rather you heard it from me. The pack has gone to your information security team, but they have not come back. Enterprise includes support for the review in the implementation, and our security lead is ready to join a session with them whenever they want. What I cannot do is tell you what they will find, or when they will finish.
  48. Matthias Ebner
    Matthias Ebner None
    Then Wednesday is not realistic.
  49. Matteo Ricci
    Matteo Ricci None
    I think that is a fair reading. I would not like you to sign on Wednesday under pressure, and I would not like us to record a close date we do not believe. I will move it in our system as soon as we hang up.
  50. Owen Tallis
    Owen Tallis None
    Agreed. I won't leave a hopeful date sitting there. Matteo, what's the next dated step?
  51. Matteo Ricci
    Matteo Ricci None
    Henrik, may I ask you something? Who in information security should receive our request for a session, and do they have a preferred format?
  52. Henrik Lorenz
    Henrik Lorenz None
    I will find out and tell you today. I do not want to give you a name I am not sure of. They work from a questionnaire first, then a call if needed.
  53. Matteo Ricci
    Matteo Ricci None
    That is fine. Please send the questionnaire and we will complete it, with our security lead, before the call, not after. And what does your regulator need to see, in terms of the register? Is there a standard format?
  54. Matthias Ebner
    Matthias Ebner None
    There is. The outsourcing register is mine, and BaFin reviews it. The entry must describe the function, the location of the data, the sub-processors and the exit arrangements. Henrik maintains the file. I do not discuss the detail, I have delegated it.
  55. Henrik Lorenz
    Henrik Lorenz None
    Right. I will send you the template, Matteo, the blank one, so you can see which fields we need from you. Mostly those four.
  56. Matteo Ricci
    Matteo Ricci None
    Perfect. We will fill in the parts that are ours and flag anything we cannot answer, rather than guess.
  57. Owen Tallis
    Owen Tallis None
    Can I ask a question, Matthias? Assuming security comes back clean, is there anything on price or scope that would still stop you?
  58. Matthias Ebner
    Matthias Ebner None
    Two things. The treatment of the current Growth term, as Dennis said. And the exit wording. If both are in the document, and the two functions have confirmed, I see no reason to delay.
  59. Owen Tallis
    Owen Tallis None
    Good. Then those are the two I own with Matteo. Anything you want in the Enterprise support side that we haven't covered, such as the named engineer or a sandbox?
  60. Matthias Ebner
    Matthias Ebner None
    Not at this point. I would prefer to settle the base terms first. We can discuss additions later, and separately.
  61. Owen Tallis
    Owen Tallis None
    Sensible. Let's not stack extras on a deal that isn't through security yet.
  62. Henrik Lorenz
    Henrik Lorenz None
    One more from me, a small one. The paper names the order form under the master agreement we already have. Will this be an amendment or a new order form?
  63. Matteo Ricci
    Matteo Ricci None
    A new order form under the existing master agreement, I believe, with the Growth order form referred to so that it is clearly superseded from the start date. But let me confirm that with legal in writing before you rely on it.
  64. Henrik Lorenz
    Henrik Lorenz None
    Thank you. That is what I expected.
  65. Matthias Ebner
    Matthias Ebner None
    So, to summarise. We will not close on Wednesday. Information security reviews the pack. Procurement reviews the wording. We receive in writing the price split, the Growth term treatment, the exit clause and the service level schedule. Then we decide.
  66. Matteo Ricci
    Matteo Ricci None
    That is exactly right. I would only add that I will send a single written summary after this call, with those items numbered, so nothing depends on anyone's memory.
  67. Owen Tallis
    Owen Tallis None
    And I'll put the Growth term answer in that same note, or straight after, but by the end of this week as promised.
  68. Henrik Lorenz
    Henrik Lorenz None
    Good. I will send the register template and the name for security today, or tomorrow morning at the latest.
  69. Matthias Ebner
    Matthias Ebner None
    Thank you, all. Matteo, I appreciate that you told us about the date directly.
  70. Matteo Ricci
    Matteo Ricci None
    Thank you, Matthias. It is always better that way. Best regards to you all, and speak soon.
  71. Owen Tallis
    Owen Tallis None
    Thanks everyone. Speak soon.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

HelpAsk B

Ask B

B-Brain · read-only