What was said
What this says
As at Fri 9 Oct 2026Hannah Lowe demoed the brain on Brakkevoort's sample extract. Pieter van Dam got the answers he needed on one view, own data and Snowflake residence, accepted nightly freshness, and asked for access control in writing.
What happened: Hannah ran the demo with Tom Ashdown on the sample extract, showing chat with links to source tickets and calls, a shipper page and a sketch dashboard. Pieter asked to see old untouched tickets and saw one shipper with several.
Customer view: Pieter said he wants exceptions seen before the shipper complains. He accepted that refresh is nightly, complete by 07:00 local time on business days, and called it acceptable for the review.
Commercial: Growth with the dashboards builder was confirmed, starting with three connectors and accounting as a possible fourth. Tom restated fifty-six thousand pounds all in, with the split to be confirmed in writing.
Watch: Pieter wants access control per shipper explained, and will say whether 21 March 2025 is realistic after his data lead reads the note. Marloes was not on this call.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Hannah Lowe to send the architecture note, connector list and access-control detail by the end of the week.
- Tom Ashdown to send proposal and order form as one pack to Pieter and Marloes.
- Tom Ashdown to book a short call with Pieter's data lead.
Risks
As at Fri 9 Oct 2026- Nightly refresh means exceptions raised during the day are not visible until the next morning.
- The data lead has not yet reviewed the architecture note, so the 21 Mar 2025 signing date is unconfirmed.
- Per-shipper access control must be stated exactly, as some account managers should not see all shippers.
Opportunities
As at Fri 9 Oct 2026- Growth tier with the dashboards builder for a Monday shipper review view.
- Accounting system as a fourth connector after the first three are settled.
Transcript
- Tom AshdownAfternoon, Pieter. Can you see and hear us okay?
- Pieter van DamYes. Good afternoon, Tom. Hello, Hannah.
- Hannah LoweHello, Pieter. Good to meet you properly.
- Tom AshdownHow's the week been? Vessels back on time, or are you still catching up from the last lot?
- Pieter van DamBetter. Not perfect. We had a customs hold on Tuesday and it took the whole afternoon. But that is actually a good example for today.
- Tom AshdownHa, ideal. Right, I'll hand over to Hannah, she's driving. Hannah, over to you.
- Hannah LoweThanks, Tom. Before I share anything, Pieter, what do you most need to know by the end of this hour? I'd rather aim at that than walk you through every page.
- Pieter van DamThree things. One: can an account manager open a shipper and see tickets, calls and account status in one place. Two: does it use our data, from the extract, not a demo shipper. Three: where does the data live, because my data lead will ask me and I need the answer.
- Hannah LoweGood, that's clear. I'll take them in that order and I'll put the third one in writing afterwards. Can you see my screen?
- Pieter van DamYes. I see a search box.
- Hannah LoweThat's the chat. This is loaded with the sample extract your team sent over, so these are your shippers. Let me ask it the question you just raised about customs holds. Which shippers had a customs hold exception open this week and have also spoken to us recently?
- Pieter van DamOkay. Let's see.
- Hannah LoweAnd there we are. It's given a short list, and each line links back to the ticket and the call it used. So you're not asked to trust the sentence, you can click through and check the source.
- Pieter van DamCan you open the first one? The one with the call.
- Hannah LoweSure. This is the shipper page. At the top, the account summary from the CRM. Below, the open exception tickets. And here, the recent call, with the transcript and a short summary.
- Pieter van DamSo the account manager sees the same story I see on Monday. But without five screens.
- Tom AshdownThat's the pitch in a sentence, honestly. Sorry, Hannah, carry on.
- Hannah LoweNo, that's right. To be precise, it isn't a replacement for the CRM or the helpdesk. They stay your systems of record. The brain reads from them and puts them together.
- Pieter van DamGood. Now the old tickets. I asked Tom last time. A ticket that is old and nobody touched. Can you show?
- Hannah LoweYes, that's a fair test, so let me ask it directly. Show open exception tickets with no update for a while, grouped by shipper. Give it a moment.
- Pieter van DamMm. There is one shipper with several. That one I know. They are not happy.
- Hannah LoweAnd that's the point. Because it's read together with the calls, you can see the last conversation was a week before the tickets went quiet. Whether that's a problem is your judgement, the brain just puts it in front of your account manager.
- Pieter van DamYes. That is what I want. Seen before the shipper complains.
- Tom AshdownCan I just jump in? Pieter, when you're picturing your account managers using this, is it each of them asking questions, or you building a view they all open on Monday?
- Pieter van DamBoth. First, I want a Monday view for the review. Then the managers ask their own questions. Let's make it concrete: one page, all shippers with open exceptions and the last contact date.
- Hannah LoweThat's what the dashboards builder is for, and it comes with the Growth tier. I can show you roughly what that looks like, but I'd flag that this one is a sketch I've built from your extract, not something finished.
- Pieter van DamA sketch is fine.
- Hannah LoweSo here, rows are shippers, columns are open exceptions, the most recent call and the account owner. You'd tune what's on it. The point is that it refreshes from the same layer the chat uses, so the two never disagree.
- Pieter van DamHow fresh? If a ticket opens at ten in the morning, is it here at ten past?
- Hannah LoweThe short answer is no. The longer answer is that the refresh runs nightly and it's complete by 07:00 your local time on business days. So Monday's review would reflect the weekend's activity but not something raised ten minutes ago. If you need live exceptions, the helpdesk itself stays the place for that.
- Pieter van DamOkay. That is acceptable for the review. I would rather know it now than be surprised later.
- Hannah LoweAgreed. I'd rather you knew. Now the third question, where the data lives. It's built and run inside your own Snowflake account. Nothing is copied to a store of ours. Your data team keeps control of the account, the access and the roles.
- Pieter van DamThat is the answer I need. Will they be able to see what you have built?
- Hannah LoweYes. That's one of the reasons I'd like to sit with your data lead. I can walk through the objects we create, so there's nothing hidden. I'll put the architecture in writing with a diagram, so she can read it without me.
- Tom AshdownAnd that's a good moment to say, if she's got security questions as well, Hannah's the one who'll take them, and she'll check anything she's not sure of before she answers.
- Hannah LoweYes. I won't guess on a security question. If I'm not certain, I'll go away and confirm and come back with it in writing.
- Pieter van DamGood. That is how I prefer it. Never a vague answer.
- Pieter van DamOne more. Which sources did you use for this extract? And what would be live in the real setup?
- Hannah LoweFor this demo: the CRM, the helpdesk and the call recorder. Those would be the first connectors. The accounting system you mentioned, Tom told me, is a possible fourth, for invoice disputes. Growth allows for several more, so there's room, but I'd start with the three and add the accounting system once the first are settled.
- Pieter van DamYes. Start with three. Then accounting. That is sensible.
- Tom AshdownAnd that matches how the implementation is scoped on the Growth tier, so no surprises on the plan. I'll put it all in the proposal.
- Pieter van DamAnd the proposal has the number you said to Marloes? Fifty-six thousand?
- Tom AshdownYes. Fifty-six thousand pounds all in, implementation included, as the deal currently stands. I'll confirm the split between the one-off fee and the subscription in writing, so Marloes has it as separate lines. I won't rely on memory for that.
- Pieter van DamGood. She will ask. She checks everything against the contract. She wants quarterly billing in advance.
- Tom AshdownYeah, we covered that on the first call, it's available on request. It'll be in the pack.
- Pieter van DamOkay. Now: what is the plan from here? Be concrete.
- Tom AshdownSo, three things. Hannah sends the architecture note and the connector list to you and your data lead. I send the proposal and the order form as one pack, to you and Marloes. And we get a short call in the diary with your data lead. Our working target for signing is still 21 March 2025.
- Pieter van DamI will tell you after my data lead reads the note whether that date is realistic. I do not want to promise something I cannot keep.
- Tom AshdownThat's all I'd ask. No drama if it moves. Better to get it right.
- Hannah LoweI'll send the note by the end of the week, Pieter. Anything else you'd like me to include? Questions I haven't covered?
- Pieter van DamInclude how the access is controlled. Who sees which shipper. Some account managers should not see all shippers.
- Hannah LoweNoted. I'll put that in writing, and I'll be careful to state exactly what is controlled and how, nothing broader than that.
- Pieter van DamGood. Thank you both. This was concrete. Groet.
- Tom AshdownCheers, Pieter. Speak soon. Thanks, Hannah.
- Hannah LoweThanks, both. Bye for now.