What was said
What this says
Current to 11 Oct 26Demo on Calderbrook's own sample data. Helen Marsden and Paul Rigby saw traceable answers and the double-counted repairs job exposed. Helen still needs security and counting-rule write-ups and a written proposal before going to leadership.
What happened: Hannah Lowe showed the chat answering from Calderbrook's sample extract, with links back to source records. It surfaced the same repairs job twice, which Paul confirmed as his double-count.
Customer view: Helen said she came in sceptical and found the behaviour when the data cannot answer more reassuring than a clever answer. Paul needs the nightly refresh ready before the morning stand-up.
Commercial: Helen listed three gaps: a written security answer, an agreed counting rule and a written proposal. Tom repeated the fifty-six thousand all in figure for Growth and kept 16 Aug 2024 as the target.
Watch: The access controls answer was deferred to a written follow-up. Ticket and call matching to job references is partial, and Hannah promised real match rates.
Themes
Current to 9 Oct 26Who was there
B-Brain
Them
Follow-up
Next steps
Current to 9 Oct 26- Hannah Lowe sends the security and access write-up and the counting rule note, in an attachable document.
- Tom Ashdown sends the written proposal with what is included, ahead of 16 Aug 2024.
- Helen Marsden asks her IT colleague about a short follow-up call.
Risks
Current to 9 Oct 26- The security and access answer for tenant call data is outstanding and Helen says it would stop the deal if it goes wrong.
- The counting rule for repairs jobs must be agreed with Paul's team before anything goes to the board.
- Calls and tickets without a job reference will not match, which could weaken the board-facing answer.
Opportunities
Current to 9 Oct 26- A lighter leadership view of two board pack sections using the Growth tier dashboards builder.
- Paul showed interest in building his own dashboards, which suggests wider team adoption.