Package one workflow as an offer

01 / 05

Name the work that gets stuck

Start with a concrete action: summarising enquiries, producing a weekly report or preparing records. Describe who does it now, how often and where it fails. Choose something with an available sample input. “We automate your company” does not define a system you can build.

YOUR ACTIONDescribe the current workflow in five lines, including owner and recurring bottleneck.

02 / 05

Make delivery tangible

Name the input and output. One example is a daily draft summary of enquiries with missing fields flagged. Record what the client supplies and who reviews the result. A system sold as an internal summary should not contact customers as an extra implied action.

YOUR ACTIONSpecify source, input format, output format, frequency and owner.

03 / 05

Draw the boundary

Put included work, exclusions and dependencies side by side. An additional data source or language may be a change request. Explain how it is handled. Name recurring operational work after delivery, such as responding to failures, and separate maintenance from new functionality.

YOUR ACTIONWrite three boundaries and one example change request.

04 / 05

Agree on the test

Use a small set of representative cases, including a missing field and a duplicate enquiry. Agree how the system should handle them before building. Use your own measurements for time or revenue. This card deliberately contains no default price or guaranteed revenue claim.

YOUR ACTIONCreate a table of test input, expected result, evidence and reviewer.

05 / 05

Prove one complete cycle

Run a sample from input to reviewed output and keep the result with the offer card. Agree what happens on failure and who takes over. Then describe the promise precisely. Do not present a demo as a client case or use results you have not measured.

YOUR ACTIONDone when someone else can explain the deliverable, exclusions and acceptance test.

Your worksheet

# One-page offer
Customer: [one business type or role]
Process: [recurring task]
Problem: [observable error or delay]
Input: [what the customer must supply]
Output: [one tangible result]
Included: [bounded work]
Excluded: [scope boundary]
Human approval: [who decides what?]

| Acceptance case | Test input | Expected output | Evidence |
| Normal | [example] | [result] | [file] |
| Missing input | [example] | [report/stop] | [log] |
| Exception | [example] | [human handoff] | [log] |

Handoff: [what does the customer receive?]
Maintenance: [who does what and when?]
Discussed fee: [proposal, no invented benchmark]
First trial cycle: [date and actual result]

STARTER

Make it concrete.

Help me scope one workflow as an offer using my current process and sample input. Write an offer card with problem, owner, input, output, included work, exclusions, dependencies, test cases and failure handoff. Flag missing decisions. Invent no prices, savings or evidence.

Download worksheet ↓

Sources and further reading

The AI Operator · M4.0.2, M4.A.1, M4.D.1, M4.D.2, M3.H.2