Following up on Thursday's demo

Hi all, Thanks for your time this afternoon. It was good to see the demo running on your own temperature-excursion tickets and not a sample set. Wes, your point about wanting orders and contract reviews sat next to the excursions for each client was the bit I took away most. I've copied Tobias, our CTO, because Dan asked how it all hangs together on the data side. Short version: the brain is built and run inside your own Snowflake account, so nothing leaves your own controls. Two things from me. First, if you can tell me which systems you would want connected first, I'll get a proper scope together. Second, let's get something in the diary for a technical chat between Dan and Tobias. No drama on timing, we have a good few weeks. Cheers, Tom

Hi Tom, Thanks for the follow-up. The demo was useful. From my side the main questions are about access and refresh. Who sets up the connections to our systems, and what do you need from my team? And how fresh is the data each morning, given the account managers check excursions first thing? I'd also like to understand what happens to the data if we ever stopped using it. Kerensa and Wes are copied in case they want to add to the list. Regards, Dan

Hi Dan, Thanks for the questions, and sorry for the delay, I wanted Tobias to check my answers. On set-up, we do the connection work with you and you approve each system, so your team's time is mainly granting access and answering our questions. On freshness, the nightly refresh is complete by 07:00 your local time on business days, so the account managers have it before they start. On leaving, the data stays in your own Snowflake account because that is where it lives, so there is nothing to hand back. Tobias would be glad to go through the detail with you, and with your security colleagues if they want to be there. I'll send a couple of times this week. Leave that with me. Cheers, Tom