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: €100 gives the Dreamer €85. 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.
- 01
Before you back
Read the story and the milestones. Check that the amounts add up and that each step has something concrete to prove. If anything is unclear, ask in chat first.
- 02
While the dream runs
Your backing is split across the milestones. When proof is posted you are notified and can release your share or ask for more. You can back anonymously.
- 03
If something goes wrong
If you do not release a milestone in time, the money still held for it and later steps comes back to you, minus the fee. You can report a dream or block a user at any time.
Example milestone plan
An example plan for a SaaS startup dream with a goal of €22,000. Backers fund the whole goal, but each milestone's money stays held until you post the proof and Backers release it.
Milestone 1
€4,400 · 20%
Define the customer workflow
Post a workflow map, interactive mockup and anonymised interview notes identifying the first problem the software addresses.
Milestone 2
€8,800 · 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
€4,400 · 20%
Test service reliability
Upload test summaries for account separation, error handling and recovery, with sensitive configuration details removed.
Milestone 4
€4,400 · 20%
Prepare ongoing operations
Post onboarding documentation, monitoring examples and a support plan showing how reported problems will be recorded and handled.
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.
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.
Can I see how my money was used?
Yes. Each milestone shows the Dreamer's proof, how much is held and how much is released. You only release money for milestones you have reviewed yourself.
Budget example
A typical cost split for a SaaS startup dream in Dublin, shown in EUR. Backers are charged the equivalent in US dollars.
Example goal
€22,000
- Core software development€13,200 · 60%
- Hosting and infrastructure€3,300 · 15%
- Reliability and security testing€2,200 · 10%
- Onboarding and support reserve€3,300 · 15%
What you receive
- Backers give
- €22,000
- Platform fee (15%)
- −€3,300
- You receive
- €18,700
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