Laura Penhaligon

Merriott Lyle Distribution / BB-Demo – Onboarding

Callcompleted

Merriott Lyle Distribution: documents logo Merriott Lyle Distribution: documents · 2025-04-11 11:00

Onboarding call with Deepa Chauhan and Tariq Saleem. Connector order, a match table and a small first wave were agreed. Deepa needs a date for the regional directors; Laura owes one early the following week.

What was said

What this says

Current to 11 Oct 26

Onboarding call with Deepa Chauhan and Tariq Saleem. Connector order, a match table and a small first wave were agreed. Deepa needs a date for the regional directors; Laura owes one early the following week.

What happened: Laura Penhaligon took Deepa and Tariq through the connector order: CRM, branch system, accounting, helpdesk, call recorder last. Tariq explained a mapping change behind a failed first overnight branch load and agreed to record such changes in writing.

Customer view: Deepa wants a date she can give the regional directors, not a feature list. She would rather have an honest date than a quick one.

Commercial: Merriott Lyle is on Enterprise with two hundred licensed users, and SSO, SCIM and security review support were confirmed as included. A small first wave and agreed roles protect early adoption, which is where the value will show.

Watch: Laura owes Deepa a date early the following week, after checking the plan with Amara. Unmatched accounts go to Deepa's monthly review and need working through.

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

Themes

Current to 9 Oct 26
Theme
Onboarding connector plan
Importance
neutral
Sentiment
neutral
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Laura Penhaligon to give Deepa a realistic date for matched accounts early the following week, after checking with Amara.
  • Laura to send the connector plan, owners table and draft role rules by the end of the day or Monday morning at the latest.
  • Tariq Saleem to send the branch system field list and a name for the finance credentials.

Risks

Current to 9 Oct 26
  • Unmatched accounts between the branch system and the CRM could undermine trust if the first users see half-matched records.
  • Deepa has no date yet for the regional directors, so expectations in the regions are open.

Opportunities

Current to 9 Oct 26
  • Enterprise has two hundred licensed users and the first wave is only a handful, so there is large seat headroom as the rollout widens.
  • SSO, SCIM and security review support are included and wanted by the customer's IT team.

Transcript

  1. Laura Penhaligon
    Laura Penhaligon None
    Hello, can you hear me all right? I've got you both on the screen but I'm not sure my sound is behaving.
  2. Deepa Chauhan
    Deepa Chauhan None
    Loud and clear, Laura. Morning. Tariq, you're on mute, I think.
  3. Tariq Saleem
    Tariq Saleem None
    Sorry, morning both. Yes, that's better. I was on the other call until two minutes ago, so I'm still switching over.
  4. Laura Penhaligon
    Laura Penhaligon None
    No rush at all. Good Friday so far? Anything planned for the weekend, or is it all just catching up?
  5. Deepa Chauhan
    Deepa Chauhan None
    Catching up, mostly. It's been raining across the Midlands all week, so the branch managers have been ringing in about deliveries and I've been the one fielding it. But it's Friday, so, you know.
  6. Laura Penhaligon
    Laura Penhaligon None
    Right, the builders' merchants must feel that more than most. Well, shall we make a start? Today is the onboarding call, so what I'd like is to leave with the order we're connecting things in and a name against each one. Does that suit?
  7. Deepa Chauhan
    Deepa Chauhan None
    It does. Can I say the one thing I need from this call first?
  8. Laura Penhaligon
    Laura Penhaligon None
    Please.
  9. Deepa Chauhan
    Deepa Chauhan None
    I need to be able to tell the regional directors, in plain words, when a branch manager will be able to open one trade account and see the orders, the disputes, the calls and the invoices together. Not a feature list. A date, roughly, and who is responsible for getting there.
  10. Laura Penhaligon
    Laura Penhaligon None
    That's fair, and I think we can get you most of the way to that today. Tariq, did you want to go through the tickets first? I know that's usually where you start.
  11. Tariq Saleem
    Tariq Saleem None
    Yes, if that's okay, it'll take a minute. There are two open. One is a how-to, it's about who can see which accounts, and I think that's more of a permissions question than a fault. The other one I marked high priority, because the first overnight load from the branch system didn't complete.
  12. Laura Penhaligon
    Laura Penhaligon None
    Yes, I've looked at that one this morning. The re-run did complete, and what held it up was the account reference field not being mapped the way the loader expected. Would you agree with that from your side?
  13. Tariq Saleem
    Tariq Saleem None
    I'll check the load log before I say that. I don't want to guess. But the timing fits, the second run was after I'd changed the reference field. So it is a mapping question, not a connectivity one, as far as I can see.
  14. Deepa Chauhan
    Deepa Chauhan None
    Which field did you change, Tariq? Just so I know. I don't want the account codes the branches use to shift under them without anyone saying.
  15. Tariq Saleem
    Tariq Saleem None
    Fair. It was the branch system's account code, we were passing it with the leading branch prefix and the loader wanted it without. I haven't touched anything in the CRM itself. I should have told you before I did it, and I'll write it up so there's a record.
  16. Deepa Chauhan
    Deepa Chauhan None
    Thanks. That's all I wanted. It isn't a blame thing, I just like to know what changed.
  17. Laura Penhaligon
    Laura Penhaligon None
    That's exactly the kind of record we want, actually. I'll put it in the implementation notes too, so we have one place for every mapping decision. Okay, can I share my screen? I've got the connector plan open.
  18. Tariq Saleem
    Tariq Saleem None
    Go ahead.
  19. Laura Penhaligon
    Laura Penhaligon None
    Can you see it? It's a simple table. Down the left, the sources. Across, who owns the source at Merriott Lyle, who is the technical contact, and what we need from you before we connect it.
  20. Deepa Chauhan
    Deepa Chauhan None
    Yes, I can see it. The text is a bit small but I can follow.
  21. Laura Penhaligon
    Laura Penhaligon None
    I'll send it over afterwards so you don't have to squint. So, the way I'd suggest ordering it: the CRM first, because everything else hangs off the account record. Then the branch system, which we've already begun. Then the accounting system for invoices and balances, then the helpdesk, then the call recorder last.
  22. Tariq Saleem
    Tariq Saleem None
    Why the call recorder last? Out of curiosity.
  23. Laura Penhaligon
    Laura Penhaligon None
    Mostly because it's the one where the matching is least certain. Calls come in with a person's name and an email address, and they only become useful once the account matching underneath is solid. If we do it early we just get a lot of calls attached to nothing.
  24. Tariq Saleem
    Tariq Saleem None
    Right, that makes sense. That's a mapping question again, really. People ring from a mobile and the CRM has them under the branch landline.
  25. Deepa Chauhan
    Deepa Chauhan None
    Which is half my life, to be honest. Which account, which branch, and who is it actually, that's the conversation I have every month with credit control.
  26. Laura Penhaligon
    Laura Penhaligon None
    Yes, and that's where I'd like to spend a bit of time today. Account matching. Tariq, can you describe how an account looks in the branch system versus the CRM today?
  27. Tariq Saleem
    Tariq Saleem None
    Sure. In the branch system, an account is a code plus a branch, so the same builder can have an account at several branches. In the CRM we've tried to have one company record with the branches underneath. Most of them line up. The ones that don't are usually where a firm has been trading under a limited company name at one branch and a trading name at another.
  28. Laura Penhaligon
    Laura Penhaligon None
    And how many of those, roughly? Not an exact count.
  29. Tariq Saleem
    Tariq Saleem None
    I'd rather not give you a number off the top of my head. I'll run the match and check the load log, then I can say properly. It's a minority, but it's the minority people complain about.
  30. Deepa Chauhan
    Deepa Chauhan None
    It's the same few hundred names that come up in every review. The big regional contractors, mainly.
  31. Laura Penhaligon
    Laura Penhaligon None
    Okay. What I'd propose is a match table that sits alongside the load. Tariq, you own it. Anything the brain can't match confidently goes onto a list rather than being guessed at, and the list goes to Deepa's monthly review.
  32. Deepa Chauhan
    Deepa Chauhan None
    I like that. It turns it into something we work through together, with credit control in the room, rather than a thing that's quietly wrong.
  33. Tariq Saleem
    Tariq Saleem None
    And no one on the branch side gets told their data's bad. It's just unmatched.
  34. Laura Penhaligon
    Laura Penhaligon None
    Exactly that wording. Unmatched, not wrong.
  35. Laura Penhaligon
    Laura Penhaligon None
    Right, let me scroll down. This is the part about people. You're licensed for two hundred users on Enterprise, and I know that's the whole of the key-account, branch and credit-control teams eventually. What I'd normally recommend is not switching on two hundred people in one go.
  36. Deepa Chauhan
    Deepa Chauhan None
    No, I wouldn't want that either. If the first thing a branch manager sees is a half-matched account, we've lost them.
  37. Laura Penhaligon
    Laura Penhaligon None
    Agreed. So a first wave. Who would you put in it?
  38. Deepa Chauhan
    Deepa Chauhan None
    Three groups, really. A handful of key-account managers who already live in the CRM. Two or three people from credit control, because they're the ones chasing disputes. And a few branch managers I trust to tell me honestly if it's useless.
  39. Laura Penhaligon
    Laura Penhaligon None
    That's a good first wave. Small enough that we can sit with them and see what questions they actually ask.
  40. Tariq Saleem
    Tariq Saleem None
    On access, can I raise single sign-on now? Because my colleague in IT will want to know early. Enterprise includes it, doesn't it, along with the user provisioning?
  41. Laura Penhaligon
    Laura Penhaligon None
    It does, SSO and SCIM both. And the security review support is part of the Enterprise implementation, so I'll ask for your IT contact's questionnaire up front rather than at the end. That usually saves a fortnight.
  42. Tariq Saleem
    Tariq Saleem None
    Good. I'll introduce you to them next week. They're careful, so expect questions about where the data lives.
  43. Laura Penhaligon
    Laura Penhaligon None
    That one's easy, it all sits inside your own Snowflake account. I'll put that in the first paragraph of whatever I send them.
  44. Deepa Chauhan
    Deepa Chauhan None
    Can I ask something about that? When we say it's in our Snowflake account, does that mean the branches can't see anything they shouldn't? Because the regional directors will ask me within about five minutes.
  45. Laura Penhaligon
    Laura Penhaligon None
    Good question, and I'd rather answer it properly than quickly. Access follows the roles you set up, so a branch manager sees what their role allows. We'd want to agree those roles with you and Tariq before the second wave, not after.
  46. Deepa Chauhan
    Deepa Chauhan None
    Okay. Then that's something I'll bring to the data review so the regions have signed off the principle. Show me where that rule is written down, when it is.
  47. Laura Penhaligon
    Laura Penhaligon None
    I'll draft it and you can mark it up. Not me deciding for you.
  48. Tariq Saleem
    Tariq Saleem None
    Laura, one practical thing on the accounting system connector. Our finance team will want to give read-only access and nothing else. Is that enough?
  49. Laura Penhaligon
    Laura Penhaligon None
    Read-only is all we need. Invoices, balances, payment status. We never write back.
  50. Tariq Saleem
    Tariq Saleem None
    Good. Then it's a question of which person in finance sets up the credentials. I'll ask, and I'll come back to you with a name.
  51. Deepa Chauhan
    Deepa Chauhan None
    And I'll have a word with credit control before then. They'll be the heaviest users of that connector, so they should be involved from the start. Let's get credit control in the room for the next review, properly.
  52. Laura Penhaligon
    Laura Penhaligon None
    That would help a lot. Could I join it, even just for the first twenty minutes? I'd like to hear how the review actually runs.
  53. Deepa Chauhan
    Deepa Chauhan None
    Of course. It's the best way to see what people really ask, honestly.
  54. Laura Penhaligon
    Laura Penhaligon None
    Okay. Before we finish, let me pull it together, and you correct me. One: the CRM and the branch system are the first two connectors. Tariq owns both on your side, and the load log is where we both look when something doesn't arrive.
  55. Tariq Saleem
    Tariq Saleem None
    Yes. And I'll tell Deepa before I change any mapping, in writing, so it's not only in my head.
  56. Laura Penhaligon
    Laura Penhaligon None
    Two: a match table, owned by Tariq, with an unmatched list that goes to Deepa's monthly review. Three: a first wave of users, three groups, small. Four: roles agreed before the second wave. Five: IT's security questions come to me early.
  57. Deepa Chauhan
    Deepa Chauhan None
    And six, which is mine. A date I can give the regional directors.
  58. Laura Penhaligon
    Laura Penhaligon None
    Yes. I don't want to promise a date I haven't checked against the plan, so give me till early next week. I'll come back with a view on when the first wave could realistically see matched accounts, and I'll go through it with Amara first, since she'll be looking after the account once we're live.
  59. Deepa Chauhan
    Deepa Chauhan None
    That's fine. I'd rather have an honest date than a quick one. I'll say that to the regions as well.
  60. Tariq Saleem
    Tariq Saleem None
    I'll send you the field list from the branch system today, Laura, so you've got it before you do the plan. And the name for the finance credentials once I have it.
  61. Laura Penhaligon
    Laura Penhaligon None
    Perfect. And I'll send the connector plan, the owners table and the draft role rules, by the end of the day if I can, Monday morning at the latest.
  62. Deepa Chauhan
    Deepa Chauhan None
    Lovely. Lewis mentioned you'd be thorough, and that's been true so far. Thanks, both.
  63. Laura Penhaligon
    Laura Penhaligon None
    That's kind. Thank you, Deepa, thank you, Tariq. Have a good weekend, and I hope the rain eases off.
  64. Tariq Saleem
    Tariq Saleem None
    Cheers, Laura. Cheers, Deepa. Speak soon.

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
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

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.

HelpAsk B

Ask B

B-Brain · read-only