Brenneck Pay / BB-Demo – Onboarding
Callcompleted
Brenneck Pay: documents · 2026-03-23 12:00
Structured onboarding with Katrin Vogelsang and Jonas Albrecht. The goal is one sourced view per merchant. Four connectors go first, a read-only role is targeted for Thursday, and an untrusted status mapping must be cleaned first.
What was said
What this says
Current to 11 Oct 26Structured onboarding with Katrin Vogelsang and Jonas Albrecht. The goal is one sourced view per merchant. Four connectors go first, a read-only role is targeted for Thursday, and an untrusted status mapping must be cleaned first.
What happened: Katrin Vogelsang ran the agenda and minutes on 23 Mar 2026, with Jonas Albrecht joining late. They agreed the first-wave connectors, the access route and an audit pack built as they go.
Customer view: Katrin wants one sourced view of each merchant for account management and merchant risk, and a document she can show BaFin. Her test is whether every answer can be clicked through to its source.
Commercial: Procurement asked whether the order form is final. Hamza Akhtar confirmed Growth, forty users, £50k a year, and named Matteo Ricci as account owner and Elena Novak as CSM; Katrin wants Elena at the second session.
Watch: Three slip points were named: access, the CRM administrator and the status mapping. Only three of forty licences are active until the visibility table is agreed.
Themes
Current to 9 Oct 26Theme
Onboarding scope and audit
Importance
neutral
Sentiment
positive
Voice
decision-maker
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Hamza sends the object list early next week and Jonas creates the read-only role, target Thursday.
- Hamza drafts the data flow note by Thursday and the visibility table for review.
- Katrin names the pilot users and sends the weekly Tuesday invitation.
Risks
Current to 9 Oct 26- The implementation can slip on access, the CRM administrator's availability or the status mapping clean-up.
- Merchant status has three values Jonas does not trust, so early answers could be wrong.
- Risk notes are sensitive, so visibility rules must be agreed before they are connected.
Opportunities
Current to 9 Oct 26- Four of eight connectors in the first wave leaves room for finance and email later.
- A pilot across account management and merchant risk could extend use of the forty licences.
Transcript
Hamza Akhtar NoneHello, Katrin. Can you hear me alright? I can see you, but the audio was a bit thin a second ago.
Katrin Vogelsang NoneYes, hello Hamza, I hear you clearly now. Jonas is still on the way. He wrote that he is closing something off in the warehouse and will join in a few minutes.- Hamza Akhtar NoneNo problem at all. We have forty-five minutes, so we can start with the easy part. How is the week going?
- Katrin Vogelsang NoneBusy, but a good busy. It is raining in Frankfurt, which I think is our national weather. And in London?
- Hamza Akhtar NoneGrey, and a bit of drizzle. So the same, just with worse coffee.
- Katrin Vogelsang NoneHa. Good. I put a written agenda in the chat, you should see it. Five points, to be precise: goals and scope, the sources and connectors, access and the EU region, owners and dates, and then the minutes.
- Hamza Akhtar NoneGot it, thank you. That is tidier than mine, so let us use yours. I will take my own notes, but you keep the minutes.
- Katrin Vogelsang NoneOf course, I always do. And let us agree the next step at the end of each point, not only at the end of the call.
Jonas Albrecht NoneHi. Sorry. A load failed on an unrelated pipeline. I checked the load history, it was a schema change upstream, a column renamed without a word to anyone. Fixed now.- Hamza Akhtar NoneHello Jonas. Sounds like a proper Monday.
- Jonas Albrecht NoneIt is a Monday. That is the whole story.
- Katrin Vogelsang NoneJonas, we are at point one, goals and scope. I will go through it quickly so you are in.
- Katrin Vogelsang NoneWhat we bought is Growth, forty users, and the reason is simple. Today our merchant account managers look at one system, merchant risk looks at another, and when a merchant is unhappy or flagged, the two teams spend the first meeting just agreeing what the facts are. I want one view of each merchant, with a source behind every statement.
- Hamza Akhtar NoneThat matches what we scoped with Matteo and Elena. One view per merchant, shared by account management and merchant risk, running inside your own Snowflake account, with the data kept in an EU region.
- Katrin Vogelsang NoneYes. And what is the source, when the brain answers? That is my first question every time. If it says a merchant's chargeback pattern has changed, I need to click through to where that came from.
- Hamza Akhtar NoneEvery answer carries its references back to the record it was built from. The page, the ticket, the call, the table row. If there is no source, it says so, it does not guess. I can show you that on your own data once the first connector is live, which is better than me promising it now.
- Katrin Vogelsang NoneGood. Then point one, next step: I will write the three questions we want answered first, and you tell me which ones the first connectors can really support.
- Hamza Akhtar NoneAgreed. Send them over and I will mark each one as yes, partly, or not yet.
- Jonas Albrecht NoneCan I ask something before we move on? Scope. Growth has eight connectors. Which ones are we actually using? I do not want to spend them on things we turn off in six months.
- Hamza Akhtar NoneFair. Let us go through that now, it is point two anyway. My suggestion for the first wave is your CRM, for the merchant accounts and the owners. The helpdesk, for merchant tickets. The call recorder, for what account managers actually say to merchants. And the transaction summaries you already have in Snowflake.
- Katrin Vogelsang NoneYes. And the merchant risk notes. At the moment they live partly in documents and partly in a shared mailbox, which is not what I would call a system.
- Jonas Albrecht NoneThe mailbox is a problem. Mixed content, personal data, no structure. I would not connect it in the first wave.
- Katrin Vogelsang NoneI agree with Jonas, to be precise. Let us first move the risk notes into the document store properly, and then connect that. The mailbox waits.
- Hamza Akhtar NoneThat is sensible. It also leaves you spare connectors, so the first wave uses four of the eight and you keep room for finance and email later, once you are sure what you want from them.
- Jonas Albrecht NoneFour. Fine. The transaction data is the one I care about. It is already in Snowflake, in a curated schema. Two schemas, actually, one raw, one modelled. The brain reads the modelled one only.
- Hamza Akhtar NoneUnderstood. So which role has access, is what you will ask me. And my answer is that we want a dedicated role for the brain, read only, on the named schemas and nothing else.
- Jonas Albrecht NoneGood, that is my line. I will create the role myself. I do not grant access by email, and I will not do it from a ticket either. You send me the list of objects you need, I review it, I create the role, and I document it.
- Hamza Akhtar NoneThat works for us. I will send the list as a document, with each object and the reason we need it. If something is not on your approved list, we will not ask for it informally.
- Jonas Albrecht NoneAnd the timing. I do not change production on a Friday. So if the list comes late in the week, it waits until Monday. Just so nobody is surprised.
- Katrin Vogelsang NoneNoted, and I will put that in the minutes, Jonas. It is a good rule, I do not want to argue with it.
- Hamza Akhtar NoneNor do I. So the list goes to you early next week, and you have the role in place before the end of that week, ideally by Thursday.
- Jonas Albrecht NoneThursday is possible. If the list is clean.
- Katrin Vogelsang NoneLet us agree it then. Hamza sends the object list, Jonas reviews and creates the role, target Thursday. I have written it down.
- Hamza Akhtar NonePerfect.
- Katrin Vogelsang NoneSorry, I was writing the minutes for point two. Hamza, one more thing there. The CRM. Who connects it, and with which user? Our CRM administrator is not on this call.
- Hamza Akhtar NoneSomeone in your team needs to create an integration user with read access, and approve it from the CRM side. It would be good to have your CRM administrator on a short call, perhaps twenty minutes, just for that. I do not want to guess at the permission model of your CRM.
- Katrin Vogelsang NoneThat is correct. I will ask our CRM administrator to join the next session. Please send me two sentences describing what he needs to prepare, so he does not come unprepared.
- Hamza Akhtar NoneYes, I will send that today.
- Jonas Albrecht NoneHamza, the helpdesk. We have one ticket open with you at the moment, as far as I know. That one was mine.
- Hamza Akhtar NoneYes, I saw it. It was a how-to about the service user and key pair authentication for the connection into Snowflake. I believe it was answered.
- Jonas Albrecht NoneAnswered, tested, closed. I tested it before I believed it. One ticket in a month, I would say that is a good sign, or a sign we have not done anything yet.
- Hamza Akhtar NoneBoth, probably. It will get busier once the connectors go in, and that is normal. I would rather have the questions early.
- Katrin Vogelsang NonePoint three, then: access and the EU region. Jonas, can you say where we stand?
- Jonas Albrecht NoneShort version. The Snowflake account is in an EU region. Everything the brain stores, the indexes and the embeddings, lives in that account, so it stays in the EU. What I need in writing is exactly what leaves the account, if anything, and for what.
- Hamza Akhtar NoneThe honest answer is that the data and the index stay inside your account. What does involve a call outside is the language model that writes the answers, and I do not want to hand-wave on that one. I will give you a written description of the data flow, in particular which text snippets are sent to the model for an answer, where that is processed, and what is retained. If it is not in the document, do not assume it.
- Jonas Albrecht NoneGood. That is the right way round. Send it, I will test it against what I see in the network logs, and then I will sign it off.
- Katrin Vogelsang NoneAnd for the auditor. We are supervised by BaFin, and when they come, I need a document I can put in front of them. Not a presentation. A description of the data flow, the access model, and who approved it, with dates.
- Hamza Akhtar NoneUnderstood. I would suggest we build that as we go. Each step, the role creation, the connector approval, the data flow note, gets a short record with who did it and when. At the end you have one pack and nobody has to reconstruct it.
- Jonas Albrecht NoneI like that. Documentation I can hand to an auditor is the thing. If it is built afterwards, it is fiction.
- Katrin Vogelsang NoneExactly. Let us agree the next step: Hamza prepares the data flow note and the structure of the audit pack, Jonas reviews. I put it in the minutes with the owner and a date, and we revisit it at the next session.
- Hamza Akhtar NoneFine by me. I can have a first version of the note by the end of the week.
- Jonas Albrecht NoneNot Friday.
- Hamza Akhtar NoneHa. Thursday, then. I hear you.
- Katrin Vogelsang NoneNow users. We have forty licences, and as far as I see, three of us are active at the moment. That is you two and one colleague from merchant risk. Hamza, how do you suggest we bring in the rest?
- Hamza Akhtar NoneI would not switch on forty people on the first day. If they open it and the data is thin, they decide it is not useful, and it is very hard to change that opinion afterwards. I would take a small group from account management and a small group from merchant risk, the people who really sit in the same merchant discussions, and let them use it for a couple of weeks on real cases.
- Katrin Vogelsang NoneThat is how I thought about it too. Account managers first, because they ask the most questions about merchants. Then merchant risk. I do not want to give licences to people who will not use them.
- Jonas Albrecht NoneI need to know who gets which rights inside the brain. Who can see what. Risk notes are not for everyone.
- Hamza Akhtar NoneRight, and that is a design question we should answer before the notes are connected, not after. Visibility follows the source system's permissions where we can, and where we cannot, we set it by group. I will draft a simple table, group by group, and you correct it.
- Katrin Vogelsang NoneI will help with that. The risk team lead should be consulted. To be precise, I do not want to decide on behalf of merchant risk what they may share.
- Hamza Akhtar NoneQuite right. So, next step on users: you name the pilot people from each team, I draft the visibility table, and we review it together before anyone outside the pilot is invited.
- Katrin Vogelsang NoneYes. I will write the names to you directly, not to the whole list.
- Jonas Albrecht NoneSorry, I was checking something while you were talking. The modelled schema has a column for merchant status, and it has three values that I do not trust. Someone changed the coding last year. I want that cleaned before the brain reads it, otherwise it will confidently tell Katrin something wrong.
- Katrin Vogelsang NoneThat is exactly the kind of thing I want to know now. Jonas, what is the source of the status? Which system sets it?
- Jonas Albrecht NoneThe onboarding platform, via a nightly job. The job is fine. What changed is the mapping in the model, a schema change on our side. I will write down the old and new mapping and give it to Hamza.
- Hamza Akhtar NonePlease do. If the brain knows the mapping, it can say which version it used. And I would rather flag it in the first answers than hide it.
- Katrin Vogelsang NoneGood. Put that in as an open item with Jonas as the owner.
- Jonas Albrecht NoneOwner Jonas. Fine.
- Hamza Akhtar NoneLet me say a word on the timeline, which is point four. The implementation is eight weeks from the start. The first two are access and the first connectors, then the CRM and helpdesk, then the call recorder, and by the middle of it we should be looking at real merchants with the pilot group.
- Katrin Vogelsang NoneEight weeks. What are the points where it can slip? Please tell me now, not in week six.
- Hamza Akhtar NoneHonestly, three. Access, if the role takes longer than a week. The CRM administrator being unavailable. And the status mapping if the cleaning turns out larger than it looks. Everything else I can handle on our side.
- Jonas Albrecht NoneThe mapping will not be large. A day, maybe two, if nobody changes it again.
- Katrin Vogelsang NoneThen let us write those three as risks in the minutes, each with an owner. Access is Jonas, the CRM administrator is me, the mapping is Jonas again.
- Jonas Albrecht NoneI am being given a lot of homework.
- Hamza Akhtar NoneYou are the admin. It comes with the badge.
- Katrin Vogelsang NoneHamza, who on your side do we call about commercial things? Procurement on our side asked me whether the order form is final. They have it as Growth, fifty thousand a year, forty users.
- Hamza Akhtar NoneThat matches what I have: Growth, forty users, fifty thousand a year, and the contract runs for the first year from the start in February, so it renews a year on. Anything commercial, Matteo Ricci is your account owner. Once we are live, Elena Novak is your customer success manager and she will run the quarterly reviews with you.
- Katrin Vogelsang NoneGood. I will tell procurement that the numbers agree. And I would like Elena at the second session already, so she knows what we promised each other.
- Hamza Akhtar NoneI will ask her. I think she will want that anyway.
- Jonas Albrecht NoneOne more technical point, then I am quiet. Refresh. When does the brain refresh from the sources? If account managers read this before a merchant call at the start of the day, it must be current.
- Hamza Akhtar NoneThe nightly refresh completes by 07:00 your local time on business days. That is across all tiers. If you want to know whether it ran, the load history shows it, and we will show your team where to look.
- Jonas Albrecht NoneGood. I will check the load history myself in the first weeks. I trust what I see more than a promise.
- Hamza Akhtar NoneI would expect nothing less.
- Katrin Vogelsang NoneLet me use a minute for the other side. Hamza, what do you need from us that we have not yet said? I do not want to find out later that we forgot something obvious.
- Hamza Akhtar NoneThree things. A named person who can answer questions about the merchant data from the business side, I assume that is you. A contact for the helpdesk and call recorder administrators. And a regular slot, even if it is only thirty minutes, so that issues are discussed while they are small.
- Katrin Vogelsang NoneI will take the first. The administrators I will find by the end of the week. And the slot, let us do weekly, same day, same time. I will send an invitation.
- Jonas Albrecht NoneNot Friday afternoon.
- Katrin Vogelsang NoneNot Friday. Tuesday, I think. I will look at the calendars.
- Hamza Akhtar NoneTuesday works for me.
- Katrin Vogelsang NoneThen the last point, the minutes. I will read back what I have so you can correct me. Goals: one merchant view for account management and merchant risk, with a source behind every answer. Connectors in the first wave: CRM, helpdesk, call recorder and the modelled transaction schema. The mailbox waits until the risk notes are in the document store.
- Katrin Vogelsang NoneAccess: Hamza sends the object list early next week, Jonas reviews and creates a read-only role, target Thursday, nothing on a Friday. Hamza also writes the data flow note, first version Thursday, Jonas tests it against the logs. The audit pack is built as we go.
- Jonas Albrecht NoneCorrect. One addition: the status mapping, old and new, from me to Hamza. Before the model is connected.
- Katrin Vogelsang NoneAdded. Users: pilot group named by me, from account management and merchant risk, a visibility table drafted by Hamza and reviewed by me, the risk team lead, and Jonas. Nobody else is invited before that.
- Hamza Akhtar NoneThat is complete as far as I can tell. Two of mine to add: the short note for your CRM administrator today, and asking Elena to join the second session.
- Katrin Vogelsang NoneYes, both are in. And the weekly slot, Tuesday, I send the invitation. Anything missing?
- Jonas Albrecht NoneNothing missing. I would only say, if the object list is vague, I will send it back. Not personal.
- Hamza Akhtar NonePlease do. I would rather have it sent back than approved by mistake.
- Katrin Vogelsang NoneThen I will send the minutes this afternoon, and each of you confirms or corrects in writing. Please do not only say fine, say what you are fine with.
- Jonas Albrecht NoneUnderstood.
- Hamza Akhtar NoneWill do. And thank you both, this was a very clear session. Most onboarding calls do not leave me with a list this specific.
- Katrin Vogelsang NoneThat is the idea. Precision now saves us arguments in week six.
- Jonas Albrecht NoneI will go back to my broken pipeline, then. Speak on Tuesday.
- Hamza Akhtar NoneGood luck with it. Speak on Tuesday.
- Katrin Vogelsang NoneThank you, both. Goodbye for now.
- Hamza Akhtar NoneGoodbye, Katrin. Bye, Jonas.
Callsmade from