What was said
What this says
As at Fri 9 Oct 2026Demo to Ian Nuttall, Operations Director, on pulling maintenance, call and cost data per vessel. He was positive and the timeline suited him. Tom Ashdown owes a proposal. No price was discussed.
What happened: Tobias Renwick demoed chat, dashboards and the Snowflake model to Ian. Ian wanted one view of everything known about a vessel and called the result brilliant.
Customer view: Ian asked about security, access control, fixing bad data and support. He said the start timeline works for his team and the implementation plan is straightforward.
Commercial: The pitch was Starter: fifteen users, four-hour first response on a priority issue, and a four-week implementation. Tom will send a proposal and then book a pricing call.
Watch: No price, budget or other decision-maker came up, and the evidence does not show who else must approve. The proposal is an open item, not a commitment.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Tom Ashdown to send the proposal and book a pricing and terms call with Ian Nuttall.
Risks
As at Fri 9 Oct 2026- No price or budget was discussed, so affordability is untested.
- The evidence does not show who else must approve the purchase.
Opportunities
As at Fri 9 Oct 2026- A Starter subscription with the four-week implementation for the operations team.
- Dashboards for vessel downtime and repeat maintenance issues could deepen use after go-live.
Transcript
- Tom AshdownAfternoon, Ian. How's the week been?
- Ian NuttallNot bad, mate. Looking forward to seeing what you've built.
- Tom AshdownBrilliant. So Tobias is going to walk you through the brain. Tobias is our CTO, he built the whole platform. Tobias, over to you.
- Tobias RenwickThanks, Tom. Ian, so what I'm going to show you is how the brain queries across your data at once. We've loaded sample boatyard records, call transcripts, maintenance logs. The honest answer is that the magic is in the connectors and the data mapping. To be precise, we'll show you the architecture, then I'll walk you through a live demo. What questions matter most to you?
- Ian NuttallWell, we get a lot of calls about maintenance on different boats. I'd like to see how we could quickly pull together everything we know about a specific vessel.
- Tobias RenwickPerfect. So let me show you the brain's chat interface. I'm going to type: 'Show me all maintenance history for vessel X, including all calls about this vessel, any safety notes, and cost.' And here's what the brain returns. It's pulled maintenance records from your system, it's found all calls mentioning this vessel, it's aggregated costs. One question, everything in one place.
- Ian NuttallThat's brilliant. How does it know what to search?
- Tobias RenwickWe connect your systems upfront and map the data. So we know your call recorder has vessel metadata, your maintenance system has cost data, your email has customer context. When you ask a question, the brain knows where to look and how to join the data. Does that make sense?
- Ian NuttallYeah. And how secure is this?
- Tobias RenwickTo be precise, the data never leaves your infrastructure. We run inside your Snowflake account. Audit logs show every query. Your IT team controls access. We don't copy data, we don't send it to us, we query inside your account. The trade-off is that it's your responsibility to keep Snowflake secure, but most customers prefer that to us holding the data.
- Ian NuttallThat's reassuring. What about dashboards?
- Tobias RenwickLet me show you. So we have a dashboard builder, no code required. You pick fields, drag them in, set a refresh schedule. So if you wanted to show 'vessel downtime by month', or 'repeat maintenance issues', you'd build it here. Your team maintains these, not us.
- Ian NuttallCan everyone see everything?
- Tobias RenwickNo. On Starter tier, you get fifteen users. We set access controls so someone in operations only sees operational data. You manage who sees what.
- Ian NuttallAnd if the data is wrong, how do we fix it?
- Tobias RenwickIf the source data is wrong, you fix it in the source system and we refresh nightly. If there's a bug in how we're reading the data, we fix that. It's usually the former. Our responsibility is to map it correctly the first time.
- Ian NuttallOkay. And support, what does that look like?
- Tobias RenwickStarter gives you four-hour first response on a priority issue. We have a helpdesk, you can email or phone. Most issues are 'how do I build a dashboard' or 'why isn't this data showing'. We solve those quickly.
- Ian NuttallAnd implementation, you said four weeks?
- Tobias RenwickYes. Week one, we audit your systems and data. Weeks two and three, we build and test the connectors. Week four, you pilot with a team, we gather feedback, go live. We need read access to your systems and a champion on your side.
- Ian NuttallThat's straightforward. When would we start?
- Tobias RenwickIf you sign by the end of November, we'd start in early December and be live by end of January or early February.
- Ian NuttallThat works for us. So what's the next step?
- Tom AshdownI'll put together a proposal and we'll go through pricing and terms. Should have that to you by end of next week. Then we'd schedule a call to run through it, answer questions, and hopefully move towards a signing.
- Ian NuttallSounds good.
- Tom AshdownBrilliant. I'll send the proposal over as soon as it's ready.
- Ian NuttallCheers, Tom.
- Tom AshdownNo drama. Speak soon.