Oosterdijk Logistiek / BG-Demo – Demo
Callcompleted
Oosterdijk Logistiek · 23 Oct 2025 14:15
The 23 Oct 2025 demo confirmed Growth for Oosterdijk Logistiek: forty users, eight connectors, £44k annual plus £12k implementation. Targets are mid-December signature and late February go-live. Signature is not evidenced.
What was said
What this says
As at Fri 9 Oct 2026The 23 Oct 2025 demo confirmed Growth for Oosterdijk Logistiek: forty users, eight connectors, £44k annual plus £12k implementation. Targets are mid-December signature and late February go-live. Signature is not evidenced.
What happened: Matteo Ricci, newly on the account, ran the 23 Oct 2025 demo with Anya Petrova to confirm requirements with Lieke Hermans and Stijn Gielen. Anya said the WMS is connected and API access to three shippers is in hand.
Customer view: Lieke agreed the summary of unifying WMS, shipper and finance data for profitability and exception dashboards. Stijn confirmed Snowflake and said two weeks to prepare is reasonable.
Commercial: Matteo restated Growth at £44k annual plus £12k implementation, with forty users and eight connectors. Mid-December signature and late February go-live are targets, and the call does not show a signed order form.
Watch: Stijn is the main contact and the sole admin, so the account leans on one person. The call does not show who signs for Oosterdijk Logistiek.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Matteo Ricci to send the written summary of tier, price and timeline the day after the call.
- Matteo Ricci to send Stijn Gielen the technical readiness checklist covering Snowflake, credentials and API documentation.
- Stijn Gielen to prepare the Snowflake environment and shipper API keys once the contract is signed.
Risks
As at Fri 9 Oct 2026- Stijn Gielen is both main contact and sole admin, a key-person dependency from day one.
- Mid-December signature is a target only and no order form is evidenced.
- Go-live depends on the customer preparing Snowflake and shipper API keys within about two weeks.
Opportunities
As at Fri 9 Oct 2026- Growth subscription at £44,000 plus £12,000 implementation, with forty users and eight connectors.
- Profitability and exception dashboards give the customer a clear use case to build on.
Transcript
Matteo RicciGood afternoon, all. I'm Matteo, I've just joined BG-Demo, Priya's been leading your conversation, and I wanted to join in today to understand your technical requirements more deeply and confirm that we can deliver what you need. Shall we dive in?
Stijn GielenYeah, go ahead.- Matteo RicciRight. So from what I understand, you're looking to unify order data from your WMS, shipper systems, and finance, and you want to build dashboards around profitability and exception tracking. Is that a fair summary?
Lieke HermansThat's it.- Matteo RicciGood. Anya, let me ask, we've connected to their WMS already. What's the state of the shipper system integration?
Anya PetrovaWe're in good shape. I've got API access to three shippers, the ones that matter most for their volume. The data's clean and it maps well to the financial records.- Matteo RicciExcellent. Stijn, I want to confirm something with you: you've got your core data in Snowflake already, yes? The brain runs inside your environment, so we need you to have Snowflake if you don't already.
- Stijn GielenYeah, we're on Snowflake.
- Matteo RicciPerfect. That makes implementation straightforward. Anya, show them what that looks like from an architecture perspective?
- Anya PetrovaSure. So the brain is a layer on top of Snowflake. Your data stays in Snowflake, we add connectors that pull from your WMS, your shipper APIs, your accounting system. All of that flows into Snowflake, and the brain queries it. It's all inside your Snowflake account, so security-wise you're in control.
- Stijn GielenDo you manage the Snowflake account or do we?
- Matteo RicciYou do. We manage the brain software, you manage the Snowflake infrastructure. That keeps everything clean: you've got full audit trails, you control costs, and if something goes wrong with Snowflake, that's your infrastructure team. But the brain is our responsibility.
- Stijn GielenOkay, that makes sense.
- Matteo RicciRight. Now, from a timeline perspective, Priya told you mid-December for decision. If you sign then, how quickly can you be ready for implementation? Do you need time to prepare access credentials?
- Stijn GielenWe'd need a couple of weeks, probably. Get the Snowflake environment sorted, pull together API keys for the shippers. Two weeks is reasonable.
- Matteo RicciThat aligns well. So contract signed mid-December, you're ready in early January, and we go live in... Anya?
- Anya PetrovaEight weeks from January is basically the end of February. We'd be live in late February.
- Matteo RicciGood. Lieke, from your team's perspective, what's your bandwidth for supporting onboarding? Do you need someone dedicated?
- Lieke HermansWe can spare someone for most of it. Stijn's going to be the main contact, and I'll be in the QBRs and that kind of thing.
- Matteo RicciPerfect. And Stijn, will you be the technical owner: the person who owns access, manages users, that sort of thing?
- Stijn GielenYeah, I'll be the admin.
- Matteo RicciExcellent. Okay, so here's what I want to confirm in writing to you all: that Growth is the right tier, forty users, eight connectors. That we're targeting mid-December for signature and end of February for go-live. And that the investment is forty-four thousand annual plus twelve thousand implementation. Let me send you a summary after this call confirming all of that, yes?
- Lieke HermansYes, please.
- Matteo RicciAnd Stijn, I'll send you a technical readiness checklist, Snowflake, credentials, API documentation, that kind of thing. Once you've got that sorted, you let me know and we're ready to kick off onboarding.
- Stijn GielenThanks.
- Matteo RicciAny final questions from either of you?
- Lieke HermansI think we're good.
- Matteo RicciBrilliant. Then I'll follow up with those documents tomorrow. Cheers, all.