What was said
What this says
Current to 11 Oct 26Marcus Bell sends the formal Growth renewal notice. Craig Oduya says the contract is in a supplier review, they are building in-house on Microsoft, and he asks about exit and termination wording. He will not discuss renewal.
Ask: Craig wants the exit position for the data and pipelines in Calderbrook's Snowflake account, and the notice and termination wording from the contract.
Customer view: he said every supplier contract is under review and the capability is being built in-house, so low usage is expected. He is not in a position to talk about renewal.
Next: Marcus offered a note of what is configured, and Tom Ashdown is to send the wording. The thread does not show the renewal outcome or whether it was signed by the 1 Sep 2026 term end.
The thread
Updated 9 Oct 26Messages
- Marcus Bell 3 Jun 2026 10:08Hi Craig, I look after the day to day on the Calderbrook account, and I'm writing with the formal renewal notice so you have plenty of runway. I've copied Tom Ashdown, who owns the commercial side. - Your Growth subscription (£44,000 a year, 40 licensed users) runs to 1 Sep 2026. - Renewal would move you onto the v2 price book for Growth. Tom will confirm the exact figure in writing, so please don't take a number from me. - Tom has a renewal open in our system with a target of 6 Jul 2026, so there is time to talk it through properly. I've also pulled the numbers on usage. Over the last thirty days you've had about four active users on a typical day, which is down on the previous quarter. Three tickets came in over the same period and none were high priority. I'd like to understand what the business-intelligence team needs from the brain from here, and whether the current set-up still matches that. Happy to jump on a call. Shall we book 30 minutes in the next couple of weeks? Thanks, Marcus
- Craig Oduya 3 Jun 2026 11:32Marcus, Thanks for the notice. Received and noted. We are reviewing every supplier contract against the platform strategy at the moment, and this one is in that review. We're building that capability in-house on our existing Microsoft estate, so I'd expect usage to look as you describe. Two things would help me: - What's our exit position? In particular, what happens to the data and the pipelines in our Snowflake account when the term ends. - The notice and termination wording, so I'm working from the contract rather than from memory. I'm not in a position to talk about renewal itself at this stage. Craig Oduya, Director of Digital and Data
- Marcus Bell 4 Jun 2026 15:49Hi Craig, Thanks for coming back so quickly, that's really helpful. On the exit question, here's where I can help: - The brain was built and runs inside your own Snowflake account, so the data and the tables sit with you throughout. Nothing has to be extracted from our side. - I can put together a short note listing what is configured today: the connectors, the tables and the pages and dashboards your team built. That gives you a clean picture of what you'd be taking over. - Tom will send the notice and termination wording from the executed order form. The order form is the document that counts, so I'd rather you had it from him than a paraphrase from me. If you want it, I can also look at the usage by team, so the review has something concrete behind it. Shall we book 30 minutes once you've had a look at the note? No pressure on timing. Thanks, Marcus On 3 Jun 2026, at 11:32, Craig Oduya wrote: > What's our exit position? In particular, what happens to the data and the pipelines in our Snowflake account when the term ends.