B-Viz
Tom Ashdown

Eccup Software / BG-Demo – Demo

Callcompleted

Eccup Software logo Eccup Software · 4 Mar 2024 12:00

Demo to Holly Garside and Becky Lofthouse. They liked ticket history beside renewal dates and asked about data location. The £54k deal figure was given as provisional, and nothing is agreed without Vincent and the chief executive.

What was said

What this says

As at Fri 9 Oct 2026

Demo to Holly Garside and Becky Lofthouse. They liked ticket history beside renewal dates and asked about data location. The £54k deal figure was given as provisional, and nothing is agreed without Vincent and the chief executive.

What happened: Tom showed a provider page, chat and the dashboards builder on a demo workspace shaped like Eccup Software's world. Tobias answered the data location question: B-Viz runs inside the customer's own Snowflake account.

Customer view: Becky said the ticket history under the renewal date is the part she rebuilds in a spreadsheet every quarter. Holly wanted answers that link back to records so they can be checked.

Commercial: Tom quoted the pencilled deal at fifty-three thousand eight hundred, including implementation, and said it would be confirmed in the proposal. Holly will bring Vincent to the next call and said nothing is agreed until he and the chief executive have looked at it.

Watch: Becky worried about who sets it up, as there is no spare data person. Tom promised connector limits in writing with the proposal. The target close was 22 Apr 2024.

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

Themes

As at Fri 9 Oct 2026
Theme
Growth tier product demo
Importance
upsell
Sentiment
positive
Voice
champion

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Tom Ashdown to send the recording, a short note and the proposal outline, including connector limits in writing.
  • Holly Garside to bring Vincent Ackerley to the next call.
  • Tom Ashdown to diary a follow-up for the following week.

Risks

As at Fri 9 Oct 2026
  • Eccup Software has no spare data person, so setup capacity could slow implementation.
  • Nothing is agreed until the chief financial officer and chief executive have reviewed the proposal.

Opportunities

As at Fri 9 Oct 2026
  • Growth tier sale with fixed-fee implementation, using ticket and renewal views that Becky rebuilds by hand today.
  • Calls and emails can be connected later as extra sources.

Transcript

  1. Tom Ashdown
    Tom Ashdown
    Hello, hello. Can you hear me alright? I've got you on screen but I'm not sure my mic's playing ball.
  2. Holly Garside
    Holly Garside
    Loud and clear, Tom. Hi. Becky's just joining, she's stuck behind a meeting that overran.
  3. Tom Ashdown
    Tom Ashdown
    No drama, we've got a minute. How's your week been? Anything exciting up in Leeds?
  4. Holly Garside
    Holly Garside
    Busy. It's renewal season for a few of our providers, so I've lived in spreadsheets since Monday. Which is rather why we're here.
  5. Becky Lofthouse
    Becky Lofthouse
    Sorry, sorry. Hi everyone. Can you see me? Right, yes, hello.
  6. Tom Ashdown
    Tom Ashdown
    Hi Becky. Good to meet you properly. I've also got Tobias with me, our CTO. He built the thing, so if I say anything daft he'll correct me.
  7. Tobias Renwick
    Tobias Renwick
    Hello both. Before Tom starts, can I ask what your security people will need to see? I'd rather we cover that early than leave it to the end.
  8. Holly Garside
    Holly Garside
    Fair. Honestly, the main question is where the data lives. We hold information about care providers and their staff, so it can't wander off anywhere.
  9. Tobias Renwick
    Tobias Renwick
    Then the honest answer is quite reassuring. B-Viz is built and run inside your own Snowflake account. The data stays under your controls, and we don't copy it into a store of ours. To be precise, we work in your environment, we don't take it away.
  10. Holly Garside
    Holly Garside
    Good. That's the sentence I'll need to repeat to our own team. Let's start with what it looks like though.
  11. Tom Ashdown
    Tom Ashdown
    Right. I'm sharing my screen now. What you're looking at is a demo workspace, but I've set it up with the shape of your world. Providers, tickets, renewals, usage. Say if it's off.
  12. Holly Garside
    Holly Garside
    Looks about right. Can you show me one provider end to end? I want to see what I'd see on a renewal call.
  13. Tom Ashdown
    Tom Ashdown
    Yep. So this is a provider page. Contract dates at the top, pulled from the CRM. Then tickets from the helpdesk, then usage from your product, all on one page. Nobody has stitched that by hand.
  14. Becky Lofthouse
    Becky Lofthouse
    Hang on, go back. Is that the ticket history sitting under the renewal date? Because that's exactly the bit I rebuild in a spreadsheet every quarter.
  15. Tom Ashdown
    Tom Ashdown
    That's it. Same page, same provider. And this is chat, so rather than click about you just ask.
  16. Tom Ashdown
    Tom Ashdown
    I'll type: which providers renew soon and have raised more tickets than usual. Give it a moment.
  17. Tom Ashdown
    Tom Ashdown
    There. A list, and each line links back to the records it came from. So you can check it rather than just trust it.
  18. Holly Garside
    Holly Garside
    That's what I care about. What does the usage say? Can I ask it that, per provider?
  19. Tom Ashdown
    Tom Ashdown
    Go on, tell me what to type.
  20. Holly Garside
    Holly Garside
    Which providers have fewer active users this quarter than last, and when do they renew?
  21. Tom Ashdown
    Tom Ashdown
    Okay, so, that's the shape of it. It's showing falls in activity next to renewal dates. The thing to keep in mind is it's only as fresh as your last refresh, and the nightly refresh finishes early on business days.
  22. Tobias Renwick
    Tobias Renwick
    If I can add to that. The trade-off is that it reads from the sources you connect, so the quality of an answer depends on the connectors being healthy. We show you when a source stops loading, so you know before it matters.
  23. Becky Lofthouse
    Becky Lofthouse
    Would that tell us if, say, the helpdesk connection broke?
  24. Tobias Renwick
    Tobias Renwick
    Yes. Records indexed would go flat, and we'd see it and so would you. It wouldn't fail silently.
  25. Holly Garside
    Holly Garside
    Mm. Good. Can you show me the dashboards? Our chief executive likes a picture.
  26. Tom Ashdown
    Tom Ashdown
    Ah, the dashboards builder. That comes with Growth, which is the tier we've scoped for you. Let me open one.
  27. Tom Ashdown
    Tom Ashdown
    So this is renewals by month, split by provider size, built from a question rather than from code. Becky, you could make this yourself.
  28. Becky Lofthouse
    Becky Lofthouse
    I would not want to bet on that, but I'm willing to be talked into it. Is there a way to see who's asking what? Like for training.
  29. Tom Ashdown
    Tom Ashdown
    Yeah, there's usage reporting for your own admins. Questions asked, by person. Handy for spotting who's getting value and who needs a nudge.
  30. Holly Garside
    Holly Garside
    Right. Let's do a real one. Pick a provider from your sample, and show me how I'd prepare for a tricky renewal in five minutes.
  31. Tom Ashdown
    Tom Ashdown
    Love that. Give me a second.
  32. Tom Ashdown
    Tom Ashdown
    So I asked for a summary of the last quarter of tickets, grouped by category. Connector sync, how-to, that kind of thing. Then the usage trend underneath. You'd walk into the call knowing the story.
  33. Holly Garside
    Holly Garside
    That's the bit that would have saved me last renewal round. Becky, you'd use that, wouldn't you?
  34. Becky Lofthouse
    Becky Lofthouse
    Daily, probably. My worry is who sets it up. We don't have a spare data person.
  35. Tobias Renwick
    Tobias Renwick
    That's where implementation comes in. We connect the sources and check the results with you, and for Growth that runs over several weeks. You wouldn't be left to wire it up.
  36. Holly Garside
    Holly Garside
    Okay. How many connectors would we realistically need? Helpdesk, CRM, the product usage, finance probably.
  37. Tom Ashdown
    Tom Ashdown
    That's about right, and Growth has room beyond that. I'd rather not quote you limits from memory, so I'll put it in writing with the proposal.
  38. Holly Garside
    Holly Garside
    Sensible. And roughly where does this land commercially? Vincent will ask before I've finished my sentence.
  39. Tom Ashdown
    Tom Ashdown
    So the deal we've pencilled in is fifty-three thousand eight hundred, which includes the implementation. Don't hold me to it on the call, I'll confirm it properly in the proposal. Is Vincent able to join the next one?
  40. Holly Garside
    Holly Garside
    I'll get him there. He'll want a usage case, and I'm not going to commit anything without our chief executive anyway.
  41. Tom Ashdown
    Tom Ashdown
    Completely fair. Let's get something in the diary for next week.
  42. Becky Lofthouse
    Becky Lofthouse
    Before we stop sharing, one more thing. Can I search across call notes and emails too, or is it just tickets and the CRM?
  43. Tobias Renwick
    Tobias Renwick
    Calls and emails can be connected as well. If the source is on our supported list, it joins the same layer. We'd agree the list with you first.
  44. Holly Garside
    Holly Garside
    Right, I think I've seen enough to take it to Vincent. Tom, can you send the recording and a short note of what we covered?
  45. Tom Ashdown
    Tom Ashdown
    Leave that with me. I'll send it today with the proposal outline, and we'll aim to close this out by Monday 22 April 2024, if that still suits you.
  46. Holly Garside
    Holly Garside
    That works as a target. Nothing is agreed until Vincent and our chief executive have looked at it.
  47. Tom Ashdown
    Tom Ashdown
    Absolutely. Thanks both, thanks Tobias. Speak soon.
  48. Becky Lofthouse
    Becky Lofthouse
    Thanks everyone, that was useful. Bye.
  49. Holly Garside
    Holly Garside
    Thanks all. Bye.

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