What was said
What this says
As at Fri 9 Oct 2026Brianna Ocampo probed architecture, compliance, model ownership and support in a second demo with Hannah Lowe. She said she was clear on how it works and will discuss with Wade and the IT team.
What happened: Hannah Lowe walked Brianna through connectors, the nightly refresh by 07:00, Snowflake access control, audit logging and how the data model is designed. Brianna asked who owns the model and what happens if implementation slips.
Customer view: Her questions were about control and risk, not price. She closed by saying she was clear on how it works and would take it to Wade and IT.
Commercial: Implementation was given as eight weeks, with worst case week nine or ten, and Growth critical support at one business hour. This differs from the four weeks quoted on the earlier demo, and the evidence does not show an outcome.
Watch: IT is a new reviewer to satisfy before any order form.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Jordan Pike to send the additional documents promised on the call.
- Jordan Pike to follow up early the following week and confirm the implementation timeline in writing.
Risks
As at Fri 9 Oct 2026- Brianna must win over Wade and the IT team, and the evidence does not show their views.
- Implementation was four weeks on the earlier demo and eight weeks here, so the timeline needs to be made consistent.
Opportunities
As at Fri 9 Oct 2026- Clear answers on Snowflake control, audit logging and model ownership may help the IT review.
- A Customer Success manager after go-live gives a route to refine the model and show value.
Transcript
- Jordan PikeHi Brianna. Hannah's one of our lead Solutions Engineers and she's going to go deeper into some of the architecture and data-design questions you might have.
- Hannah LoweHi Brianna. So what I want to cover today is how we connect your systems, how we model your data, and how we ensure accuracy and compliance. To be precise, everything runs inside your Snowflake account.
- Hannah LoweYou give us read-only credentials to your CRM and your call system. We build connectors that run on a schedule, typically nightly, and load new data into a staging layer in your Snowflake.
- Hannah LoweFrom there, we transform that raw data into a data model designed around your business questions. So instead of tables, you're asking questions about customers and placements.
- Brianna OcampoHow do you handle updates? If a customer record changes, does the brain reflect that?
- Hannah LoweYes. Every night we pull the latest data. So if a customer status changes in your CRM, by tomorrow morning the brain reflects it. There's a nightly refresh complete by seven a.m.
- Hannah LoweOne thing to understand is that the brain is a point-in-time view. So if you ask 'which customers called yesterday', it's based on yesterday's data. You can go back in time, but you're always looking at a historical snapshot.
- Brianna OcampoThat's fine. What about compliance? How do you handle data retention and access control?
- Hannah LoweAll data stays in your Snowflake, so you control retention. We don't copy anything to BG-Demo systems. On access control, you use Snowflake's native permissions and we respect those. If someone doesn't have access to a customer in your CRM, they won't see it in the brain.
- Hannah LoweWe do have audit logging, all queries are logged so you can see who asked what and when. That helps with compliance and troubleshooting.
- Brianna OcampoGood. What about the data model? How do you design that?
- Hannah LoweWe'd have a series of design calls with your team. We'd map your CRM fields, understand your business terminology, identify key relationships. For instance, how do you define a 'placement'? What makes it successful?
- Hannah LoweOnce we understand your language, we build the model to match. That way, when you ask the brain a question, it interprets it correctly in your domain.
- Brianna OcampoWho owns the model once it's built? Can we change it if we want?
- Hannah LoweWe own the technical implementation, but you own the business logic. If your definition of a successful placement changes, you can tell us and we'll update the model. We'd support that.
- Jordan PikeThe longer answer is that once you're live, you've got a Customer Success manager who helps you refine the model based on what you're seeing in the brain.
- Brianna OcampoOkay, that makes sense. What happens if there's a problem during implementation?
- Hannah LoweWe build in buffer. We aim for eight weeks, but we've got contingency for things like system access delays or changes you want to make. Worst case, we're talking week nine or ten, but we've never overrun significantly on a Growth-tier implementation.
- Hannah LoweAnd if something breaks after go-live, you've got support. On Growth, we respond to a critical issue in one business hour.
- Brianna OcampoWhat counts as critical?
- Hannah LoweIf the brain is down or returning incorrect data consistently, that's critical. If a specific query is slow or a dashboard isn't loading, that's high priority but not critical. We'd get to critical in an hour, high priority in four.
- Brianna OcampoGot it. And once we sign the order form, when would you start?
- Jordan PikeWe'd kick off the following week with access requests and an initial design call. You'd be live eight weeks after that.
- Brianna OcampoAlright. I think I'm clear on how this works. Let me discuss with Wade and our IT team and we'll come back to you.
- Jordan PikePerfect. I'll send over any additional docs and we'll follow up early next week.
- Hannah LoweThanks, Brianna. Happy to answer follow-ups anytime.
- Brianna OcampoThanks, you two. Really helpful.