Key takeaways
- Cost follows scope: the more the site must do, the more planning, building and testing it needs.
- Always separate one-off build costs from yearly or monthly running costs.
- Cheap and expensive quotes usually differ in what is left out, so compare inclusions, not totals.
- Ask who owns the domain, hosting and code before you pay anything.
Quick answer: why do website prices vary so much?
Because websites are not a single product. A one-page profile for a caterer and an online store with stock, payments and delivery zones are different jobs, even though both are called a website. Price follows the work involved and the risk the builder takes on.
Seven things drive nearly every quote: the purpose of the site, size, features, design, content, who does the work, and what happens after launch. Understanding them lets you ask for exactly what you need and spot a quote that is missing something important.
This guide does not give prices, because honest prices depend on your requirements. What it gives you is the checklist to get a clear, comparable written quote from anyone.
Driver 1: what is the website for?
Start with the job, not the page count. Typical purposes, from simplest to most demanding:
- Online brochure. Tells people who you are, what you offer and how to reach you.
- Lead generation. Same as above plus forms, tracking and pages built to bring enquiries.
- Booking or appointments. Calendars, availability, reminders and confirmations.
- Online store. Product pages, cart, checkout, payments, stock, delivery and order emails.
- Portal or system. Logins for customers, students, staff or members, with records behind them.
Each step adds logic that must be designed, built, tested and secured. A brochure can be mostly design and writing. A store or portal is closer to building software.
Driver 2: size and structure
Number of pages matters, but structure matters more. Ten similar service pages built from one template are easy. Ten pages that each need a different layout are not.
Think about:
- How many unique page types you need (home, service, product, blog, team, gallery).
- How many products or listings must be entered, and who will enter them.
- Whether you need more than one language or more than one location.
- How the menu and navigation should work so visitors reach things in two taps.
Planning the structure before design starts saves money. Changing a menu after everything is built costs more than deciding it first.
Driver 3: features and integrations
Features are usually the largest cost jump. Some common ones, and why they matter:
- Payments. Connecting a gateway, testing success and failure paths, handling refunds and recording orders correctly takes real care.
- User accounts. Registration, login, password reset and permissions all need security work.
- Bookings and calendars. Time zones are easy, double-booking rules are not.
- Stock and customer records. The site must talk to your inventory or CRM so numbers agree.
- Search, filters and comparison. Helpful for large catalogues, and not trivial to do well.
- Email, SMS or WhatsApp notifications. Often involve third-party services with their own accounts and limits.
- Admin dashboards and reports. What you can see and change without calling the developer.
- Custom or imported data. Moving products or members from spreadsheets or an old site.
List every feature as a must-have, nice-to-have or later. Many projects save a lot by launching with the must-haves and adding the rest when there is revenue.
Driver 4: design and user experience
Design ranges from adapting a ready template to creating a custom look and layout around your brand. Neither is wrong, but they cost different amounts of time.
- Template-based. Quicker. Fine for simple needs, with limits on how unique it looks and how well it fits unusual requirements.
- Custom design. Layouts, spacing, icons and flows made for your business. Takes more design time and more revisions.
- Brand work. If you do not yet have a logo, colours or photography, those are extra jobs. Ask whether they are included.
- Phone-first design. A site that is easy to use on a small screen with slow data takes deliberate effort. Insist on it.
- Revisions. Ask how many rounds of changes are included and how extra rounds are handled.
Driver 5: content, photos and text
This is the most overlooked cost, and the most common cause of delays. A site is only as good as its words and pictures.
- Who writes the text? If you supply it, you need time. If the builder writes it, ask whether that is in the quote.
- Photography. Real photos of your work, team and premises beat stock images. Budget for a shoot, or take clear photos on a good phone in daylight.
- Product entry. Titles, descriptions, sizes and prices for each item take longer than most owners expect.
- Search visibility basics. Page titles, descriptions and sensible headings should be part of the build.
Projects stall when the builder is waiting for content from the client. Agree a content deadline in writing.
Driver 6: who builds it, and how
You will meet three broad options, each with trade-offs.
- Do it yourself on a builder. Cheapest upfront, costs your time, and can be limiting when you need custom behaviour.
- Freelancer. Flexible and often good value. Check that they work consistently, can support you later and will hand over everything.
- Company or agency. Usually a team with design, development and support, and a clearer process. A bigger organisation also means more overhead.
Also ask about the technology. A site made from a heavy page-builder with many plugins has different long-term costs from a site written for your needs. Neither is automatically better, but you should know which you are buying, and whether you can leave without starting again.
Driver 7: running costs after launch
A website is not paid for once and forgotten. Ask for these to be listed separately.
- Domain name. Renewed yearly, and the renewal rate can differ from the first-year offer.
- Hosting. Monthly or yearly, depending on traffic, storage and how important speed and uptime are.
- SSL certificate. The padlock that encrypts traffic. Many hosts include it; confirm it.
- Backups. Automatic copies stored away from the server. Ask how often and who restores them.
- Updates and security. Software needs updating and monitoring. Someone has to do it.
- Paid tools. Email services, SMS credits, premium plugins, payment gateway charges, which are per transaction.
- Edits and growth. Whether small changes are included in a maintenance plan or billed each time.
Budget for the year, not only for launch day.
How do you compare website quotes properly?
Never compare totals first. Compare what is inside.
- Give every builder the same written brief. Purpose, pages, features, who supplies content, deadline. Otherwise each quote answers a different question.
- Ask for an itemised quote. Design, development, content, integrations, testing, training, domain, hosting, first-year support.
- Check the deliverables. Number of pages, number of revisions, mobile design, speed optimisation, basic search setup, contact forms, analytics.
- Clarify ownership. The domain and hosting accounts should be in your name. Ask whether you get the files and, for custom work, the source code.
- Understand the payment schedule. A common pattern is a deposit, a mid-project payment and a final payment on delivery. Avoid paying everything upfront.
- Ask about timelines and what delays them. Usually late content or slow feedback.
- Ask what is not included. The answer is often the most useful part of the quote.
- Check real work. Open their previous sites on your phone. Ask to speak to a client if possible.
- Ask about support. After launch, who do you call, how fast do they respond and is it free for a period?
Be cautious of quotes that are far below the rest with no explanation, that promise first place on Google, or that avoid putting anything in writing.
How can you reduce the cost without hurting quality?
- Launch with the essentials and add features in phases.
- Prepare your text, logo and photos before the project starts.
- Give consolidated feedback in one list per round, not message by message.
- Choose a smaller number of well-designed pages over many thin ones.
- Learn to edit simple things yourself, such as text and photos, if the system allows it.
- Pay for the right foundations: speed, security, and a structure that can grow. Fixing those later is more expensive.
Frequently asked questions
Why do some Nigerian designers charge much less than others?
Usually because the scope, experience or aftercare is different. A low quote may leave out content, mobile testing, security, backups or support, or may use a basic template with limited customisation. Ask for the quote in writing and compare line by line before assuming the cheaper one is the better deal.
Should I pay the full amount upfront?
It is safer to pay in stages tied to progress, such as a deposit to start, a payment when the design is approved and a final payment before handover or launch. Make sure the agreement is written, and that you hold the login to your domain and hosting before the last payment.
Is the domain name and hosting included in the quote?
Not always. Some quotes include the first year, some do not include them at all. Ask which account they are registered under, the renewal date and the renewal cost, so you do not discover later that the domain belongs to your designer or that renewal is due.
Is a website builder cheaper than a custom website?
Often the first year is cheaper and faster, and for simple sites it is a sensible choice. Over time costs include monthly plans, paid add-ons and the difficulty of moving away. Custom sites cost more to build but may suit complex needs better. Match the choice to your goals.
Do I have to pay every month after the website is built?
You will usually pay for hosting and domain renewals, either yearly or monthly. Maintenance, updates and support may be separate or part of a plan. Ask for the running costs in writing so you can budget, and ask what happens if you stop paying for support.
How long does it take to build a website?
A small information site can take a few weeks if content is ready, while stores, portals and custom features take longer. Most delays come from slow feedback or missing content. Ask for a written timeline with milestones and agree who is responsible for each deliverable.
We repair laptops and build websites and business systems. Have a question this guide did not answer? Message us.
This guide is general advice. Every device and business is different, so if you are unsure, ask a technician before you act.
