Operator evidence

Operating results, shown with their evidence.

Every example on this page states its context, baseline and measurement basis. If a number cannot be evidenced, it is not published.

The results below come from operating roles held before Clerq, included to show the measurement standard Clerq applies now. They are anonymised to respect confidentiality, and none of them is a Clerq client engagement.

Get the Sample Diagnostic

No client names, no invented results, measurement basis stated on every figure.

The evidence policy

Why these examples look different from most case studies.

Public examples remain anonymous. Clerq does not publish client names, logos or identifying details without permission, and does not use confidentiality as an excuse to invent results. Where an example is shown, it states the context and measurement basis that can be verified. The two results below predate Clerq: they come from operating roles, not client engagements, and they are included because they set the measurement standard every Clerq engagement is now held to.

Operating result 01

Retail rollout that didn't break the back office.

Omnichannel consumer business, sub-£20m growing to mid-£30m revenue. From an operating role held before Clerq, anonymised.

Context and baseline

  • A growth-stage founder-led brand more than doubled its physical footprint while ecommerce kept growing.
  • Store estate grew from 12 to 28 stores over the measured period.
  • At the start, store P&L visibility took 5 days.
  • The risk was the usual one: retail expansion outrunning the finance and operations capacity behind it.

Intervention and measured outcome

  • The operating work connected 3PL information, store reporting and finance controls without expanding the finance team.
  • Stores opened: 12 to 28.
  • Store P&L visibility: 5 days to 2 days.
  • Revenue doubled on the same finance team.

Measured over 18 months: store count, time to store P&L and revenue supported by the existing finance team.

Operating result 02

Returns reconciliation with controlled exceptions.

DTC consumer business, £5-10m revenue. From an operating role held before Clerq, anonymised.

Context and baseline

  • Three systems held different records of the same returns.
  • Reconciling them was manual finance work, and unmatched return value went unrecovered.
  • The workflow is common in DTC: refund, warehouse and accounting records that disagree by default.

Intervention and measured outcome

  • The workflow matched routine cases daily and sent exceptions, with evidence, to the accountable reviewer.
  • £36k+ recovered in year one.
  • 2 days per month returned to finance.
  • Payback period under 3 months.

Measured in year one: recovered return value, monthly finance time and cost-to-recovery payback.

The same workflow pattern is described as a service at returns reconciliation and as a process guide in the ecommerce returns reconciliation article.

The method, worked end to end

The Sample Diagnostic: fictional business, real method.

The Sample Diagnostic shows how Clerq assesses, prioritises and controls workflow opportunities before a build. The example is fictional, its figures are illustrative, and it makes no claim about a real client's results. It is not based on a named or anonymous client and it is not a promise of savings, payback or implementation scope. What it does show is the standard of analysis and control thinking you should expect: a workflow inventory, an evidence-based prioritisation, explicit controls and a roadmap written for a management decision.

Client case studies will appear here, with consent.

Clerq is a young consultancy and says so. As engagements complete, client results will be published on this page only with permission, each with its context, baseline and measurement basis stated in the same format as the results above. Until then, the honest offer is the method: inspect the Sample Diagnostic, then test the fit on your own workflow.

  • Two-week Diagnostic from £2,500
  • No required follow-on Build
  • Fixed-price Clerq recommendations where appropriate
  • Three months of Run included after a Clerq Build
Get the Sample Diagnostic
Questions

Evidence policy FAQ

Are these results from Clerq client engagements?
No, and the page says so. The two operating results come from operating roles held before Clerq. They are included to show the measurement standard Clerq applies now. Client case studies will be published only with consent as engagements complete.
Why are the businesses not named?
Clerq does not publish client names, logos or identifying details without permission, and does not use confidentiality as an excuse to invent results. Where an example is shown, it states the context and measurement basis so it can be assessed on its evidence.
Is the Sample Diagnostic based on a real client?
No. The Sample Diagnostic is fictional, its figures are illustrative, and it makes no claim about a real client's results. It exists to show the standard of analysis and control thinking you should expect from a paid Diagnostic.
When will Clerq publish client case studies?
As engagements complete and clients consent. Each will state the context, the baseline, what changed and how the outcome was measured, in the same format as the operating results on this page. Nothing is published without permission.
Start with the workflow

The next measured result could be yours.

Request a short fit call. Clerq will reply to arrange a time and establish whether the operating problem is suitable.

Get the Sample Diagnostic