B-Brain
Laura Penhaligon

Merriott Lyle Distribution / BB-Demo – Onboarding

Callcompleted

Merriott Lyle Distribution logo Merriott Lyle Distribution · 2025-04-10 11:45

Onboarding call on 10 Apr 2025. A high-priority ticket shows the branch load coming back thin because the service account sees only some tables. Laura Penhaligon set out the twelve-week plan and a go or no-go gate.

What was said

What this says

Current to 13 Oct 26

Onboarding call on 10 Apr 2025. A high-priority ticket shows the branch load coming back thin because the service account sees only some tables. Laura Penhaligon set out the twelve-week plan and a go or no-go gate.

What happened: Laura Penhaligon laid out a twelve-week plan with five connectors first and a sixth, the shared drive, in a second block. Tariq Saleem's high-priority ticket is that the service account sees only a subset of branch tables.

Customer view: Deepa Chauhan wants a one-page plan for the regional directors and has told them numbers will be low for a while. She and Tariq treat the permissions gap as a scoping issue, not a fault.

Commercial: Two hundred users are licensed, and the first wave is key accounts and credit control, a few dozen people. Daniel picks up the relationship after go-live and Lewis stays commercial contact.

Watch: Some branches open before 07:00, so they will see the previous night's data. The evidence does not show whether the permissions fix worked.

AI · claude-sonnet-5-5 · 13 Oct 2026

Themes

Current to 9 Oct 26
Theme
Onboarding plan and access
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Tariq Saleem to check the load log and grants and report on the ticket that afternoon.
  • Laura Penhaligon to send the one-page plan, security pack and access list by the end of the next day.
  • Deepa Chauhan to give Laura the information security name and the first-wave list by the end of the week.

Risks

Current to 9 Oct 26
  • The branch load comes back thin until the service account can see all the branch tables that matter.
  • Branches that open before 07:00 will see the previous night's data, which may matter to them later.
  • Account matching between the CRM and the branch system is the biggest open piece of work.

Opportunities

Current to 9 Oct 26
  • The shared drive of credit control dispute notes is a sixth connector, planned for the second block.
  • Two hundred users are licensed, so rollout by region can grow well beyond the first few dozen.
  • A go or no-go decision at the end of matching gives the directors a clear checkpoint.

Transcript

  1. Laura Penhaligon
    Laura Penhaligon None
    Hello, can you hear me all right? I've got the recording going, so you'll see the little banner.
  2. Deepa Chauhan
    Deepa Chauhan None
    Loud and clear, Laura. Morning. Tariq's just joining, I can see him in the lobby.
  3. Tariq Saleem
    Tariq Saleem None
    Sorry, sorry. Morning both. My headset decided to update itself. Can you hear me?
  4. Laura Penhaligon
    Laura Penhaligon None
    Yes, perfect. No rush, we've only just started. How's the week been?
  5. Deepa Chauhan
    Deepa Chauhan None
    Busy. The regional directors have all discovered they have opinions about the account view, which is good, but it means my inbox is a lot.
  6. Tariq Saleem
    Tariq Saleem None
    Mine's mostly the rain. Half the branch network seems to be reporting a leak somewhere, so the helpdesk is flat out.
  7. Laura Penhaligon
    Laura Penhaligon None
    Ha, well, timing for a builders' merchant. Right, shall we crack on? Deepa, you said in the invite there was one thing you wanted out of today.
  8. Deepa Chauhan
    Deepa Chauhan None
    Yes. I need to leave this call knowing which teams go first, who owns which connector on our side, and roughly what the next few weeks look like. That's it. If I can take a one-page version to the regional directors, I'm happy.
  9. Laura Penhaligon
    Laura Penhaligon None
    That's a good brief, and it's exactly what I'd hoped to cover. Tariq, I know you usually start with tickets. Do you want to do that first?
  10. Tariq Saleem
    Tariq Saleem None
    Please. We've got two open. One is a how-to, it's about how the account page picks which contact to show first. That's not urgent. The other is high priority, and that's the one I'd like to clear before anything else.
  11. Laura Penhaligon
    Laura Penhaligon None
    Go on.
  12. Tariq Saleem
    Tariq Saleem None
    It's the nightly load from the branch system. It authenticates fine, but the service account we gave you can only see a subset of the branch tables. So the load runs, it just comes back thin. I raised it as high because I don't want the branches' orders missing when people start looking at accounts.
  13. Laura Penhaligon
    Laura Penhaligon None
    Right. And do we know whether it's the permissions on the account, or the way the extract view is defined?
  14. Tariq Saleem
    Tariq Saleem None
    I'm not going to guess at that. I'll check the load log and the grants this afternoon and put what I find on the ticket. My instinct is permissions, but I'd rather see it.
  15. Deepa Chauhan
    Deepa Chauhan None
    And that's fine, Tariq. Let's not turn it into a hunt for who set it up. It was set up before we knew which tables mattered.
  16. Tariq Saleem
    Tariq Saleem None
    No, agreed. It's a scoping thing, not a mistake.
  17. Laura Penhaligon
    Laura Penhaligon None
    Good. Then I'll treat that as the first thing in the plan, because everything downstream depends on the branch data landing properly. Let me share my screen and walk you through how I've laid out the twelve weeks. Can you see it?
  18. Deepa Chauhan
    Deepa Chauhan None
    I see a grid with coloured bars. Is that the one?
  19. Laura Penhaligon
    Laura Penhaligon None
    That's the one. So, left to right. The first couple of weeks are connectors and access. We get the CRM, the branch system, the helpdesk, the call recorder and the accounting system all loading cleanly into your Snowflake account. Weeks three to six are matching and checking: do the accounts in the branch system line up with the accounts in the CRM, and do they line up with what credit control sees.
  20. Deepa Chauhan
    Deepa Chauhan None
    Which account, which branch? That's always my question. A trade account can have a dozen delivery sites and each one sometimes has its own account code.
  21. Tariq Saleem
    Tariq Saleem None
    That's a mapping question, and it's the biggest one we have. There's a parent account in the CRM, then the branch system has the trading accounts under it, and in places the two don't share a clean key.
  22. Laura Penhaligon
    Laura Penhaligon None
    Yes, and that's why I've given it four weeks rather than a couple of days. What I'd suggest is we don't try to be clever on day one. We take your key-account list, the accounts that matter most, and match those by hand first, with you two eyeballing the results. Then we use what we learn to set the rules for the rest.
  23. Deepa Chauhan
    Deepa Chauhan None
    I like that. Show me where that number comes from, every time. If the brain says an account has an open dispute, I want a branch manager to be able to click through and see the dispute.
  24. Laura Penhaligon
    Laura Penhaligon None
    That's how it's built. Every answer carries its sources, so you can see which record it came from.
  25. Tariq Saleem
    Tariq Saleem None
    Can I ask about changes to the mapping, though? Once it's live, if we find a bad match, who changes it?
  26. Laura Penhaligon
    Laura Penhaligon None
    In the build phase, me, and I'll tell both of you before I do. After go-live it's an admin job, so you, Tariq. The mapping lives in a table you can see in your own account, and every change is logged.
  27. Tariq Saleem
    Tariq Saleem None
    Good. And Deepa gets told, always. I don't change a mapping without her knowing.
  28. Deepa Chauhan
    Deepa Chauhan None
    Which I appreciate. Honestly, that's the thing that keeps the branches trusting it.
  29. Laura Penhaligon
    Laura Penhaligon None
    Okay. Let me scroll on. After matching there's a block for the security review. You're on Enterprise, so that's included in the implementation, and I'll support whoever on your side is handling it. Do you know yet who that will be?
  30. Deepa Chauhan
    Deepa Chauhan None
    It'll be someone in our information security team. I haven't got a name yet. I'll have one by the end of the week.
  31. Laura Penhaligon
    Laura Penhaligon None
    That's fine. What they'll want is a description of how the brain runs inside your own Snowflake account, where the data sits, and who can see what. I've got a standard pack. I'll send it to you, Deepa, and you can pass it on.
  32. Deepa Chauhan
    Deepa Chauhan None
    Please. And if they have questions I'd rather they came to you directly than through me. I'm not the right person to answer a question about encryption.
  33. Laura Penhaligon
    Laura Penhaligon None
    Understood. Just copy me in and keep the thread going.
  34. Tariq Saleem
    Tariq Saleem None
    Sorry, while you're on that screen, can you go back up to the connectors row? You've got five connectors in the first block.
  35. Laura Penhaligon
    Laura Penhaligon None
    I have. CRM, branch system, helpdesk, call recorder, accounting. There's room for plenty more on Enterprise, so if there's a sixth you want early, say now.
  36. Tariq Saleem
    Tariq Saleem None
    There's the shared drive where the credit control team keeps their dispute notes. It's a mess, honestly. But it's where the real history lives.
  37. Deepa Chauhan
    Deepa Chauhan None
    Oh, yes. That's a good shout. Half of what credit control knows about an account is in a spreadsheet someone emailed round last spring.
  38. Laura Penhaligon
    Laura Penhaligon None
    Which is the kind of thing the brain is meant to replace. Let me add it, but I'll put it in the second block, not the first. I want the core five loading reliably before we point it at a drive full of free text.
  39. Tariq Saleem
    Tariq Saleem None
    Fair. I'd rather the load log is clean for the five first anyway.
  40. Deepa Chauhan
    Deepa Chauhan None
    Can we talk about who goes first? That's the bit I need for the directors.
  41. Laura Penhaligon
    Laura Penhaligon None
    Yes, let's. What's your instinct?
  42. Deepa Chauhan
    Deepa Chauhan None
    Key-account managers and credit control, together. They're the ones who argue over the same customer from different spreadsheets. If those two teams see one account view, the rest of the argument gets easier. Then branch managers in waves, a region at a time, starting with whichever director is keenest.
  43. Laura Penhaligon
    Laura Penhaligon None
    That makes sense. We've got two hundred licensed users, so you have room to bring everyone in without rationing. I'd still go in waves, because every wave will teach you something about what people actually ask.
  44. Tariq Saleem
    Tariq Saleem None
    How many are in the first wave, roughly? I need to know for the access setup. Single sign-on and the provisioning side.
  45. Deepa Chauhan
    Deepa Chauhan None
    Key accounts and credit control, so a few dozen. I'll get you the actual list.
  46. Laura Penhaligon
    Laura Penhaligon None
    Good. Since you're on Enterprise you've got single sign-on and automatic provisioning, so rather than setting up each person by hand, we connect it to your identity provider and groups drive who gets in. Tariq, who looks after that at your end?
  47. Tariq Saleem
    Tariq Saleem None
    A colleague in IT. I'll introduce you by email. He's good, but he needs to know what you'll ask for before he opens a change request.
  48. Laura Penhaligon
    Laura Penhaligon None
    I'll send a short list of what we need. Nothing exotic.
  49. Deepa Chauhan
    Deepa Chauhan None
    While we're here. Right now, how many people are actually using it? I know a handful have been poking around.
  50. Laura Penhaligon
    Laura Penhaligon None
    A small group, as you'd expect at this point. Mostly your team and a few curious key-account managers. Nothing to worry about. It's what an onboarding looks like before the data's properly in.
  51. Deepa Chauhan
    Deepa Chauhan None
    Good. Because I've said to the directors that numbers will be low for a while and I don't want anyone panicking.
  52. Laura Penhaligon
    Laura Penhaligon None
    Quite right. I'd rather see people asking good questions of clean data than lots of people asking questions of half-loaded data.
  53. Tariq Saleem
    Tariq Saleem None
    Can I raise one thing about freshness? The nightly refresh. What time will it have finished by?
  54. Laura Penhaligon
    Laura Penhaligon None
    Seven in the morning, your local time, on business days. That's the standard. So the branch managers should see yesterday's orders when they open up.
  55. Tariq Saleem
    Tariq Saleem None
    Right, because some branches open at half past six. We'd need to say that to them. They'll see last night's data until seven.
  56. Deepa Chauhan
    Deepa Chauhan None
    That's fine, I'll put it in the note. Nobody's making an order decision at six thirty from an account view. Or if they are, they ring the customer.
  57. Laura Penhaligon
    Laura Penhaligon None
    Ha. Exactly. Though if the early branches turn out to matter, we can talk about it later. I'd rather get the first load stable first.
  58. Deepa Chauhan
    Deepa Chauhan None
    Let's get credit control in the room, though. They haven't heard any of this from you. Would you be willing to do a short session with them next week? Twenty minutes, not a full training.
  59. Laura Penhaligon
    Laura Penhaligon None
    Of course. I'd want to hear from them too. What do they need to see on an account that they can't see now?
  60. Deepa Chauhan
    Deepa Chauhan None
    Disputes, mainly. What's been raised, what's been promised, and whether the branch has already phoned the customer. At the moment the two teams chase the same customer on the same day and don't know.
  61. Tariq Saleem
    Tariq Saleem None
    Which is partly the matching problem again. If the dispute sits on a trading account and the call sits on the parent, nobody sees both.
  62. Laura Penhaligon
    Laura Penhaligon None
    Right, and that's the first thing I'd demo to them once the key accounts are matched. A real customer, with the orders, the dispute and the last call in one place.
  63. Deepa Chauhan
    Deepa Chauhan None
    Okay. I think I can write that up. Can I read it back to you? Tell me if I've got anything wrong.
  64. Laura Penhaligon
    Laura Penhaligon None
    Please.
  65. Deepa Chauhan
    Deepa Chauhan None
    First couple of weeks, connectors and access, five of them, with Tariq clearing the branch system permissions first. Then matching, starting with key accounts by hand. Security review in parallel, with our information security person and Laura. Key accounts and credit control go first, then branches by region. The shared drive comes in as a second block. Is that right?
  66. Laura Penhaligon
    Laura Penhaligon None
    That's spot on. One addition. At the end of the matching block we sit down together and decide whether the first wave is ready, rather than assuming it is.
  67. Deepa Chauhan
    Deepa Chauhan None
    Good. A go or no-go. I like that, the directors will like that.
  68. Tariq Saleem
    Tariq Saleem None
    One last practical one. Who do I raise things with day to day? You, or the support desk?
  69. Laura Penhaligon
    Laura Penhaligon None
    During the build, me. Email or ticket, whichever you prefer, and I'll keep an eye on both. Once you're live your CSM, Daniel, picks up the relationship, and I'll introduce you properly before then.
  70. Tariq Saleem
    Tariq Saleem None
    Okay. And Lewis is still the commercial contact?
  71. Laura Penhaligon
    Laura Penhaligon None
    Yes, for anything about the contract or scope. For the day to day, it's me.
  72. Deepa Chauhan
    Deepa Chauhan None
    Then I think I've got what I came for. Anything else from you, Tariq?
  73. Tariq Saleem
    Tariq Saleem None
    No, I'll go and check the load log. If it's permissions I can probably have it fixed today.
  74. Laura Penhaligon
    Laura Penhaligon None
    Lovely. Then here's who sends what. I'll send the plan as a one-pager, the security pack and the access list by the end of tomorrow. Tariq puts what he finds on the ticket this afternoon. Deepa, you give me the name from information security and the first-wave list by the end of the week.
  75. Deepa Chauhan
    Deepa Chauhan None
    Done. And I'll set up the credit control session for next week and put you in it.
  76. Laura Penhaligon
    Laura Penhaligon None
    Perfect. Thanks both, this was useful. Speak soon.
  77. Tariq Saleem
    Tariq Saleem None
    Cheers, Tariq. Sorry, cheers all. Bye.
  78. Deepa Chauhan
    Deepa Chauhan None
    Thanks, both. Bye.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain 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 Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations225
People at customers862
BB-Demo staff58
Calls1,995
Email threads3,013
Support tickets1,159
Documents1,218
Deals315
Invoices285
Events49
News items119

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

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

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Brain · read-only