The Ward Method
Five stages, run in order, every time. This page describes what happens at each one, what you see while it happens, and the artifacts you hold at the end.
01 — The stages
Every engagement begins with a forty-five-minute audit. We map your workflows, rank them by risk and return, and name the one worth automating first. Some are not worth automating at all — we say so.
What happens
A structured walkthrough of how work actually moves through your company — not how the org chart says it does. We look for the workflows where errors cost money and humans cost patience.
What you see
One call, one week of quiet analysis, one written findings document. No sales sequence. You receive the findings whether or not we proceed.
Artifacts
A ranked workflow map, a risk-and-return assessment for each candidate, and a one-page recommendation with a fixed price band and timeline.
Before construction starts, we write the quality gates — executable checks that define what "working" means for your system. Then we build until every gate is green. The gates are code, not promises, so they cannot quietly expire.
What happens
Gates first, system second. Every change the system will ever receive must pass the full gate suite. Nothing advances on assurance alone.
What you see
A gate dashboard you can open any day of the build, and a weekly note in plain language: what turned green, what is still red, what we learned.
Artifacts
The executable gate suite itself, an audit trail running from the system's first action, and documentation written for your team rather than ours.
Go-live is where most vendors leave. It is where we begin the watch: ninety days of live observation while the system meets reality — the malformed documents, the API changes, the edge cases no demo ever sees.
What happens
We monitor every run, investigate every anomaly, and correct drift before you feel the difference. Each incident becomes a written lesson and, where possible, a new gate.
What you see
Incident notes when something happens, silence when nothing does, and a monthly summary of what the system did, declined to do, and learned.
Artifacts
The lesson library, an unbroken ninety-day gate record, and a system measurably harder to surprise than the day it launched.
Handoff is a ceremony with a document, not an email with a zip file. The Warrant of Handoff states what we built, what it does, what it must never do, and what we still stand guard over. Both parties sign it.
What happens
A closing session where we walk your team through the system, the evidence, and the Warrant, line by line. Questions are settled before signatures.
What you see
One signing meeting and a complete evidence folder. Every claim in the Warrant points to an artifact that proves it.
Artifacts
The signed Warrant of Handoff and the full six-proof set: audit trail, gates, resumable runs, lesson library, governance report, Warrant.
For clients who keep us on watch, the guardianship never lapses. The Watch is a standing retainer — $1,500 to $5,000 per month — that keeps a named human answerable for your system for as long as it runs.
What happens
Continuous monitoring, drift review as models and APIs change, gate maintenance, and small improvements folded in before they become requests.
What you see
A monthly governance report in owner's English, and a person whose name you know answering the phone when something feels wrong.
Artifacts
Monthly governance reports, a growing lesson library, and gates that keep pace with a changing system instead of decaying beneath it.
02 — The six proofs
Six artifacts ship with every engagement, regardless of tier. They are not paperwork. They are the difference between a system you own and a system you merely host.
Every action the system takes is logged, timestamped, and attributable from its very first run. When someone asks, months later, why the system did what it did on a Tuesday in March, the answer is a query, not an archaeology project. The trail is designed to be read by your auditor, your counsel, or your successor — not just by us.
Quality checks that run as code on every change to the system, forever. A slide deck's promises expire when the meeting ends; a gate suite fails loudly the moment a change would break something you care about. The gates are written before the system is, and they are handed over with it — your permanent, self-enforcing definition of "working."
When something fails mid-run — a timeout, a malformed record, an upstream outage — the system pauses, records where it stopped, and resumes from that point. No silent restarts, no double-processed invoices, no lost work. Failure is treated as a normal event with a designed response, because at 2 a.m. it is.
Every incident, edge case, and near miss becomes a written, versioned lesson: what happened, why, and what changed as a result. This is institutional memory that survives staff turnover — including ours. A year in, the library is often the most valuable artifact of the engagement: a record of everything reality taught the system.
A plain-language account of what the system did, what it declined to do, and why — written for owners, not engineers. It covers volumes, exceptions, escalations, and drift, in sentences a board can read without translation. If your automation cannot be explained to the people accountable for it, it is not governed. This report is how it stays explainable.
The closing document, signed by both parties. It states what we built, what it does, its known limits, what it must never do, and what we still stand guard over. Every claim references evidence in the other five proofs. It is the answer to the question most automation contracts leave vacant: who answers for this system now.
03 — The tiers
The tier sets the scope and the stakes. The method — gates, watch, Warrant, six proofs — is identical at every level.
Tier I
$750 – $8,000
For the company automating seriously for the first time, or testing whether we are who we say we are.
One workflow — intake, routing, reporting, follow-up — scoped in a single audit and delivered in weeks. Small in price, not in discipline: the same gates, the same watch, the same Warrant as the largest engagement. Most clients meet us here, and most retainers begin here.
Tier II
$8,000 – $60,000
For operations that read, decide, and act — where a wrong answer has a cost and an unlogged answer has a bigger one.
Document intelligence pipelines and governed agents for contracts, claims, compliance queues, and client correspondence. Agents operate with defined authority: what they may decide alone, what requires review, what they must never touch. Every decision logged. Every action reviewable.
Tier III
$25,000 – $90,000
For financial and regulated workflows, where trust is not granted at go-live. It is earned in production, with evidence.
Reconciliation assurance and earned-autonomy operations. Systems begin fully supervised and expand their authority only as the gate record justifies it — autonomy is a measured, staged privilege, never a launch feature. Human-approval controls are mandatory and contractual, and reconciliation work is advisory-only: the system surfaces, a human signs.
Forty-five minutes. A ranked map of your workflows. Yours to keep, whether or not we proceed.
Book a Watch Audit