How to Prepare Your Website Requirements Before Hiring a Developer

How to Brief a Developer and Get a Quote You Can Compare

A
Arijeniwa Oluwasina Oromidayo
Reviewed by Arijeniwa Oluwasina OromidayoOctober 2, 202611 min read

Ask three developers to price the same website and the numbers can be far apart, for example ₦180,000, ₦650,000 and ₦1.4 million. Nobody is necessarily cheating. A quote is only as accurate as the information it was built from, and when a developer has to guess, the price is a guess too.

Three things usually explain a gap like that. Each developer imagined a slightly different project because the brief was thin. Each included different things, since one counted content setup and testing and another did not. And they work differently: a freelancer, a small studio and a large agency really do charge different amounts for the same job. So the way to a better quote is not haggling. It is giving everyone the same clear information, so they quote the same thing.

This guide covers the whole preparation in the order you will need it: explaining your idea, writing a short requirements list, gathering what the developer will ask for, and then asking for a price you can compare.

Step 1: Explain the idea so a stranger can build it

Most people with an app or website idea can talk about it for an hour. The trouble starts when a developer asks, "So what exactly should it do?" and the hour of passion turns into a few vague sentences. You do not need technical words to close that gap. You need a few plain answers in the right order.

  • Start with the person and the problem, not the screens. "Small laundry shops in Lagos lose customers because nobody remembers who dropped what" tells a developer far more than "I want a laundry app." The first has a real person and a real problem in it. The second is a label.
  • Walk through one journey, one line per step. A customer opens the app and sees what? They choose a pickup time, and then? The shop gets a message, and then? Developers call this a user flow, but all you need is the steps.
  • Separate what must exist from what can wait. Almost every first idea is too big. For the laundry example, "customer books a pickup and the shop sees it" is a must. Loyalty points and live rider tracking can wait. This one list saves more money than anything else you can bring.
  • Show examples instead of describing them. Two or three screenshots of products you like, each with a note on what you like and what you do not. Pictures carry detail that words lose.
  • Sketch it on paper. Boxes for screens and arrows between them are enough. Roughness is fine. Drawing often exposes a gap, like "wait, how does the shop mark an order as ready?"
  • Be open about budget and deadline. Hiding your budget rarely lowers the quote. A developer who knows your range can suggest what fits inside it and tell you honestly if the idea does not. A real deadline, such as a launch event or a busy season, helps too.
  • Ask them to say it back. Two minutes of "tell me in your own words what we are building" catches a surprising number of misunderstandings, and shows you how well they listen.

You do not have to know the technology. Your job is to explain the problem, the people and the steps. Theirs is to suggest how to build it. A developer who makes you feel foolish for not knowing a term is showing you how the rest of the project will feel.

Step 2: Turn it into a short requirements list

"Just make it look professional" is not a requirement. It is a hope, and hopes are expensive to build because the developer has to guess, build, and then hear "this is not what I pictured." A requirements document answers one question: when this is finished, what must be true? It does not need to be long or technical, only specific.

A diagram showing the main sections of a simple website requirements document
  1. The goal, in one sentence. "Get more people in Abuja to book our dental clinic online" is a goal. "Have a nice website" is not. When two options compete, pick the one that serves the goal.
  2. Who will use it. Mostly phones? Slow data? Which languages: English, Hausa, Yoruba, Igbo, Pidgin? This changes real decisions, such as how heavy pages can be.
  3. The pages, each with one line on what it must do. "Services: shows the five treatments with price and a Book button." This list is the quickest way to see the real size of the project.
  4. The features, ranked as must have (cannot launch without it), should have (important, but can wait for a first release) and later. Online booking is a must, a newsletter a should, a blog later. This ranking is what lets a developer offer a smaller, cheaper first version.
  5. How it should behave, as "when this happens, that should happen." When a customer books, they get an SMS. When they pay, you get an email. When a phone number is wrong, the form says so. This is where a lot of hidden work lives, and why "simple" projects turn out bigger.
  6. Who manages it after launch. Can you edit prices yourself? Can staff add posts? Do different people need different logins? An admin area is real work and is often missing from the first quote.
  7. Content and design. Who writes the text and supplies the photos, and by when? Add three example sites you like, plus brand colours and fonts. To get a "premium" or "friendly" feel, show examples instead of using the words.
  8. Connections to other services: payment gateway, WhatsApp, SMS, Google Maps, a booking calendar, accounting tools. Each adds work and some have their own fees.
  9. Rules for the whole site: loads fast on a weak connection, keeps customer details safe, works on common browsers, easy for a non-technical person to update.
  10. Budget, deadline and what is not included. A short "Not included in this project" list prevents the most common argument in web projects, which is "I thought that was included." Typical entries: writing the content, product photography, ongoing marketing, a mobile app.

The document will change. That is normal. Just agree that changes go through a short written step, so everyone knows what each one costs.

Step 3: Gather the starter pack

The most common reason a website launches weeks late is not a slow developer. It is a developer waiting for the client. Put everything in one folder and share it at once, not in twelve WhatsApp messages over three weeks. A developer who has everything on day one can work in a straight line, and you pay for every stop in a stop-and-start project.

  • The brief. Half a page of clear sentences beats five pages of vague ones.
  • Brand materials: original logo files (not a screenshot from WhatsApp), brand colours and fonts. If you have no logo yet, say so, because designing one is a separate job.
  • Real content. Developers can build the container, but they cannot invent your business. Prepare your text, prices, contact details, opening hours and photos. A site full of "Lorem ipsum" and stock photos often stays that way for months after launch.
  • Examples you like and dislike, with one sentence each.
  • Access to anything that already exists: an old website, domain, hosting, Google Business Profile, social pages, and who holds each login. Share access to accounts you keep in your own name rather than your main password.
  • Documents for integrations. Payment companies usually verify your business before you can go live, which can take days and needs registration or identity documents. The same goes for a WhatsApp Business account, an SMS sender name or a settlement bank account. Start verification early, because it runs in parallel with the build and is a common source of last-minute delay.
  • One named decision-maker. When three people give three opinions on the same page, nothing moves. One person approves, others advise.
  • A communication rhythm: one channel, one weekly check-in, agreed reply times.

Step 4: Ask for a quote you can compare

Send the same written brief to every developer you approach. Then ask for these things, in this order:

  • A breakdown, not one number. Design, building, content setup, payment connection, testing, training, hosting and support after launch. When two quotes are far apart, the breakdown shows why. Maybe one included the admin area and the other forgot it.
  • The assumptions behind the price. "Assumes you provide all text and photos," "up to two rounds of changes," "one payment gateway." Every quote rests on assumptions, written or not, and most later arguments come from one nobody said aloud.
  • What is not included. Domain, hosting, writing the content, product photos, bug fixes after launch, changes after approval. A fair quote lists these without being pushed. A suspiciously cheap quote often leaves most of them out.
  • Fixed price or pay-as-you-go? In a fixed-price quote you agree one total for a defined list of work. That suits small, clear jobs. The developer carries the risk, so they usually add a margin, and any change costs extra. In a time-based arrangement you pay for hours or days actually worked. That suits projects still taking shape, but you need a ceiling and regular progress reports. Neither makes a poor estimate better; they only decide who pays when the estimate is wrong. Many careful clients pay for a short planning phase first and fix the price for the build once the plan is clear.
  • How changes are handled. You will change your mind. The healthy process: you describe the change, the developer states cost and time, and you approve in writing before work starts.
  • Payments tied to progress. A deposit to start, a payment when a working first version is shown, and the balance when everything is delivered and checked. Be wary of anyone who wants the whole amount before any work is visible.

What realistic numbers look like in Nigeria

Prices move with the exchange rate, so treat these as a sense-check and not a price list. At roughly ₦1,330 to the dollar (check the current rate when you read this): a simple template-based business site often lands between ₦150,000 and ₦500,000 (about $115 to $375). A custom-designed business site is more like ₦500,000 to ₦2,000,000 ($375 to $1,500). An online shop or web app starts around ₦400,000 ($300) for a basic template-based store and climbs well past ₦3,000,000 ($2,250) when built from scratch. Our guide to what a website costs in Nigeria goes into more detail. A quote far outside these ranges is a reason to ask questions, not to panic. Also keep a cushion of ten to twenty percent aside for changes. That is a rule of thumb, not a law, but it is far better to have it and not need it.

Warning signs in a quote

  • A price with no questions asked. If someone quotes in five minutes without asking what you need, the number is made up.
  • "Unlimited" anything. Nobody delivers unlimited revisions or pages for a fixed price, so something will give.
  • No written scope. If it is not on paper, it is not part of the deal.
  • Pressure to pay today for a "special offer."

A worked example: a requirements list in under a page

Illustrative example: the people, businesses and numbers in this section are made up to show how this works. They are not real clients or real results.

A tailor in Ibadan writes this: Goal: let customers see my styles and request a fitting. Users: women aged 25 to 45, mostly on phones. Pages: Home, Styles (gallery), Prices, Book a Fitting, Contact. Must have: gallery, and a booking form that sends me an SMS. Should have: a WhatsApp button. Later: online payment. Content: I will supply all photos and text by the end of week two. Admin: I want to edit the gallery myself. Not included: logo design and photography. Budget and launch date: written here. That is about one page, and any developer can quote from it.

Keep reading

With a brief in hand, you are ready to compare people. Read how to hire a web developer in Nigeria without getting burned to check them out, and what you should own after paying a developer before you sign. If you would like our quote, our quote builder is a gentle place to start, and you should ask us, as you would anyone, for the breakdown, the assumptions and the exclusions.

A
Arijeniwa Oluwasina Oromidayo
Co-Founder

Software engineer with over 9 years of experience in software development and digital technology. B.Sc. in Industrial Chemistry from Adekunle Ajasin University. Has worked across web development, mobile applications, e-commerce platforms, VTU and fintech solutions, API integrations and custom software.

Reviewed by Arijeniwa Oluwasina Oromidayo, Co-Founder

Comments

No comments yet. Be the first to share your thoughts.

Leave a comment

Comments are reviewed before they appear. Links are not allowed.

Related Articles