B-Brain
Merriott Lyle Distribution logo

Kickoff follow-up: actions and what I need from your side

Email thread

Merriott Lyle Distribution logo Merriott Lyle Distribution · cs

Callie Brennan recapped the kickoff with Deepa Chauhan, Tariq Saleem and Gareth Pugh and asked for written access, the security questionnaire and the SSO approver. Tariq is waiting on IT confirmation; no first refresh date is committed.

What was said

What this says

Current to 13 Oct 26

Callie Brennan recapped the kickoff with Deepa Chauhan, Tariq Saleem and Gareth Pugh and asked for written access, the security questionnaire and the SSO approver. Tariq is waiting on IT confirmation; no first refresh date is committed.

Ask: Callie wants written read-only access, the security questionnaire, the SSO approver for the 200 licensed users and the first group of teams. She will not commit to a refresh date until access is in writing.

Customer view: Tariq put the CRM first and the branch system least certain. He prefers matching keys read from the branch system rather than spreadsheets by email.

Next: Gareth Pugh and Deepa have not replied in this thread. The Enterprise implementation and SSO review are waiting on them.

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

The thread

Updated 9 Oct 26
Typecs
Messages3
First message2025-03-07
Last message2025-03-11

Messages

  1. Callie Brennan
    Callie Brennan 7 Mar 2025 12:37
    to Deepa Chauhan, Tariq Saleem, Gareth Pugh
    Hi all, Thanks for your time on the kickoff call today. It was good to have commercial systems, the platform side and IT security in the same conversation, because it saves us a few rounds of emails later. To recap where we landed. The plan is to connect your sources in a sensible order, check the field mapping against your branch and key-account data, and only then let the first refresh run. The goal is that the first refresh lands cleanly and Tariq can run things day to day without needing us. What I need from your side is: - Tariq: the list of systems you want connected first, with a named owner for each, and the service account details for the CRM. Please send these in writing, as I won't start any connector without written access. - Gareth: your security questionnaire and anything you need from us for the review, so we can answer it as part of the Enterprise implementation. Please also tell me who needs to approve SSO for the 200 licensed users. - Deepa: confirmation of which teams (branch, key-account, credit control) should be in the first group of users, so we can set up sensible starting pages for them. Before we switch on the refresh, I'd like all three of those in hand. If I get them early next week I can show you a draft mapping that maps cleanly before anything goes live. Daniel is copied so he has the full picture from the start. Thanks, Callie
  2. Tariq Saleem
    Tariq Saleem 10 Mar 2025 08:35
    to Callie Brennan
    Callie, Thanks for the recap. A few points from me. I have the CRM service account details and I'm waiting on a colleague in IT to confirm the permissions are read-only. I'll send them in writing once that's done, and not before. For the source order, I'd put the CRM first, then the branch system, then the accounts data. The branch system is the one I'm least sure of. The account matching between it and the CRM is a mapping question and I'd rather we look at it together than guess. Which connector do you want to run first for the mapping check, the CRM or the branch system? One other thing. I'd prefer not to pass spreadsheets of account IDs around by email. Is there a way you can read the matching keys straight from the branch system once access is agreed? Gareth and Deepa are copied so they can see the access side. Cheers, Tariq
  3. Callie Brennan
    Callie Brennan 11 Mar 2025 09:18
    to Deepa Chauhan, Tariq Saleem, Gareth Pugh
    Hi all, Thanks, Tariq, that's helpful. On your questions. CRM first is right, so that's what we'll do. Reading the matching keys directly from the branch system is the better route and avoids the spreadsheets, but I'll need the access for that in writing too. Once you have it, send it over and I'll check the keys before we go anywhere near the refresh. I'll tell you plainly if a mapping needs a decision from you or Deepa. So the next steps are: - Tariq: written read-only access for the CRM, then the branch system. Please say when you have it. - Gareth: the security questionnaire and the SSO approver. If it's easier to talk it through, tell me and I'll set up a short call. - Deepa: the first group of teams, when you have a view. No rush on this one. I'll come back to you after that with the draft mapping and a date for the first refresh. I don't want to commit to a date until I've seen the access in writing. Thanks, Callie

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