Customer says “do it for me”
Supports testing the service form, but only if the commitment and workload are recorded.
Variants & Pivots · legacy source VU-G01-V001-SS01-ST02
Compare reinterpretations without erasing the source mechanism.
The source permits product, service or platform forms, but the release needs one concrete test. These variants exist as decision alternatives; none is described as validated, superior or available now.
Venture state Future Concept / unvalidatedResource state release candidateScope DNA Star / FocusedCapital band $0–$1,000 planning boundary
Comparison
Three forms, three different proof burdens.
The service form is selected for the current prototype because it can expose workload, price response and customer objections with less built software/inventory. That is an editorial test-design choice, not a market conclusion.
| Variant | Concrete interpretation | First proof | Key break risk |
|---|---|---|---|
| Service · selected prototype | Bespoke micro-sprint for one sleep-adjacent brand promotion. | Paid pilot / refundable reservation from a narrow business audience. | Customization workload outruns price/capacity. |
| Productized kit | Claim-aware ad-to-landing-page templates + test workbook for sleep-adjacent brands. | Purchase or pre-order of one inspectable version. | Generic templates may not solve the actual customer job. |
| Platform workflow | Software workspace guiding claim screen, creative brief, landing prototype and evidence log. | Commitment to use/pay for a narrow workflow before full build. | Software build cost and integration complexity precede proof. |
Customer says “give me the system”
Could justify a kit test if the same objection repeats and prospects commit to the self-serve format.
Customer says “make this repeatable across campaigns”
Could motivate a platform workflow only after repeated process evidence shows software is solving a real bottleneck.