Llano Crossing Software / BG-Demo – Kickoff
Callcompleted
Llano Crossing Software · 30 Jun 2026 15:15
Kickoff for Llano Crossing Software's Starter implementation on 30 Jun 2026. Kayla Ramirez is keen and wants a live training session for about 15 people. Product analytics depends on Hector, who was not on the call.
What was said
What this says
As at Fri 9 Oct 2026Kickoff for Llano Crossing Software's Starter implementation on 30 Jun 2026. Kayla Ramirez is keen and wants a live training session for about 15 people. Product analytics depends on Hector, who was not on the call.
What happened: Hamza Akhtar walked Kayla Ramirez through a four-week plan: connectors and access in week one, data flowing in week two, validation and training in week three, buffer in week four. Hollie Grieve set out the Starter cadence of six-monthly check-ins.
Customer view: Kayla said she was excited and had been waiting for this. She asked for a live training session rather than a recorded walkthrough, for maybe 15 people.
Commercial: Fifteen users is the Starter soft limit, so adoption beyond that team is a possible Growth conversation later. Hollie also promised a check-in after 30 days to see where value is showing.
Watch: The product analytics schema questionnaire sits with Hector, who owns that engineering and was not on the call. Slow access to helpdesk or Salesforce admin rights would eat into the buffer week.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Hamza Akhtar sends the access request and schema questionnaire by end of day on 30 Jun 2026.
- Hollie Grieve schedules the live training session for week three.
- Hollie Grieve holds the 30-day check-in on where value is showing.
Risks
As at Fri 9 Oct 2026- Product analytics mapping depends on Hector, who was not on the call.
- Access to the helpdesk and Salesforce admin rights could delay week one.
Opportunities
As at Fri 9 Oct 2026- About 15 people for training sits at the Starter user soft limit, so Growth could follow if adoption spreads.
Transcript
Hamza AkhtarHi Kayla, Hollie here too, thanks for getting on. I'm Hamza, I'll be running your implementation.
Kayla RamirezHey Hamza, Hollie, good to meet you both.
Hollie GrieveGreat to have you on board. This call is to make sure everyone's aligned on the next four weeks: connectors, data, timeline, and what we need from your side.- Hamza AkhtarExactly. So we've got four weeks from today. We'll configure connectors to your helpdesk, Salesforce, and your product analytics. Once data starts flowing, we'll run a couple of validation calls and do some light training. Sound okay?
- Kayla RamirezYeah. Do you need anything from us right now?
- Hamza AkhtarA few things. We'll need admin access to your helpdesk and Salesforce. API keys or OAuth tokens, depending on what you've got. And someone who can answer questions about your product analytics, is that you or Hector?
- Kayla RamirezThat's probably Hector. He owns the engineering on that side. But I can be in the loop.
- Hamza AkhtarPerfect. I'll send out an access request and a questionnaire, we need to understand the schema of your product analytics so we can map it correctly. You and Hector can fill that in.
- Kayla RamirezHow long is that going to take?
- Hamza AkhtarAn hour or two, maybe. It's pretty straightforward: table names, field definitions, that sort of thing.
- Hollie GrieveAnd Kayla, once Hamza kicks off the connectors, I'll be your main point for adoption questions, check-ins, and anything you want to get out of the brain. We'll do a check-in every six months with Starter, so we'll touch base in December and then again next June around your renewal.
- Kayla RamirezWhat should we be ready for on day one?
- Hamza AkhtarYou'll get access to the brain, the search interface, the chat. Your data starts flowing that day, but it'll take a night or two to complete the first load. By day three or four, you'll have two to three months of historical data.
- Kayla RamirezAnd then it updates every night?
- Hamza AkhtarEvery night, yes. We refresh by 07:00 your time on business days. So you wake up each morning with fresh tickets and usage data.
- Kayla RamirezGreat. So who should I loop in for the actual user training?
- Hollie GrieveYou. We'll send you a recorded walkthrough and a user guide. You can get your team up to speed, or if you want us to do a live session, we can do that in week three.
- Kayla RamirezI think a live session would be good. We've got maybe 15 people who'd be on.
- Hollie GrievePerfect. We'll schedule that for week three. That'll give Hamza time to get data flowing and stable, and you'll have working examples to show.
- Hamza AkhtarSo here's the timeline: week one is connectors and access setup. Week two, data starts flowing. Week three, we validate the data, run the user training, and make sure everyone's got hands-on time. Week four is buffer and final validation.
- Kayla RamirezThat sounds good. What could slow us down?
- Hamza AkhtarIf we hit any blockers: data quality issues, API limits, things like that, we'll surface them early. But from what we saw in the demo, your data looks solid.
- Kayla RamirezOkay. Anything else?
- Hollie GrieveJust to set expectations: the first month or two, your team might be learning the interface. Don't expect huge wins immediately. We'll check in after 30 days and see where you're getting value. Then we'll expand from there.
- Kayla RamirezThat makes sense. I'm excited. We've been waiting for this.
- Hamza AkhtarGreat. I'll send the access request and questionnaire by end of day. Once you get those back, we'll kick off formally, probably mid-next week.
- Hollie GrieveAnd I'll be in your inbox if you have any questions between now and the start of implementation. Cheers.