Techbanq

Cost guide · web

A page count is the least useful way to price a website

The same brochure of pages can be a template a small team fills in an afternoon or a platform with a content model, integrations, an editing workflow and full Arabic and accessibility support. What moves a website's price is almost all behind the design: how the content is structured, what the site connects to, and who has to be able to change it without a developer. This page is about those drivers rather than a rate per page.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
Head of Digital, Commercial Director
Decision
Understand what drives website development cost
Languages
EN · AR

Information security for software delivery

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

Behind the design

What actually moves a website figure once the look is agreed

Each driver is listed with the direction it pushes the figure. The visual design matters, but it is rarely where a website's cost is decided — these are.

VariableEffect on priceWhy
The content modelSets the effort more than page countA site of a few page types repeated with different content is efficient; a site where many pages are each bespoke is not. How the content is structured — the types, the reusable blocks, the relationships between them — decides how much of the site is built once and reused versus built one page at a time, and that is a far better predictor of cost than the number of pages.
Who has to be able to edit itA managed system costs more than a fixed oneA site whose content never changes can be built as fixed pages. A site a marketing team updates weekly needs a content management system with an editing workflow, roles and previews — real software behind the pages. Deciding whether the owners edit it themselves, and how much control they need, moves the figure well before any page is designed.
Integrations the site depends onEach connection is its own workBookings, payments, a CRM, identity, analytics, a maps or availability service — every connection a site makes is building and testing beyond the pages themselves. A marketing site with none of these is one thing; a site that takes a payment or shows live availability is a small application, and the integrations are where the two diverge in cost.
Arabic, right-to-left and multilingualA build requirement in this marketA bilingual site in Arabic and English is not a translated copy of one design; the layout mirrors, the typography changes, and the content model has to hold both languages cleanly. Building for right-to-left from the first template is part of the work here, and adding a second language to a site that was not designed for it costs more than designing for both at the start.
Performance, SEO and accessibilityStandards to build to, not tune laterA fast site, one search engines can read, and one usable with assistive technology are outcomes of how the site is built, not settings switched on at the end. Meeting them is ordinary engineering when designed in and a rebuild when bolted on, so a quote that treats performance and accessibility as later tuning has underpriced the build.

Ask any supplier quoting this

  • Is this a set of fixed pages or a content management system our team can edit?
  • How many distinct page types does the figure cover, and how much is reused?
  • Which integrations are included — bookings, payments, CRM, analytics?
  • Is full Arabic and right-to-left support in this figure or priced separately?
  • Are performance, SEO and accessibility built in, and how will we verify them?
  • What is the hosting and ongoing cost after the site is live?

Two sites, one page count

Why the same number of pages can cost worlds apart

Two organisations ask for a twenty-page site and receive quotes that are nowhere near each other, and both are right. One means twenty static pages of text and images, editable only by a developer, in one language, with no functionality behind them. The other means a content-managed, bilingual site whose team publishes without help, that takes bookings and payments, and that has to load fast and pass accessibility. Those are different products that happen to share a page count, and the count is the one number that does not distinguish them.

So the useful conversation is never about how many pages but about what the site has to do: who edits it and how often, what it connects to, which languages it serves, and the standards it must meet. Answer those and the quote follows naturally, and two suppliers quoting the same answers can finally be compared. A rate per page, by contrast, is a figure that survives only until the site has to do something, at which point it was never the price of the site you were describing.

Where cost is set

The stages at which a website's price is actually decided

Cost is not set at the design stage, where most buyers assume it is. It is set earlier and later than that, at the points below.

STAGE 01

Structure the content before the pages

We agree the page types, the reusable blocks and how they relate before designing a single screen, because the content model decides how much is built once and reused — the largest lever on the figure. A structure that prices the site by how it is built, not by how many pages it has.

STAGE 02

Decide the editing model

We settle who publishes and how much control they need — fixed pages, a light editor, or a full content management system with roles and workflow — because that decision separates a document from an application. An editing system matched to the team, so the site is neither a burden nor a black box.

STAGE 03

Name the integrations and languages

We list what the site connects to and which languages it serves, and build for Arabic and right-to-left from the first template, because both are far cheaper designed in than added to a finished site. A build that carries its functionality and languages rather than retrofitting them.

STAGE 04

Set the standards to build to

We fix the performance, search and accessibility targets up front and verify them at delivery, because meeting them is ordinary engineering when designed in and a rebuild when bolted on afterwards. A site that meets its standards by construction, not by a scramble before launch.

Our role

What we define before we quote a website at all

  1. 01

    The model before the mockup

    We agree the content model and the editing workflow before designing screens, because those decide the effort and a design signed off without them prices a site that cannot yet be built.

  2. 02

    Arabic and standards, built in

    We build for right-to-left, performance and accessibility from the first template and verify them at delivery, so the site meets what this market and its users require without a late, expensive rework.

  3. 03

    A quote against what it does

    We quote against the content model, the integrations and the standards rather than a rate per page, and name what is excluded, so the figure reflects the site you described instead of the cheapest thing that shares its page count.

How much your team needs to control the site, and what it must do beyond showing pages, are yours to decide; we structure and quote it around those so the price is for the website you actually need rather than a number attached to a page count.

Common questions

What buyers ask

We were quoted a flat price per page — is that a fair way to cost a site?+

It is a fair way to cost a brochure of static pages and a misleading way to cost anything else. A rate per page assumes every page is roughly the same effort, which is only true when the pages are text and images with nothing behind them. The moment the site has a content management system, integrations, more than one language or real functionality, the pages stop being equal and the per-page figure describes a simpler site than the one you asked for. A flat rate is a useful signal, though: it usually means the supplier has priced a static site, so it is the prompt to ask what the number assumes about editing, integrations and languages.

Does building the site in Arabic and English double the cost?+

No, but it is not free either, and treating it as a simple translation is where the cost hides. A bilingual site shares its structure and much of its build across both languages, so it is well short of two sites. What it does require is designing for right-to-left from the start — the layout mirrors, the typography and spacing change, and the content model has to hold both languages cleanly — and producing and maintaining the content in each. Designed in from the first template this is a modest, planned part of the build. Added to a site that was only ever meant to be English, it is a rework that costs far more than the second language would have if it had been there from the beginning.

What makes a website cost more than a marketing team expects?+

The two things they cannot see in a design: the content management system and the integrations. A design shows the pages, and the pages get budgeted; the software that lets a team publish without a developer, and the connections to bookings, payments or a CRM, are invisible in a mockup and can be the larger part of the work. The other common surprise is the standards — performance, search and accessibility treated as tuning at the end rather than as how the site is built, which turns a quick fix into a rebuild. Naming the editing model, the integrations and the standards at the start is how the final figure matches the first one.

A scoping conversation that defines the content model, the integrations and the editing workflow, so a website is quoted against what it has to do rather than how many pages it shows.

Scope your site properly