Ask
Merriott Lyle Distribution: documents logo

Merriott Lyle demo: recap and next steps

Email thread

Merriott Lyle Distribution: documents logo Merriott Lyle Distribution: documents · sales

After the demo, Lewis Kerr recaps an Enterprise purchase at £146k excluding VAT, aiming to sign by 14 Feb 2025. Tariq Saleem agrees but raises account matching between CRM and branch system as his main worry.

What was said

What this says

Current to 11 Oct 26

After the demo, Lewis Kerr recaps an Enterprise purchase at £146k excluding VAT, aiming to sign by 14 Feb 2025. Tariq Saleem agrees but raises account matching between CRM and branch system as his main worry.

Ask: Tariq wants to know how the brain handles two records for the same customer under different names. He also wants to know which connector runs nightly first, so he can check the load log.

Customer view: the recap matched his notes, but he treats matching as a mapping question before a connector question.

Next: Hannah Lowe is to write up matching with a worked example and confirm connector order once she has Tariq's list. Lewis is to send the written proposal.

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

The thread

Updated 9 Oct 26
Typesales
Messages3
First message2024-12-18
Last message2024-12-24

Messages

  1. Lewis Kerr
    Lewis Kerr 18 Dec 2024 17:21
    to Deepa Chauhan, Tariq Saleem
    Deepa, Tariq, Thank you both for your time today. To confirm what I took from the session: you want one view of each trade account for the branch, key-account and credit-control teams, on the Enterprise tier, with a decision in the new year and a view to signing by 14 Feb 2025. To put a number on it, the overall deal value we are working to is £146,500, excluding VAT. I'll send that over properly in the written proposal, with the subscription and the one-off implementation shown separately, so nobody has to guess what sits inside the total. Three things I'd like to pick up from here: - Tariq, a list of the systems you would want connected first, so Hannah can sketch the connector design against your CRM and the branch system. - Deepa, who else should see the proposal on your side, particularly credit control and the regional directors. - Both of you, any questions the demo raised that you would rather have in writing. Hannah is copied and will cover anything technical or security related. Kind regards, Lewis
  2. Tariq Saleem
    Tariq Saleem 20 Dec 2024 08:43
    to Lewis Kerr
    Lewis, Thanks for the recap, it matches my notes. On the connector list, the CRM is the obvious first one, then the branch system, then the credit control data. My main worry is account matching. The branch system and the CRM do not always agree on what a trade account is, and that's a mapping question before it's a connector question. Can Hannah explain how the brain handles two records that are the same customer under different names? I'd also like to know which connector would be the first to run nightly, because I'll check the load log against it during any trial. On 18 Dec 2024, at 17:21, Lewis Kerr wrote: > Tariq, a list of the systems you would want connected first, so Hannah can > sketch the connector design against your CRM and the branch system. Cheers, Tariq
  3. Lewis Kerr
    Lewis Kerr 24 Dec 2024 13:31
    to Deepa Chauhan, Tariq Saleem
    Tariq, Deepa, Thank you, Tariq, that is exactly the right question to put to Hannah. She will write up how matching works in practice, with a worked example using two records for the same trade account, and I'll make sure it reaches you both in the new year. I'd rather it was in writing than summarised by me. On the first nightly connector, I won't answer that from memory. Hannah will confirm the sequence once she has seen your list, and I'll send the proposal over today or first thing after the break, whichever you prefer. Deepa, if you can let me know who should be copied from credit control, I'll include them from the start. The date we are still aiming at is 14 Feb 2025, but I'd rather the questions were answered properly than rushed. Have a good Christmas, both. Kind regards, Lewis

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.

Help

Ask B

B-Brain · read-only