The hidden costs of a web agency project

You sell a website redesign project for 30,000 EUR. You've quoted the design, front-end development, back-end, content integration. Your theoretical margin is 30%. Six months later, the project is delivered, the client is satisfied, but your actual margin hovers around 12%. What happened?

What happened is that you forgot to account for between a quarter and a third of the actual time spent on the project. Not through negligence, but because these time items are structurally invisible in the way web agencies quote their projects. This article identifies these hidden costs, quantifies them on a typical project, and proposes a method for integrating them into your future quotes.

The 5 time items nobody accounts for

Most web agencies know how to quote what they produce: mockups, integration, development, content. What they systematically forget are the hours required for that production to happen. These hours are real, consumed by team members whose hourly cost is identical to that of the producers, but they appear nowhere in the quote.

1. Pre-sales

Before the quote is even signed, your agency has invested time. An initial scoping call with the prospect. An analysis of the existing site. Drafting a commercial proposal with a macro timeline. Sometimes an exploratory mockup or a homepage prototype to win the deal.

This time is very real. For a 30,000 EUR project, count 8 to 20 hours of pre-sales depending on pitch complexity and the level of competition. If your conversion rate is 30% -- which is a high average for the industry -- you need to amortize the pre-sales hours of three prospects to fund a single won project. The real cost of pre-sales is therefore not 15 hours, but 45.

Key figure: With a 30% conversion rate, each hour of pre-sales on a won project actually represents 3.3 hours when you include lost pre-sales. On a 30,000 EUR project, this can represent 2,500 to 4,000 EUR in absorbed cost.

2. Project management

This is the most massively underestimated item. Project management isn't optional "overhead." It's what makes the project move forward: sprint planning, resource allocation, progress tracking, backlog management, priority decisions, schedule updates, client communication.

On a 3-to-4-month redesign project, a project manager typically devotes 15 to 25% of the total project time to these coordination tasks. This time is almost never quoted as a separate line item. It's "diluted" into production items, which completely distorts your actual cost per phase.

The problem worsens on projects where the client is unavailable or poorly organized internally. The project manager then spends a significant portion of their time following up, rephrasing, rescheduling -- additional time that was planned for nowhere.

3. Internal meetings

Sync meetings. Team stand-ups. Sprint reviews. Collective design sessions. Post-presentation debriefs. Each meeting involves at minimum two people, often three or four. A 45-minute meeting with three participants consumes 2h15 of production time.

On a redesign project, internal meetings typically represent 8 to 12% of total time. This percentage mechanically increases with the size of the assigned team: the more people on a project, the more coordination time grows -- and not linearly, but exponentially.

Concrete example: A project with 2 developers, 1 designer, and 1 project manager generates an average of 3 internal meetings per week of 30 to 45 minutes. Over 3 months: 36 to 54 meetings, or 72 to 162 cumulative team hours. At an average loaded cost of 60 EUR/h, that represents 4,300 to 9,700 EUR.

4. QA and fixes

QA is the moment when the delivered project is tested, anomalies are identified, and fixes are applied. In theory, a well-executed project has a short QA phase. In practice, QA is almost always longer than expected, for two reasons.

First, acceptance criteria are rarely defined precisely in the specifications. The client discovers behaviors they consider bugs, when they were never specified. Second, each fix can generate new side effects requiring additional testing.

QA typically represents 10 to 15% of total time on a web project. And it's an item where the boundary with scope creep is particularly blurry: when is client feedback a legitimate fix, and when is it a disguised feature request?

5. Post-delivery support

The project is delivered. The site is in production. The client is trained. Case closed? Not quite. During the 2 to 4 weeks following launch, your team will handle requests: content to adjust, a dead link found, a display issue on a specific browser, a question about the admin tool.

This post-delivery support is rarely billed. It's considered an implicit "warranty," a goodwill gesture, a mark of professionalism. But it consumes time -- between 8 and 15 hours on a medium-sized project. And this time is consumed by technical profiles whose hourly cost is not negligible.

Key takeaway: These 5 items -- pre-sales, project management, internal meetings, QA, post-delivery support -- represent 25 to 35% of total project time. This isn't a rough estimate. It's a third of your production capacity that disappears from your radar if you don't track it.

Quantifying these costs on a typical site redesign project

Let's move from theory to numbers. Take a real project: a brochure site redesign with a headless CMS, 15 to 20 templates, editorial integration, a technical SEO phase. Sold budget: 30,000 EUR excl. tax. Team: 1 designer, 2 developers, 1 project manager. Duration: 3 months.

Here's the typical breakdown between visible costs (those in the quote) and hidden costs (those actually consumed but never quoted).

The initial quote budgeted approximately 450 hours of production. Hidden costs add 157 hours, or 35% of the budgeted time. On a project sold at 30,000 EUR, that's 8,635 EUR billed to nobody. Your theoretical gross margin of 30% (9,000 EUR) melts to 365 EUR in reality. In other words, you worked three months for virtually no margin.

Key figure: On a 30,000 EUR project, hidden costs average 8,000 to 10,000 EUR. That's the difference between a profitable project and one that loses you money.

This calculation isn't a worst-case scenario. It's the reality for the majority of agencies that don't track their time spent versus the quote. Without reliable data, the gap between quoted and actual remains invisible -- until the day you look at your annual balance sheet and wonder why your cash flow doesn't match your revenue.

How to integrate these costs into your future quotes

Identifying hidden costs is a first step. The next step is integrating them into your business model so that every project sold is truly profitable.

Method 1: The indirect cost coefficient

The simplest method is to apply a multiplier coefficient to your production hours. If your hidden costs represent 30% of time, multiply your production hours by 1.30 to get the actual total time.

Concretely, if you estimate 400 hours of production for a project, the actual time will be 520 hours. Your quote must cover these 520 hours, either by increasing the price or by raising your base hourly rate to absorb the coefficient.

The advantage of this method: it's invisible to the client and doesn't complicate the quote structure. The disadvantage: it doesn't incentivize reducing hidden costs since they're covered by a flat rate.

Method 2: Explicit line items in the quote

A more transparent approach is to add separate line items in your quote for typically hidden items.

• Project management and coordination: 15-20% of total budget, expressed in hours or as a flat fee.
• QA phase: 10-15% of budget, with a defined scope (number of QA cycles, acceptance criteria).
• Post-delivery support: a flat fee of X hours over Y weeks, clearly delimited.

This method has a major advantage: it educates the client. When a marketing director sees a line item "project management: 60 hours" in a quote, they understand that the work isn't limited to "designing mockups and coding." They perceive the real complexity of coordination, and they'll be less surprised if the project requires management time.

Concrete example: A 15-person Parisian agency has systematically added a "project management" line item at 18% of their quotes since 2024. Result: no client has rejected this line item, and the average margin per project went from 14% to 27%. Transparency pays off.

Method 3: Systematic tracking to refine ratios

Methods 1 and 2 rely on averages. To go further, you need to measure your actual hidden costs, project by project, and refine your ratios over time.

This involves tracking all time dedicated to a project, including typically unaccounted items: pre-sales, meetings, QA, support. With 6 to 12 months of data, you'll be able to calculate your own hidden cost ratios by project type and adjust your estimation methods accordingly.

These ratios vary from one agency to another based on your internal organization, process maturity, and client profile. The only way to know yours is to measure them.

Protecting your margin without scaring the client

The question every agency director asks is: "If I increase my quotes by 30%, I'll lose tenders." It's a legitimate concern, but it rests on a misunderstanding.

Your competitors who propose lower prices have exactly the same hidden costs as you. They just don't see them. They deliver projects at a loss, compensate through volume or team overwork, and eventually decline in quality -- which sends you their dissatisfied clients down the road.

Your competitive advantage isn't offering the lowest price. It's offering a fair price, accompanied by a transparent explanation of what it covers. A serious client will always prefer an agency that masters its costs -- it's an indicator of professionalism and reliability.

Key takeaway: Hidden costs don't disappear when you ignore them. They silently eat into your margin. The only question is whether you prefer to absorb them (and work at a loss) or integrate them into your quotes (and preserve your profitability). The answer should be obvious -- but you need the data to quantify them first.

The hidden costs of a web project are not inevitable. They are real, measurable expenditure items that can be integrated into your business model. Pre-sales, project management, internal meetings, QA, and post-delivery support represent 25 to 35% of a project's total time. Ignoring them means giving away a third of your work to your clients.

The first step is to measure them. The second is to integrate them into your quotes. The third is to optimize your organization to reduce them. But to measure, you need to track -- and to track effectively, you need a time tracking system that covers the entire scope, including both production and non-production time.