What was said
What this says
Current to 11 Oct 26Second 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.
Themes
Current to 9 Oct 26Who was there
B-Brain
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.