Give one workflow an owner and a finish line
A useful implementation plan tells you what will change, who can approve it, what data it can use, and how you will know the work is acceptable.
This fictional plan covers one capture-to-proposal handoff: prepare a source-linked pursuit brief and a response outline for human review. It illustrates how to scope the work; it is not a delivered project or a commitment to the hours and costs below.
One workflow, with explicit limits
- Input
- One public or approved solicitation, a synthetic capability record, and a list of questions supplied by the capture owner.
- Work
- Select the relevant source passages; assemble a pursuit brief; map requirements to a response outline; route unresolved claims to their owners.
- Output
- A review packet with source references, open questions, an owner for each gap, and an accept/rework decision.
- Outside the example scope
- Automatic bid submission, contract interpretation, production integrations, historical data cleanup, customer communications, and certification or compliance attestation.
Assign the decisions before building
| Owner | Decision and evidence |
|---|---|
| Capture owner | Selects the pursuit, defines fit, and signs the pursue/hold/pass decision. |
| Proposal owner | Approves the response outline and checks every material claim against a source. |
| Data / environment owner | Approves records, users, runtime location, model endpoint, retention, and permitted export. |
| Implementation lead | Builds the bounded workflow, records defects, and demonstrates acceptance tests. |
| Budget owner | Approves the fixed scope and spending limit before paid work starts. |
Keep the data boundary testable
For this example, use only the provided synthetic packet. Before a real implementation, record the source systems, approved users, storage location, inference provider, logs, retention, and export path. Approve any external service before it receives data.
Sequence work around acceptance
This implementation plan sits inside Deliver.
Agree the test packet
Approve inputs, owners, permissions, outputs, and a spending cap. Start only when the required access exists.
Make the handoff inspectable
Record source passages, missing information, and review decisions. Keep manual transfer explicit where an integration is unproven.
Run the failure cases too
Reject an unsupported claim; deny an unauthorized read; retry without creating a second review item. The owner records acceptance or rework.
Acceptance requires all three fictional requirements to be represented, every factual response claim to cite an approved source, and every unresolved item to remain visibly unresolved. The proposal owner must be able to reject the packet. Export must preserve its source references and review status.
Define the stop and recovery decision
Pause if data leaves the approved route, a required owner is unavailable, acceptance fails, or the spending cap is reached. The implementation lead returns work to the agreed manual process, preserves the review packet and logs, and asks the responsible owner to authorize a restart. Test the rollback procedure before enabling the workflow.
Show the operating assumptions
The following numbers are deliberately illustrative planning inputs, not Cabrillo prices, measured savings, or vendor quotes. Replace each with observed usage and an agreed rate before authorizing work.
| Input | Assumption | Calculated amount |
|---|---|---|
| Human review | 20 packets × 30 minutes × $100/hour | $1,000 / month |
| Model / compute usage | 20 packets × $2 usage allowance | $40 / month |
| Environment allocation | $100 assumed monthly allocation | $100 / month |
| Illustrated subtotal | Review + usage + environment | $1,140 / month |
The subtotal excludes implementation, software subscriptions, support, security operations, storage growth, taxes, and rework. Capture those costs separately. Track actual review time, rejected packets, usage, and support effort before making an economics claim.
Download the blank implementation scope worksheet
Start with the problem you need to solve
A free, 25-minute founder conversation helps clarify fit and the next step. A detailed implementation plan belongs in separately scoped work.
AI Integration Assessment: $12,500, fixed scope, 4–6 calendar weeks. Credits in full against an implementation engagement. The conversation is free; it does not purchase the assessment.