B-Glass
Merriott Lyle Distribution logo

Merriott Lyle Distribution - QBR

Documentfinal

Merriott Lyle Distribution logo Merriott Lyle Distribution · QBR deck · final · 9 Aug 2026

Final QBR deck from CSM Daniel Okafor on the Enterprise account. Contracted annual recurring revenue is £128k with no overdue invoices, but active users sit at just over fifty of 200 licensed and are falling. Two of four tickets were high priority.

What it says

What this says

As at Fri 9 Oct 2026

Final QBR deck from CSM Daniel Okafor on the Enterprise account. Contracted annual recurring revenue is £128k with no overdue invoices, but active users sit at just over fifty of 200 licensed and are falling. Two of four tickets were high priority.

What it is: a customer-facing quarterly review prepared by Daniel Okafor, dated 9 Aug 2026. It says "adoption has softened this quarter" and frames the rest as hypotheses to test.

Commits: no contractual terms are set. It lists the term end as 27 Feb 2027 and proposes actions owned by Daniel, with timings such as "Within the next couple of weeks" and a ticket review "by the end of next week".

Unusual: it raises a possible service credit if either high-priority ticket touched freshness, and offers the on-site training day add-on to be scoped.

Not settled: questions asked, records indexed and connector status are not shown. The categories and response times of the two high-priority tickets are not given, and the value case is still to be evidenced.

AI · claude-sonnet-5-5 · as at Fri 9 Oct 2026

As found in this document

As at Fri 9 Oct 2026
  • Date end27 Feb 2027Source: the AI read of this record
  • Date renewal27 Feb 2027Source: the AI read of this record

The document

Body

Merriott Lyle Distribution - QBR

Quarterly business review | Enterprise | Prepared by Daniel Okafor, Customer Success Manager, BG-Demo | 9 Aug 2026

Status: Final


Purpose of this review

Thank you for making the time. This review covers how B-Glass is being used across your branch, key-account and credit-control teams, what has gone well, what has not, and what we propose to do together before the end of the current term.

I want to be straightforward from the start: adoption has softened this quarter, and most of this deck is about understanding why and what we do about it.

Account at a glance

ItemDetail
CustomerMerriott Lyle Distribution, Birmingham
SectorWholesale distribution
TierEnterprise
Customer since28 February 2025
Current term ends27 Feb 2027
Contracted annual recurring revenue£128k
Licensed users200
BG-Demo account ownerLewis Kerr
BG-Demo Customer Success ManagerDaniel Okafor
Read the whole document (7,357 characters)

Merriott Lyle bought Enterprise so that branch, key-account and credit-control teams could see each trade account's orders, disputes, calls and invoices together in one place, rather than reconciling them by hand across systems. That remains the outcome we are measured against.

Usage: where we are

  • Active users, measured as a thirty-day average, sit at just over fifty. Against two hundred licensed users, that is a quarter of the licence in regular use.
  • The thirty-day average is down on the prior quarter. The trend matters more than the level here, and the direction is the wrong one.
  • The business is spread across about one hundred and twenty branches, so a base of around fifty regular users suggests the brain is being used by a core group rather than being part of everyday branch routines.

What this deck does not show. The usage data in front of us covers active users only. Questions asked, records indexed and connector status are not part of this review, so I am not drawing conclusions on them. I will bring those figures to the follow-up so we can see who is asking questions and whether any source has stopped loading.

Value: what the brain is for

The original case rested on three groups of people working from the same view of a trade account.

  • Branch teams: seeing a customer's recent orders and any open dispute before a conversation at the counter or on the phone.
  • Key-account teams: having calls, emails and invoices alongside the order history when preparing for a review with a large trade customer.
  • Credit control: seeing disputes and call notes next to the invoice before chasing payment, so that a chase does not land on an account with an unresolved delivery problem.

A fall in active users puts the third of these most at risk, because credit control only gets value when the whole picture is current and the teams around them are using it too. If the value case is going to be defended at renewal, it needs concrete examples from your own teams, and I would like us to collect them together.

Support and service: this quarter

MeasurePosition
Tickets raised in the last thirty daysFour
Of which high priorityTwo
Overdue invoicesNone
  • Four tickets in a month is modest for an Enterprise customer of this size, and on its own it could read as health. Set against a falling user count, I would rather treat it as a point to look at than as reassurance.
  • Two of the four were high priority. I will go through both with your team, confirm the category of each (connector sync, data freshness, how-to or service query), and check the response times against the Enterprise service level.
  • Enterprise is credited for both availability and data freshness. If either of the high-priority tickets touched freshness, we will look at whether a service credit applies and tell you plainly.
  • Your account is fully up to date on invoices, which is appreciated. There is nothing on the commercial side that is holding anything back.

What we think is going on

I do not want to guess at causes this deck cannot support, so these are hypotheses to test with your team, not conclusions.

  • Rollout depth. Adoption may have stayed with the teams who championed the brain first, without reaching every branch group.
  • Trust in the data. If people met stale or incomplete answers, even once, they may have gone back to their old routines. The two high-priority tickets could be related.
  • Change of people or process. A reorganisation or change of role in a team can quietly take regular users out of the picture.
  • Training and habit. New joiners may not have been shown how to ask the brain a question.

I would value your view on which of these rings true. You know the branches far better than I do.

Proposed actions

ActionOwnerTiming
Review the two high-priority tickets with your team, including response times against the Enterprise service levelDaniel OkaforWithin the next couple of weeks
Pull questions asked, records indexed and connector status for the last two quarters, and share who is askingDaniel OkaforAhead of the follow-up session
Identify the branch and credit-control groups with the largest gap between licensed and active usersDaniel Okafor with your operations leadNext few weeks
Run short refresher sessions for the teams where use has dropped, including the on-site training day add-on if you would like it scopedDaniel Okafor, with Lewis Kerr for any commercial questionBefore the end of the quarter
Agree two or three worked examples of value (a resolved dispute, a faster credit-control call) to anchor the renewal conversationDaniel Okafor with your key-account leadBefore the renewal conversation begins

I will come back to you by the end of next week with the ticket review, so you are not waiting on me for that.

Looking ahead to renewal

Your current term runs to 27 Feb 2027. I would much rather we spend the coming months making the brain visibly useful to more of your people than arrive at the renewal conversation with a usage gap and a hurried story. Our aim is that, by the time we sit down, you can say with confidence what the brain is worth to Merriott Lyle, and that the numbers back it up.

If the usage picture improves, there is also a conversation to be had about whether the licence is sized correctly for how you actually work. We will only raise that if the evidence supports it.

What we need from you

  • A named contact in operations to work with on the branch-by-branch picture.
  • Ten minutes with whoever raised the two high-priority tickets, so we understand the impact on their day.
  • Your honest view on where the brain is not earning its place.

Summary

  • The commercial relationship is healthy: contracted annual recurring revenue of £128k and no overdue invoices.
  • Usage is the concern: active users are well below the licensed two hundred and falling on the prior quarter.
  • Support volume is low but includes two high-priority tickets that we will review in detail.
  • The next step is a joint look at who is using the brain, who is not, and why.

Just to close the loop: how is the team finding it? That is the question I most want to hear your answer to.

Best wishes, Daniel

Documentsmade from

Unusual terms

As at Fri 9 Oct 2026
  • possible service credit if a ticket touched freshness
  • on-site training day add-on offered for scoping

BG-Demo is a fictional company; every organisation and person here is invented. B-Glass is the tool. Data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Glass 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 B (the speech bubble) in the header, or open the Ask B page. Type a question, or pick one of the suggestions.

What the data covers

DataRecords
Organisations225
People at customers862
BG-Demo staff records (in post and leavers)58
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 AI 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.

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

Who to contact

Email info@b-glass.uk or talk to your B-Glass account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Glass · read-only