The Workflow Blueprint · $750
Send us one workflow. We’ll send back the spec.
Six to ten pages on a single recurring process: what it actually is, which parts an agent can own, the rules it has to obey cited to where they come from, and the drafted prompt in full. Five business days. No call required, and nothing installed.
What you send
Things you already have.
Intake is a forwarding job, not a writing job: your last three real examples of the finished work as it actually went out, whatever governs it, the blank forms you are obliged to use, the deadline calendar, and who does it today. Redact names and figures if you want — the structure is what we need.
And one thing that matters more than the rest: the last five times it went wrong, with the reason you were given. That is what turns your paperwork into a list of checks an agent can actually run, and it is the one item nobody can reconstruct for you.
What comes back
Eight sections.
Scope, and the refusals
Three lists: what an agent takes, what it drafts for you to approve, and what stays with a person — with the reason each item is on the third list. Plus the exact moment somebody signs off, and what they are looking at when they do.
Your process, written down as a procedure
Reconstructed from your own last three examples of the finished work — not from what you tell us the process is. Every step, who does it, what it consumes, what it produces. Where your own three examples disagree with each other, we say so, and which one we followed.
The rules that govern it, cited to source
Each rule as a checkable assertion, cited to the contract clause, statute section or page of your customer’s instructions it comes from. Deadlines as dates, thresholds as numbers. You can open every citation and check it.
The exception catalogue
The last five times this went wrong, classified into the rules above — or flagged as not rule-shaped, which is a finding in itself. This is the only part of the document that is evidence rather than analysis, and it decides what the agent checks first.
The agent’s job description
Inputs, tools, outputs stated precisely enough to be falsifiable, and an explicit refusal list — the things it must never do regardless of what anyone types at it.
The drafted system prompt, in full
The actual text, complete, ready to paste into your own Claude account. Not a description of a prompt and not a summary. We do not withhold it to protect the build.
The check sequence
Ordered assertions run against a draft, each traced to the rule it enforces, sequenced so the expensive failure is caught before the cosmetic one. The order is the design.
Where it plugs in, how it fails, what a build costs
The integration point named concretely. Failure modes with the guardrail for each. The escalation rule stated as a rule. Then hours, dollars and monthly run cost — and the build-it-yourself path, so the document is worth $750 even if you never hire us.
Written into every prompt we draft
It emits a checklist and a diff. A person still signs.
- It never signs anything.
- It never submits anything.
- It never touches your customer’s portal.
- It never alters a dollar figure — it can flag one as inconsistent with a source document, and that is all.
These are not negotiable downward at a client’s request. Liability stays capped at fees paid and you remain the filer of record — an agent that signs destroys that position, and the exposure behind a certification is not something insurance covers.
What $750 does not buy
Stated here rather than in a contract.
- No live call. The Blueprint is a written product.
- No code written and no prompts deployed.
- No access to your systems, your data or your credentials — we will not hold a login to anything of yours.
- No firm-wide assessment. One workflow.
- No vendor selection or procurement advice.
- No security, privacy or compliance review.
- No revisions beyond one written round.
- No ongoing availability afterwards.
And one more, which is the point of the whole thing: if the honest answer is that an agent should not touch this workflow, that is what the document will say — and you keep it. A Blueprint that recommends a build you don’t need is worth less than the $750.
How it runs
A worked example
The pre-submission pay application check.
For a commercial specialty trade subcontractor — mechanical, electrical, plumbing, fire protection — the workflow we lead with is the one that runs before the packet goes out. Not assembling the pay application: checking it, against your subcontract terms, your state’s waiver and prompt-pay rules, and the specific billing instructions of the GC whose portal you are stuck in this month.
Which is where the seam is. You don’t choose your stack — your customers impose it, differently on every job, and no vendor can normalise the union of every GC’s rules for one subcontractor. Your last five kick-backs can, because they tell us exactly which rules yours actually break.
Intake for this one: one executed subcontract or its payment articles · the last three pay apps for a job as actually submitted, with backup · the schedule of values · the GC’s billing instructions and cutoff calendar · blank waivers, transmittals and WH-347 if it’s public work · the COI tracker · and the last five short-payments or rejections with the stated reason.
Start with the free twenty minutes.
Tell us the workflow and we’ll tell you whether it’s a Blueprint, a Sprint, or nothing worth building. That conversation costs nothing and does not need an account.