Lab · Workflow design
Exceptions first: an AI step for the brief form
The brief form on this site, extended on paper with one AI step: read the request, suggest where it goes, and hand anything uncertain to a person. Capability in development, not client work.
A design, not a demo: the workflow runs on this site, the AI step is not built.
Every brief sent from this site goes through a function we wrote: it checks the fields, drops spam, delivers the brief by webhook or keeps it in storage, and tells the sender the truth when nothing is connected. That part is real and you can read about it on the technology page.
This experiment asks what one AI step would add to it, and what it would take to trust that step. It is written before it is built, so the failure cases are decided first.
The chain
| Step | What happens | State |
|---|---|---|
| 1. Problem | Briefs arrive by form; some wait, some reach the wrong person, all are retyped. | Observed |
| 2. Workflow | Validate, drop spam, store, deliver, confirm. Plain code. | Runs on this site |
| 3. AI step | Read the free text; suggest a project type, an urgency and a draft reply, each with a one-line reason. | Designed, not built |
| 4. Tools | Webhook to the inbox or CRM; storage when nothing is connected. The step can label and draft, never send. | Runs on this site (without the AI step) |
| 5. Person | Below the confidence line, any mention of price or contracts, any first reply to a new client: a person decides. | Designed |
| 6. Result | Time to first reply, briefs needing no correction, share sent to a person, measured on real briefs. | Not measured: nothing to measure yet |
Rules decided before any code
- The AI step returns a label and a reason. No reason, no label: the brief goes to a person.
- Below a confidence line set from a test set of past briefs, the step does nothing but pass the brief on.
- It drafts, it never sends. Sending stays a person’s click.
- Every run is logged: input, suggestion, reason, who accepted or changed it.
- If the model is down, the workflow still runs without it, as it does today.
- Anything that answers a visitor directly says it is automated.
- Kind
- Workflow design
- Technology
- Cloudflare Pages Functions, Webhooks, Workers KV, Language model API with structured output (not built)
- Status
- Capability in development. Steps 1, 2, 4 and 6 run on this site; step 3 is designed, not built.
Bring an experiment like this into a product
Tell us what you need and by when. We read every enquiry and reply in writing, with questions, a next step, or a plain no if we’re the wrong studio.


