What was said
What this says
Current to 11 Oct 26Technical kickoff for Brenneck Pay's Growth brain. Katrin Vogelsang agreed a three-connector first wave, named owners and four acceptance checks. The helpdesk is left for a second wave and the audit log export is unconfirmed.
What happened: On 16 Feb 2026 Hamza Akhtar recapped the contract in place since 3 Feb 2026 on Growth with forty users. The group agreed the first wave: merchant master, CRM and risk case system.
Customer view: Katrin wants one trusted view of each merchant and wants good defined before data is shown. She asked for names not teams, and for citable documents rather than call statements.
Commercial: Spare connector slots are deliberately kept free, and call notes are a likely later request. The helpdesk owner sits in another department and Katrin will promise nothing until she has a yes.
Watch: Hamza must confirm in writing what the brain's activity log can export, by Friday. Jonas Albrecht will create the role by Thursday, but not before he has seen the unmatched merchant export.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Jonas Albrecht exports the unmatched merchants on Wednesday and creates the role by Thursday.
- Katrin Vogelsang names the risk case system owner by Thursday and introduces Jonas to the CRM administrator today.
- Hamza Akhtar confirms the audit log export in writing by Friday and sends a proposed first test load date.
Risks
Current to 9 Oct 26- The brain's activity log export is unconfirmed, and Katrin Vogelsang needs it as audit evidence.
- The helpdesk sits with another department and has no owner or commitment yet.
- The merchant mapping is only partly clean, and unmatched merchants could cost account managers' trust on day one.
Opportunities
Current to 9 Oct 26- Several of the eight Growth connector slots are kept free for sources teams ask for after the first results.
- Account management is expected to want call notes eventually, which would be a later connector.
Transcript
- Hamza Akhtar NoneHello, can you hear me all right? The recording says it's running, so that's a good start.
- Katrin Vogelsang NoneYes, good morning Hamza, I can hear you and see you. Jonas is still finishing something, I think he will join in a moment.
- Hamza Akhtar NoneNo problem at all, we'll give him a minute. How's your week started?
- Katrin Vogelsang NoneBusy, as Mondays are. We had a merchant escalation over the weekend, so I am a little behind. But I have the agenda, I sent it to you both yesterday evening. Did you receive it?
- Hamza Akhtar NoneI did, thank you. Four points, if I remember: the connectors and their order, who owns what on your side, the Snowflake access and the EU region, and then the minutes and next steps.
- Katrin Vogelsang NoneTo be precise, five. I added a short point at the end about what evidence we can show to an auditor. But yes, that is the shape.
- Jonas Albrecht NoneHi. Sorry. Was fixing a failed task on a different pipeline. Fixed now. I'm here.
- Hamza Akhtar NoneMorning Jonas. Good to have you. Nothing on fire, I hope?
- Jonas Albrecht NoneOnly a warehouse that was too small for a nightly job. I resized it. It was a schema change upstream, not our fault, but it was our problem.
- Katrin Vogelsang NoneThis is exactly why I want him on this call. Shall we begin? Hamza, would you like to start with where we are?
- Hamza Akhtar NoneYes, happy to. So, as a quick recap, the contract has been in place since 3 Feb 2026, you're on Growth, forty users, and the order form is fifty thousand pounds a year. Today is the kickoff for the technical side: I want us to leave with a connector order, a named owner for each, and a date for the first load.
- Katrin Vogelsang NoneGood. Let us agree the next step at the end of each point, so that nothing is left vague. I will take the minutes and send them today.
- Hamza Akhtar NonePerfect, thank you. And I'll send my own notes on the technical side, so you can compare.
- Katrin Vogelsang NonePlease do. I like two sets of notes, it is how we find the differences.
- Hamza Akhtar NoneFair enough. Right, connectors. Growth gives you up to eight. From the discovery notes I have your CRM, the payments platform export, the helpdesk, and the risk case system as the main ones. Is that still the picture, Katrin?
- Katrin Vogelsang NoneMostly. The goal, to be precise, is one view of each merchant. Account management sees the relationship, the contacts, the contract, and merchant risk sees the monitoring flags and the cases. At the moment they argue about whose spreadsheet is right.
- Hamza Akhtar NoneYes, I remember that from the demo. So the first two connectors should be the ones that give you that merchant identity. Which system holds the merchant ID that both teams trust?
- Katrin Vogelsang NoneThat is a good question, and I want a source for the answer, not my opinion. Jonas?
- Jonas Albrecht NoneThe merchant master table in Snowflake. Account management's CRM carries a copy, with a different key format. Risk uses the master key. I checked the load history last week, the master table is the only one that's complete.
- Hamza Akhtar NoneOkay, that's really useful. So we build the merchant spine on the master table and map the CRM key to it. Does the mapping exist somewhere, or do we create it?
- Jonas Albrecht NoneExists. Partly. About most merchants match on a clean key. The rest need a lookup. I'll export the unmatched ones so you can see them.
- Katrin Vogelsang NonePlease do that before we promise anything to the account managers. Otherwise they will find their own merchants missing and lose trust on the first day.
- Hamza Akhtar NoneAgreed. And I'd rather show a smaller set that's right than a larger set that's wrong. So, first step: Jonas exports the unmatched merchants, and I'll put together a mapping proposal from that.
- Katrin Vogelsang NoneLet us agree the next step. Jonas, by when can you export?
- Jonas Albrecht NoneWednesday. Not Friday, I don't change anything on a Friday. Wednesday gives us a day to look at it.
- Katrin Vogelsang NoneWednesday. Noted.
- Hamza Akhtar NoneGood. Second point is access, which I think is Jonas's favourite.
- Jonas Albrecht NoneWhich role has access? That's my favourite question, yes.
- Hamza Akhtar NoneRight, so here's how it works. The brain runs inside your own Snowflake account, so nothing leaves it. What I need from you is a dedicated role for the brain, with read access to the schemas you choose and write access to one schema that we own. Nothing else.
- Jonas Albrecht NoneGood. I'd create a service user, key pair authentication, no password. Role scoped to named schemas. No access to anything with card data. Tokenised references only.
- Katrin Vogelsang NoneI would like to understand that last point, for the minutes. The brain will not see card numbers at all?
- Jonas Albrecht NoneNot even masked. The role can't select from those schemas. I'll show you the grants when it's done, and you can hand them to the auditor.
- Hamza Akhtar NoneAnd that matches what we'd ask for. We never need the sensitive columns to answer questions about merchants. If a column's not granted, the brain simply doesn't know it exists.
- Katrin Vogelsang NoneGood. What is the source for that statement, Hamza? I want to be able to cite a document, not a call.
- Hamza Akhtar NoneFair. There's an architecture note and a data access summary in the onboarding pack. I'll point you to the exact pages in the email after this call, so you have something citable.
- Katrin Vogelsang NoneThank you. That is what I need.
- Jonas Albrecht NoneCan I ask about the EU region? Where does the compute for the brain run? In my account, or somewhere of yours?
- Hamza Akhtar NoneIn your account, in the region your Snowflake account sits in. For you that's an EU region, and that was a condition of the contract. Data residency is in the order form, so it isn't a favour, it's a commitment.
- Jonas Albrecht NoneOkay. I'll check the region setting anyway. I checked once, I'll check again, I don't like to assume.
- Katrin Vogelsang NoneI would be unhappy if you did not.
- Hamza Akhtar NonePlease do. If anything looks off, I want to hear it before we load a single row.
- Katrin Vogelsang NoneNow owners. This is point three. For each connector I want a name, not a team. In the past, with other projects, a team name meant nobody.
- Hamza Akhtar NoneCompletely agree. I'd suggest, as a starting point, Jonas owns the technical side of every connector: access, schema, refresh. And then a business owner per source, who can say whether the data looks right.
- Katrin Vogelsang NoneI can be the business owner for the merchant master and the CRM, since the account managers report to me. For the risk case system, it should be someone in merchant risk. I will ask the head of that team, and give you a name by Thursday.
- Hamza Akhtar NoneBrilliant. And the helpdesk? Is that your area or a different one?
- Katrin Vogelsang NoneSupport belongs to another department. The merchant tickets are useful for us, but I do not own the system. I will ask a colleague there, and I will not promise anything until I have a yes.
- Hamza Akhtar NoneThat's sensible. We can leave the helpdesk for the second wave, so it doesn't block the start.
- Jonas Albrecht NoneSecond wave is fine. Fewer moving parts first.
- Katrin Vogelsang NoneThen let me write that: first wave is the merchant master, the CRM and the risk case system. Second wave is the helpdesk and the rest. Correct?
- Hamza Akhtar NoneCorrect. And I'd keep a couple of the eight slots free, because teams always find one more source after they see the first results.
- Katrin Vogelsang NoneThat is probably true. Account management will want call notes eventually. Not now.
- Hamza Akhtar NoneNot now, no. Let's make the first thing work properly.
- Jonas Albrecht NoneOne more thing for the plan. The CRM connector. Who is the admin there? I need a service account created, and it isn't me.
- Katrin Vogelsang NoneA colleague in sales operations administers it. I will introduce you by email today. Please do not ask him directly before I have explained the project, he is careful, like you.
- Jonas Albrecht NoneGood. Careful people are fine with me.
- Hamza Akhtar NoneOkay. So on timing. What I'd propose is that once the role and the service user exist, I run the first load of the merchant master into the brain, in a test state, and we look at it together before anyone else sees it. Is that acceptable?
- Katrin Vogelsang NoneYes. And what do we look at, exactly? I would like to define what good means before we see the data.
- Hamza Akhtar NoneGood question. Three checks. Does the count of merchants in the brain match your master table. Do a handful of merchants you pick yourselves look complete. And does a question like, which merchants have an open risk case and a renewal due, return an answer you can verify.
- Jonas Albrecht NoneI'll add a fourth. Freshness. The nightly refresh should finish before seven in the morning, local time. I want to see the timestamps on it, not take it on trust.
- Hamza Akhtar NoneThat's a commitment on our side, every business day, so yes, I'll make the refresh log visible to you.
- Katrin Vogelsang NoneFour checks then. I will write them in the minutes exactly like that, so that we cannot argue later about what we agreed.
- Hamza Akhtar NoneGood. Now, users. You've got forty licensed users. Who do you want in first? I'd suggest a small group, a few account managers and a couple from risk, rather than everyone at once.
- Katrin Vogelsang NoneYes. I do not want forty people opening it on the first day and finding one bug. I will pick a pilot group, and I will include one sceptic on purpose.
- Hamza Akhtar NoneHa, a sceptic is the best tester. Honestly, they tell you the truth.
- Katrin Vogelsang NoneThis is why. There is one person in risk who will say, show me the source, and if the brain can answer that, everyone else will be fine.
- Jonas Albrecht NoneThat's my kind of user.
- Hamza Akhtar NoneMine too. Okay, last point on your agenda, the evidence for the auditor. What are you hoping to be able to show?
- Katrin Vogelsang NoneThree things. Where the data is held, and that it stays in the EU. Who can access it, and with which role. And what the brain did with it, meaning a log. The supervisor will ask, and I would like to answer with documents.
- Jonas Albrecht NoneWhere it's held and who can access it, I can produce from Snowflake itself. Grants, query history. The brain's activity log, that's on Hamza.
- Hamza Akhtar NoneUnderstood. I'll find out exactly what we can export from the activity side and confirm it in writing. I don't want to promise a format I haven't seen. Is that acceptable?
- Katrin Vogelsang NoneYes, that is the right answer. Please confirm by Friday, so that the note is not left open over the weekend.
- Hamza Akhtar NoneFriday it is. Noted.
- Katrin Vogelsang NoneThen let us recap, so the minutes are right. Jonas exports the unmatched merchants on Wednesday. Jonas creates the role and the service user and shows the grants. I introduce Jonas to the CRM administrator today and name the risk owner by Thursday. Hamza sends the architecture pages, the mapping proposal and the audit log answer. Is that all?
- Hamza Akhtar NoneThat's all of it, and one more: I'll send a proposed date for the first test load, once the role exists.
- Jonas Albrecht NoneRole by Thursday. Not before I've seen the export.
- Katrin Vogelsang NoneFine. Thank you both, this was efficient. I will send the minutes this afternoon.
- Hamza Akhtar NoneThanks, Katrin, thanks Jonas. Speak soon.
- Jonas Albrecht NoneCheers.
- Katrin Vogelsang NoneBye for now.