Hamza Akhtar

Merriott Lyle Distribution / BB-Demo – Onboarding

Callcompleted

Merriott Lyle Distribution: documents logo Merriott Lyle Distribution: documents · 2025-05-07 09:45

Onboarding call on 7 May 2025 with Tariq Saleem. Connector order, account matching between branch system and CRM, SSO and admin cover were agreed. Tariq left with a plan and three actions for the week.

What was said

What this says

Current to 11 Oct 26

Onboarding call on 7 May 2025 with Tariq Saleem. Connector order, account matching between branch system and CRM, SSO and admin cover were agreed. Tariq left with a plan and three actions for the week.

What happened: Hamza Akhtar and Tariq agreed to land the CRM connector first, then the branch system, accounting, helpdesk and call recorder. Tariq described the main worry as account matching, where the branch system code is missing from some CRM records.

Customer view: Tariq cares most about the nightly refresh finishing by seven each business morning, because stale numbers lose branch managers' trust. He left the call reassured.

Commercial: This is Enterprise implementation work, with SSO and provisioning in scope and a training day mentioned as an add-on. Tariq said he would keep it in mind and see how the pilot lands first.

Watch: Tariq is the only admin and wants two by the end of next week. The account matching review list has no confirmed owner, and the CRM account code coverage was an unchecked estimate.

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

Themes

Current to 9 Oct 26
Theme
Enterprise onboarding and matching
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Tariq Saleem to set up the Snowflake role and warehouse, confirm the review list owner and name a second admin.
  • Hamza Akhtar to send the connector checklist and the account matching mapping sheet.
  • Hamza to send the invite for next Wednesday at the same time and copy Amara.

Risks

Current to 9 Oct 26
  • Only one admin on the customer side, so a nightly failure has no cover until a second admin is named.
  • Account matching depends on a CRM account code that Tariq thinks only some records hold, and the review list owner is unconfirmed.
  • Branch managers will stop using the brain if the nightly refresh is late or stale.

Opportunities

Current to 9 Oct 26
  • On-site training day add-on was raised and left open until the pilot lands.
  • Rollout in waves from a pilot group to one region to all branches deepens use across the licensed users.

Transcript

  1. Hamza Akhtar
    Hamza Akhtar None
    Morning Tariq, can you hear me alright?
  2. Tariq Saleem
    Tariq Saleem None
    Morning Hamza. Yes, loud and clear. Can you see me, or is it just a grey box?
  3. Hamza Akhtar
    Hamza Akhtar None
    Grey box for a second, there you are. Lovely. Sorry, I'm a minute or two behind myself, the last call overran.
  4. Tariq Saleem
    Tariq Saleem None
    No problem at all. I've only just sat down. The train from the depot was a nightmare, half the Midlands seems to be under a rain cloud this morning.
  5. Hamza Akhtar
    Hamza Akhtar None
    Same here in London, it's been drizzling since about six. Anyway, good to finally do the proper onboarding session. Amara said you've been getting on with things already.
  6. Tariq Saleem
    Tariq Saleem None
    A bit, yes. I like to open with the tickets, if that's all right, so we know where we stand. We've got one open. It's a how-to, really. Which connector? The CRM one. I couldn't see where to set the field scope after the first test load.
  7. Hamza Akhtar
    Hamza Akhtar None
    Yes, I saw that come through. It's in the connector settings under the objects tab, you pick which objects and which fields the brain should index. I'd say that one is nearly closed on our side, support just want you to confirm it's working.
  8. Tariq Saleem
    Tariq Saleem None
    Right, I'll check the load log after this call and close it off. I did see the objects tab, I just didn't realise it applied per object rather than across the whole connector.
  9. Hamza Akhtar
    Hamza Akhtar None
    It trips everyone up the first time. Mm. So for today I thought we'd do four things. The order we switch connectors on, who owns what on your side, the account matching between the branch system and the CRM, and then single sign-on and user provisioning, because you're on Enterprise and that's a bigger piece than for most.
  10. Tariq Saleem
    Tariq Saleem None
    That's about what I had. I'd add one more, which is what the branches actually see on day one. I don't want a hundred and twenty branch managers logging in to an empty screen.
  11. Hamza Akhtar
    Hamza Akhtar None
    Agreed, we'll put that at the end so we don't run out of time on it. Shall we start with the connectors?
  12. Tariq Saleem
    Tariq Saleem None
    Please.
  13. Hamza Akhtar
    Hamza Akhtar None
    So the order form gives you up to twenty connectors on Enterprise. You won't use all of them in the first weeks, and I'd rather you didn't try. My suggestion is we land the CRM first, since you've already got a test load there, then the branch system, then the accounting system, the helpdesk and the call recorder. Email and the shared drive come after that.
  14. Tariq Saleem
    Tariq Saleem None
    Why the branch system second? I'd have said the accounting system, because credit control are the loudest team and they've been waiting longest.
  15. Hamza Akhtar
    Hamza Akhtar None
    Fair question. It's because the matching problem sits between the branch system and the CRM. If we get that wrong, everything we add after it inherits the mess. Accounting joins on the trade account, so it's much easier once that key is right.
  16. Tariq Saleem
    Tariq Saleem None
    Okay, that makes sense. That's a mapping question, and it's the one that worries me most, to be honest. Do you want me to describe how it looks today?
  17. Hamza Akhtar
    Hamza Akhtar None
    Yes please, go on.
  18. Tariq Saleem
    Tariq Saleem None
    So every branch creates trade accounts in the branch system, and they do it by hand at the counter. The CRM gets a nightly feed, but the feed matches on trading name and postcode and not on anything stable. If a builder has two sites, or changes the way the name is typed, you end up with two CRM accounts. And the other way round, two different builders with near-identical trading names get merged into one. I'd rather have a short list of rules than a clever one.
  19. Hamza Akhtar
    Hamza Akhtar None
    Yes, and I think you're right to want it simple. Is there any stable identifier in the branch system? An account number that survives a rename, something like that?
  20. Tariq Saleem
    Tariq Saleem None
    There's an account code. It's issued once and never reused. The problem is the CRM doesn't hold it on every record, only on the ones that came through the newer feed. So perhaps seven in ten have it, if I'm honest, and I'd want to check that properly before I said a number out loud.
  21. Hamza Akhtar
    Hamza Akhtar None
    That's fine, don't quote it. What I'd propose is that the brain treats the account code as the key wherever it exists, and falls back to name and delivery address only where it doesn't. Anything that falls back gets flagged in a review list rather than silently merged.
  22. Tariq Saleem
    Tariq Saleem None
    A review list I like. Who reads it?
  23. Hamza Akhtar
    Hamza Akhtar None
    That's partly my question for you. In my experience it's someone who knows the accounts, not someone from IT. Often a key-account person or a credit controller.
  24. Tariq Saleem
    Tariq Saleem None
    Then it's going to be one of the credit control team leads, because they already chase the duplicates when invoices go to the wrong place. I'll ask. I won't commit anyone before I've spoken to them.
  25. Hamza Akhtar
    Hamza Akhtar None
    No, quite right. Let's call that owner to be confirmed, and I'll put it on the plan as yours to close.
  26. Tariq Saleem
    Tariq Saleem None
    Fine. One thing I should say now so it doesn't surprise you. I won't change any mapping on the CRM side without telling my colleague who looks after the sales team's data. So if you suggest a rule that touches the CRM fields, it goes through her before it goes live.
  27. Hamza Akhtar
    Hamza Akhtar None
    That's sensible, and it's how I'd want it. Everything we change in the brain is a view over your data, nothing is written back to the source unless you ask for it. So the only edits that touch the CRM are ones you choose to make.
  28. Tariq Saleem
    Tariq Saleem None
    Good. That's the bit people at the branches worry about, that someone's going to overwrite their notes.
  29. Hamza Akhtar
    Hamza Akhtar None
    Not from our side. Right, access. Because the brain runs inside your own Snowflake account, the connectors read into tables there. I'll need a role and a warehouse that we can use, and I'd suggest a dedicated one so it's easy to see what the brain is costing you in compute.
  30. Tariq Saleem
    Tariq Saleem None
    I can do that. Do you want it small to start?
  31. Hamza Akhtar
    Hamza Akhtar None
    Small is fine. The nightly refresh is the heavy part and it has to be finished by seven o'clock each business morning. If it's too slow we'll tell you and you can size it up.
  32. Tariq Saleem
    Tariq Saleem None
    Seven in the morning, right. That's what I really care about, to be honest. If a branch manager opens it at half past and the numbers are from last week, they stop trusting it and it doesn't come back.
  33. Hamza Akhtar
    Hamza Akhtar None
    Completely. And that's why I'd like you to have the load log view from day one, not just us. I'll show you where it lives, it's on the admin page. Do you want me to share my screen?
  34. Tariq Saleem
    Tariq Saleem None
    Yes please. Go ahead.
  35. Hamza Akhtar
    Hamza Akhtar None
    Okay, can you see the admin page? This is your tenant. Left side, connectors. You've got the CRM there with the green tick from the test load, and the others are greyed out because they haven't been configured yet.
  36. Tariq Saleem
    Tariq Saleem None
    I can see it. Go into the CRM one, would you? I want to see that objects tab again.
  37. Hamza Akhtar
    Hamza Akhtar None
    Here. So accounts, contacts, opportunities, activities. Each one you can switch on and then choose the fields. You can see the records indexed count at the top, that's the number to watch. If it goes flat for several days and your sales team are still working, something's broken at the source.
  38. Tariq Saleem
    Tariq Saleem None
    Flat is the thing to look for. Got it. And that's per night, is it, the load history?
  39. Hamza Akhtar
    Hamza Akhtar None
    Per night, yes, with the start time, end time and what it loaded. Click on a night and you get the detail by object. That's your load log. Everyone asks for a spreadsheet of it and honestly this is better.
  40. Tariq Saleem
    Tariq Saleem None
    I won't argue. Fewer spreadsheets passed around by email is half of why I wanted this in the first place.
  41. Hamza Akhtar
    Hamza Akhtar None
    Ha. Yes, I got that from Lewis when we were scoping. Right, so let me stop sharing and we'll talk about people. Single sign-on first.
  42. Tariq Saleem
    Tariq Saleem None
    Go on. This is where I'll need someone from the identity side, I don't own that.
  43. Hamza Akhtar
    Hamza Akhtar None
    That's the usual picture. For Enterprise you get single sign-on and automatic user provisioning and removal. What we need from your colleague in IT is the metadata for your identity provider, and agreement on which groups map to which roles in the brain. Admin, builder and reader are the three.
  44. Tariq Saleem
    Tariq Saleem None
    Who's an admin? Right now it's me, and that's one too few. If I'm off sick on a nightly failure there's nobody.
  45. Hamza Akhtar
    Hamza Akhtar None
    I'd say two at least. You and one more, ideally someone who's comfortable in the CRM and not only in the data platform. Do you have a name in mind?
  46. Tariq Saleem
    Tariq Saleem None
    I think so, but I'd rather ask first. Let's say two admins by the end of next week.
  47. Hamza Akhtar
    Hamza Akhtar None
    Good, I'll write it as a target and not a promise. And builders, those are the people who make dashboards. I'd start with a very small group, a couple from credit control and a couple from the key-account team.
  48. Tariq Saleem
    Tariq Saleem None
    That fits. I don't want fifty people building fifty versions of the same chart. Readers are the branch managers, then?
  49. Hamza Akhtar
    Hamza Akhtar None
    Readers and askers. They can ask the brain questions in chat and search across everything, they just can't change the shared pages. You've got two hundred licensed users, so you've plenty of room, but I'd roll out in waves. A pilot group, then one region, then the rest.
  50. Tariq Saleem
    Tariq Saleem None
    Waves, yes. We've done that with the CRM before and it saved us. I'd say the pilot should be the branches nearest to Birmingham, so I can actually go and stand next to people.
  51. Hamza Akhtar
    Hamza Akhtar None
    Makes complete sense. And if you do want us there for a training day at some point, that's an add-on we can talk through with Lewis, there's no need to decide now.
  52. Tariq Saleem
    Tariq Saleem None
    I'll keep that in mind. Let's see how the pilot lands first.
  53. Hamza Akhtar
    Hamza Akhtar None
    Right. Security review. Your security team will have questions, and as part of the implementation we support that, so anything they send, forward it to me and I'll help turn it round.
  54. Tariq Saleem
    Tariq Saleem None
    They've got a questionnaire. It isn't started yet, but they do want to see how the data is held and where it sits. When I told them it's all in our own Snowflake account they were noticeably calmer.
  55. Hamza Akhtar
    Hamza Akhtar None
    That's usually the reaction. The short answer is nothing leaves your account, and I can put that in writing in the format they like.
  56. Tariq Saleem
    Tariq Saleem None
    Good. Then I'll forward the questionnaire once it lands. So, what do you need from me this week? I'd like to write it down properly.
  57. Hamza Akhtar
    Hamza Akhtar None
    Three things. One, the role and warehouse in Snowflake, with a service account for each connector, read-only on the source side. Two, confirmation of who reads the review list for account matching. Three, a name for the second admin.
  58. Tariq Saleem
    Tariq Saleem None
    Role and warehouse, review list owner, second admin. And you'll send me the service account list so I don't have to guess which permissions each one needs?
  59. Hamza Akhtar
    Hamza Akhtar None
    Yes, I'll send a connector checklist today, it's one page per source. And a mapping sheet for the account matching with the rules we talked about, so your colleague can see it before anything changes.
  60. Tariq Saleem
    Tariq Saleem None
    Perfect. I'd also like the first week of loads watched properly. If something fails at three in the morning, I'd like to know why before I'm asked.
  61. Hamza Akhtar
    Hamza Akhtar None
    We'll watch them on our side too for the first couple of weeks, and I'll message you if there's a miss, with the reason. No guessing at root causes, I'll check the log first and tell you what it shows.
  62. Tariq Saleem
    Tariq Saleem None
    That's how I work too, so we'll get on. Last thing, can we agree a regular slot? Same time next Wednesday, perhaps, once I've done the Snowflake bits.
  63. Hamza Akhtar
    Hamza Akhtar None
    Next Wednesday at the same time works for me. I'll send the invite and copy Amara so she's in the loop.
  64. Tariq Saleem
    Tariq Saleem None
    Lovely. Thanks Hamza, this was genuinely useful. I came in a bit nervous about the matching and I'm leaving with a plan.
  65. Hamza Akhtar
    Hamza Akhtar None
    Good, that's what it's for. Speak next week, Tariq. Enjoy the rain.
  66. Tariq Saleem
    Tariq Saleem None
    Cheers, Tariq. Ha, I mean cheers, Hamza. Bye for now.

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