Pelton Grange Care / BB-Demo – Demo
Callcompleted
Pelton Grange Care · 2025-06-23 12:30
Technical follow-up demo on 23 Jun 2025. Pelton Grange Care probed connectors, Snowflake data control, access and what happens if Xero changes. Lindsay Pallister asked when they could move forward; the order form was to be sent.
What was said
What this says
Current to 13 Oct 26Technical follow-up demo on 23 Jun 2025. Pelton Grange Care probed connectors, Snowflake data control, access and what happens if Xero changes. Lindsay Pallister asked when they could move forward; the order form was to be sent.
What happened: Hannah Lowe and Lewis Kerr walked Lindsay Pallister and Stephanie Lowes through connector setup on 23 Jun 2025. The talk covered Snowflake, permissions, training and support.
Customer view: Stephanie stressed the sensitivity of family and care data. Lindsay asked what happens if the Xero connector breaks and was told it would usually be fixed within a day.
Commercial: Lindsay asked when they could move forward. Lewis restated 40 users, 8 connectors, £12k implementation and £44k annual, and Stephanie said they would review and reply.
Watch: The evidence does not show a signature or a decision date. The fix-within-a-day line is now an expectation to meet.
Themes
Current to 9 Oct 26Theme
Connector setup and data control
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- Lewis Kerr to send the order form to Lindsay Pallister and Stephanie Lowes, as promised on the call.
- Stephanie Lowes to review the order form and reply to Lewis.
Risks
Current to 9 Oct 26- A broken Xero connector was raised as a worry, and the customer now expects a fix within about a day.
- The customer's team is not very technical, so training during implementation matters.
Opportunities
Current to 9 Oct 26- Growth leaves several connectors free, so further systems could be added later.
- Premium support was mentioned again as an add-on.
Transcript
Lewis Kerr NoneMorning, Lindsay, Stephanie. Thanks for squeezing this in. Hannah's here to walk through the architecture and connector setup in more detail.
Hannah Lowe NoneHi both. I wanted to make sure we're clear on how this would sit in your systems. You mentioned CRM, helpdesk and accounting. I'd like to understand those data structures a bit better.
Stephanie Lowes NoneWe use the standard systems: our CRM for family data, ticketing system for incidents, and Xero for invoices. All in the cloud.- Hannah Lowe NoneGood. So what we'd do is build connectors for each. The CRM connector pulls your contact records and any related fields. The helpdesk connector gets incidents, dates, status. Xero connector gets invoice records. Each one runs nightly, so by 07:00 every morning your data is fresh.
Lindsay Pallister NoneHow long does a nightly sync take?- Hannah Lowe NoneUsually under an hour for data your size. You wouldn't notice it happening. And if there's an issue, say a connector fails, we get an alert and fix it the next business day.
- Stephanie Lowes NoneWhat if we want to add a new system later?
- Hannah Lowe NoneGrowth includes eight connectors. You'd use, say, three for CRM, helpdesk, accounting. That leaves five free. Add them anytime.
- Lewis Kerr NoneAdditional connectors are available as an add-on too, if you ever need more than eight.
- Hannah Lowe NoneThe brain itself lives in your Snowflake. You give us a service account and we set everything up. Your data never leaves Snowflake, never leaves your account. We can't see it.
- Stephanie Lowes NoneThat's important for us. We have a lot of sensitive family and care information.
- Hannah Lowe NoneUnderstood. That's exactly why we work this way. You own the data, you own the Snowflake account, we just run the queries. And you can revoke our access anytime.
- Lindsay Pallister NoneHow do we control who sees what?
- Hannah Lowe NoneYou set user roles and permissions inside the brain. You could restrict one team to their own homes' data, or give someone access to everything.
- Lewis Kerr NoneSo finance sees all invoices, operations sees incidents and contacts for their regions. You set the rules.
- Stephanie Lowes NoneAnd if someone leaves, we can just remove them?
- Hannah Lowe NoneYes. Remove them from the brain and they're gone. No lingering access.
- Lindsay Pallister NoneWhat about training? Will people need to know SQL or anything?
- Hannah Lowe NoneNo SQL required. The interface is search and dashboard builder. You type questions in plain English and it translates. For example...'show me all invoices overdue in Sunderland homes', and it brings back the rows.
- Stephanie Lowes NoneThat's good. Our team isn't super technical.
- Lewis Kerr NoneWe'd also run training during implementation. One of our consultants would spend time with your team, walk them through the interface, show them how to build dashboards.
- Hannah Lowe NoneAnd we're here for questions. Standard support, one business hour response. If you need something faster, there's premium support as an add-on.
- Lindsay Pallister NoneI have one more question. If Xero changes and the connector breaks, what happens?
- Hannah Lowe NoneWe'd notice it, fix it, and let you know. Usually within a day. Once we fix it, the next sync pulls the data again. You're not stuck.
- Stephanie Lowes NoneAnd the implementation timeline, eight weeks, you said?
- Lewis Kerr NoneEight weeks from signature. We'd have you live before the end of summer.
- Lindsay Pallister NoneOK. I think I have a much clearer picture now. When can we move forward?
- Lewis Kerr NoneI'll send the order form. It's forty users, eight connectors, twelve thousand implementation and forty-four thousand annual. Once signed, we get rolling straight away.
- Stephanie Lowes NoneSounds good. We'll review and get back to you.
- Hannah Lowe NoneGreat. Any other questions before we finish?
- Lindsay Pallister NoneNot from me.
- Lewis Kerr NoneExcellent. I'll send the docs over today. Cheers, both.
- Hannah Lowe NoneThanks for your time.
Callsmade from