What drives the cost of a website? The factors behind price and timeline
Maybe Digital · 7 min read · Updated:
Short answer
Scope drives most of a website's cost and timeline: the number of pages and templates, custom design versus a theme, who prepares the content, the integrations needed (payments, CRM, multiple languages), SEO and performance work, and maintenance after launch. When comparing quotes, check which of these are included before you look at the price.
Why two quotes can be far apart
"Website" covers everything from a one-page introduction to a platform with hundreds of products and user accounts. Two agencies can read the same brief and picture very different jobs: one may be pricing text dropped into a ready-made theme, the other a design, content and SEO structure built from scratch.
The way to understand a price is to break the work into parts. The headings below help you see what a quote contains and what it leaves out.
1. Scope: templates matter more than page count
What drives cost is less the number of pages than the number of distinct page types (templates). Twenty service pages with the same layout are one template filled twenty times. A home page, service detail, project detail, blog post and contact page are five templates, each designed and built separately.
The easiest way to pin down scope is a draft site map: which pages exist, which share a layout, and which contain special features such as forms, filters or calculators.
2. Design: theme or custom?
Starting from a theme is fast; most design decisions are already made. But you stay inside the theme's limits, changing parts that don't fit your brand can take more effort than building them fresh, and themes often ship with unused code that can slow the site down.
With custom design, the brand language, page structure and user journeys are worked out first, then each template is designed and built. It takes longer, but the result belongs to your brand, loads fast and lasts. Every animation, 3D element or custom interaction adds design and development time.
3. Content: the item that causes most delays
Projects stall on content more often than on code. If nobody agrees up front who writes the text, where the photos come from and how long approvals take, the design gets finished and the site sits waiting for content.
- Will you supply the text, or is SEO-ready copywriting part of the job?
- Do products, team or premises need a photo shoot, or will stock images be used?
- Will the site be multilingual, and who translates and reviews it?
- Is there content to migrate from the old site, and who moves it?
4. Content management and integrations
If you'll update content yourself, a content management system (CMS) is set up and each template's editable fields are defined. The more flexible the panel, the more work it takes to set up.
Integrations change cost the most: online payments, booking, sending form leads to a CRM, links to accounting or inventory software, user accounts, multiple languages and maps are each a separate piece of development and testing. Whether the other system has documentation and a test environment also directly affects the timeline.
5. Invisible but decisive: SEO, speed, accessibility, maintenance
Technical SEO (heading structure, URLs, structured data, sitemap, redirects from old URLs), performance work and accessibility (keyboard navigation, sufficient colour contrast, alt text on images) aren't visible on screen. That's why they're usually the first things cut from cheap quotes.
The work continues after launch: hosting, domain renewal, SSL, updates, security patches, backups and error tracking. Always ask whether a quote covers only the build, or the first period of maintenance as well.
How to get comparable quotes
Send everyone the same written brief and ask for quotes that list the same items separately. You'll then see whether the "cheap" quote simply contains less work, or whether the "expensive" one covers costs that would otherwise appear later.
The lowest quote can end up costing more when missing work is priced separately later, when the site is slow or invisible on Google, or when the code and accounts aren't handed over to you. Judge the price together with the list of deliverables.
- How many templates will be designed and built, and how many design revision rounds are there?
- Are copywriting, translation and images included?
- Which integrations are included, and which are priced separately?
- Are technical SEO, redirects from old URLs and performance work included?
- Whose name will the domain, hosting, source code and accounts be in?
- How will maintenance work after launch, and what does it cover?
Frequently asked questions
- How long does it take to build a website?
- It depends on scope, whether content is ready, integrations and approval times. A site with few templates and ready content can be finished quickly; a multilingual, integrated, custom-designed project needs a longer plan. A realistic schedule can only be set once scope is clear.
- Why can't you give a fixed price straight away?
- Because scope sets the price. A figure given before templates, content, integrations and maintenance are clear either leaves work out or is padded to cover the uncertainty. A short discovery call makes an honest, comparable quote possible.
- What can I do to keep costs down?
- Limit scope to what the first release truly needs, prepare text and images on time, have one person give approvals, and schedule nice-to-have features for a second phase. Cutting basics such as SEO and performance usually costs more later.
- Are there costs after the site goes live?
- Yes. The domain, hosting and some third-party services renew regularly, and updates, security, backups and content support need a maintenance plan. Agreeing these in writing at quote stage avoids surprises.