Example milestone plan
An example plan for a SaaS startup dream with a goal of ₹2,400,000. Backers fund the whole goal, but each milestone's money stays held until you post the proof and Backers release it.
Milestone 1
₹480,000 · 20%
Define the customer workflow
Post a workflow map, interactive mockup and anonymised interview notes identifying the first problem the software addresses.
Milestone 2
₹960,000 · 40%
Develop the core service
Share a demo using sample accounts, a completed feature checklist and evidence that the main workflow runs from start to finish.
Milestone 3
₹480,000 · 20%
Test service reliability
Upload test summaries for account separation, error handling and recovery, with sensitive configuration details removed.
Milestone 4
₹480,000 · 20%
Prepare ongoing operations
Post onboarding documentation, monitoring examples and a support plan showing how reported problems will be recorded and handled.
- 01
Make every step provable
A milestone only works if a Backer can look at your proof and agree it is done. 'Buy equipment' is weak; 'equipment bought, receipt and photo posted' is strong.
- 02
Order by risk
Put the cheapest, fastest step first. Each released milestone proves you deliver and funds the next. Leave the biggest amount for the step where most of the work is already done.
- 03
Keep the amounts honest
Milestones must add up exactly to your goal. Price each step from real quotes, include tools and services, and split any step that is too big to prove in one go.
Risks to plan for
- R1
Too many customer requests
Early feedback can pull the service toward unrelated workflows. Define one initial use case and keep optional requests outside the core development milestone and budget.
- R2
Account boundaries fail
Errors in account separation can expose information between users. Budget dedicated boundary tests before onboarding and share results without revealing real account data.
- R3
Operating costs grow unseen
Usage-heavy features can raise hosting needs before revenue is established. Test representative workloads and keep an operating reserve tied to monitored resource use.
Budget example
A typical cost split for a SaaS startup dream in Bengaluru, shown in INR. Backers are charged the equivalent in US dollars.
Example goal
₹2,400,000
- Core software development₹1,440,000 · 60%
- Hosting and infrastructure₹360,000 · 15%
- Reliability and security testing₹240,000 · 10%
- Onboarding and support reserve₹360,000 · 15%
What you receive
- Backers give
- ₹2,400,000
- Platform fee (15%)
- −₹360,000
- You receive
- ₹2,040,000
How Backers are protected
14-day review per milestone
When proof is posted, each Backer has 14 days to release their share or ask for more. Money not released in time goes back to the Backer.
15% fee, deducted — never added
Backers pay exactly what they choose. The 15% fee comes out of each backing: ₹10,000 gives the Dreamer ₹8,500. The fee is kept if money is returned.
Gifts, not shares
Backings are gifts. No shares, equity, interest or repayment, and Dreamers keep full ownership. Nothing on cohero is an investment or a loan.
Questions and answers
Can I fund a SaaS service before it has paying customers?
Describe the workflow, available prototype and remaining development honestly. Use milestones for working software and reliability evidence rather than making paying customers or future subscription income the proof.
What should I show if the software handles private business data?
Demonstrate the workflow with synthetic records and separate test accounts. Share summaries of account-boundary and recovery tests, while removing credentials, customer identifiers and sensitive infrastructure details.
How many milestones should a SaaS startup dream have?
Three to six works for most dreams. Fewer gives Backers little to review; more than seven makes each step feel small. The example plan on this page uses four.
Ready when you are
Sign in or create an account to publish a dream or back the ones you believe in.
Sign in / Create account