A useful startup goal connects a business outcome to evidence, capacity and a deadline. Start with what you need to learn or achieve, then choose a small number of milestones that show progress. Once the plan is underway, use our weekly milestone review template to diagnose delays and record changes.
Choose an outcome before choosing a number
Identify the next important business question. Do customers understand the offer? Can you deliver it at a sustainable cost? Will a buyer pay for it? A revenue target may be premature if these assumptions are untested.
Match the milestone to the stage of the business. Early research could produce documented customer interviews and a revised offer. A delivery pilot could produce an accepted service, actual labour hours and a cost comparison. A sales milestone could produce paid bookings. Each requires different evidence.
Estimate targets from your actual capacity
List the hours, skills, cash and dependencies needed to complete the work. Separate tasks you control from outcomes that depend on customers or suppliers. Do not set a target simply because another business achieved it.
For example, a founder with six hours available for research might plan four 30-minute interviews, allow two hours for arranging them and use the remaining two hours to analyse notes. This is an illustrative workload estimate, not a universal quota. It may need to change if recruitment takes longer or interviewees are unavailable.
Write a milestone that can be verified
Use these fields to turn an intention into a checkable plan:
| Field | Illustrative example |
|---|---|
| Outcome | Understand the main booking objections |
| Deliverable | Interview notes and a ranked list of recurring concerns |
| Owner | Founder |
| Deadline | End of the next research week |
| Completion evidence | Notes recorded and offer changes explained |
| Assumption | Suitable interviewees can be recruited within the available hours |
Keep a completion criterion distinct from a success criterion. Publishing a landing page completes a task. Generating qualified enquiries tests whether the page and offer are effective. Tracking only completed tasks can hide weak customer demand.
Sequence milestones around dependencies
Put prerequisite work first. Confirm the scope before asking suppliers to quote. Check how enquiries reach you before spending money to attract them. Verify that the service can be delivered before promising a launch date.
Limit the number of active milestones to what the team can realistically deliver. Assign an owner to each handoff and record the resource constraint. Where uncertainty is high, use a research or pilot milestone before a large commitment.
Define how you will review the plan
Agree the review date and what information will be available. Record the initial targets and assumptions so changes remain traceable. A missed milestone may reflect an execution problem, a dependency or a false assumption; the response should follow the evidence.
Set goals to guide decisions, not to create a promise of guaranteed growth. Customer demand, delivery costs and available resources can change. A useful plan makes these uncertainties visible and identifies the next piece of evidence needed before increasing the commitment.
