Brindlecote Insurance Brokers / BG-Demo – Kickoff
Callcompleted
Brindlecote Insurance Brokers · 6 Jun 2023 13:30
On 6 Jun 2023 BG-Demo walked Brindlecote through the four-week Starter implementation: three connectors, nightly refresh, fifteen users and access needs. The customer was engaged and asked about connector failure and data restriction.
What was said
What this says
As at Fri 9 Oct 2026On 6 Jun 2023 BG-Demo walked Brindlecote through the four-week Starter implementation: three connectors, nightly refresh, fifteen users and access needs. The customer was engaged and asked about connector failure and data restriction.
What happened: Daniel Okafor set out a four-week plan from data mapping to go-live, and Tobias Renwick covered access, connectors and refresh. Toby Underwood agreed to provision read access by the end of the week.
Customer view: Ed Duckworth worried about what happens if a source such as Salesforce breaks. Toby asked about the refresh time and about restricting what brokers can see.
Commercial: three of four Starter connectors will be configured, leaving one open. Fifteen users are included, with Growth as the route to forty.
Watch: no executive sponsor or finance contact attended, so the value case rests with Ed and Toby.
Themes
As at Fri 9 Oct 2026Theme
Starter implementation kickoff
Importance
neutral
Sentiment
positive
Voice
champion
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- Send the access checklist after the call.
- Customer to provision read access to Salesforce and the claims system by the end of week one.
- Schedule the week three training session for the team.
Risks
As at Fri 9 Oct 2026- The customer is concerned about connector breakage if Salesforce or another source changes.
- Access provisioning by the end of week one is on the critical path for the build.
- No executive sponsor or finance contact attended, so the value case is not yet owned above the working team.
Opportunities
As at Fri 9 Oct 2026- One Starter connector is left open, and Growth offers forty users once usage is clear.
- Row-level restriction for brokers could justify wider rollout across teams.
Transcript
Daniel OkaforAfternoon, everyone. Thanks for taking the time. I'm Daniel, I'll be your CSM for the next four weeks. Tobias is here to walk through the technical side. How is everyone doing?
Ed DuckworthGood, mate. Excited to get going.- Daniel OkaforGreat. So here's what we're going to do over the next four weeks. Week one is about understanding your data. Tobias will map your Salesforce, your claims system, and the calls. We'll identify the connectors you need and where the gaps are. Week two, we build. Week three is testing and training your team. Week four is go-live.
Tobias RenwickTo be precise, I'll need access to your Salesforce instance and your claims system. Just read access. We'll also need a test environment we can use safely. Once you give us access, we'll map the fields, the relationships, and work out which data flows into which connectors.
Toby UnderwoodI can provision all of that. What's the timeline for us to get that ready?- Tobias RenwickIdeally by end of week, so we can start building on Monday of week two.
- Toby UnderwoodWe can do that.
- Daniel OkaforBrilliant. I'll send you a checklist after this call. Tobias, talk them through the connectors.
- Tobias RenwickYou've got four connectors in Starter. We'll configure three for you: Salesforce, your claims system, and the call recordings. That leaves one open for later. Each connector pulls fresh data nightly and loads it into your Snowflake warehouse. The brain queries the warehouse, so you're always working with data from last night.
- Ed DuckworthWhat if a connector breaks? Like, if Salesforce goes down or changes something?
- Tobias RenwickThe honest answer is, we monitor all connectors. If one fails to load for more than a couple of hours, we get alerted and we look into it. Usually it's a permissions issue or a schema change. We fix it, usually within a couple of hours. You'll see in the brain that records stopped loading and we'll tell you when it's live again.
- Toby UnderwoodOkay. And the nightly refresh, what time is that?
- Tobias RenwickComplete by seven in the morning your local time, every business day. So Monday through Friday, your team wakes up to fresh data.
- Daniel OkaforAnd on the usage side, you get fifteen licensed users in Starter. That's how many people can log in and ask questions. If you want to grow, we upgrade you to Growth and you get forty. For now, let's start with fifteen and see who's using it most.
- Ed DuckworthHow do we manage user access?
- Daniel OkaforYou tell me who you want added, we add them, they get a login. If someone leaves, you tell us, we remove them. Simple as that.
- Toby UnderwoodAnd what do they see? Can we restrict data?
- Tobias RenwickThat's something we can configure during implementation. If you want brokers to see their own clients' data only, we can set that up. Usually that means adding a filter in the brain based on user ID or team. It's doable.
- Ed DuckworthGood. And training, how does that work?
- Daniel OkaforWeek three we do a training call with your team. Tobias or I walk through how to use the brain, how to ask questions, what the data means. We usually do one session, maybe an hour or so, and anyone who couldn't make it can review a recording.
- Toby UnderwoodThat works. Is there anything we need to do on our end before week one starts?
- Daniel OkaforJust get Tobias the access we talked about and the checklist I'll send. Other than that, we'll handle the heavy lifting. I'll be checking in with you weekly, and if anything's unclear, just reach out.
- Ed DuckworthGreat. When do we kick off properly?
- Daniel OkaforI'll send a calendar invite for Monday morning, week one. We'll do a quick sync and then Tobias gets into the data mapping. From there, you'll see us building.
- Ed DuckworthPerfect. Cheers, Daniel.
- Daniel OkaforBest wishes. Speak soon.
Callsmade from