Services

Illustrative · composite scenario

Worked example · Draft-and-Approve pilot

Redgate Freight

From a mispriced quote that slipped out unattended, to an approval layer the ops team can put their name to.

IllustrativeComposite scenarioThe shape of one real pilot
01

The problem

Redgate quote hundreds of repeat freight jobs a week. Each one starts as an email and ends as a line in their transport system — re-keyed by hand, twenty minutes a time.

So they bolted an AI copilot onto it. It reads the email, drafts the quote, and — to save the twenty minutes — some drafts went out without anyone checking them. Mostly fine. Until a fuel surcharge was read from the wrong month and a quote went out 12% under the lane’s floor price. Nobody saw it until the customer accepted it.

Their WFK audit had already flagged this: strong on speed, weakest on governance — an agent acting with no gate and no record. The ops manager, Dana, put it plainly: “I can’t put my name to a number I never saw.” That sentence is the whole brief.

02

What I took in

Not access to rebuild anything — just enough to understand the decision. The pilot’s raw material:

  • The workflow“We quote repeat lanes from customer emails and key them into our TMS.” In their words, not a spec.
  • The AI, todayA copilot that drafts a quote from the email — sometimes held, sometimes sent unattended.
  • The systems it touchesTheir email inbox (the input) and their TMS (the record). Named and understood — not mine to rebuild.
  • Twenty real casesActual emails and the quotes they became — including the one that went wrong.
  • The human decisionWhat Dana’s team checks before a quote is trusted: lane, rate floor, surcharge table, margin.
  • The stakesA mispriced quote is money out the door and a credibility hit. That’s what a gate has to protect.
03

The reasoning

The obvious fix is to make the copilot a better estimator. I didn’t. A better guesser is still a guesser — and Dana still can’t stand behind a number she didn’t see. The problem was never accuracy. It’s accountability.

So I weighed three shapes, out loud, with them:

Turn it off. Safe — and it throws away the twenty minutes a quote it just gave them back. Nobody wants that trade.

Automate it fully with pricing rules.Brittle the first time a lane isn’t in the table — and it still puts a machine, not a person, on the hook for the price.

Design the moment of approval.The copilot drafts; a person confirms in a glance; every decision is recorded. We built this one — not because it’s the clever answer, but because it’s the only one Dana can defend to her MD when a quote is questioned.

And here’s the actual craft: the win isn’t the gate, it’s making the gate cost five seconds, not five minutes. Show the draft, the one reason it landed there, the single thing worth checking — and one button. Get that wrong and people route around it. Get it right and oversight stops feeling like friction and starts feeling like cover.

04

What I designed

Not a new system — the layer in between. First, where it sits:

Their systemInboxThe quote request arrives. Untouched.
WFK designs thisThe approval layerDraft + reasoning + the gate + the record.
Their systemTMSThe approved quote is keyed as normal. Untouched.

The whole boundary in one line: I design the middle. Their systems keep working exactly as they do — the approval layer just sits on top and holds the moment a human says yes.

The deliverable, made visible — the approval screen a Redgate approver would use

redgate-freight · quote approvals
Northbound pallets · Acme FoodsNeeds approval
The draft
LaneMCR → GLA
Rate£412
Fuel surcharge+£38
Quote total£450
Why

Matched to 3 prior quotes on this lane. Surcharge from the current fuel table. Margin 18%. Source: Acme email, 08:41.

Rate is 12% below this lane’s floor. Confirm before approving — this is the check that was missed.
ApproveEditRejectlogged either way
Decision record
08:41
Request in from Acme Foods
08:41
Drafted by copilot
now
Held — floor-price flag raised
Awaiting Dana

Grey bars are placeholder content — the labels, numbers, the flag and the gate are the real design. The agent drafts; the flag surfaces the one thing worth checking; a person approves; the record writes itself.

05

The handoff pack

Not a mysterious bundle — a working thing and four documents. Everything below is theirs to keep: if I vanish, nothing stops and anyone can extend it.

  • The approval interface

    The working screen above, running on their real quote flow — draft, reasoning, the gate.

    Owned by Redgate
  • The decision-record model

    The append-only log — who approved what, when, and why — plus a sample trail Dana can hand an auditor.

    Owned by Redgate
  • The gating spec

    A short document: which actions are gated, the thresholds (the floor-price rule), and what escalates to whom.

    Owned by Redgate
  • The runbook

    How it works and how to maintain it as lanes, rates and volumes change — in plain language, for their team.

    Owned by Redgate
  • The interface spec

    The design documented so any builder — theirs or a future one — can rebuild or extend it. Your no-lock-in guarantee.

    Owned by Redgate
06

The pay-off

The design solution at work

The copilot didn’t get smarter. It got accountable.

That’s the real pay-off — not a productivity stat, but a change in what the business can trust. The same AI, the same speed — but now every price carries a name, every decision leaves a record, and Dana can defend any quote in the room. The design didn’t remove the human; it gave the human back control they can actually exercise in five seconds. Watch the flag catch the floor-price miss above: that’s the solution doing its job, in one glance.

Kept
~5 min
to approve a quote — the copilot’s speed, with a human on it.
Removed
0
quotes sent unattended. Every price now carries a name.
Gained
100%
of decisions logged — an audit trail Dana can show her MD.

What this is, and isn’t

Straight about the boundary

  • We design the approval layer— the review surface, the gate, the record. That’s the craft you’re buying.
  • You own everything we hand over, and it rides on the systems you already run. No lock-in, no dependency on us.
  • We don’trebuild or integrate your systems, and we don’t own your data plumbing.
  • The agent neveracts unattended. If a human isn’t in the loop, it isn’t what we do.
← Back to services

Illustrative composite · not a real client · the shape of a real Draft-and-Approve pilot

WFK — we design the moment a person says yes.