Hiring a digital agency is one of those areas where the pricing feels deliberately opaque. You talk to three agencies about the same project and get three wildly different numbers with three completely different structures. One quotes hourly. Another gives you a fixed price. A third pitches a monthly retainer. How are you supposed to compare them?
The truth is, the pricing model matters as much as the price itself. Different models create different incentives, shift risk in different directions, and work better for different types of projects. Understanding the models is the first step to getting a deal that actually makes sense for your business.
Hourly / Time and Materials
The most straightforward model: the agency bills for the hours worked at an agreed rate. You pay for the time, they do the work.
When it works: Projects with evolving requirements, discovery phases, and situations where you cannot define the full scope upfront. If you are figuring out what you need as you go, hourly gives you the flexibility to change direction without renegotiating a contract.
When it doesn't: Projects with tight budgets and fixed deadlines. Hourly billing creates an inherent tension... the agency has no financial incentive to be efficient. Every question, every meeting, every revision is billable time. Good agencies are ethical about this, but the incentive structure is what it is.
What to watch for:
- Ask for detailed time tracking reports, not just invoice totals. You should know where the hours went.
- Set a budget ceiling with a notification threshold. "Tell me when we hit 80% of the budget" prevents surprises.
- Clarify what is billable. Is a 15-minute Slack conversation billable? What about project management overhead? Internal meetings? These add up fast.
Fixed Price / Fixed Bid
The agency quotes a total price for a defined scope of work. You pay that price regardless of how many hours the work takes.
When it works: Well-defined projects with clear requirements, limited unknowns, and a scope that both parties agree on before work starts. A marketing website with a defined page count, a known content model, and agreed-upon designs is a good candidate for fixed pricing.
When it doesn't: Projects where the requirements will change (and they almost always do). Fixed-price contracts handle scope changes through change orders, which add friction and cost. Every "oh, can we also..." becomes a mini-negotiation. This leads to either nickel-and-diming or the agency quietly absorbing extra work and resenting it.
What to watch for:
- The scope document is the contract. If it is vague, you will disagree later about what was included. "Build a blog" is not a scope. "Build a blog with listing page, category filtering, pagination, individual post pages, and related posts sidebar" is closer.
- Agencies pad fixed-price bids for risk. This is rational. If they are absorbing the risk of scope uncertainty, they charge for it. A fixed-price bid is almost always higher than the equivalent hourly estimate.
- Quality can suffer. When the agency realizes they underestimated, the temptation is to cut corners to stay within the bid. This is rarely explicit... it shows up as "good enough" code, minimal testing, and thin documentation.
Monthly Retainer
You pay a fixed monthly fee for a defined amount of the agency's time and attention. Think of it as a subscription to agency services.
When it works: Ongoing relationships where you need continuous work but the specific tasks change month to month. A retainer is great for post-launch support, ongoing content creation, iterative feature development, and situations where having a team that knows your codebase is more valuable than finding the cheapest provider for each task.
When it doesn't: One-time projects with a clear end date. If you need a website built and then you are done, a retainer is just hourly billing with a minimum spend. You are paying for continuity that you do not need.
What to watch for:
- "Use it or lose it" terms. Some retainers expire unused hours at the end of each month. Others roll over. This matters a lot if your needs are uneven month to month.
- Understand what the retainer covers. Is it just development hours, or does it include project management, strategy, and design? A "40-hour retainer" that includes 10 hours of PM overhead is really a 30-hour retainer.
- Exit clauses. How much notice do you need to give to end the retainer? Being locked into a 12-month contract when the relationship is not working is expensive and frustrating for both sides.
Value-Based Pricing
This is the model agencies love to talk about and rarely execute well. The price is based on the value delivered to the client, not the time spent. If the project is expected to generate $500,000 in new revenue, the agency might charge $75,000 regardless of whether the work takes 200 hours or 400.
When it works: Situations where the value is quantifiable and both parties can agree on the metrics. A website redesign that is expected to increase conversion rate by a measurable amount is a candidate. An agency that has done similar projects and can point to historical results has the credibility to propose this model.
When it doesn't: Most of the time, honestly. Value is hard to isolate. Did the new website increase revenue, or was it the simultaneous ad campaign? The attribution problem makes pure value-based pricing tricky in practice. Most "value-based" pricing is really just fixed pricing with a narrative around ROI.
How to Compare Apples to Apples
When you have proposals from multiple agencies with different pricing models, here is how to normalize them:
| Factor | Hourly | Fixed | Retainer |
|---|---|---|---|
| Budget predictability | Low | High | High |
| Scope flexibility | High | Low | Medium |
| Risk bearer | Client | Agency | Shared |
| Best for | Discovery, evolving scope | Well-defined projects | Ongoing partnerships |
| Incentive alignment | Agency rewarded for more hours | Agency rewarded for speed | Agency rewarded for retention |
Beyond the model itself, ask every agency these questions:
- What is included in the price? Hosting, ongoing maintenance, bug fixes after launch, content migration, SEO setup... these are often not included and they add up.
- What does "done" look like? How many rounds of revision are included? What is the acceptance process? When does the warranty period start?
- What is not in scope? This is often more revealing than what is. A good agency is explicit about what they are not doing.
- What is the team composition? A senior developer at $200/hour can often do in 10 hours what a junior developer does in 40 at $75/hour. The hourly rate is not the whole story.
The Model We Prefer (and Why)
At Last Rev, we tend toward time-and-materials for initial builds and retainers for ongoing work. Here is the honest reasoning: web projects almost always evolve during execution. Requirements change. Stakeholders have new ideas. Technical discoveries shift the plan. A pricing model that accommodates this reality serves both parties better than one that pretends scope is static.
We pair time-and-materials with detailed estimates, regular budget check-ins, and transparent time tracking. Clients always know where they stand financially. If the project is trending over estimate, we have that conversation early... not in the final invoice.
The retainer model works well for post-launch because the work is genuinely continuous. Bug fixes, content updates, new features, performance optimization... these do not stop when the site launches. Having a team that knows your codebase and your business context is worth more than rebidding every small project.
If you are evaluating agencies and want a straight conversation about pricing, reach out. We will tell you exactly how we would structure an engagement for your situation... and whether we are the right fit.