- 01
Start with one clear goal
Name the single outcome your dream should reach and the date. Backers swipe through many dreams, so your first line must say what will exist when you are done.
- 02
Turn the goal into proof points
Every milestone needs something you can show: a receipt, a photo, a certificate or a link. Put the cheapest, fastest one first, because early proof brings the next Backer.
- 03
Publish and keep people updated
Publish your dream with a monthly membership. Share it with your own circle first, answer questions in chat and post proof as soon as each step is done.
Example milestone plan
An example plan for a mobile app dream with a goal of €27,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,050 · 15%
Validate the core flow
Post an interactive screen prototype, a prioritised feature list and anonymised notes from guided usability sessions.
Milestone 2
€10,800 · 40%
Build the main features
Share a recorded walkthrough of a working app build, completed feature checks and a summary of remaining development tasks.
Milestone 3
€6,750 · 25%
Test across devices
Upload a device test matrix, anonymised crash reports and before-and-after evidence for the main issues resolved.
Milestone 4
€5,400 · 20%
Prepare the release build
Post release build screenshots, setup documentation and a maintenance checklist with credentials and private data removed.
Budget example
A typical cost split for a mobile app dream in Athens, shown in EUR. Backers are charged the equivalent in US dollars.
Example goal
€27,000
- App design and development€17,550 · 65%
- Hosting and service integrations€2,700 · 10%
- Device testing and quality checks€4,050 · 15%
- Release and maintenance reserve€2,700 · 10%
What you receive
- Backers give
- €27,000
- Platform fee (15%)
- −€4,050
- You receive
- €22,950
Risks to plan for
- R1
Feature scope keeps growing
Extra features can absorb development time before the core flow works. Lock the first build scope in the prototype milestone and keep optional ideas outside its budget.
- R2
Device-specific failures
A build that works on one phone may fail on another screen or operating system. Budget for a defined device test matrix and reserve time for fixes before release preparation.
- R3
External service changes
An app may depend on services with changing limits or interfaces. Identify those dependencies early and include integration checks and a fallback plan in the release work.
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.
Questions and answers
Do I need a finished app before creating a funding dream?
You can start with a clearly scoped prototype and development plan. Show which screens are interactive, which features still need code and how later milestones will provide working builds and device test evidence.
Can I share app progress without exposing user data?
Record a demonstration using invented accounts and sample content. Remove credentials from logs and screenshots, and use anonymised issue summaries so Backers can review the build without seeing real user records.
How long does it take to fund a mobile app dream?
It depends on the goal and how active you are. Dreams with a small first milestone, real photos and fast replies usually get their first Backers within days. Plan for weeks and keep posting progress.
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