Ask
Tobias Renwick

Tannahill Systems / BB-Demo – Kickoff

Callcompleted

Tannahill Systems: documents logo Tannahill Systems: documents · 2023-04-14 10:45

Kickoff on 14 Apr 2023 for Tannahill Systems. Kenny Lockhart named himself adoption owner and Scott Galbraith admin. Kenny accepted overnight refresh, and his stated priority was getting the team using the brain.

What was said

What this says

Current to 11 Oct 26

Kickoff on 14 Apr 2023 for Tannahill Systems. Kenny Lockhart named himself adoption owner and Scott Galbraith admin. Kenny accepted overnight refresh, and his stated priority was getting the team using the brain.

What happened: Daniel Okafor and Tobias Renwick set out a four-week build covering connectivity, connectors and a first index, validation, then training and go-live. Customer roles were fixed: Kenny owns adoption, Scott handles user access and connector health.

Customer view: Kenny was positive and said the main thing is getting the team using it. He accepted that the brain is an overnight batch and not real time.

Commercial: The call was delivery-focused with no price or renewal talk. Daniel mentioned 15 user seats and that a new connector such as product usage data can be scoped on request, which is the only expansion signal.

Watch: Adoption rests on Kenny as the single owner, and Daniel described changing workflow for the support team as the hard part.

AI · claude-sonnet-5-5 · 11 Oct 2026

Themes

Current to 9 Oct 26
Theme
Kickoff and adoption ownership
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Scott Galbraith to set up the API keys and Tobias Renwick to test the connections.
  • Daniel Okafor to run the check-in call the following week once everything is connected.

Risks

Current to 9 Oct 26
  • Adoption depends on Kenny Lockhart as the single go-to owner for the support team.
  • Customer expectations on freshness rest on an overnight batch, not live data.

Opportunities

Current to 9 Oct 26
  • A further connector such as product usage data was raised and can be scoped on request.

Transcript

  1. Daniel Okafor
    Daniel Okafor None
    Hi Kenny, hi Scott. Thanks for your time. Tobias is here from our engineering team. This is the kickoff, we'll walk through how we're going to build this over the next four weeks.
  2. Kenny Lockhart
    Kenny Lockhart None
    Great. We're excited to get going.
  3. Tobias Renwick
    Tobias Renwick None
    Good to be here. So I've pulled your data export again, Zendesk, Salesforce, Xero, and we've started the initial load into your Snowflake instance. I wanted to check a few things with you both, particularly Scott as the admin.
  4. Tobias Renwick
    Tobias Renwick None
    First, connectivity. You need to give us read-only access to your live systems so that every night, we can pull the latest data. That's Zendesk, Salesforce and Xero. We'll set up service accounts in each system with minimal permissions, just read, no write. Does that sit OK with your security posture, Scott?
  5. Scott Galbraith
    Scott Galbraith None
    Yeah, that sounds right. Do you need me to set those up or can you guide me?
  6. Tobias Renwick
    Tobias Renwick None
    I'll send you documentation with the exact steps. It's usually a couple of minutes per system. Once you've done that, send me the API keys and I'll test the connections.
  7. Daniel Okafor
    Daniel Okafor None
    Now, one big question for Kenny, in terms of your support team using the brain, who's going to be the go-to person here? Someone to answer questions, manage user access, that kind of thing?
  8. Kenny Lockhart
    Kenny Lockhart None
    I think that's me, probably. I can kind of own it on our side.
  9. Daniel Okafor
    Daniel Okafor None
    Perfect. So you'll be our main contact for adoption questions. And Scott, you're the admin, you'll handle technical things like user access and connector health. That work for you both?
  10. Scott Galbraith
    Scott Galbraith None
    Yeah, that's fine.
  11. Tobias Renwick
    Tobias Renwick None
    Timeline-wise, here's what we're planning. This week I'll have the base infrastructure live. Next week, connectivity week, you'll set up those API keys and I'll test everything. Week three, I'll build the connectors and the first index. You'll get a test instance and we'll do a data validation call: you'll check that tickets, accounts, and invoices are all there and look right. Week four is training and go-live.
  12. Kenny Lockhart
    Kenny Lockhart None
    And who do we train? Just the eight support people?
  13. Daniel Okafor
    Daniel Okafor None
    Yeah, the support team. We'll do a group training, how to search, how to answer common questions with the brain. Then we'll be on hand for the first week after go-live if anyone gets stuck.
  14. Scott Galbraith
    Scott Galbraith None
    And after that, do we just manage it ourselves?
  15. Daniel Okafor
    Daniel Okafor None
    Mostly yes. You've got 15 user seats, you can add and remove people as you need. If you need to add a new connector later: say, product usage data, you can ask and we'll scope that. Any technical issues, you can email support. And we'll check in with you at six months to see how you're getting on and talk about what's working and what isn't.
  16. Kenny Lockhart
    Kenny Lockhart None
    OK, so I think the main thing for us is just getting the team using it.
  17. Daniel Okafor
    Daniel Okafor None
    That's the bit we're here to help with. The tool itself is straightforward, search and answers. But adoption, getting eight busy people to change their workflow, that's the hard part. So we'll do training, and then Tobias and I will both be on email for the first month if people have questions.
  18. Tobias Renwick
    Tobias Renwick None
    One last thing, data freshness. The brain updates every night. So a ticket you log this afternoon will show up tomorrow morning. If your team is looking for real-time data, like a ticket that came in an hour ago, the brain won't have that. It's overnight batch, not live streaming. Does that work for your use case?
  19. Kenny Lockhart
    Kenny Lockhart None
    Yeah, that's fine. We're not dealing with millisecond-critical stuff. Overnight is good.
  20. Daniel Okafor
    Daniel Okafor None
    Great. So to recap, Scott's going to set up the API keys, Tobias will test the connections. Then we kick off the build. The brain should be live and your team trained by end of month. Kenny, you're the main contact on adoption. Any questions?
  21. Scott Galbraith
    Scott Galbraith None
    I don't have any. I'll get the keys sorted.
  22. Kenny Lockhart
    Kenny Lockhart None
    No, I think we're good. Looking forward to it.
  23. Daniel Okafor
    Daniel Okafor None
    Brilliant. Tobias will send you that documentation today. If you get stuck on the API key setup, just shout. Otherwise, we'll do a check-in call next week once everything's connected. Cheers, both of you.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Brain · read-only