B-Viz
Tom Ashdown

Kelbrook Mutual Insurance / BG-Demo – Discovery

Callcompleted

Kelbrook Mutual Insurance logo Kelbrook Mutual Insurance · 30 Oct 2023 16:00

Rebecca Ainsworth described member services lacking one view of a member. Malcolm Hebden, the CFO, wants full cost over a two-year term and said the board decides. A demo was agreed as no commitment, with the proposal to follow it.

What was said

What this says

As at Fri 9 Oct 2026

Rebecca Ainsworth described member services lacking one view of a member. Malcolm Hebden, the CFO, wants full cost over a two-year term and said the board decides. A demo was agreed as no commitment, with the proposal to follow it.

What happened: Tom Ashdown ran discovery with Rebecca Ainsworth and Malcolm Hebden. Rebecca described relationship managers piecing a member together from the policy system, claims, call recordings and inboxes.

Customer view: Malcolm said he was there to listen and would not decide on the call. He wants every cost laid out, and the proposal after the demo, not before.

Commercial: Tom pointed to the Growth tier and a working deal value of £124k, stating it is the total including implementation, not an annual price. He promised the split, term and renewal position in writing, and an order form marker of Wed 3 Jan 2024.

Watch: Malcolm said he would never sign a multi-year commitment without the board. The Snowflake account is run by a small IT team, so IT and compliance sign-off is a gate. Competitors were raised but none had been spoken to in depth.

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

Themes

As at Fri 9 Oct 2026
Theme
Discovery, member view, cost
Importance
neutral
Sentiment
positive
Voice
decision-maker

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Tom Ashdown to send a note confirming the demo commits the customer to nothing.
  • Tom to send Rebecca the list for the demo data slice and check Marcus Bell's diary for demo dates.
  • Malcolm to ask the IT lead to join a technical call.

Risks

As at Fri 9 Oct 2026
  • Malcolm will not commit to a multi-year term without board approval and wants the whole cost stated with its base.
  • IT and compliance must be comfortable that member data stays in the customer's own Snowflake account.
  • Helpline staff may be uneasy with new tools, which could slow adoption.

Opportunities

As at Fri 9 Oct 2026
  • Growth tier across member services, underwriting and claims, with a two-year arrangement of interest to the CFO.
  • Extra users and connectors can be priced in the proposal, as Malcolm asked, leaving room to grow later.

Transcript

  1. Tom Ashdown
    Tom Ashdown
    Hello, hello. Can you hear me alright? I've got the little green bar moving on my side, so I think we're recording.
  2. Rebecca Ainsworth
    Rebecca Ainsworth
    I can hear you fine, Tom. Good afternoon. Malcolm's just dialling in, he's in the other room with the board papers, so give him a minute.
  3. Tom Ashdown
    Tom Ashdown
    No drama, we've got all the time. How's your week been, Rebecca? Properly busy, or just normal busy?
  4. Rebecca Ainsworth
    Rebecca Ainsworth
    Normal busy, which is to say not very quiet. I had a lovely one on Tuesday, actually. A lady who looks after the parish hall for a village church rang the helpline. She was a bit tearful because the hall's heating had gone and she wanted to know if the gutters were covered as well. And the first thing she said was, I've told someone all this before.
  5. Tom Ashdown
    Tom Ashdown
    Ah, that's the one that gets you, isn't it. Having to say it twice.
  6. Rebecca Ainsworth
    Rebecca Ainsworth
    It is. Let's not make them tell us twice, that's what I keep saying to the team. She'd spoken to claims the month before and to her relationship manager before that, and nobody on the helpline could see either conversation without ringing round. That's more or less why you're here.
  7. Malcolm Hebden
    Malcolm Hebden
    Good afternoon, both. Apologies, I was finishing something. Can you hear me?
  8. Tom Ashdown
    Tom Ashdown
    Loud and clear, Malcolm. Good afternoon. Thanks for making the time, I know the diary at this end of the year is a bit of a scrum.
  9. Malcolm Hebden
    Malcolm Hebden
    It is, but Rebecca was quite firm that I should be on this one. I should say at the outset that I am here to listen and to understand the shape of it. I won't be deciding anything on the call.
  10. Tom Ashdown
    Tom Ashdown
    Completely fair, and that's exactly how I'd like to use the time. Discovery, so mostly me asking questions and you telling me where it hurts. I'll say a bit about what we do near the end, and then we can work out whether a demo on your own data is worth anyone's time. Does that sound sensible?
  11. Rebecca Ainsworth
    Rebecca Ainsworth
    That sounds right to me.
  12. Malcolm Hebden
    Malcolm Hebden
    Yes. May I ask one thing first? What would be the usual route from a call like this to an actual commitment? I would like to know what it commits us to, and for how long, before we get fond of anything.
  13. Tom Ashdown
    Tom Ashdown
    Good question, and I'd rather you asked it now. Usual route is this call, then a demo on your data so you're not looking at a glossy sample, then a proposal in writing, then an order form under our master agreement. Nothing binds you until you've signed that last bit. I'll go through terms properly when we get there, I don't want to quote you things off the top of my head.
  14. Malcolm Hebden
    Malcolm Hebden
    Thank you. That is helpful.
  15. Tom Ashdown
    Tom Ashdown
    Right then. Rebecca, you've told me a bit already, but could you walk me through what actually happens when a relationship manager goes to a member's renewal meeting? Start from the day before.
  16. Rebecca Ainsworth
    Rebecca Ainsworth
    Right. So we insure schools, churches, charities, community buildings, and every one of them is a member, we're owned by them. The relationship manager has a renewal coming up, say a primary school in the north of the county. The day before, they open the policy system and see the cover and the premium history. Then they go to the claims system and look at whether there's been anything in the year. Then they ask someone on the helpline whether the school has rung us, and that someone has to go and search the call recordings, or more often just remembers.
  17. Tom Ashdown
    Tom Ashdown
    Mm. So three places, and the third one is basically a person.
  18. Rebecca Ainsworth
    Rebecca Ainsworth
    Basically a person, yes. And emails are a fourth. People's inboxes. A head teacher will have written to someone about a flood last spring and that's sitting in one inbox and nowhere else.
  19. Tom Ashdown
    Tom Ashdown
    And how long does that prep take, roughly? Not to the minute, just a feel.
  20. Rebecca Ainsworth
    Rebecca Ainsworth
    It depends on the person. The good ones spend a good chunk of the morning on it, and honestly I think that's time we're not giving to the member. The less experienced ones skip bits, and then the meeting starts from what we think we know rather than the facts. Is that the whole picture? That's the question I want them asking themselves, and at the moment they can't answer it.
  21. Tom Ashdown
    Tom Ashdown
    Right, that's really clear. What about underwriting and claims, are they feeling the same thing or is it mainly your side?
  22. Rebecca Ainsworth
    Rebecca Ainsworth
    It's all of us, differently. Underwriting want to see claims history alongside the policy without asking for an extract. Claims want to know if the member's rung us three times this month before they ring back. Nobody has the same picture. I'd say member services feels it first, because the member's on the phone to us when it goes wrong.
  23. Malcolm Hebden
    Malcolm Hebden
    If I may add the finance view. We have, at present, some reconciliation work every month that is done by hand, and I suspect part of the reason is that different teams hold slightly different versions of the same member. I cannot put a number on it today and I would not want to guess.
  24. Tom Ashdown
    Tom Ashdown
    No, and please don't guess, we'd only be building on sand. That's useful though. So the pain is partly about the member's experience and partly about people's time and trust in the figures.
  25. Malcolm Hebden
    Malcolm Hebden
    Members' money, not ours. If we spend hours reconciling, it is their money being spent on it. That is how I frame it with the board.
  26. Tom Ashdown
    Tom Ashdown
    Fair enough. Can I ask about the systems themselves? You don't need to name every product, just what kind of thing they are. Policy admin, claims, the phones, email, anything else that matters?
  27. Rebecca Ainsworth
    Rebecca Ainsworth
    There's the policy administration system, which is the old workhorse. A separate claims system. The call recorder on the helpline. Microsoft 365 for email and documents, and a lot of important things live in shared folders on SharePoint. And relationship managers keep their own notes in the CRM, when they remember.
  28. Tom Ashdown
    Tom Ashdown
    Ha, when they remember. Right. And is there a data warehouse anywhere, or a team who looks after data? I'm thinking about Snowflake in particular, because that's where we'd build.
  29. Malcolm Hebden
    Malcolm Hebden
    We do have a Snowflake account. It is used by the finance and actuarial teams for reporting, and a small team in IT looks after it. I would need to check what they would be comfortable with before saying more.
  30. Tom Ashdown
    Tom Ashdown
    That's the best answer you could've given me, honestly. So the way we work is we build inside your Snowflake account, not ours. Your data stays where it is, under your controls, and the brain sits on top. Your IT people stay in charge of the keys, and I'd want them in the room early rather than finding out in week six.
  31. Rebecca Ainsworth
    Rebecca Ainsworth
    And that matters for us. We're regulated, and I'd be nervous about anything where member data leaves the building.
  32. Tom Ashdown
    Tom Ashdown
    Understood, and it doesn't leave. I'll leave the detail on security to when we've got the right people on a call, I'd rather someone who knows the plumbing answered that properly than me waving my arms about.
  33. Malcolm Hebden
    Malcolm Hebden
    That is a sensible approach. Please do bring the technical person, and I will ask our IT lead to join.
  34. Tom Ashdown
    Tom Ashdown
    Brilliant. Now, who'd actually use it? If this existed tomorrow, who's the first person asking it a question?
  35. Rebecca Ainsworth
    Rebecca Ainsworth
    The relationship managers, no question. Then the helpline team, because they'd see a member's recent calls and claims before they say hello. Then I'd hope underwriting and claims would join in once they'd seen it work. I don't want to promise their teams will adopt it, they'd have to see it for themselves.
  36. Tom Ashdown
    Tom Ashdown
    That's how it usually goes, one team proves it and the others come to you. What does the member see, Rebecca? Sorry, I'm borrowing your line. If it works, what's different for the person on the phone?
  37. Rebecca Ainsworth
    Rebecca Ainsworth
    They don't repeat themselves. They get someone who says, I can see you rang about the hall heating last month, how did that go? That's all. It's not clever, it's just being known.
  38. Tom Ashdown
    Tom Ashdown
    Lovely. Let me do the bit about us then, quickly, and you tell me where I'm wide of the mark. So B-Viz is one layer over your CRM, calls, emails, tickets and finance data, built in your Snowflake. People ask it questions in plain English, they get pages and search and chat, and every answer points back at the source so you can check it.
  39. Malcolm Hebden
    Malcolm Hebden
    Pointing back at the source is important. Can it be wrong?
  40. Tom Ashdown
    Tom Ashdown
    It can be wrong if the data underneath is wrong or stale, and I'd be lying if I said otherwise. That's why it shows its sources, and why we watch how fresh each connector is. It refreshes overnight, so people start the day on yesterday's close, not last month's.
  41. Malcolm Hebden
    Malcolm Hebden
    Thank you for saying so plainly. Many suppliers do not.
  42. Rebecca Ainsworth
    Rebecca Ainsworth
    Can I ask about the calls? We record the helpline, and some of those calls are difficult. Someone's lost a roof or a minibus. Is it all transcribed and sitting in front of everyone?
  43. Tom Ashdown
    Tom Ashdown
    Good one. It follows your permissions, so who sees what is something you decide with your IT team, not something we decide for you. I'd want to understand which teams should see call content and which shouldn't before we switch any of it on.
  44. Rebecca Ainsworth
    Rebecca Ainsworth
    Good. Because I'd start with claims and policy and add the calls once we were happy.
  45. Tom Ashdown
    Tom Ashdown
    That works fine. We can phase connectors, it's common. Malcolm, I can tell you're itching about the commercial side, so shall I give you the shape of it now?
  46. Malcolm Hebden
    Malcolm Hebden
    Please. With the base for every figure, if you would.
  47. Tom Ashdown
    Tom Ashdown
    Always. So you'd be looking at our Growth tier, because you've got several teams in play, not one. Growth is an annual subscription, plus a one-off fixed-fee implementation at the start. The working number we've got against this opportunity is £123,600, and I want to be careful what that is. It's the total value of the deal, so it includes the implementation as well as the subscription. It is not an annual price. I'll confirm the split in writing, because I don't trust myself quoting it from memory.
  48. Malcolm Hebden
    Malcolm Hebden
    Thank you, that is precisely the distinction I wanted. So £123,600 is the whole of the deal, the one-off element included, over whatever term is proposed?
  49. Tom Ashdown
    Tom Ashdown
    Yes, that's how I'd read it, over the term we propose. And I'd rather confirm the term and the split than let you carry a half-remembered version into your board. Leave that with me.
  50. Malcolm Hebden
    Malcolm Hebden
    Then let me say how we think. We plan in multi-year cycles. A two-year arrangement would be of interest, since it gives predictability, but I would never sign a multi-year commitment without the board. And over the full term, please, I would want to see every cost laid out: subscription, implementation, anything that moves.
  51. Tom Ashdown
    Tom Ashdown
    Understood, and a two-year view is perfectly normal for us. I'll set it out so a board paper can lift it straight off the page. Anything that could change the price during the term, you'll see it in the proposal, not in the small print.
  52. Malcolm Hebden
    Malcolm Hebden
    Good. And what happens to price at the end of the term? I would like to know that now rather than in two years' time.
  53. Tom Ashdown
    Tom Ashdown
    Fair challenge. I'll put the renewal position in writing as well, I won't wing it on a call. What I can say is you'd have a named person on our side, Marcus Bell, who looks after customers after they go live, and he'd be the one raising renewal with you well ahead of time.
  54. Rebecca Ainsworth
    Rebecca Ainsworth
    Will Marcus be on the demo, or is that just you?
  55. Tom Ashdown
    Tom Ashdown
    I'd like him there, so you meet him before you've signed anything rather than after. I'll check his diary and come back to you.
  56. Rebecca Ainsworth
    Rebecca Ainsworth
    I'd like that. People here care about who they're dealing with. We're a mutual, it's all relationships.
  57. Tom Ashdown
    Tom Ashdown
    I can tell, and I like that about you. Right, a few more questions, then next steps. Malcolm, who else would need to be comfortable? The board, obviously. Anyone else?
  58. Malcolm Hebden
    Malcolm Hebden
    Our head of IT, as discussed, and our compliance function, since we handle member data under the regulator's eye. Rebecca will be the day to day sponsor. The board would see a paper from me, and I would not want to take one forward before the proposal is firm. Our aim would be to have the decision made around the start of the new year, though I do not wish to be held to that.
  59. Tom Ashdown
    Tom Ashdown
    No, understood. On our side we've pencilled Wednesday 3 January 2024 as the point we'd hope to have an order form in front of you, but that's just a marker so we both plan backwards from something. It moves if you need it to.
  60. Malcolm Hebden
    Malcolm Hebden
    A marker is fine. I will treat it as no more than that.
  61. Rebecca Ainsworth
    Rebecca Ainsworth
    Tom, can I ask about the demo? You said on your data. What would you need from us to do that, because I don't want to hand over a mountain of member records for a first look.
  62. Tom Ashdown
    Tom Ashdown
    And you shouldn't. Usually we start small. A slice of policies, claims and a few call records, with anything sensitive masked or left out, working inside your own Snowflake so it never travels. Your IT lead would agree what the slice is. I'll write it down so nobody's guessing.
  63. Rebecca Ainsworth
    Rebecca Ainsworth
    That's reassuring. And how long does it take to get to the point where you can show us something real?
  64. Tom Ashdown
    Tom Ashdown
    I'd rather give you a proper answer than a number I'd have to walk back. It depends how quickly we get access sorted, and that's mostly down to your IT team's diary. I'll come back with a plan once we've talked to them.
  65. Malcolm Hebden
    Malcolm Hebden
    That is acceptable. I would prefer an honest range to a confident figure.
  66. Tom Ashdown
    Tom Ashdown
    You'll get honest. Rebecca, one more from me. If we got this wrong, if we did the demo and it didn't land, what would the reason be?
  67. Rebecca Ainsworth
    Rebecca Ainsworth
    Honestly? If it was clever but the relationship managers didn't trust it. Or if it showed us half a picture and we didn't know which half. Is that the whole picture, you see. If I can't tell what's missing, I'd rather not have it.
  68. Tom Ashdown
    Tom Ashdown
    That's a good test and I'll build the demo around it. We'll show where the data came from and where there are gaps, not hide them.
  69. Malcolm Hebden
    Malcolm Hebden
    May I raise one more point? Competing options. We have not spoken to anyone else in any depth, but I would be remiss not to ask whether we should.
  70. Tom Ashdown
    Tom Ashdown
    You should always look around, I'd think less of you if you didn't. I'd only say, compare them on where the data lives, who holds the keys and how it deals with all your sources together, not just one. Beyond that I'll leave you to judge, I'm not going to run anyone down.
  71. Malcolm Hebden
    Malcolm Hebden
    Thank you. That is a measured answer.
  72. Rebecca Ainsworth
    Rebecca Ainsworth
    I'm happy to move to a demo, for what it's worth. As long as Malcolm's happy that it isn't a commitment.
  73. Malcolm Hebden
    Malcolm Hebden
    I am content with a demonstration. It commits us to nothing and I would like that written down, if only in an email.
  74. Tom Ashdown
    Tom Ashdown
    It'll be in the email, in black and white. Right, let me play back what I've heard, and shout if I've got it wrong. The member experience is the heart of it: people shouldn't have to repeat themselves. The relationship managers lose time pulling the picture together from the policy system, claims, calls and inboxes. You're regulated, so the data stays in your Snowflake. And Malcolm needs the whole cost over a two-year view with every base stated, because the board decides.
  75. Rebecca Ainsworth
    Rebecca Ainsworth
    That's it. You've missed nothing that I can think of.
  76. Malcolm Hebden
    Malcolm Hebden
    One small addition. I would want the proposal to say what changes if we need more people or more systems than first planned. Not today, but on paper.
  77. Tom Ashdown
    Tom Ashdown
    Noted. Extra people, extra connectors, what they'd cost and when. Going in the proposal.
  78. Rebecca Ainsworth
    Rebecca Ainsworth
    Can I just ask about the helpline team specifically? Some of them aren't very comfortable with new tools. I'd want them to feel it was helping, not watching them.
  79. Tom Ashdown
    Tom Ashdown
    That's a real point, and it's a rollout thing as much as a product thing. Marcus does a lot of work with teams on that side, getting people comfortable with it. We can talk about how training would work when we get nearer. I wouldn't want to promise a plan until I've heard more about the team.
  80. Rebecca Ainsworth
    Rebecca Ainsworth
    That's fair. I'd like to bring two or three of the helpline team to the demo, if that's alright. They'll tell me straight whether it makes sense.
  81. Tom Ashdown
    Tom Ashdown
    Please do, that's the best test going. Bring the sceptics.
  82. Rebecca Ainsworth
    Rebecca Ainsworth
    Oh, I will.
  83. Malcolm Hebden
    Malcolm Hebden
    Before we close, may I ask who on your side is accountable for this from start to finish?
  84. Tom Ashdown
    Tom Ashdown
    Me until you sign, I own the commercial side and the proposal. After that, Marcus looks after you day to day. One name each, so you always know who to ring.
  85. Malcolm Hebden
    Malcolm Hebden
    That is clear. Thank you.
  86. Tom Ashdown
    Tom Ashdown
    So, next steps, and I'll say who does what so we don't all assume. One: I send a short note today or tomorrow with what we covered, including that the demo commits you to nothing. Two: I send Rebecca a plain list of what we'd need for the demo slice, and she passes it to your head of IT. Three: Malcolm, you ask your IT lead to join a short technical call. Four: I check Marcus's diary and propose a few dates for the demo. Does that match what you remember?
  87. Rebecca Ainsworth
    Rebecca Ainsworth
    Yes. I'll speak to our head of IT this week and tell him roughly what's coming. He'll want to know it's inside our own Snowflake before he says anything else.
  88. Malcolm Hebden
    Malcolm Hebden
    And I will ask for a time on his diary. May I suggest that the proposal follows the demo, not precedes it? I would prefer to see the thing before I read the price.
  89. Tom Ashdown
    Tom Ashdown
    Suits me. Demo first, proposal after, and the proposal will carry the whole cost over the full term with the base for every figure, as you asked.
  90. Malcolm Hebden
    Malcolm Hebden
    Excellent.
  91. Rebecca Ainsworth
    Rebecca Ainsworth
    Tom, thank you for not pitching at us. I was braced for a long deck.
  92. Tom Ashdown
    Tom Ashdown
    Ha, there's a deck somewhere, I just didn't want to subject you to it. Lots of chat is better. If you think of anything between now and the demo, just email me, no need to save it up.
  93. Rebecca Ainsworth
    Rebecca Ainsworth
    I will. Actually, one thing now, and then I'll stop. The parish hall lady I mentioned. If your system had been in place, would she have been looked after any better?
  94. Tom Ashdown
    Tom Ashdown
    I can't say what would have happened for her, and I'd not want to claim it. What I can say is the person who picked up the phone would have seen her last conversations before saying hello. What they did with that is down to your people, and from what I've heard today they'd do something decent with it.
  95. Rebecca Ainsworth
    Rebecca Ainsworth
    That's an honest answer. Thank you.
  96. Malcolm Hebden
    Malcolm Hebden
    If there is nothing further, I shall return to my papers. Thank you, Tom, for the candour, particularly on the figure and what it contains.
  97. Tom Ashdown
    Tom Ashdown
    Any time, Malcolm. I'll get that note out, and I'll make sure the numbers in it are ones I've checked, not ones I've remembered.
  98. Rebecca Ainsworth
    Rebecca Ainsworth
    Speak soon then, Tom. Have a good rest of the week.
  99. Tom Ashdown
    Tom Ashdown
    And you, both. Cheers now, take care. Let's get something in the diary.
  100. Malcolm Hebden
    Malcolm Hebden
    Goodbye.
  101. Rebecca Ainsworth
    Rebecca Ainsworth
    Bye, both.

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