Why four weeks — not a weekend, not six months?
A weekend gets you a demo: something that works once, on a good day, with you watching. Six months gets you a consulting engagement: a roadmap, a committee, and very often still no running system. Four weeks is the honest middle — long enough to run the agent on real work and fix what reality breaks, short enough that the finish line is visible from the start and the scope can't quietly grow.
The constraint that makes it work is one agent. Not a suite, not a transformation — one defined recurring job, done properly, owned at the end. Every failed first build we've examined broke that rule first.
Week 1: how do you pick the right workflow?
You don't start by building. You start by mapping the recurring work and asking three questions of each candidate: does it happen often enough to matter? Does the information it needs exist somewhere an agent can reach? And what would "working" mean, in numbers you choose — inquiries answered inside an hour, the Monday report on time every week, quote drafts in minutes instead of evenings?
Writing that definition down before building is the single highest-value hour of the month — it's what lets you judge the agent honestly in week 4 instead of squinting at it hopefully. And it has an edge a fair engagement has to keep: if no workflow clears the bar, the right answer is to stop, say so, and not build. In our engagements that means the deposit goes back in full.
Week 2: what does "building" look like when you're not a developer?
Less like programming, more like training a very fast, very literal new hire. Your dedicated specialist does the engineering; the decisions get made out loud with you in plain-English sessions: what the agent is allowed to see, what it drafts, what it must never do, where its output lands, and how it announces failure. The instructions read like a brief you'd give a person, tightened until a literal-minded reader can't misread them — that's where your knowledge becomes the system's rules.
Between sessions, the homework belongs to the agent and the specialist, not to you. The design premise of a first build for a time-poor owner is that your 2–3 hours a week are spent deciding and approving, not doing. Every deliverable also passes the practice's quality review before it reaches you — how that works.
Week 3: what happens when it runs on real work?
Reality files its objections. The agent runs on live inputs — real inquiries, real numbers, real documents — and the first drafts are never quite right: the tone's slightly off, an edge case nobody predicted shows up on day two, a source turns out to be messier than everyone remembered. This is the week that separates a working system from a demo, and the schedule protects all of it.
Two guardrails are in place before anything runs live, and they're non-negotiable: the human-approval gate — nothing sends, posts, or spends without your sign-off, enforced by the system's permissions, not a promise — and honest failure: the agent must report a broken source or a job it can't do, never improvise around it. Then the tuning loop runs daily and stays small: read what the agent produced, correct the rules, run again. By the end of the week you've done that loop enough times to keep doing it alone.
Week 4: what does handover actually include?
A named deliverable set, not a goodbye: the working agent; every credential in accounts you own; plain-English documentation your next hire could follow; a recorded maintenance walkthrough; and an honest measurement against week 1's written definition of "working." Then the engagement ends — and the system doesn't. It keeps running whether or not you ever call us again, which is the whole point of the ownership model.
What goes wrong when this process is skipped?
The failure patterns are consistent: building before defining success (nobody can say whether it worked); scoping three agents at once (none of them finish); skipping the live week (the demo dies on contact with reality); and vendor-owned handover (the system works — for as long as you keep paying). The four-week structure isn't ceremony. Each week exists because skipping it has a named cost.