Why the pricing model matters more than the rate

Buyers comparing offshore and onshore teams often focus on the hourly or day rate. In practice, the engagement model has as much influence on the final bill and on your stress levels. The same team can feel cheap on one model and expensive on another, depending on how well the model matches the work.

Every model is a way of answering three questions: who carries the risk if the work takes longer than expected, how changes are handled, and how much of your time goes into directing the team. Get those answers right and the rate becomes a much smaller part of the decision.

Fixed price: one scope, one price

You agree a defined scope, a price and a set of deliverables before work starts. The supplier carries the risk of the work taking longer than estimated.

When it works well

• The project is well understood: a marketing website, a hotel or restaurant site, a redesign with an agreed sitemap and content.
• You have a fixed budget that needs sign-off, as many small businesses and agency clients do.
• You can supply content, branding and decisions on time.

What to watch for

• Vague scope. A fixed price is only as fixed as the brief. "A modern website with booking" can mean very different things. Our guide to writing a website brief for an outsourced team helps here.
• Change requests. Agree up front how changes are priced and approved, so you are not surprised later.
• Padding. Because the supplier carries the risk, they will build some contingency into the price. That is reasonable; just make sure you understand what is included.

Time and materials: pay for the work done

You pay for the hours or days actually worked, usually against an estimate and a budget cap, with regular reporting. You carry more of the risk, but you gain flexibility.

When it works well

• The scope will change as you learn: a startup MVP, a web app, an integration with a booking engine, CRM or payment provider.
• You want to prioritise as you go, sprint by sprint, and drop features that turn out not to matter.
• You or someone on your team can be the product owner who makes decisions quickly.

What to watch for

• Open-ended spend. Always agree a budget ceiling per phase and a point at which the team must stop and check in.
• Visibility. Ask for weekly time reports tied to tasks, a shared board and working demos, not just invoices.
• Decision lag. On this model, slow feedback costs you money. Plan for regular, short check-ins.

Dedicated team or monthly retainer: capacity on tap

You reserve a set amount of a team's time each month, either named people working mainly on your account or a pool of hours with an agreed scope of services. This is the model most agencies use for white-label work and most businesses use for ongoing care.

When it works well

• You are an agency with a steady stream of client sites and want reliable overflow capacity without hiring. Our guide to white-label web development for agencies explains how this runs day to day.
• Your website needs continuous work: new landing pages, SEO, performance, security updates, accessibility fixes.
• You value a team that already knows your codebase, brand and customers.

What to watch for

• Unused hours. Agree whether unused time rolls over and how priorities are set each month.
• Drift. Without a monthly plan and review, retainers can turn into a to-do list nobody owns. Ask for a short monthly report on what was done and what is next.
• Continuity. Ask how knowledge is documented so you are not dependent on one person.

Side-by-side comparison

The hybrid that works for most small businesses

For a typical small business or agency client, the pattern we see work best is:

1. Short paid discovery to agree goals, sitemap, features and integrations. This turns a vague idea into something that can be priced fairly.
2. Fixed-price build of the agreed scope, with a clear change process.
3. Monthly plan after launch for updates, security, backups, SEO improvements and accessibility monitoring.

That last step is where many projects fall down. A site launched and then left alone slowly loses speed, security and search visibility, and new content can introduce accessibility barriers. Our guides to website maintenance plans and ongoing accessibility monitoring explain what a good monthly plan covers.

What to put in the contract, whatever the model

• Scope or backlog: a written list of what is included, and what isn't.
• Definition of done: tested on which browsers and devices, meeting which performance and accessibility standards (WCAG 2.2 AA is a sensible baseline).
• Change process: how changes are requested, estimated and approved.
• Communication: meeting rhythm, overlap hours across time zones, the tools you will use and who the single point of contact is on each side.
• Ownership: you should own the code, design files, domain, hosting accounts and content. Make that explicit.
• Exit: how handover works if you part ways, including documentation and credentials.

Contract terms have legal consequences, so have a lawyer review anything significant. For more on running the relationship once it starts, see how to hire an offshore web team without the headaches.

Frequently asked questions