B-Viz
Callie Brennan

Strensall Merchants / BG-Demo – Kickoff

Callcompleted

Strensall Merchants logo Strensall Merchants · 6 Mar 2025 09:00

Kickoff for the Enterprise implementation. Customer asked about data location, access, single sign-on and account mapping. Credentials, a second admin and mailbox choices are open. Contract end and renewal dates were stated.

What was said

What this says

As at Fri 9 Oct 2026

Kickoff for the Enterprise implementation. Customer asked about data location, access, single sign-on and account mapping. Credentials, a second admin and mailbox choices are open. Contract end and renewal dates were stated.

What happened: Callie Brennan and Daniel Okafor took Neil Craven, Ashok Patel and Stuart Kitson through connectors, security review, roles and dates. Callie would not start a connector without written access.

Customer view: Neil wants branches, key accounts and credit to see one trade account, and wants to show the board something real. Ashok flagged that one builder can carry three account numbers.

Commercial: Daniel described Enterprise as up to twenty connectors, single sign-on, SCIM and 160 licensed users. He stated the contract end as 27 Feb 2026 and renewal on 28 Feb 2026.

Watch: Ashok is the only admin and plans to name a second. The evidence does not show the renewal outcome.

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

Themes

As at Fri 9 Oct 2026
Theme
Enterprise implementation kickoff
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Callie Brennan to send the written plan with a date against every step, plus the setup note template.
  • Daniel Okafor to send a summary of the call by Monday.
  • Ashok Patel to send access details and name a second admin; Stuart Kitson to confirm the identity source by the end of the following week.

Risks

As at Fri 9 Oct 2026
  • Credit access depends on the finance team, which owns that ledger and has not yet agreed.
  • Ashok Patel is the only admin until a second person is named and trained.
  • Neil Craven worries the rollout will take longer than expected, and older key account managers are wary of the mailbox indexing.

Opportunities

As at Fri 9 Oct 2026
  • Neil Craven wants to show the board something real well before renewal, which gives a value case to build early.
  • Short role-based training could lead on to the on-site training day add-on if the branches need it.
  • A second trained admin would strengthen continuity and adoption.

Transcript

  1. Daniel Okafor
    Daniel Okafor
    Morning, everyone. Can you hear me all right? I can see Neil and Ashok. Stuart, I think you're just joining.
  2. Stuart Kitson
    Stuart Kitson
    Morning. Yes, sorry, the meeting room link took a minute. Can you hear me?
  3. Daniel Okafor
    Daniel Okafor
    Loud and clear. Thank you all for making time this morning, I know the diaries are tight. Just to check who we've got: Neil, Ashok, Stuart from your side, and Callie and me from ours. Is anyone else expected?
  4. Neil Craven
    Neil Craven
    No, that's the lot. Bit of a rush to get here, to be honest. I had one of our big housebuilder accounts on the phone at seven this morning, about a delivery that went to the wrong site. Two branches both thought the other had it.
  5. Daniel Okafor
    Daniel Okafor
    That sounds like a good way to start a Thursday. Did you get it sorted?
  6. Neil Craven
    Neil Craven
    Lorry's turned round. But that's exactly why we're here. What's the builder actually seeing? Nobody could tell me quickly, and it took four phone calls to find out.
  7. Callie Brennan
    Callie Brennan
    Which is a perfect way in, Neil, thank you. Hi everyone, I'm Callie, I'll be running the implementation. Let me give you the plan for the next hour so you know where we're heading. First, ten minutes on what you've bought and what live looks like. Then the connectors, one by one, and what I need from your side is access in writing for each. Then Stuart's security review. Then roles and who owns what. And we finish with next steps and dates.
  8. Ashok Patel
    Ashok Patel
    That works for me. Can I say what I've changed since we last spoke, before we start?
  9. Callie Brennan
    Callie Brennan
    Please do.
  10. Ashok Patel
    Ashok Patel
    So, I've set up a new service account in the branch system, read only, and I've pulled a list of the systems we think we'll connect. Branch orders, deliveries, trade credit, the call recorder and the mailboxes. I haven't switched anything on. I want to test each one on a single branch first.
  11. Callie Brennan
    Callie Brennan
    That's exactly the order I'd want. And it maps cleanly onto how we'd do it anyway. We prove one branch, check the account numbers line up, then widen out.
  12. Ashok Patel
    Ashok Patel
    Which account number is that, though? That's my worry. A trade account can have a different reference in credit than it has in the branch system. The data says otherwise to what people assume.
  13. Neil Craven
    Neil Craven
    Aye, that's the whole problem. One builder, three numbers, and nobody agrees which is the real one.
  14. Daniel Okafor
    Daniel Okafor
    Can I just frame it for Stuart, since he's coming at this from a different angle? Strensall has bought Enterprise. So that's a company-wide set-up, with up to twenty connectors, single sign-on and SCIM, and 160 licensed users. The point, as Neil said when we first spoke, is that branches, key accounts and trade credit all see the same trade account, with orders, deliveries, calls and credit together.
  15. Stuart Kitson
    Stuart Kitson
    Right. And where does the data actually sit? I've read the paperwork but I'd like to hear it said.
  16. Callie Brennan
    Callie Brennan
    Good question to ask early. B-Viz is built and runs inside your own Snowflake account. So the data doesn't leave your environment to sit in ours. We build the layer there, you hold the keys, and we work in it with the access you grant us.
  17. Stuart Kitson
    Stuart Kitson
    And that access, it's role based? I don't want anyone at your end with more than they need.
  18. Callie Brennan
    Callie Brennan
    Role based, and I'd suggest we write it down as part of the setup note. Who at BG-Demo has what, and for how long. You can revoke it when we hand over.
  19. Stuart Kitson
    Stuart Kitson
    Good. I'll want that in writing, as part of the review.
  20. Daniel Okafor
    Daniel Okafor
    Of course. And just so it's clear, the Enterprise implementation includes support through the security review, so Callie and I will help you with the questionnaire rather than leave you with it.
  21. Stuart Kitson
    Stuart Kitson
    That's helpful. Our questionnaire is long, I'll warn you now.
  22. Daniel Okafor
    Daniel Okafor
    Long is fine. Better long and early than short and late.
  23. Neil Craven
    Neil Craven
    Can I ask the daft question? How long until my branch managers can actually use this? Because I've got about ninety-five branches waiting and they've heard a lot of talk.
  24. Callie Brennan
    Callie Brennan
    Not daft at all. The Enterprise implementation is planned over twelve weeks. That includes the connectors, the first refresh, the security review and training. I'd rather not promise you a branch rollout date today, because it depends on credentials arriving before we need them. Give me the access and the clock runs faster.
  25. Neil Craven
    Neil Craven
    Fair. Let's sort it, not talk about it. What do you need?
  26. Callie Brennan
    Callie Brennan
    Let me share my screen and take you through the connector list. Give me a second. Can you all see it?
  27. Ashok Patel
    Ashok Patel
    I can see it. Bit small.
  28. Callie Brennan
    Callie Brennan
    Is that better?
  29. Ashok Patel
    Ashok Patel
    Yes, that's fine.
  30. Callie Brennan
    Callie Brennan
    So the list is in four groups. Commercial: your branch order and delivery systems. Credit: the trade credit ledger. Conversations: the call recorder and email. And then reference data, like the account hierarchy. We start with credit and branch orders, because that's where the three account numbers collide.
  31. Ashok Patel
    Ashok Patel
    Agreed. If we get the account mapping right first, everything else hangs off it. If we get it wrong, we load a lot of wrong data very quickly.
  32. Callie Brennan
    Callie Brennan
    Which is why I won't start a connector until I have access in writing. Ashok, if you can send the service account details and the scope you've set, I'll confirm back what I'm going to read.
  33. Ashok Patel
    Ashok Patel
    Yes. I'll send the branch system one today and credit tomorrow. Credit needs a conversation with the finance team first, because they own that ledger.
  34. Neil Craven
    Neil Craven
    I'll have a word with them. Credit and sales agreeing on a customer is the reason I wanted this in the first place, so they'll not want to be left out.
  35. Daniel Okafor
    Daniel Okafor
    That's lovely, Neil. And we can join that conversation if it helps. Sometimes it lands better when the finance team hears it from us directly.
  36. Neil Craven
    Neil Craven
    Might do. Let me ask them first.
  37. Callie Brennan
    Callie Brennan
    Right, I've been through the call recorder and email in the notes. One thing I want to flag: for email we need to agree which mailboxes. Not everything, just the trade and credit teams and key account managers, otherwise we index a lot of noise.
  38. Stuart Kitson
    Stuart Kitson
    I'd rather be selective there as well. Shared mailboxes, yes. Individual ones, only where the person has agreed and we've told them. There are privacy questions.
  39. Callie Brennan
    Callie Brennan
    That makes sense. I'll put a column in the plan for mailbox, owner and who has been told. Then you can tick them off.
  40. Stuart Kitson
    Stuart Kitson
    Thank you. That would help.
  41. Neil Craven
    Neil Craven
    Do the key account managers get a say? Because some of them keep things in their own folders and won't like being looked at.
  42. Daniel Okafor
    Daniel Okafor
    I'd always suggest they hear it from you first, Neil, and in plain terms. It isn't about looking at people, it's about the builder's account being complete when anyone opens it. How is the team finding the idea so far? Is there much worry?
  43. Neil Craven
    Neil Craven
    Some. Mostly the older hands. They've got it all in their heads and they think that's job security. I'll talk to them.
  44. Daniel Okafor
    Daniel Okafor
    Thank you. If it helps, I can sit in on one of their team meetings later on and just answer questions.
  45. Neil Craven
    Neil Craven
    I might take you up on that.
  46. Stuart Kitson
    Stuart Kitson
    Can I come back to single sign-on? Because that's the bit I need to plan. We have one identity system for head office and a different arrangement for branch staff, and I don't want two logins.
  47. Callie Brennan
    Callie Brennan
    Understood. Enterprise includes SSO and SCIM, so users can be created and removed from your side. What I need from you is which identity system should be the source, and who administers it. Then we test with a handful of users before we switch it on for everyone.
  48. Stuart Kitson
    Stuart Kitson
    Head office will be the source, I think. I need to confirm with a colleague in IT who runs the branch side. I'll come back to you.
  49. Callie Brennan
    Callie Brennan
    Perfect. I'll put it in as an open item with your name against it, and a date for you to confirm by. Is next Thursday realistic?
  50. Stuart Kitson
    Stuart Kitson
    I'd say the end of next week to be safe.
  51. Callie Brennan
    Callie Brennan
    End of next week it is.
  52. Ashok Patel
    Ashok Patel
    Can I ask about the first refresh? When it lands, how will I know it's right? I'm used to reports that have to match the ledger, otherwise nobody trusts them.
  53. Callie Brennan
    Callie Brennan
    We'd do a reconciliation together. Pick a sample of trade accounts, ideally some of the awkward ones, and compare what B-Viz shows against the ledger line by line. If it doesn't match, we don't go live on that source. I won't say a mapping is fine until I've checked it.
  54. Ashok Patel
    Ashok Patel
    That's what I wanted to hear. I'll pick the sample. I'd include the housebuilder Neil mentioned.
  55. Neil Craven
    Neil Craven
    Ha, yes. Use that one. If it's right for them, it's right for anyone.
  56. Daniel Okafor
    Daniel Okafor
    Just to close the loop on that, then. Ashok picks the sample accounts, Callie runs the reconciliation, and nothing goes live on a source until you're both happy.
  57. Ashok Patel
    Ashok Patel
    Yes.
  58. Neil Craven
    Neil Craven
    One thing from me on training. Branch managers are busy, they're on the counter, they're not at desks. Whatever you do needs to be short and practical. Show them how to look up a builder and see what's going on. Not a lecture.
  59. Callie Brennan
    Callie Brennan
    Agreed. We'd do short sessions built around real questions from your own accounts. Something like, has this builder got an open delivery problem and is their credit on hold? And a quick reference page after.
  60. Neil Craven
    Neil Craven
    That's the stuff. Which branch, which account, what's the answer.
  61. Daniel Okafor
    Daniel Okafor
    And I'll keep an eye on how the first groups get on, so we can adjust before the wider rollout. We've got the contract running through to 27 Feb 2026, with renewal on 28 Feb 2026, so there's plenty of time to make sure this lands properly and people are asking it questions every day.
  62. Neil Craven
    Neil Craven
    Good. I'd like to be showing the board something real well before then.
  63. Ashok Patel
    Ashok Patel
    Roles, then. I'm the admin. I'd like a second person trained as well, so it's not all down to me. If I'm off ill, I don't want the whole thing sitting still.
  64. Callie Brennan
    Callie Brennan
    I was going to suggest exactly that. A second admin is the single best thing for continuity. Have you someone in mind?
  65. Ashok Patel
    Ashok Patel
    One of my analysts. I'll check they're up for it and let you have a name.
  66. Daniel Okafor
    Daniel Okafor
    That would be lovely. I always say the happiest customers are the ones where more than one person knows how it works.
  67. Stuart Kitson
    Stuart Kitson
    And from my side, I'm the contact for the review and for access. If something changes in our environment, I'd want to hear about it before it hits you, not after.
  68. Callie Brennan
    Callie Brennan
    Same from ours. If a system changes under us, a connector can stop loading and we find out late. So a quick note to Ashok or me whenever you upgrade or move something. It saves a lot of grief.
  69. Ashok Patel
    Ashok Patel
    I'll add it to our change process. Anything that touches a connected system gets a copy to you.
  70. Callie Brennan
    Callie Brennan
    Let me pull it together, then. From today: Ashok sends the branch system access details today and credit tomorrow, once the finance team has agreed. Stuart confirms the identity source by the end of next week, and sends the security questionnaire. Neil speaks to the finance team and to the key account managers. Ashok picks the sample accounts and names a second admin. And I send a written plan, with a date against every step, and the setup note template.
  71. Ashok Patel
    Ashok Patel
    That's everything I have. Plus I'll test on one branch first, before anything else.
  72. Stuart Kitson
    Stuart Kitson
    Yes, that matches mine.
  73. Daniel Okafor
    Daniel Okafor
    And I'll come back to you by Monday with a short summary of today, so everyone has the same list. Anything we've missed? Anyone nervous about anything?
  74. Neil Craven
    Neil Craven
    Only the usual. That it takes longer than we think. But I've heard what you need, so we'll get it to you quick.
  75. Callie Brennan
    Callie Brennan
    That's all I ask. Credentials before the kickoff steps, not after, and we'll be fine.
  76. Neil Craven
    Neil Craven
    Right, I'd best ring that builder back. Thanks all.
  77. Daniel Okafor
    Daniel Okafor
    Thank you, Neil. Thanks, Ashok, Stuart. Lovely to have you all on the call.
  78. Stuart Kitson
    Stuart Kitson
    Thanks. Speak soon.
  79. Ashok Patel
    Ashok Patel
    Thanks, everyone. I'll send those details this afternoon.
  80. Callie Brennan
    Callie Brennan
    Sorry, one last thing before I drop. I'll send the plan this afternoon. Thanks, all.

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