You send the same message to three developers, “I need an app like Jumia, how much will it cost,” and you get three replies that make no sense together. One says ₦1.5 million, another says ₦7 million, and the third says ₦20 million and six months. None of them is necessarily lying. They are pricing three different apps in their heads, because your message left every important question unanswered. A proper app brief fixes that. It is a short document, usually two to four pages, that describes exactly what you want built, who it is for, and what success looks like, so every developer quotes on the same thing and you can compare those quotes fairly.
Why vague ideas produce wild quotes
Developers price risk, not just features. When a developer cannot tell what you want, they protect themselves in one of two ways. Some add a large safety margin in case your “simple app” has hidden work. Others quote low to win the job, planning to charge extra for every feature you mention later. Both outcomes hurt you.
Every feature has hidden layers. Take “users can sign up.” Does that mean email and password, phone number with an OTP code sent by SMS, Google sign in, or all three? One developer assumes the simplest version, another assumes the full version, and their quotes differ by hundreds of thousands of naira for that one line alone. Multiply that across thirty features and you understand the gap between ₦1.5 million and ₦20 million.
Timelines depend on clarity too. A developer who understands the work can tell you honestly whether it is six weeks or six months. A developer guessing at the work will promise whatever timeline you want to hear, then miss it, while the scope keeps growing in conversations that were never written down.
What a good brief actually contains
1. The problem in plain language. Start with one short paragraph on what your business does and what problem the app solves. For example, “We run a laundry service in Yaba with three riders. Customers order by WhatsApp, orders get lost, and riders cannot see their deliveries in one place. We need an app where customers place orders and track them, and riders see their assigned pickups.” That paragraph tells a developer more than ten voice notes of excitement about changing the world.
2. Who will use the app. List every type of user, because each type usually means a separate set of screens. A typical Nigerian service app has customers, the business admin, and sometimes riders, agents, or vendors. If vendors need their own dashboard to upload products and see their earnings, say so, because a whole user type appearing halfway through the project brings weeks of extra work.
3. A feature list, split in two. This is the heart of the brief. List your must have features first, the things the app cannot launch without, such as accounts, product or service listings, payments, order history, and notifications. Then list your nice to have features separately, things like live chat, loyalty points, or referral bonuses that could come in version two. Ask the developer to quote the two groups separately. That way, if the full price is above your budget, you can launch smaller without starting the conversation again.
4. How money moves. Payments change the cost and the timeline, so be specific. Will customers pay by card, bank transfer, USSD, or wallet balance? Will you use Paystack or Flutterwave, which most Nigerian developers know well, or do you need something else? If other people earn money inside the app, for example vendors or riders taking a percentage, state who gets what and when payouts happen. An app that holds money for other people is a serious build, and developers need to know that on day one, not month three.
5. What the app should look like. Name two or three apps whose look and feel you like, and say what you like about them. Simple sketches help too, even hand drawn screens photographed with your phone. Also state whether the developer is responsible for the logo, colours, and design, or whether you already have a brand guide, because design is real work and quotes differ sharply depending on who is doing it.
6. Platforms and devices. State whether you need Android, iPhone, or both, and whether you also need a web admin panel, which most businesses do. Roughly nine out of ten Nigerian smartphone users are on Android, but iPhone users are often your highest spending customers. Mention special needs too, such as working on low end phones or partly offline where network coverage is poor.
7. What you will provide, and when. Who provides the product photos, the written content, and the business documents needed for payment gateway approval? If the developer has to wait three weeks for your CAC certificate for Paystack verification, the timeline should reflect that. Name one contact person on your side who can answer questions and approve screens quickly.
8. Budget range and deadline, honestly stated. Many owners hide their budget, fearing the developer will simply charge whatever number they mention. In practice, a stated range saves everyone time. If your ceiling is ₦5 million, a developer can tell you which features fit instead of quoting ₦18 million of work you will never buy. For a frame, a solid freelancer built minimum viable product in Nigeria commonly lands between ₦2 million and ₦8 million, while agency builds often run from ₦8 million to ₦25 million and above. Give your real launch date too, and say whether it is fixed or flexible.
A simple brief template you can copy
Open a document and use these headings, Problem and Goal, Users, Must Have Features, Nice to Have Features, Payments, Design References, Platforms, What We Will Provide, Budget Range, Target Launch Date, and Questions for the Developer. Under each heading, write short sentences or a simple list. Keep the whole thing under four pages. A brief does not need big grammar or a graphic designer. It needs to be clear enough that a stranger can read it once and understand the job.
How to send the brief and compare the replies
Send the identical brief to three to five developers. Do not adjust the story for each person. Identical input is the only way to get quotes you can compare line by line. Give them a fair window, usually a few days to a week for a considered quote, and be suspicious of anyone who prices a serious app in ten minutes without asking a single question.
Ask for the quote in parts. Request separate figures for design, development, testing, and store submission, plus running costs such as servers, payment gateway fees, SMS for OTP codes, and app store charges. Apple charges a yearly developer fee and Google a one time fee, both in dollars, so ask who pays. Also ask what maintenance will cost after launch, because that figure is rarely in the headline quote.
Ask what is not included. The cheapest quote often wins by quietly excluding things the others included, like the admin panel, payment integration, or publishing the app under your own store accounts. Ask, “If I pay this amount, what exactly will I be holding at the end, and what will I still need to pay for?” Get the answer in writing.
Insist on owning everything. Your brief should state that the source code, the app store accounts, the payment gateway account, and the domain and server accounts will be in your name and your control. Projects in Nigeria have ended in painful disputes where a developer held the code hostage over a disagreement. A professional developer expects this clause.
Red flags a good brief reveals
A proper brief acts like a filter. Be cautious with a developer who ignores your document and quotes from a voice note instead, who refuses to break the price into parts, or who promises every feature at half the price of everyone else. A developer who replies with thoughtful questions, points out an expensive feature, and suggests a cheaper way to achieve the same result is showing you exactly the honesty you want during the build itself.
The bottom line
Accurate quotes are not about finding the one honest developer in Nigeria. They are about giving every developer the same clear picture of the job. Spend two or three days writing a proper brief, split your features into must have and nice to have, state your budget range and your payments plan, and demand itemised replies. You will get quotes that sit close together, make sense, and hold up during the build, and that is worth far more than the days you spent writing.
Recommended: Grow Your Business Online
- Facebook Ads Domination (for Business Owners) — learn to run profitable Facebook ads and get more customers ($21). Check it out
- Facebook Advertising In 60 Minutes — fast-track course to launch your first ads in an hour ($50). Check it out
- FAF Mastery System — Facebook ads plus sales funnels that turn clicks into customers ($15). Check it out
Disclosure: These are affiliate links. If you buy through them, I may earn a commission at no extra cost to you.

Leave a Reply