How Should an Agency Price a Website Project?

You know the pages, templates, functionality, integrations, content responsibilities and expected delivery process.

Now the client asks the obvious question:

How much will it cost?

This is where many agencies jump from scope straight to a number.

Perhaps a similar website sold for £10,000 last year. A competitor appears to charge £15,000. The developer has quoted £4,000, so the agency adds 30%. Or somebody simply decides that it “feels like a £12k project”.

Those methods can produce a price.

They do not tell you whether the project will be commercially worthwhile.

A better approach is:

1. define the scope;
2. estimate what it will actually cost your agency to deliver;
3. account for uncertainty;
4. understand the margin the project leaves;
5. consider the commercial value to the client;
6. choose appropriate pricing and payment terms.

The client's price should not be your delivery cost plus an arbitrary markup. It should be the commercial result of scope, cost, risk, margin, value and terms.

That matters because revenue and profitability are not the same thing. Productive's 2025 survey of 93 agency leaders found that 59% reported revenue growth, while only 31% reported improved margins. It also found project-based fees were still the primary pricing model for 76% of respondents.

Selling more work does not automatically mean selling profitable work.

How should an agency calculate a website price?

A useful way to think about website pricing is through six layers:

Layer Question

Scope What exactly are we delivering?

Cost What will it cost us to deliver?

Risk What could reasonably make delivery more expensive?

Margin What does this project need to contribute commercially?

Value What is solving this problem worth to the client?

Terms How and when do we get paid, and what happens if things change?

The final fee comes after considering all six.

Let us work through them.

1. Start with a defined website scope

Do not price a website you have not scoped.

“12-page website” is not enough.

A 12-page website could involve:

• four reusable page templates;
• finished client-supplied copy;
• one standard contact form;
• no migration;
• no third-party integrations.

Another 12-page site could involve:

• 11 bespoke layouts;
• copywriting;
• HubSpot integration;
• a searchable resource library;
• 200 existing URLs;
• animations;
• complex CMS requirements;
• several approval stakeholders.

The page count is the same.

The delivery economics are not.

Before estimating the fee, understand at least:

• strategy and discovery;
• information architecture;
• unique templates;
• UI/UX design;
• development;
• CMS requirements;
• functionality;
• integrations;
• content responsibilities;
• migration;
• SEO requirements;
• revisions;
• project management;
• QA;
• launch;
• handover.

If these are not sufficiently understood, go back to the scope before pricing.

2. What does the website actually cost your agency to deliver?

Start by estimating direct project delivery cost.

For a website, this may include three broad categories.

Internal delivery cost

Estimate the internal resources the project requires.

For example:

• strategy;
• UX;
• UI design;
• development;
• project management;
• account management where treated as a project delivery cost;
• content work;
• QA;
• launch support.

For each role, estimate:

expected project time × internal cost rate

The important word here is cost.

Your designer may be billed to clients at £100 per hour.

That does not mean the designer costs the agency £100 per hour.

Equally, simply dividing their salary by annual working hours may understate the real cost of maintaining that capacity.

Depending on how your agency manages its finances, internal cost may need to account for:

• salary;
• employer costs;
• benefits;
• directly attributable software;
• realistic billable capacity;
• other costs associated with employing that delivery resource.

Not every paid working hour becomes billable client work. Resource-planning systems therefore distinguish available capacity from billable utilisation when assessing agency economics.

Use a costing method that is consistent with your agency's financial model rather than inventing a different cost rate for every proposal.

External delivery cost

Add specialist work bought specifically for the project.

For example:

• freelance designer;
• development partner;
• white-label website partner;
• copywriter;
• animator;
• photographer;
• SEO migration specialist;
• accessibility specialist.

If a development partner quotes £3,500, that £3,500 is a direct project cost.

It is not automatically what you should charge the client for “development”.

We will return to that distinction later.

Project-specific expenses

Include costs that exist because this project exists.

For example:

• premium software or plugins bought specifically for the project;
• stock assets;
• specialist testing;
• migration software;
• paid datasets;
• project-specific licences.

You can therefore start with:

Estimated direct delivery cost = internal delivery cost + external delivery cost + project-specific expenses

That number is not your selling price.

It is the economic starting point.

3. How should uncertainty affect the price?

Two projects can have identical estimated hours and very different levels of risk.

Consider these two situations.

Project A

• approved sitemap;
• approved copy;
• familiar CMS;
• standard functionality;
• no migration;
• one stakeholder;
• clear deadline;
• repeatable delivery process.

Project B

• copy still being written;
• legacy website;
• undocumented API;
• 500 pages of existing content;
• simultaneous rebrand;
• several stakeholders;
• tight fixed launch date.

Even if the initial production estimate happens to be identical, Project B contains substantially more uncertainty.

That uncertainty needs to be managed commercially.

Possible approaches include:

• charging for discovery first;
• documenting assumptions;
• narrowing the fixed scope;
• separating uncertain work into time-and-materials;
• adding reasonable contingency;
• obtaining specialist estimates before quoting;
• using formal change control.

Do not automatically add an arbitrary “20% contingency” to everything.

The correct response depends on what is uncertain.

A useful classification is:

Defined

You understand the requirement well enough to estimate it.

Assumed

You can estimate it, provided a documented assumption remains true.

Unknown

The requirement could materially change the work and should be investigated before committing to a fixed price.

For example:

Defined: Six responsive page templates.

Assumed: Client supplies approved copy before design.

Unknown: Proprietary CRM must “fully integrate” with the website, but nobody has reviewed its API.

The third item should not quietly disappear inside your fixed fee.

4. What project margin should an agency price for?

First, distinguish revenue, gross profit and project gross margin.

Suppose:

Client fee: £10,000 Direct delivery cost: £6,000

Gross profit before wider company overhead is:

£10,000 − £6,000 = £4,000

Project gross margin is:

(Revenue − direct project cost) ÷ revenue × 100

So:

£4,000 ÷ £10,000 × 100 = 40%

Project gross margin shows what remains after direct delivery costs.

It does not mean the agency has made £4,000 of final net profit.

The business still has wider costs such as:

• leadership;
• sales;
• finance;
• administration;
• rent;
• shared software;
• insurance;
• marketing;
• non-billable time;
• other operating overhead.

Teamwork similarly distinguishes gross margin, which removes direct project costs, from net margin, which also considers overhead and wider operating costs.

That is why a project can look profitable while the agency itself is struggling.

Margin and markup are not the same thing

This is one of the most common pricing mistakes.

Suppose a website costs your agency £5,000 to deliver.

You decide:

“Let's add a 50% markup.”

£5,000 + 50% = £7,500

Your profit before wider overhead is £2,500.

But your margin is:

£2,500 ÷ £7,500 = 33.3%

You have a 50% markup, not a 50% margin.

Here is the difference:

Delivery Markup on cost Client price Actual project margin cost

£5,000 20% £6,000 16.7%

£5,000 50% £7,500 33.3% £5,000 100% £10,000 50%

These are mathematical examples, not recommended margin targets.

If you know the direct cost and want to calculate the price required for a particular gross margin:

Price = Direct cost ÷ (1 − target margin)

For a £5,000 cost and a hypothetical 50% target gross margin:

£5,000 ÷ 0.50 = £10,000

Understanding this distinction prevents an agency from believing it has more commercial room than it actually does.

What margin should a website project have?

There is no single percentage that every agency should use.

A healthy project margin for one business model may be inappropriate for another.

Consider the differences between:

• a distributed five-person agency;
• a 50-person agency with senior account teams;
• a freelancer-heavy agency;
• a consultancy-led agency;
• an agency with significant premises and management overhead;
• an agency outsourcing most production.

Industry benchmarking can be useful context, but it should not replace your own economics.

Your agency needs to know how much project-level gross profit must remain to contribute towards:

• overhead;
• sales;
• non-billable activity;
• capacity gaps;
• investment;
• tax obligations where applicable;
• and actual business profit.

A project margin target should therefore come from the economics of your agency.

The important rule is simpler:

Know the margin before you send the quote. Do not discover it after delivery.

5. Should agencies use cost-plus or value-based pricing?

Neither should be used blindly.

Cost matters because it tells you whether delivering the project makes commercial sense.

Value matters because clients do not buy your hours. They buy the outcome the website helps create.

Suppose two clients require projects with similar delivery complexity.

For one client, the website primarily acts as a basic corporate presence.

For another, it sits at the centre of an established sales process where one additional customer may be commercially significant.

The production effort may be comparable.

The commercial importance of solving the problem may not be.

That does not mean charging an arbitrary amount simply because the client is larger.

It does mean your price does not have to be determined only by:

hours × rate.

A sensible approach is:

Cost establishes your economic floor.

Can your agency deliver this profitably?

Value informs the commercial opportunity.

What is solving this problem worth to this particular client?

Market and positioning provide context.

What alternatives does the client have, and where is your agency positioned?

Scope determines what is actually being sold.

What work and responsibility are included?

The final price needs to make sense from both sides.

6. Fixed fee vs hourly vs time-and-materials: which should agencies use?

There is no universally superior pricing model.

Choose based largely on how clearly the work can be defined and who should carry the risk if effort changes.

Pricing model Works best when Main risk

Fixed fee Scope and boundaries are clear Agency absorbs overruns

Time & Requirements may evolve Client has less cost certainty materials

Hourly/day rate Advisory, investigation or Efficiency remains linked to time additional work

Retainer Website work continues regularly Monthly scope can become unclear

Value-based Business value can be credibly Weak value assumptions create understood arbitrary prices Productive's current project-management guidance makes a similar distinction: with fixed fees, the agency carries the risk of work taking longer, while time-and-materials transfers more of that cost risk to the client.

When does a fixed website fee make sense?

Fixed pricing works well when:

• deliverables are clear;
• revisions are defined;
• integrations have been investigated;
• migration is understood;
• dependencies are documented;
• assumptions are reasonable.

The client receives price certainty.

The agency receives the opportunity to benefit from efficient delivery.

But there is an important condition:

Fixed price requires fixed boundaries.

If you cannot explain what is excluded, what constitutes a change and what assumptions underpin the quote, the project may not actually be ready for a fixed fee.

When does time-and-materials make more sense?

Consider it where:

• technical requirements will evolve;
• legacy systems require investigation;
• the client controls the volume of requests;
• requirements cannot yet be fixed;
• the work resembles ongoing product development rather than a defined website build.

You can also combine models.

For example:

Discovery: time-based or fixed discovery fee Defined website build: fixed project fee Post-launch enhancements: time-and-materials or retainer

Pricing does not need to follow one model across every stage.

How should an agency price outsourced or white-label website delivery?

This is especially important for agencies that sell websites but do not employ every delivery capability internally.

Suppose your development partner quotes:

£4,000

It can be tempting to say:

“We'll add 25% and charge the client £5,000.”

But what is that 25% meant to cover?

Your agency may still be responsible for:

• winning the client;
• strategy;
• briefing;
• design;
• account management;
• project management;
• creative direction;
• QA;
• revisions;
• communication;
• payment risk;
• launch;
• post-launch responsibility.

The supplier's £4,000 is therefore one component of project cost.

It is not automatically the client-facing development price.

Instead, calculate the full project economics:

Internal delivery cost

• external delivery cost
• project expenses
• appropriate risk treatment = your delivery basis

Then assess the client fee against the margin and commercial value you need.

This is why a reliable white-label quote is useful to an agency: it converts one part of website delivery from an uncertain future cost into a known input before the agency commits to its client price.

How should revisions and scope changes be priced?

Your original price should include an expected amount of normal revision work.

Define:

• which stages allow revisions;
• how many rounds are included;
• how feedback must be submitted;
• what constitutes a revision;
• what constitutes a new requirement.

For example:

Included revision

Change the image and adjust the spacing on the approved service-page design.

Potential scope change

Add an interactive pricing calculator that was not part of the agreed requirement.

A genuine change request should be assessed for its effect on:

• design;
• development;
• QA;
• timeline;
• dependencies;
• previously completed work.

Then price it appropriately.

That could mean:

• a separate fixed fee;
• hourly/day rate;
• time-and-materials;
• revised project price.

Do not try to predict and pre-price every possible future request.

Instead:

Price the agreed project properly and define how changes to that agreement will be handled.

What happens when you discount a website project?

Discounts can damage project economics faster than they appear to.

Consider a hypothetical project:

Original fee: £12,000 Direct delivery cost: £6,000 Gross profit: £6,000

Now the client asks for 10% off.

New fee:

£10,800

Direct delivery cost remains:

£6,000

New gross profit:

£4,800

The client price fell by 10%.

Your gross profit fell by 20%.

That does not mean agencies should never discount.

It means the cost of the discount should be understood before agreeing to it.

Where appropriate, consider exchanging price for another commercial concession:

• reduced scope;
• fewer deliverables;
• fewer revision rounds;
• longer/flexible timeline;
• faster payment;
• lower strategic involvement.

Avoid doing identical work for materially less money simply because the client asked.

How should website payment terms be structured?

Price and payment structure solve different problems.

A £20,000 project can be profitable on paper and still put pressure on cash flow if your team and suppliers are paid long before the client pays you.

Before starting, define:

• initial payment;
• milestone invoices;
• final payment;
• invoice timing;
• payment terms;
• responsibility for third-party expenses;
• what happens if invoices become overdue;
• what happens if the client pauses the project;
• cancellation terms;
• payment requirements before final handover where appropriate.

There is no need to prescribe one universal structure such as “50% upfront”.

The appropriate model depends on:

• project length;
• supplier obligations;
• client type;
• procurement process;
• agency cash-flow requirements.

The principle is:

Make sure cash enters the project at sensible points relative to when the agency incurs its costs.

A practical website pricing example

Imagine a branding agency has scoped a corporate website.

Its estimated direct delivery cost looks like this:

Work Estimated direct cost

Strategy and architecture £600

UX/UI design £1,600

Development £2,500

Project management £700

QA and launch £500

Project-specific expenses £300

Estimated direct delivery £6,200 cost

The project also contains some manageable uncertainty around content and implementation.

For this hypothetical example, assume the agency allows £600 for that identified risk.

Risk-adjusted delivery basis:

£6,800 Now compare possible client prices:

Client price Gross profit before wider Project gross overhead margin

£8,000 £1,200 15%

£10,000 £3,200 32%

£13,600 £6,800 50%

Again, these are mathematical scenarios, not recommended website prices or target margins.

The spreadsheet still cannot make the final commercial decision for you.

At £13,600, for example, you still need to ask:

• Does the client perceive sufficient value?
• Is that price credible for your positioning?
• What alternatives does the client have?
• What is the opportunity cost of accepting the project?
• How strong is the probability of closing?
• Do you have the capacity to deliver it?

Pricing combines arithmetic with commercial judgement.

The arithmetic should come first because it tells you what the judgement actually means.

What should not determine your website price?

“What did we charge the last client?”

Useful reference.

Not a pricing methodology.

The scope, costs and risk may be different.

“What are competitors charging?”

Useful market context.

But your competitors do not necessarily have your cost structure.

“The client's budget is £20,000.”

Budget tells you what the client may be able or willing to invest.

It does not automatically make £20,000 the correct price.

“Our developer costs £4,000, so we'll add 20%.”

Why 20%?

Unless that markup comes from a deliberate economic model, it is arbitrary.

“It feels like a £15k project.”

Experience and judgement matter.

But gut feel should be checked against actual delivery economics before the proposal leaves your agency.

Review estimated vs actual profitability after delivery

Pricing should become more accurate as your agency completes more projects.

That only happens if you compare what you thought would happen with what actually happened.

After the project, review:

Metric Estimate Actual d Strategy effort

Design effort

Development effort

Project management

QA

External supplier cost

Project expenses

Total delivery cost

Revenue

Gross margin

Then investigate the difference.

Was the estimate wrong because of:

• extra revisions?
• underestimated development?
• content population?
• migration?
• project management?
• technical issues?
• poor client responsiveness?
• missed requirements?
• QA?

Project-profitability guidance from Teamwork similarly recommends forecasting before delivery and comparing revenue with direct costs rather than treating revenue alone as evidence that a project performed well.

This creates a much stronger pricing loop:

Scope → Estimate → Price → Deliver → Measure → Improve

Over time, your agency stops pricing from memory and starts pricing from evidence.

How do you know whether a website project is worth taking?

Before sending the proposal, ask:

1. Do we understand what we are being asked to deliver?
2. Have we estimated the actual cost of delivering it?
3. Have material assumptions and unknowns been identified?
4. What gross margin would this price leave?
5. Is that contribution commercially sensible for our agency?
6. Does the price make sense relative to the value for the client?
7. Do we have the capacity to deliver the project properly?
8. Are revisions and scope changes controlled?
9. Are payment terms workable?
10. Would we still be comfortable with this project if delivery goes slightly worse than planned?

That final question is particularly useful.

If a website project is profitable only when:

• every estimate is perfect;
• every client response arrives on time;
• no unexpected issue appears;
• no extra PM is required;
• every stakeholder agrees immediately;

then the project economics are fragile.

Good website pricing does not mean charging the highest number you can persuade a client to accept.

It means understanding the work well enough to set a price that makes sense for both the client and the agency delivering it.

What should your agency do?

Start with scope.

Calculate your real delivery cost.

Identify uncertainty rather than burying it.

Understand the difference between markup and margin.

Use value to inform the commercial opportunity, but do not let value-based thinking hide bad project economics.

Choose a pricing model that matches the certainty of the work.

Then track what actually happens.

A website price should not come from page count, competitor rates or gut feel. It should come from understanding what you are delivering, what it will cost, what could change, what the project needs to contribute and what solving the problem is worth to the client.

If part of your delivery is outsourced, obtain that delivery cost before committing to the final client fee. Oncreation works behind the scenes with agencies as a white-label website delivery partner across website strategy, design, development, QA and launch, allowing an agreed delivery scope to become a defined project cost rather than an unknown.

Sources

Productive — 2025 Agency Industry Report

Used for current agency data on revenue growth, margin improvement and adoption of project-based pricing.

Productive — Agency Project Management Guide

Used for the distinction between pricing models and which party carries the risk when delivery effort changes.

Productive — Billing Types

Used to verify current definitions of fixed-price and time-and-materials billing.

Teamwork — Project Profitability Metrics Every Agency Should Track

Used for definitions of gross and net project profitability and the importance of forecasting project economics before delivery.

Teamwork — Project Financial Management

Used for current guidance on measuring direct project costs, gross margin, utilisation and cash-flow considerations.