Startup Evaluation Example: Assumptions Before Conclusions

Example evaluation: CoachSlot

This is a fictional editorial example of the analysis structure, not a customer result or an AI-generated score. The idea is a scheduling service for independent fitness coaches charging a proposed $19 per month.

Known inputs

The proposed user is an independent coach currently using messages and spreadsheets. The intended product handles availability, booking, and rescheduling. These statements describe the proposal, not external market evidence.

Demand — unverified

Scheduling may create administration, but no interviews, observation records, paid pilots, or revenue have been supplied. Do not classify demand as validated. Observe current workflows and test willingness to pay.

Customer — defined, still to be tested

Coaches with 10–30 recurring clients are a practical first segment. Check whether these coaches experience the problem and have authority to buy.

Competition — research required

General calendar products and specialist coaching software may already solve the job. Build a comparison based on verified current features before claiming differentiation.

Market — not yet sized

A price alone is insufficient. Count the relevant reachable buyers, document the source, and distinguish annual revenue potential from a sales forecast.

Execution — narrow the first release

Build availability, booking, confirmation, and cancellation first. Defer workout plans and billing clients. Test double booking, time zones, and notification failure.

Next experiment

Observe five coaches, then offer a small paid pilot. Set the decision threshold in advance. Record negative responses as well as positive ones. Repeat usage and payment are stronger evidence than a hypothetical survey answer.

Decision

Proceed to inexpensive discovery and a scoped pilot, not a broad launch. The useful output is a set of testable assumptions. A more polished description alone does not reduce real-world risk.