Quaystead Marine Services / BB-Demo – Kickoff
Callcompleted
Quaystead Marine Services: documents · 2025-01-03 12:15
Kickoff for Quaystead's four-week Starter implementation. Luke Oakes and Emma Haworth want contracts, jobs and CRM connected, with accounting possibly later. Credentials are the blocker, and the customer expects a slight holiday delay.
What was said
What this says
Current to 11 Oct 26Kickoff for Quaystead's four-week Starter implementation. Luke Oakes and Emma Haworth want contracts, jobs and CRM connected, with accounting possibly later. Credentials are the blocker, and the customer expects a slight holiday delay.
What happened: Callie Brennan walked through the implementation plan and what BB-Demo needs from the customer. Luke and Emma agreed the timeline, with go-live around mid-January.
Customer view: Contracts and jobs come first, the CRM second, and accounting is something they can revisit later. Luke said "Accounting we can revisit later if needed."
Commercial: Three systems fit within the four connectors included on Starter, leaving one spare. Accounting is a possible later use of that spare connector, not a firm ask.
Watch: Credentials are the blocker, and Emma warned they might arrive a day or two late because of the holiday. Only Luke and Emma attended, so no budget holder or executive sponsor was present.
Themes
Current to 9 Oct 26Theme
Starter implementation kickoff
Importance
neutral
Sentiment
positive
Voice
champion
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Callie Brennan to send the setup checklist straight after the call.
- Luke Oakes and Emma Haworth to supply system credentials early the following week.
- Marcus Bell to book a check-in with Luke Oakes for the following week.
Risks
Current to 9 Oct 26- Credentials are the blocker and the customer expects them a day or two late over the holiday.
- Only two working-level contacts attended, so no budget holder is yet engaged.
Opportunities
Current to 9 Oct 26- Accounting could use the spare fourth Starter connector later if the customer wants it.
Transcript
Callie Brennan NoneHi everyone, and welcome to BB-Demo. I'm Callie, and I'll be taking you through the implementation over the next four weeks. Marcus is your success manager, and he'll be with you after go-live to help you get the most out of the brain. What I wanted to do today is walk through what we need from you, and set the timeline.
Luke Oakes NonePerfect. So we've got three systems we want to bring in: our contracts system, our job tickets, and our CRM. Is four connectors enough for that?- Callie Brennan NoneYeah, that's fine. Four connectors is exactly what you get on Starter. So we could do contracts, jobs, CRM, and maybe a fourth system: accounting, HR, whatever makes sense. What's the priority?
Emma Haworth NoneDefinitely contracts and jobs first. The CRM is second priority. And maybe accounting later, but that's not essential to start with.- Callie Brennan NoneGood. So what I need from your side is, API credentials for each system, and time with someone who knows the data model. That's usually you, Luke, or Emma if you're more familiar with the backend. We need to map your fields: what you call a 'contract ID', what we ingest as a contract ID, that kind of thing. That mapping takes the longest, but once we've got it right, the refresh is automated.
- Luke Oakes NoneHow long does mapping usually take?
- Callie Brennan NoneDepends on system complexity. Simple systems, a day or two. Complex ones, a week. Once we've got credentials, and that's the blocker, we'll schedule sync calls with you to walk through it. Before we switch on the refresh, I'll run you through what we've built and make sure you're happy.
- Emma Haworth NoneAnd what happens when the refresh goes live? Will it impact our systems, like, does it slow anything down?
- Callie Brennan NoneNo, the refresh happens in your Snowflake account, not in your operating systems. It pulls data via API, loads it into your Snowflake, and doesn't touch your source systems. The refresh runs nightly, complete by seven a.m. your time on business days.
Marcus Bell NoneAnd I'll touch base with you weekly during implementation to make sure everything's on track. Any blockers, any questions, just flag them and we'll sort it.- Luke Oakes NoneWhat happens if one of our systems goes down during the refresh? Does the whole refresh fail?
- Callie Brennan NoneGood question. If one connector fails, we skip it and refresh the others. You'd see a notification that the contracts system connector failed, for example. Then we investigate and fix it. If it's still broken the next night, it alerts you again. If it's a persistent issue, like your source system changed API structure, we'd work with you to remap it.
- Emma Haworth NoneOkay, that makes sense. What about training, when does that happen?
- Marcus Bell NoneWe'll do a training session once the brain is live. I'll show the team how to use search, how to ask questions in chat, how to build dashboards if you want to go there. We usually schedule that for a couple of days after go-live, once people have poked around a bit.
- Callie Brennan NoneSo here's the timeline, I need credentials from you by next week at the latest. Then we spend a week mapping. Week two and three, we build and test. Early the following week: so around mid-January or so: we do a final check with you, and then go live. Does that work?
- Luke Oakes NoneYeah, that timeline works. We can get credentials to you early next week.
- Callie Brennan NonePerfect. I'll send you a checklist with what I need, API endpoints, field documentation, that kind of thing. Can you get that to us by Wednesday?
- Emma Haworth NoneWe'll do our best. Might be a day or two later given the holiday, but not much longer than that.
- Callie Brennan NoneThat's fine. And before we wrap, are there any other systems you think might want to connect? Any tools you use to track things?
- Luke Oakes NoneNot really, I think contracts, jobs, and CRM cover the main use case. Accounting we can revisit later if needed.
- Callie Brennan NoneGood. So I'll send the setup checklist within the hour, you turn that around early next week, and we go from there. And Marcus, I'll hand over to you for the first check-in call in a couple of weeks.
- Marcus Bell NoneYep, I'll get on Luke's calendar for next week anyway. Just to keep the momentum, even before the build kicks off. Any questions before we wrap?
- Emma Haworth NoneNo, I think we're clear. We'll get you what you need.
- Callie Brennan NoneBrilliant. Thanks so much. Speak soon.
Callsmade from