Skip to content

Examples and measurement

A concrete project. Results to verify.

Explore a tool built for our own operations and how we check an improvement. No client results or public testimonials are published at this time.

Book a call

An internal project

Our enquiry form, from message to follow-up.

We connected enquiries from our own website to follow-up in an internal interface. A concrete example of what connected tools can do.

  1. Receive the enquiry

    The form brings together the message, contact details and consent to reply.

  2. Find the context

    A reference connects the enquiry to its record and the information needed for follow-up.

  3. Track its handling

    An internal list lets the team mark the enquiry as handled or reopen it.

What was checked

Internal checks recorded on September 11, 2026 covered concurrent enquiries, consent and recovery after an error in a test environment.

Internal project. These checks verify functions; they do not establish time savings or commercial results.

Start with the current work

Describe who does the work, what they are trying to accomplish, recent examples, workarounds and starting data. State the assumption to test before selecting a solution.

Compare after implementation

Review agreed user and operating outcomes over a comparable period: task completion, time, errors, delays, human review and costs. Keep outputs, observations, assumptions and projections distinct; record what decision each measure informs.

What would we know, observe and decide?

Illustrative evidence template · No client values. Each measure needs a source, period, method, owner and decision.

Evidence template: no client values
ClassRecordDecision use
BaselineTask + starting pointDAY 00 · Define the current work and comparable volume before production. Record source, period and owner
EstimatedCritical assumptionBEFORE LAUNCH · Name what must be true for the approach to help. Test with people · Not an observed result
ObservedUse + operating outcomeLIVE RUN · Record comparable volume, task outcome, review effort, exceptions and costs. Observed after launch · Method and limits recorded
Projection + decisionContinue / adjust / stopREVIEW · Keep any forecast conditional and separate from the decision. Continue, adjust or stop based on evidence
Read the explanation

An evidence record starts with a defined task and comparable baseline, records an assumption before testing, observes use and operating cost after launch, then separates any conditional projection from the decision to continue, adjust or stop. No numbers shown here are client results.

  1. Baseline: Task + starting point DAY 00 · Define the current work and comparable volume before production. Record source, period and owner
  2. Estimated: Critical assumption BEFORE LAUNCH · Name what must be true for the approach to help. Test with people · Not an observed result
  3. Observed: Use + operating outcome LIVE RUN · Record comparable volume, task outcome, review effort, exceptions and costs. Observed after launch · Method and limits recorded
  4. Projection + decision: Continue / adjust / stop REVIEW · Keep any forecast conditional and separate from the decision. Continue, adjust or stop based on evidence

Next step

What change would help your team?

We can examine the problem and the criteria for evaluating a first improvement.

Book a call