Build something new with the right developer
Building something new means a developer takes your idea from first sketch to a live product. You prepare a short brief, agree on milestones, and pay each one only when you approve the result.
Last updated:
Who this is for
This help type fits you if you have an idea for apps, SaaS, websites and games and nothing built yet. You might be a founder with a first product idea, a business owner who wants a tool for the team, or a creator with a game concept. You do not need to write code or know the right technology. You need to know what problem you want to solve and for whom.
- You have an idea and a rough picture of the main screens, but no developer yet.
- You tried a no-code tool and hit its limits, and now you want a fresh start in real code.
- You want a first version to test with real users, often called an MVP.
- You are not sure about the platform and want a developer to help you choose.
What to prepare
A good brief makes proposals easier to compare. It does not have to be long. The project brief guide and the project brief tool walk you through it.
A short brief covers
- The goal
- What should the product do, and what does success look like in the first months?
- The users
- Who uses it, and what is the one thing they must be able to do?
- Must have and later
- A short list of features for version one, and a separate list for after launch.
- Examples
- Two or three products you like, and what you like about them.
- Constraints
- Your timeline, your budget range and any accounts or tools you already use.
How it runs in milestones
ErdiBuilds splits work into milestones. Each milestone is funded before work starts and runs 1, 2, 3, 4, 6 or 8 weeks. Milestones are from 50 to 2,000 each in your project currency. The developer delivers, you review, and the funds are released after your approval. Unless both sides agree otherwise in writing on the platform, the rights to the result of a milestone pass to the client once that milestone is paid in full.
Here is an example plan for a small first version. Your own plan will look different, and the developer should adjust it after a short conversation. The milestone planner helps you sketch your own.
| Topic | What you get | Example timing |
|---|---|---|
| Phase 1: Plan and design | Clickable screens, a feature list and a technology choice you understand | One milestone, for example 1 to 2 weeks |
| Phase 2: Core build | Sign up, login and the one main feature working end to end | Two to three milestones, for example 4 to 8 weeks |
| Phase 3: Finish and test | Missing screens, error handling and a round of testing with you | One milestone, for example 2 weeks |
| Phase 4: Launch | Live version, store or hosting setup and a handover of access | One milestone, for example 1 to 2 weeks |
Phase 1: Plan and design
- What you get
- Clickable screens, a feature list and a technology choice you understand
- Example timing
- One milestone, for example 1 to 2 weeks
Phase 2: Core build
- What you get
- Sign up, login and the one main feature working end to end
- Example timing
- Two to three milestones, for example 4 to 8 weeks
Phase 3: Finish and test
- What you get
- Missing screens, error handling and a round of testing with you
- Example timing
- One milestone, for example 2 weeks
Phase 4: Launch
- What you get
- Live version, store or hosting setup and a handover of access
- Example timing
- One milestone, for example 1 to 2 weeks
Example only: the weeks are for illustration. Developers set the length of each milestone in their proposal, and each real milestone runs 1, 2, 3, 4, 6 or 8 weeks, so longer phases are split into several milestones.
Questions to ask developers
- Which parts of my idea would you build first, and why?
- Which technology would you use, and what happens if I need a different developer later?
- Can you show me something similar you built, ideally one that is live?
- What do you need from me, and how quickly can you work if I answer within a day?
- How will I see progress between milestones?
- What is left out of version one on purpose?
Proposals arrive with a match score from 0 to 100 and plain reasons. A score of 80 or more gets a Top match badge. Use the score as a starting point, then read the proposal and ask your questions.
Choosing the kind of product
If you are unsure what to build, read the pages for mobile apps, web apps, SaaS or websites. Each explains what is involved. For timing, see how long it takes to build an app.
Frequently asked questions
Do I need technical knowledge to start?
No. You describe the problem, the users and the main features in plain language. A good developer explains the technical choices in a way you can follow, and you can ask for more detail at any time.
Link to this answerHow big should the first version be?
Small enough that you can test it with real users soon. Pick the one thing the product must do well and leave the rest for later. The guide on what an MVP is explains how to draw that line.
Link to this answerWill I own what gets built?
Unless both sides agree otherwise in writing on the platform, the rights to the result of a milestone pass to the client once that milestone is paid in full. You can also agree on other terms in writing on the platform. The guide on who owns the code explains more.
Link to this answerWhat if I change my mind during the project?
You can request changes when a milestone is delivered. Bigger changes are best agreed as a new milestone. If both sides want to stop, mutual cancellation is possible.
Link to this answerWhen do I pay?
Each milestone is funded before the work on it starts. The funds are released after you approve the delivery and a short holding period. If you do not respond, the milestone is approved automatically after 14 days.
Link to this answerRelated pages
- Build a mobile app with a developerPlan an iPhone and Android app: typical technologies, an example milestone plan, what to put in the brief and how to spot a developer who fits.
- Build a web app with an independent developerHow to plan a browser-based web app: common technologies, an example milestone plan, what to write in the brief and how to judge a developer.
- Build a SaaS with an independent developerPlan a SaaS product: accounts, subscriptions, technologies, an example milestone plan, what to write in the brief and how to pick a developer.
- What Is an MVP? A Plain Guide for FoundersAn MVP is the smallest version of a product that real users can try. Learn what it includes, what it leaves out and how to plan one.
- How to Write a Project Brief for a DeveloperA good project brief fits on one page: goal, users, must-have features, examples and limits. Here is what to include and a free tool to draft it.
- Free milestone planner for your projectTurn your project into an editable plan of milestones with lengths that fit the rules. Runs in your browser, stores nothing and estimates no prices.
- ErdiBuilds vs Upwork: fees and how it worksA factual look at fees, applying and payment on ErdiBuilds and Upwork, with sources and check dates, for people hiring an app or SaaS developer.