Architecture Project Profitability: How to Measure It Before It's Too Late

Architecture project profitability is rarely decided at the moment fees are signed. It's built -- or destroyed -- week after week, phase after phase, between the hours actually spent and those that were budgeted. Yet most firms only discover the verdict at project closure, when there's nothing left to correct. This guide gives you the methods, ratios, and reflexes to manage your project profitability in real time.

Why Project Profitability Is Measured During the Project, Not at Closure

There's a well-known paradox in architecture firms: you intuitively know a project is "slipping," but you don't quantify it until the DET or AOR is finished. At that point, the finding is irreversible.

Let's take a concrete case. A collective housing project is budgeted at 1,200 hours across all MOP phases (ESQ to AOR). The team's average loaded hourly cost is EUR 45/h (salaries, social charges, overhead). The internal budget is therefore EUR 54,000.

If the team ultimately consumes 1,500 hours, the actual cost rises to EUR 67,500. The overrun represents EUR 13,500, or 25% in additional cost absorbed directly by the firm's margin. On a lump-sum fee contract of EUR 72,000, the margin drops from 33% to 6%. For an 8-person firm, a single project like this is enough to wipe out a semester's profit.

Key figure: According to data from the French Order of Architects (Archigraphie survey), 40% of firms with fewer than 10 employees report a net profit below 5% of revenue. A 20% overrun on a single project can tip the year into the red.

The problem isn't the overrun itself -- contingencies are part of the profession. The problem is not seeing it coming. Without structured tracking, there's no alert, no possibility of negotiating an amendment with the project owner, and no internal arbitration possible between remaining phases.

The 3 Structural Causes of Profitability Loss in Architecture Firms

Lump-Sum Fees That Don't Cover Contingencies

The lump-sum model, dominant in French project management contracts, transfers the entire overrun risk to the architect. The itemized cost breakdown freezes an amount per phase. If the brief evolves, if geotechnical studies reveal a surprise, if the project owner requests three additional iterations during APS, the fee envelope remains identical.

The common reflex is to build in a "safety margin" in the initial estimate. But without reliable historical data on time actually spent by project type, this margin is guesswork. Some firms overestimate it and lose competitions; others underestimate it and sacrifice their profitability.

Common mistake: Estimating fees based on the percentage of construction cost (CNOA scale method) without verifying that the required volume of hours is compatible with the resulting amount. A project at 8% fees on EUR 1.2M in construction generates EUR 96,000, but if the project is complex (renovation, listed site, multiple stakeholders), the required hours may far exceed this budget.

Phases That Stretch Without Control

The MOP law divides the mission into clearly defined phases: ESQ, APS, APD, PRO, EXE, DET, AOR. Each has an identified deliverable. In theory, each phase starts after the previous one is validated by the project owner.

In practice, boundaries are porous. The ESQ "bleeds" into APS because the project owner hasn't formally validated the phase transition. The team starts detailing plans that belong to APD while still billing against the APS envelope. The result: hours consumed in early phases cannibalize the budget of subsequent phases, creating a domino effect that only becomes visible at project end.

Without rigorous time tracking by phase, it's impossible to identify this drift. And without identification, no lever for action: no internal course correction, no discussion with the project owner about validation pace.

Amendments Not Costed or Negotiated Too Late

A brief change during the PRO phase, a regulatory modification affecting execution plans, a project owner request that falls outside the initial scope: these situations justify an amendment. But in many firms, the amendment isn't formalized, or it's formalized months after the additional work was completed.

The reason is often the same: the firm lacks quantified data to support its request. Telling the project owner "we spent much more time than planned" isn't enough. Presenting a precise record -- 142 hours consumed on the PRO phase versus 95 budgeted, i.e., a 49% overrun, directly linked to the June brief modification -- fundamentally changes the negotiation.

Key takeaway: An amendment is negotiated with data, not with impressions. Phase-by-phase time tracking isn't an internal control tool: it's a contractual negotiation lever with the project owner.

How to Measure Architecture Project Profitability in Real Time

The base formula is simple:

Project margin = Phase fees - (Hours consumed x Loaded hourly cost)

The loaded hourly cost varies by profile: count between EUR 42/h for a junior drafter and EUR 55/h for a senior project manager (social charges, rent share, insurance, overhead included). These figures are consistent with averages published by the CNOA and specialized management studies for architecture firms.

To turn this formula into operational management, three indicators are enough.

1. Budget Consumption Rate (BCR)

BCR = (Hours consumed / Budgeted hours) x 100

A BCR of 60% at the midpoint of a phase means you've consumed more than half the budget while the phase is only halfway through. That's a clear warning signal.

2. Consumption Velocity

Velocity = Hours consumed per week on the project

This ratio allows projecting the date when the budget will be exhausted if the current pace continues. A velocity of 25 h/week on a remaining budget of 200 hours gives a "runway" of 8 weeks. If the phase is supposed to last 12 weeks, the overrun is foreseeable.

3. Estimate At Completion (EAC)

EAC = Hours consumed + (Remaining hours estimated at current pace)

This calculation, borrowed from project management (earned value method), provides the best estimate of the final cost. Compared to the initial budget, it indicates the projected margin.

Key takeaway: The recommended minimum is a weekly tracking point per project. A monthly firm-wide dashboard then allows comparing profitability across projects and arbitrating resource allocation.

The frequency of review makes all the difference. Monthly tracking detects drift with a 4-week delay. Weekly tracking allows reacting within the week: reassigning a team member, simplifying an intermediate deliverable, or opening the amendment discussion with the project owner before the overrun becomes irreversible.

For a deeper look at tools that enable this tracking, see our comparison of time tracking software for architects.

Before/After Scenario: The Firm That Regained Control of Its Profitability

Let's take the case (simulated from consolidated real situations) of Agence Duval, 8 team members, specializing in collective housing in the Paris region. The firm wins a project of 42 housing units (off-plan sale), projected duration 18 months, lump-sum fees of EUR 128,000 excl. tax.

Before: Flying Blind

The firm allocates fees by MOP phase empirically. Time tracking is done informally -- team members note their hours "when they think of it," without fine distinction by phase. The project manager has a global view but no exploitable data.

Result at delivery:

With fees of EUR 128,000, the gross margin drops to EUR 32,765, or 25.6% instead of the planned 38.1%. The margin loss of EUR 16,035 corresponds to a team member's loaded salary for nearly 4 months. The firm has no data to justify an amendment: overruns accumulated phase after phase without any exploitable trace.

After: Real-Time Management

The following year, on a comparable project, the firm implements structured tracking:

• Each team member enters their hours daily, broken down by MOP phase
• The project manager consults a weekly dashboard with the three indicators (BCR, velocity, EAC projection)
• A monthly profitability review is established with the managing partner

By the end of the APS phase, the dashboard reveals a BCR of 78% while the phase is estimated at 65% progress. The firm identifies the cause: three additional iterations on housing typologies requested by the project owner, which weren't in the initial brief.

With this factual data, the firm initiates an amendment discussion. The project owner, faced with a precise hourly record and traceability of modification requests, accepts an amendment of EUR 12,000 covering the additional work. The project's projected margin is preserved above 35%.

Key figure: The margin difference between the two scenarios represents nearly EUR 28,000 on a single project (EUR 16,035 in avoided overruns + EUR 12,000 in secured amendment). Relative to the revenue of an 8-person firm (typically EUR 600-800K), that's a 3 to 4 point difference in net profit.

For a detailed understanding of budget overrun mechanisms in architecture projects, see our dedicated analysis.

Where to Start? The First 3 Actions to Implement

If you're starting from zero -- or from informal tracking -- there's no need to aim for a complex system. Three concrete actions are enough to transform your visibility on architecture project profitability.

1. Structure Time Tracking by MOP Phase

The first building block is hour entry broken down by phase. Each team member must be able to indicate, in less than 2 minutes per day, which project and phase they worked on. The reference phases are those of the MOP law: ESQ, APS, APD, PRO, EXE, DET, AOR. Add a "Competitions / Tenders" category and an "Administration / Non-billable" category to capture total time.

The pitfall to avoid: an entry system that's too granular (by task, by lot, by drawing) that discourages team members and produces unusable data because it's incomplete. The "MOP phase" level is the right balance between precision and practicality.

2. Define an Hour Budget per Milestone from the Project Start

Before launching each project, establish an hour budget per phase. Build on your historical data if you have it, or on industry ratios:

• ESQ: 5 to 8% of total hour volume
• APS: 12 to 15%
• APD: 15 to 18%
• PRO: 20 to 25%
• EXE: 15 to 20% (variable depending on EXE detail level)
• DET: 20 to 25% (the most time-consuming phase by calendar duration)
• AOR: 3 to 5%

These ratios vary by project type (new-build vs renovation, housing vs public facility, competition vs negotiated contract). The key is to set a reference budget, even an imperfect one, so you can measure variances.

Key takeaway: An imperfect hour budget is infinitely better than no budget at all. The first estimate will be approximate. After 3 to 4 tracked projects, your historical data will let you estimate with plus or minus 10% accuracy.

3. Establish a Monthly Profitability Review

Once a month, the partner(s) meet with project managers to review the profitability of each active project. The agenda is simple:

• BCR by phase: are we on track?
• Projects on alert: which projects show a drift of more than 15%?
• Corrective actions: amendment to negotiate, resource reallocation, deliverable simplification?
• Projection update: what is the projected margin at completion?

This monthly discipline transforms profitability from a subject "discovered at the end" into a management parameter managed continuously. It also allows progressively building an internal database that improves the reliability of future estimates.

To discover how other architecture firms structure this management, browse our resources dedicated to the sector.

Architecture project profitability isn't a fate suffered at closure. It's an indicator that is managed, measured, and corrected in real time. Firms that implement structured time tracking by MOP phase, a reference hour budget, and a monthly profitability review don't just protect their margins: they strengthen their ability to negotiate amendments, estimate more accurately, and choose the projects that sustain their business.

The first step is always the same: knowing how much time you actually spend on each project. Everything else follows from that.