Example milestone plan
An example plan for a mobile app dream with a goal of €27,000. Backers pay you directly, funding the goal all at once or milestone by milestone as you post proof for each step.
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.
- 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 proven milestone proves you deliver and encourages Backers to fund 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
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.
Budget example
A typical cost split for a mobile app dream in Barcelona, shown in EUR. Backers pay you directly using your accepted payment methods.
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
- 0% platform commission
- −€4,050
- You receive
- €22,950
How Backers are protected
14-day review per milestone
When proof is posted, each Backer has 14 days to review the proof, ask for more info, and decide whether to keep supporting your next milestone.
0% commission — direct gifts, nothing taken
Backers pay exactly what they choose directly through your payment methods. cohero takes 0% commission on backings, so you keep what is sent. Any refunds or disputes are handled directly between you, the Backer and your payment provider.
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 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 many milestones should a mobile app 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.
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.
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