The short answer
Start by writing the idea on one page, not by hiring anyone. Say who it is for, the one problem it solves and how it earns money. Then choose the form (a website, a web app that runs in the browser, or a phone app; the first two are usually the cheapest way to start), cut the feature list down to one core flow, test that flow with real people before anything is built, and only then ask for a fixed quote. You do not need a technical background for any of those five moves.
A first version, often called an MVP, is the smallest product that lets one kind of customer finish one job. Most of its cost sits in the features and rules behind the screens, not in the number of screens, so every feature you cut now is money saved later. The software project cost calculator gives you a range, and SaaS MVP development explains the route if your idea is a subscription product.
Move 1: write the idea on one page
If you have only an idea, this is the real answer to "where do I start?". Open a blank document and answer five questions in plain sentences. If you cannot answer them, the idea is not ready to quote, and no developer can fix that for you.
- Who is it for? One kind of person, described closely: "dispatch managers at small courier firms", not "everyone with a phone".
- What is the one problem? What do they do today, and what does it cost them in time, money or stress?
- How does it earn? A subscription, a fee per order, a commission or a one-off purchase. Pick one to begin with.
- What does a user do, start to finish? Three to six steps, written as sentences.
- What exists already? Name two or three alternatives, including a spreadsheet or a WhatsApp group, and say why people would switch.
How do I turn my idea into an app with no technical background?
You turn it into a short brief and let the developer handle the technical translation. Your job is to know the customer, the problem and the money. The developer's job is to turn that into screens, data and code. You never need to know what a database is to write a good brief. What you do need is to describe the steps a user takes, and only you can supply that.
Move 2: decide the form: website, web app or phone app
What is the difference between a website, a web app and a mobile app?
A website shows information and collects enquiries: pages, a contact form, perhaps bookings. A web app also runs in the browser, on a phone or a laptop, but people log in and do things: place orders, manage records, see their own data. A phone app is installed from the app store, can send push notifications and use the camera or location more smoothly, and has to be built, submitted and updated for iPhone and Android.
For most first ideas the cheapest start is a website or a web app: there is one build, no app store review, and a change can often go live the same day. Choose a phone app first only when the idea truly depends on the phone itself, for example constant location tracking, offline use where the signal is poor, or a camera-heavy flow. The table shows where our fixed quotes start for each form, in the currency of your region.
| Form | Our price, from | Best first use |
|---|---|---|
| Website | Explaining an offer and collecting enquiries | |
| Web app in the browser | Logins, orders, records and dashboards; often the best first version | |
| Phone app, one platform | Ideas that need the phone itself, aimed at iPhone or Android first | |
| Phone app, iPhone and Android | When you already know both audiences are essential |
If you are weighing the two phone routes, read Flutter vs React Native. If the choice is between a ready-made site and a bespoke one, custom vs template website helps.
Moves 3 and 4: cut to one flow, then test before you build
What should my first version include?
One core flow for one kind of user, from first tap to the moment they get what they came for. For a delivery idea that means: the customer places an order, the business sees it, the customer is told it is on the way. Add a login, a simple admin view for you, and a way to get paid if money is part of the idea. Everything else goes on a "later" list: ratings, chat, coupons, extra languages, a second type of user, reports.
A useful rule: if the product still works without a feature, it is not in version one. Our pages on MVP development in East Africa and SaaS MVP development show what a first version usually contains and how we scope it.
How do I test an idea before building anything?
In two sentences: talk to at least ten people who match your "who is it for" line, and ask what they do today and what it costs them, not whether they like your idea. Then try to get a small commitment before any code exists, such as a deposit, a signed list of interested users, or a manual version run through WhatsApp and a spreadsheet.
The manual version is the honest test. If people will not use the clumsy version, a polished app rarely changes their minds.
Move 5: money, time and a fixed quote
How much money and time should I plan for a first version?
Plan around the feature list, not the screen count. A screen that only displays information is cheap. A single feature such as taking a payment, sending a notification, handling a refund or showing two kinds of user different data adds rules, edge cases and testing behind the screen. That is where most of the money goes, which is why cutting features is the strongest budget lever you have.
For the cost shape in your market, see app development cost in Uganda and app development cost in Kenya. For the time shape, see how long it takes to build a website or app. As a rule, a focused first version takes weeks to a few months, a wide one takes much longer, and schedules slip most often because the brief changes mid-build. Also budget for running costs after launch (hosting, store accounts, fixes) and keep something back to change the product once real users touch it.
What do I get when I ask for a fixed quote?
A written scope, a price and a timeline, agreed before work starts. We use a 50/25/25 payment plan, and you own the code and the data. Growth Informer Software Services is a US-based company with remote teams, senior engineers and a team that stays, so there is a team to call when the product needs changing. Our team in Kampala works East Africa Time (UTC+3), which overlaps the UK and European working day and the start of the US East Coast day, and a US team member joins client video calls. We have 37 live website and app builds on our portfolio, and our app development page for Uganda shows how we work with founders there. Freelancer vs agency sets out when each makes sense.
What to send a developer
- Your one-page brief: who it is for, the one problem, how it earns.
- The one core flow, in three to six steps.
- Two or three products you like, with a line on what you like about each.
- Your "later" list, so we know what not to build yet.
- A budget range, and the date you need it by and why.
- Who approves decisions, and how quickly they can reply.
- Anything that already exists: logo, brand colours, domain, payment accounts, sample data.
The same habit helps with any build; what to give your web designer covers the website version of this list.
When we are not the right fit
If you have not spoken to a single customer, spend a month on that first, because no quote fixes a missing market. If a ready-made tool or a template site would do the job, use it. If you want a partner who shares the risk for equity rather than a team on a fixed fee, read technical cofounder or software agency. And if your whole product is information and a contact form, you need a website, not an app.
A worked example from Nairobi
This is an illustration, not a client. Imagine Wanjiru, a founder in Nairobi with a small budget and no technical background. Her idea is office lunches: small restaurants near her business district sell lunch, and office managers order by phone call and WhatsApp, then chase the restaurant when an item is wrong. The same shape works for a founder in Kampala.
- One page: for office managers ordering for teams of five to fifteen, the problem is calling around and chasing mistakes, and the app earns a small fee per order from the restaurant.
- Form: a web app that works in any phone browser, shared as a link on WhatsApp. No app store, one build.
- Core flow: the manager picks a restaurant, chooses items, pays by mobile money (a payment from a phone wallet, widely used in Kenya and Uganda) or marks cash on delivery, and the restaurant sees the order on one simple screen. Ratings, loyalty points, rider tracking and a second city go on the later list.
- Test: for two weeks she takes orders by WhatsApp for two restaurants and records them in a spreadsheet. She learns which orders repeat, whether managers will pay by mobile money and how many orders a day are realistic. If it fails, she has spent almost nothing.
- Quote: she checks a range in the cost calculator, then sends her brief and asks for a fixed quote for the core flow only, with mobile money payment priced as its own line so she can decide. The guide to accepting mobile money online explains what that line involves.
Notice what she did not do: she did not start with a phone app, and she did not pay for features before the manual test showed repeat orders. We build and run our own products, including Karibu and Moyo Pay, so we have started from a blank page ourselves.
What do I do this month if I only have an idea?
- Week 1: write the one-page brief and the three to six steps of the core flow.
- Week 2: talk to ten people who match your "who is it for" line.
- Week 3: run a manual version or collect small commitments, then cut the feature list to one flow.
- Week 4: send the brief to two or three teams and compare the scope in each fixed quote, not only the price.
When you are ready, send us the brief on WhatsApp at +256 702 946 946 or through the quote form on this page.
Frequently asked questions
I have an app idea. Where do I start?
Write it on one page: who it is for, the one problem it solves and how it earns. Then decide the form (website, web app or phone app), cut the features to one core flow, test it with real people, and ask for a fixed quote.
What is the difference between a website, a web app and a mobile app?
A website shows information and collects enquiries. A web app runs in the browser but lets people log in and do things, like place orders. A phone app is installed from the app store and is built for iPhone and Android. A website or web app is usually the cheapest way to start.
What should my first version include?
One core flow for one kind of user, a login, a simple admin view and payment if money is part of the idea. Ratings, chat, coupons, extra languages and reports can wait until real users ask for them.
How much will a first version cost?
Our fixed quote for a phone app on one platform starts from . The final figure depends mostly on how many features and rules the first version needs, so use the software project cost calculator for a range, then ask for a fixed quote.
What do I do this month if I only have an idea?
Week one, write the one-page brief. Week two, talk to ten likely customers. Week three, run a manual version and cut the list to one flow. Week four, send the brief to two or three teams and compare the scope in their fixed quotes.