B-Viz
Tom Ashdown

Cottingley Software / BG-Demo – Demo

Callcompleted

Cottingley Software logo Cottingley Software · 4 Sep 2026 13:00

Holly Garside's main worry is answers staying right when her customers change systems. She wants a decision signed before the end of November, with her chief executive on the proposal call.

What was said

What this says

As at Fri 9 Oct 2026

Holly Garside's main worry is answers staying right when her customers change systems. She wants a decision signed before the end of November, with her chief executive on the proposal call.

What happened: Hannah Lowe explained that B-Viz runs inside the customer's own Snowflake account. She walked through a scheduling connector and the flat indexed count as the sign of a broken source.

Customer view: Holly said her fear is confidently wrong answers after a system change. She liked the point that availability is not freshness.

Commercial: Holly said a few people have tried it and care managers like it. She wants it signed before the end of November, and her chief executive will ask about security.

Watch: Hannah will not call the security answer final until it is checked. Name hiding for care staff is also unconfirmed against her set-up.

AI · claude-sonnet-5-5 · as at Fri 9 Oct 2026

Themes

As at Fri 9 Oct 2026
Theme
Data freshness and timetable
Importance
upsell
Sentiment
positive
Voice
champion

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Hannah Lowe sends the connector notes, security answer and sync diagram to Holly, copying Tom Ashdown.
  • Tom Ashdown books the proposal call with Holly and her chief executive.
  • Hannah confirms name hiding against Cottingley Software's set-up.

Risks

As at Fri 9 Oct 2026
  • Stale or wrong answers after her customers change systems is her stated worry.
  • The security answer for her chief executive is not yet final.
  • Connector ownership on her side is not settled.

Opportunities

As at Fri 9 Oct 2026
  • She wants a decision signed before the end of November.
  • The dashboards builder in the tier shown matches her teams' differing needs.

Transcript

  1. Tom Ashdown
    Tom Ashdown
    Hiya Holly, can you see us? Hannah's joined, I think she's just got her camera on now.
  2. Holly Garside
    Holly Garside
    I can see you, Tom. Hi Hannah. Yes, it's on. Sorry, I was on the other call.
  3. Hannah Lowe
    Hannah Lowe
    Hi Holly, no problem at all. Before I start, what's the one thing you most need to know about the architecture?
  4. Holly Garside
    Holly Garside
    Honestly? Whether it stays right when our customers change their systems. That's what I lose sleep over.
  5. Hannah Lowe
    Hannah Lowe
    Good, that's the right worry. The short answer is it's built to notice. The longer answer is that it's only as good as the connector.
  6. Holly Garside
    Holly Garside
    Right. Go on then.
  7. Hannah Lowe
    Hannah Lowe
    I'll share a diagram first, so you can see where the data goes. Can you see the picture?
  8. Holly Garside
    Holly Garside
    Yes. It all runs in our own Snowflake account, is that right?
  9. Hannah Lowe
    Hannah Lowe
    To be precise, yes. It's built and run inside your Snowflake account, so your data stays with you. I'll put the detail in writing.
  10. Tom Ashdown
    Tom Ashdown
    Hannah's very good on this, Holly. Hannah, can you run the connector example?
  11. Hannah Lowe
    Hannah Lowe
    Yes. I'll take a single source, the scheduling records, and walk through a sync.
  12. Holly Garside
    Holly Garside
    Scheduling, perfect. That's where we keep getting trouble.
  13. Hannah Lowe
    Hannah Lowe
    Then it's a good example. Here's the connector page. You can see the last successful sync and the count of records indexed.
  14. Holly Garside
    Holly Garside
    And if the count stops moving?
  15. Hannah Lowe
    Hannah Lowe
    That's the signal. The count goes flat, and it usually means the source changed. A field was renamed, or a permission was removed.
  16. Holly Garside
    Holly Garside
    Yes. That's most Mondays for us. Someone updates a system and nobody tells us.
  17. Hannah Lowe
    Hannah Lowe
    That's why we'd want an owner for each connector on your side, not just us. I'll make that a point in the written notes.
  18. Holly Garside
    Holly Garside
    Good. Who owns it on your side? Tom?
  19. Tom Ashdown
    Tom Ashdown
    On our side it's the solutions team and the account team. The owner on yours should be someone close to the source system.
  20. Holly Garside
    Holly Garside
    Right. Fine. Hannah, what about the answers? Can I trust them?
  21. Hannah Lowe
    Hannah Lowe
    Trust, but check. Every answer links back to the record it came from. If the record is stale, you'll see it in the timestamp.
  22. Holly Garside
    Holly Garside
    Good. I had this at my last place and the answers were confidently wrong for a month.
  23. Hannah Lowe
    Hannah Lowe
    That's the failure we design against. Availability isn't the same as freshness. An answer can be available and still be out of date.
  24. Holly Garside
    Holly Garside
    Yes, I like that distinction. Can you show it?
  25. Hannah Lowe
    Hannah Lowe
    I can show a question and the answer's timestamp. Let me pull one up.
  26. Tom Ashdown
    Tom Ashdown
    While she does that, Holly, how's the trial going on your team? Have you had people in it?
  27. Holly Garside
    Holly Garside
    A few. The care managers like it. The managers want the renewals view. Everyone wants something different, which is fine.
  28. Tom Ashdown
    Tom Ashdown
    That's the good problem. The tier you're looking at is built for several teams, so you're in the right place.
  29. Hannah Lowe
    Hannah Lowe
    Okay, here. The question is what's been raised on the largest agency's account this quarter. The answer shows the sources and the dates for each one.
  30. Holly Garside
    Holly Garside
    Nice. And the dashboards, can I build my own?
  31. Hannah Lowe
    Hannah Lowe
    Yes. The dashboards builder is part of the tier you're looking at, so your team can make their own views without asking us.
  32. Holly Garside
    Holly Garside
    Good. Now let's talk about the renewal side again, that's the bit I need.
  33. Tom Ashdown
    Tom Ashdown
    Sure, we'll do that on the proposal call. Hannah, is there anything else on the security side?
  34. Holly Garside
    Holly Garside
    Wait, security. Is that a thing for us? Our chief executive will ask.
  35. Hannah Lowe
    Hannah Lowe
    It's a standard question, and I'd rather answer it properly than quickly. I'll put the written answer together, and I won't call it final until it's checked.
  36. Holly Garside
    Holly Garside
    Thanks. Let's keep going on the demo, then.
  37. Hannah Lowe
    Hannah Lowe
    Here's the question history. It shows who asked what, and when. You can choose whether names show.
  38. Holly Garside
    Holly Garside
    Names hidden for care staff, managers see everything. Is that something you set up?
  39. Hannah Lowe
    Hannah Lowe
    Yes, that's a configuration choice. I'd want to confirm it against your set-up before I promise it.
  40. Holly Garside
    Holly Garside
    Fine. That's useful. My real concern is how the usage looks in a month.
  41. Tom Ashdown
    Tom Ashdown
    Holly, while Hannah's looking, can I ask about the timetable? Are we aiming at a decision before the end of November?
  42. Holly Garside
    Holly Garside
    That's the plan. I'd like it signed before the end of November, if we can.
  43. Tom Ashdown
    Tom Ashdown
    Lovely. Let's get something in the diary for the proposal, then.
  44. Holly Garside
    Holly Garside
    Yes. And the chief executive needs to be on it.
  45. Tom Ashdown
    Tom Ashdown
    Agreed. I'll book it with you after this.
  46. Hannah Lowe
    Hannah Lowe
    Okay, to close. I'll send the connector notes, the security answer and the sync diagram. I'll mark anything not yet confirmed.
  47. Holly Garside
    Holly Garside
    Great. Send them to me and copy Tom.
  48. Tom Ashdown
    Tom Ashdown
    Will do. Holly, thanks for the time, and Hannah, cheers.
  49. Hannah Lowe
    Hannah Lowe
    Thank you both. Speak soon.
  50. Holly Garside
    Holly Garside
    Thanks everyone. Bye.
  51. Tom Ashdown
    Tom Ashdown
    Bye Holly.

BG-Demo is a fictional company; every organisation and person here is invented. B-Viz is the tool. Data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Viz 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 B (the speech bubble) in the header, or open the Ask B page. Type a question, or pick one of the suggestions.

What the data covers

DataRecords
Organisations300
People at customers1,880
BG-Demo staff records (in post and leavers)65
Calls2,593
Email threads3,882
Support tickets1,502
Documents1,582
Deals403
Invoices365
Events49
News items147

Data as of Fri 9 Oct 2026. Text marked AI was written by the AI 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.

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

Who to contact

Email info@b-viz.com or talk to your B-Viz account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Viz · read-only