Concierge Pilot Service Blueprint
Map the founder’s manual work in a limited software pilot so participants understand what is delivered by people and what the product actually does.
Read this resource as Markdown
When to use this template
Use this when a founder helps deliver the outcome by hand to learn about a workflow. Record each handoff and intervention instead of making a manual service look like released automation.
Choose another approach when: The pilot would involve unapproved private data or access, cannot safely deliver the task, or is being presented as a fully autonomous public product.
Gather these inputs
- An agreed pilot task and the participant’s expected outcome.
- Actual product behavior, founder responsibilities and safe test inputs.
- Available support time and a person responsible for each handoff.
Copy and adapt the template
Edit the text below and copy it into your own document. Edits stay in this browser field and are not submitted or saved by this page.
Worked example
Illustrative example, not a Crany customer result. Replace every example detail with facts you can verify.
Fictional handoff pilot lets a builder enter sample notes. The tool stores the notes, while the founder manually groups confusing items before a review. The blueprint tells the participant about that manual grouping and records its duration. It does not market the result as automatic classification. If the founder cannot review that day, the agreed workflow pauses rather than silently pretending the task is complete. Repeated grouping decisions become product-learning questions, not evidence of an already released feature.
How to use it
- Describe the actual workflow and identify every manual intervention.
- Agree safe inputs, responsibilities and the behavior when assistance is unavailable.
- Log real effort and use repeated decisions to define the next product-learning question.
Check before using it
- The participant can distinguish product output from founder service.
- No manual step is advertised as released automation.
- Support effort is recorded even when the pilot outcome looks successful.
What to measure
Compare task completion, founder effort and repeated interventions within the agreed pilot scope. A successful assisted task does not establish unassisted usability, margins or scalable acquisition.
Research and sources
The primary founder accounts discuss hands-on work and reusable-product boundaries. This original service blueprint documents those tradeoffs; it is not a validated automation roadmap or an outcome guarantee.
- Paul Graham: Do Things That Do Not Scale — checked 2026-10-24. Historical founder essay on manual recruitment and learning from early users; not a universal acquisition benchmark.
- Y Combinator: The Delicate Balance of B2B Sales — checked 2026-10-24. Historical founder discussion of early customer feedback and the risk of one-off work; not legal guidance or a claim that pilots establish product-market fit.
About Crany
Crany is an AI marketing co-founder in development for software founders and vibe coders, designed to strategize, execute approved marketing and improve based on results. This free resource is usable independently of the product. Join the public waitlist.