Protocol
Deliver the small service before automating its machinery
An automation plan can hide an untested service.
Before you use it
- Use when
- You are building infrastructure for a benefit nobody has received yet.
Keep this limit in mind
- Manual success does not prove automation feasibility, scalable economics or broad demand. Do not promise support capacity you do not have.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Offer a clearly bounded manual pilot to a suitable user. Agree the output, limits and human involvement, then deliver the useful result. Record the effort and repeat demand before deciding which part deserves software.
Steps
- Choose a small outcome you can actually deliver without pretending the service is automated.
- Agree scope, access, confidentiality and any payment terms.
- Record delivery effort, revisions and whether the user would seek the service again.
An example
Before building a full corpus subscription system, a pilot delivers a small, source-checked selection for one recurring work problem.
Check your result
Did the user receive a useful outcome, and can you explain the cost of repeating the service?
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingDeliver the small service before automating its machinery
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Compare with this ideaSimulate the interaction without pretending the system exists
Evidence and sources
Graham describes manually serving early users as a way to learn before scaling a service.
Practitioner advice, not causal evidence that a concierge pilot predicts commercial success.
Do Things that Don’t Scale · Manual work discussion.
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.