Matteo Ricci

Strathcorran Renewables / BB-Demo – Demo

Callcompleted

Strathcorran Renewables: documents logo Strathcorran Renewables: documents · 2026-09-22 16:15

Second demo for Ed Ingham covering pages, chat, freshness and training. He asked about separating maintenance and finance data; role-based access is an Enterprise feature, not in Growth. He will take it back to Fiona and the team.

What was said

What this says

Current to 11 Oct 26

Second demo for Ed Ingham covering pages, chat, freshness and training. He asked about separating maintenance and finance data; role-based access is an Enterprise feature, not in Growth. He will take it back to Fiona and the team.

What happened: Theo showed how the operations team would use pages and chat day to day. Ed asked about self-service dashboards, access control, data freshness and training.

Customer view: Ed needs maintenance operations and finance kept apart. He accepted nightly refresh as sufficient and said he had enough to take back to Fiona and the team.

Commercial: Theo said Growth does not include role-based access control and that it is an Enterprise feature, then said it could be built into scope. That is unresolved and affects tier choice.

Watch: Matteo again promised the proposal this week. The evidence does not show how the access control need will be priced or met.

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

Themes

Current to 9 Oct 26
Theme
Access control and tier fit
Importance
upsell
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Matteo Ricci sends the proposal this week, settling how maintenance and finance separation is handled.
  • Ed Ingham takes the demo back to Fiona and the team.

Risks

Current to 9 Oct 26
  • Separating maintenance and finance data may not fit Growth and could stall the proposal.
  • Saying it can be built into scope may set an expectation the Growth tier cannot meet.

Opportunities

Current to 9 Oct 26
  • The access control need points to the Enterprise tier, which includes SSO and SCIM.
  • A dedicated training day add-on was mentioned for a deeper session.

Transcript

  1. Matteo Ricci
    Matteo Ricci None
    Ed, thanks for making time again. We wanted to dig a bit deeper into how the brain would integrate with your broader operations workflow.
  2. Ed Ingham
    Ed Ingham None
    Yeah, I appreciate that. I've got a couple of questions from the team.
  3. Theo Gallagher
    Theo Gallagher None
    Great. So last time we showed you how the brain searches across your data. Today I want to show you how your operations team would actually use it day-to-day. Let me walk through the pages feature, that's where you can pin reports that your team builds.
  4. Theo Gallagher
    Theo Gallagher None
    So imagine your maintenance lead wants a dashboard that shows all assets in the field right now, their last maintenance date, and any open issues. They can build that once and then your whole team sees it. If a customer calls about an asset, you can pull that dashboard and answer them in seconds instead of hunting through spreadsheets.
  5. Ed Ingham
    Ed Ingham None
    Can they update it themselves, or do we need to go to you?
  6. Theo Gallagher
    Theo Gallagher None
    They can update it themselves. The dashboard is built from queries they write. If they want to change the scope or the way it's sorted, they modify the query. We'll train them on how to do that.
  7. Ed Ingham
    Ed Ingham None
    What about access control? We have different teams that shouldn't see each other's data.
  8. Theo Gallagher
    Theo Gallagher None
    Growth doesn't include role-based access control out of the box. That's an Enterprise feature. But we can have a conversation about what you need and whether there's a workaround.
  9. Matteo Ricci
    Matteo Ricci None
    That's something we'd want to confirm with you in the proposal. Can you tell me which teams need to be separated?
  10. Ed Ingham
    Ed Ingham None
    Maintenance operations and finance, mainly. Finance looks at invoicing, maintenance looks at asset uptime.
  11. Theo Gallagher
    Theo Gallagher None
    Noted. We can build that into the scope. Moving on, the chat feature. Imagine someone on your team just wants to ask a quick question, like, which customers have had more than two asset failures in the last thirty days? They just type that into chat and the brain answers it. No need to build a formal report, no need to hunt through systems.
  12. Ed Ingham
    Ed Ingham None
    And the brain understands natural language like that?
  13. Theo Gallagher
    Theo Gallagher None
    Exactly. It's trained on your data, so it understands the context: asset, failure, customer.
  14. Ed Ingham
    Ed Ingham None
    Okay. My team also asked about data freshness. How current is the data?
  15. Theo Gallagher
    Theo Gallagher None
    The brain refreshes nightly. So by seven o'clock each morning UK time, your latest data is indexed and searchable. If you need real-time data, that's a different conversation, but for operations reporting, nightly is usually sufficient.
  16. Ed Ingham
    Ed Ingham None
    That works for us. What about training? Will we need to send people in?
  17. Matteo Ricci
    Matteo Ricci None
    It's included in the eight-week implementation. Theo and the team will run group training during the setup, and then ad-hoc support as you go live. You can also add a dedicated training day as an add-on if you want a deeper session.
  18. Ed Ingham
    Ed Ingham None
    When would that training happen?
  19. Theo Gallagher
    Theo Gallagher None
    Weeks seven and eight of the implementation, once we've built everything and it's ready to go live.
  20. Ed Ingham
    Ed Ingham None
    Alright. I think we've covered a lot. I've got enough to take back to Fiona and the team.
  21. Matteo Ricci
    Matteo Ricci None
    Perfect. I'll get that proposal over this week. Feel free to get back to me with any other questions.
  22. Ed Ingham
    Ed Ingham None
    Will do. Cheers.

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
Organisations75
People at customers290
BB-Demo staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

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.

Ask B

Ask B

B-Brain · read-only