B-Viz
Callie Brennan

Ovenden Software / BG-Demo – Kickoff

Callcompleted

Ovenden Software logo Ovenden Software · 31 May 2024 13:00

On 31 May 2024 BG-Demo kicked off implementation with Ovenden Software. Connector credentials via IT are the bottleneck, early usage is thin and mostly Louise Sutcliffe's, and Aaron Crowther wants to run the admin himself.

What was said

What this says

As at Fri 9 Oct 2026

On 31 May 2024 BG-Demo kicked off implementation with Ovenden Software. Connector credentials via IT are the bottleneck, early usage is thin and mostly Louise Sutcliffe's, and Aaron Crowther wants to run the admin himself.

What happened: Callie Brennan led the 31 May 2024 kickoff with Louise Sutcliffe and Aaron Crowther, joined by Marcus Bell. They agreed owners for each area and the order of work: credentials, mapping, then the first refresh.

Customer view: Aaron said he would speak to IT, who are the gatekeepers, and that he would rather run things on his own. Louise asked not to be left guessing which project code is the real one.

Usage: Marcus said it is early, with a handful of people logged in and most questions coming from Louise. That is a key-person risk until the team joins.

Watch: The payroll connector still needs full access, not the read-only export login. Messy project codes may slow the timesheet mapping.

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

Themes

As at Fri 9 Oct 2026
Theme
Implementation kickoff and setup
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Aaron Crowther sends the full connector credentials through the secure form by the end of the week.
  • Callie Brennan books the first refresh once credentials are in, and sends the setup note and unmatched project codes.
  • Marcus Bell sends the owner list the same day and books a check-in after the first refresh.

Risks

As at Fri 9 Oct 2026
  • Full connector credentials depend on Ovenden Software's IT team, which holds up the first refresh.
  • Early questions come mostly from Louise, so usage depends on one person until the wider team joins.
  • Messy project codes may slow the timesheet mapping.

Opportunities

As at Fri 9 Oct 2026
  • Aaron wants to run the admin role himself, which builds a second skilled owner beside Louise.
  • Scheduled connector checks and named source owners should catch a flat feed early.

Transcript

  1. Callie Brennan
    Callie Brennan
    Hi all, good afternoon. Right, can everyone see the agenda? I've put the plan for the next hour in the chat, so we know where we're going.
  2. Marcus Bell
    Marcus Bell
    Hiya, yep, I can see it. Hi Louise, hi Aaron. I'm going to share my screen for the usage numbers in a bit, if that's alright.
  3. Louise Sutcliffe
    Louise Sutcliffe
    Hi Callie, hi Marcus. Yeah, all here. Aaron's just got his coffee, give him a sec.
  4. Aaron Crowther
    Aaron Crowther
    Hi, I'm here, sorry. I was on the phone to the payroll people. Go on.
  5. Callie Brennan
    Callie Brennan
    No bother. So first, connectors. What I need from your side is the credentials for the timesheet system, the payroll integration and the helpdesk, in writing, through the secure form, before we switch anything on.
  6. Aaron Crowther
    Aaron Crowther
    Right. I thought the payroll one was done? I sent something ages ago.
  7. Callie Brennan
    Callie Brennan
    You sent a read-only login for the export, which is useful, but it isn't the full access the connector needs. That's a separate account, and I'd like it set up properly before the first refresh, not after.
  8. Aaron Crowther
    Aaron Crowther
    Okay. Fair enough. I'll speak to IT, they're the gatekeepers on that.
  9. Marcus Bell
    Marcus Bell
    Yeah, that's the bottleneck, isn't it? Shall we get the list sorted this week, and then Callie books the first refresh?
  10. Callie Brennan
    Callie Brennan
    Yes, that's the order. Once the credentials are in, I'll run the mapping, and I won't say it's fine until I've checked the fields myself.
  11. Louise Sutcliffe
    Louise Sutcliffe
    Sensible. Marcus, go on, what does the usage look like? I want to know who's actually in it.
  12. Marcus Bell
    Marcus Bell
    Okay, I've pulled the numbers. Honestly, it's early. A handful of people have logged in properly, and most of the questions so far are from you, Louise.
  13. Louise Sutcliffe
    Louise Sutcliffe
    Ha. Yes, that's me being nosy. I'll get the team in, I promise.
  14. Callie Brennan
    Callie Brennan
    That's how it usually starts. Once the refresh has landed the questions spread, especially if the admin can show people the pages.
  15. Aaron Crowther
    Aaron Crowther
    I can do that. I'd honestly rather be the person who can run it on my own.
  16. Callie Brennan
    Callie Brennan
    That's exactly the right instinct. I'll put a setup note together for you, so you can run things without me on the call.
  17. Marcus Bell
    Marcus Bell
    I'd like the connector checks on a schedule as well, so we see early if a feed goes flat.
  18. Callie Brennan
    Callie Brennan
    Yes, I'll set that up with Aaron. A feed that stops loading usually means something changed on the customer's side, so it's worth knowing quickly.
  19. Aaron Crowther
    Aaron Crowther
    Changed like a new field, or like someone switching a system off?
  20. Callie Brennan
    Callie Brennan
    Either. That's why I'd like a named person against each source. Right, who owns what? Let's do it now, so nobody's guessing next month.
  21. Louise Sutcliffe
    Louise Sutcliffe
    Fine. I own the commercial side and the business questions. I'll sign off anything that's about the contract.
  22. Aaron Crowther
    Aaron Crowther
    I'll own the connectors and the credentials, and anything with IT.
  23. Marcus Bell
    Marcus Bell
    I'll own usage and the reviews. Callie hands over after the first refresh, yeah?
  24. Callie Brennan
    Callie Brennan
    Yes, after the first refresh, and I'll stay on the mapping questions until then. Anything else is yours.
  25. Louise Sutcliffe
    Louise Sutcliffe
    Callie, quick one. When does the first refresh finish in the morning, so we're not waiting on it?
  26. Callie Brennan
    Callie Brennan
    By 07:00 on business days, in your local time. Every tier gets that, so you can plan around it. I'll confirm the first run date once the credentials are in.
  27. Marcus Bell
    Marcus Bell
    Great. I'll put that in the owner list so people know when to expect it.
  28. Callie Brennan
    Callie Brennan
    Brilliant. And Aaron, please don't send passwords by email, use the form.
  29. Aaron Crowther
    Aaron Crowther
    Yep, got it. I'll do it today.
  30. Callie Brennan
    Callie Brennan
    Right, while we've got a minute, the mapping. The timesheet fields map cleanly to the people and the projects, I think, but I'm not saying that until I've seen a sample.
  31. Aaron Crowther
    Aaron Crowther
    Fair. We've got a lot of project codes, and some of them are a mess, honestly.
  32. Callie Brennan
    Callie Brennan
    That's normal. I'll pull a sample of records and send you the ones that don't match, so you can tell me which is right.
  33. Louise Sutcliffe
    Louise Sutcliffe
    Good. Please don't make us guess which code is the real one.
  34. Callie Brennan
    Callie Brennan
    I won't. That's the setup note's job, I'll write the rules down.
  35. Marcus Bell
    Marcus Bell
    Sorry, I'm back. Did I miss the mapping thing?
  36. Callie Brennan
    Callie Brennan
    Only a bit. Aaron's sending a sample of project codes, and I'll send back the unmatched ones.
  37. Aaron Crowther
    Aaron Crowther
    Yep, I'll have it by the end of the week.
  38. Callie Brennan
    Callie Brennan
    Right, I think we're nearly there. Next steps. Aaron, credentials by the end of the week. Then I book the first refresh once they're in, and send the setup note.
  39. Marcus Bell
    Marcus Bell
    I'll send the owner list today, and I'll book a short check-in for after the first refresh.
  40. Louise Sutcliffe
    Louise Sutcliffe
    Good. Thanks all. Sorry, I've got to drop, I've got another call at the hour.
  41. Callie Brennan
    Callie Brennan
    No problem. Thanks Louise. Aaron, thanks.
  42. Aaron Crowther
    Aaron Crowther
    Cheers. Bye.
  43. Marcus Bell
    Marcus Bell
    Bye all, speak soon.
  44. Callie Brennan
    Callie Brennan
    Thanks, 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