Picture the second Friday. A billing coordinator opens this month’s prebills and every awkward entry is already marked: the rate that differs from the client’s agreement, the narrative the client will query, the expense with no receipt. She runs the workflow herself, on real prebills, with the billing manager beside her checking each mark. Next to it sit four procedures the team has always carried in its heads, now written in its own words and signed off by their owner. That is 10X the ROI of your existing AI, starting with one team.
The 2-Week Workflow Sprint is how one team gets there. It is a fixed $3,500, once per client, and runs about two weeks from the first interview. What happens on a fit call covers how you decide whether it is the right start, and Prepare for your first workflow covers what to have ready. This piece walks through the two weeks themselves and ends with what you hold.
Before the clock starts.
The clock starts at the first interview, not the day you sign. Before it, we agree the team, the procedures in scope, the review rounds and the time each person gives. We check the workspace with you: your ChatGPT, Claude, Copilot or Gemini plan, who can reach the workflow and who approves this use of your information. Past examples are gathered in your own account, ready for testing.
Scoping also settles connections. Where the work runs through systems you already use and a connector for them already exists, connecting the workflow is part of building it, and what gets connected is agreed here, before the build. A new connector is not part of the sprint. Where nothing is connected, the workflow runs from the files and exports your team already handles, with the same rules and the same tests. Connectors: how a workflow works across your business systems shows how a connection is chosen and what it may change.
The two weeks, for one invented team.
Illustrative example with invented data. The billing team at an invented 55-person commercial law firm: a billing manager, two billing coordinators, and the firm administrator as sponsor. Days are approximate, counted in working days from the first interview.
| Days | What happens | The team’s part |
|---|---|---|
| 1 to 3 | Interviews. The two coordinators and the billing manager walk us through the last few times each job happened: the monthly prebill review, the billing summary sent with each invoice, the check against a client’s billing guidelines, and write-down requests. We ask what the best of them looks for and where they stop and ask. | About an hour each, on real examples, plus short follow-up questions. |
| 3 to 5 | Procedures written. Four procedures in plain language. The two coordinators handle possible duplicate entries differently, so both approaches go side by side. | The billing manager reads each one, chooses the way the team will follow and signs it off. |
| 5 | The priority and the standard. The prebill review is chosen to build. Before any building, we write down with the billing manager what a good result must contain, and set aside hard cases the build never sees. | The billing manager agrees the standard. A coordinator gathers past prebills in the firm’s account. |
| 6 to 8 | Build. Fully Powered Studio builds the workflow from the agreed procedure, starting from the prebill exception review workflow template and working with invented examples. It reads the billing system through the connection agreed in scoping, read only, and leaves its marks as a draft. | Answer questions as they come up. The firm’s IT lead confirms access. |
| 8 to 9 | Tests. A coordinator runs the held-back cases in the firm’s own workspace. Every result is marked right, wrong or uncertain. Each miss is shown, fixed and run again. | The billing manager marks every result and has the final say. |
| 10 | Handover. The coordinator runs the workflow on this month’s real prebills. Handover notes and the readout follow. | One real run, and an hour for the readout with the firm administrator. |
In this example every decision stays where it was. The billing attorney still decides each write-down, and the billing manager still releases every bill. The workflow prepares the marked prebill; a person checks it and decides.
The interviews are the heart of the sprint. We ask the people who do the work, and nobody is recorded, monitored or measured. Bring the work as your team does it today explains why nobody re-maps anything first, and What we test before we call an AI workflow ready shows the full test record.
What you hold at the end.
Copy this into the handover meeting and tick each line before you accept the sprint. Each item says what it is and what done looks like.
Handover checklist: 2-Week Workflow Sprint
- The procedures. Every procedure in the agreed scope, written in plain language. Done when: the owner has signed off each one and a new colleague could follow it.
- The workflow. The priority procedure built into your own ChatGPT, Claude, Copilot or Gemini workspace, connected to any systems agreed in scoping. Done when: the people it was built for can open and run it.
- The standard and the test record. What a good result must contain, and every test result as your expert marked it, misses included. Done when: each miss is fixed and rerun, or written down as a limit.
- The real-work run. Its user runs it on real work at handover. Done when: the person who decides has checked that output.
- Handover notes. How to run it, check it and change it. Done when: the owner knows where they live and who approves a change.
- The readout. What was captured, what the tests showed, what the work is for and the next workflow worth building. Done when: you have it in writing.
- Support. Ten business days after handover, in which delivery defects are corrected. Done when: you know where to report one and the end date is in your calendar.
What is included, and what is not.
- Included.Everything in the checklist above, plus the readiness checks and the interviews. Connecting the workflow to systems you already use is included where a connector exists, as agreed in scoping.
- Not included.A second built workflow or a second team. A new connector. Unattended or scheduled runs, which are agreed separately. Rollout beyond the people at handover.
- If the work changes shape.If the chosen workflow proves unsuitable, we agree the next step with you. New requirements are quoted before any work starts; correcting a delivery defect is part of the support window.
If your procedure is already written down and agreed, the 3-Day Workflow Sprint may be the quicker start: one documented procedure, built as evidence of the idea.
After the handover.
The other procedures earn their keep at once: a clearer handover, a better first week for a new hire, cover when someone is away. They are also the queue for what to build next. From working workflow to daily use takes the workflow from the people at handover to the whole team. When the support window ends, Keep it working keeps the workflow doing what was agreed, and further workflows and teams are scoped under Improve and expand. Your plan in Fully Powered Planner shows which team and which workflow come next.
All of it runs on the AI platform your team already pays for: ChatGPT, Claude, Copilot or Gemini. We build with invented examples and your people run real work in your own workspace; our security page explains how we handle your information. You set the pace, and your organization keeps control of how the work gets done.
Bring the team whose know-how lives in people’s heads, and the job you would build first.