The Proposal Is Where Profitability Is Set — or Lost

A fee proposal makes five commitments simultaneously:

• That the work can be delivered at this price
• That this scope defines what is and isn't included
• That this fee structure fits the project's risk profile
• That the team allocated can deliver the work within the budget
• That the margin built into the fee will survive a real project

Most proposals keep none of these commitments explicitly.

They present a number — sometimes calculated carefully, more often estimated — with a scope paragraph that is broad enough to invite interpretation and a fee structure chosen because the client asked for it.

That is how firms end up delivering more work than they priced, arguing about what was included, writing off hours at billing time, and finishing a project to discover the margin was gone before the first deadline.

The fix is not a better proposal template.

It is a better understanding of how the fee should be built — and what the proposal needs to communicate to protect it.

How to Calculate a Fee That Actually Covers the Work

The most common fee calculation error in A/E firms is not greed or ambition.

It is using the wrong inputs.

A fee built from a percentage of construction cost, a competitor's rate, or a rough estimate of hours without accounting for overhead is not a fee calculation. It is a guess with a number attached.

A defensible fee has three components:

Raw Labor Cost × (1 + Overhead Factor) × Target Multiplier = Minimum Fee

Raw labor cost is what the firm pays the team to do the work — salary divided by annual billable hours, not total working hours. For most A/E staff, that is 1,600–1,700 billable hours per year, not 2,080.

Overhead factor converts raw labor cost into the true cost of putting that person on a project — covering rent, insurance, non-billable staff, software, and every other cost of running the firm. If your overhead factor is 1.65, every dollar of direct labor carries $1.65 in overhead. The true cost of that hour is $2.65 in direct and indirect cost.

Target multiplier is the spread between labor cost and billed revenue that produces a sustainable operating margin. The benchmark for A/E firms is 3.0. Below 2.65, the firm is approaching break-even. Below 2.5, it is losing money on the work regardless of how efficient the team is.

The result is not a final fee. It is a floor. The fee cannot go below this number and remain profitable. It may go above it — based on market rates, value delivered, complexity, or client relationship. But the floor is not negotiable.

→ Read: How to Price Architecture Services: A Bottom-Up Approach

→ Read: Overhead Factor Explained: The Missing Link Between Busy and Profitable

→ Read: The 3.0 Rule: Why Your Projects Aren't as Profitable as You Think

Choosing the Right Fee Structure

The fee structure is not a preference. It is a risk allocation decision.

Every fee structure transfers risk differently between the firm and the client. Choosing the wrong one for the project type means the firm absorbs risks it priced as if they didn't exist.

Fixed Fee

The firm delivers a defined scope for a fixed price. The client has cost certainty. The firm absorbs the risk of over-service.

Fixed fee works well for phases with clearly defined deliverables and predictable scope — schematic design, design development, construction documents on a well-defined building type. It requires a scope of services that is specific enough to make scope expansion visible, and an additional services process that converts scope expansion into billable work rather than absorbed cost.

Fixed fee on a poorly defined scope is not a fee structure. It is an open-ended commitment.

Hourly

The firm bills time at agreed rates. The firm is protected from over-service. The client carries cost uncertainty.

Hourly works well for early phases where scope is genuinely undefined — pre-design, feasibility, programming — and for construction administration where conditions in the field create unpredictable demands on the architect's time. Clients with fixed budgets often resist hourly, which is useful information: a client who cannot tolerate cost uncertainty on a genuinely uncertain phase is signaling a scope conversation that will be needed eventually.

Percentage of Construction Cost

Fee is set as a percentage of the project's construction budget. Simple to present, easy to compare across proposals.

The risk is structural: the percentage disconnects the fee from the firm's actual cost structure. A 7% fee on a $2M project produces a specific number — but whether that number covers the work depends entirely on the project type, delivery method, and team required. A percentage fee should always be validated against a bottom-up calculation before it goes to a client. If the percentage produces a number below the multiplier floor, the percentage is wrong.

Not-to-Exceed (NTE)

Hourly billing with a defined cap. The client has cost certainty up to the limit. The firm is protected from open-ended work — up to the limit.

NTE works well as a hybrid for phases that are mostly predictable but carry some uncertainty. The risk is in how the cap is set: firms that set NTE limits as round numbers without labor estimates and overhead applied are setting a ceiling without knowing whether it covers the work. Clients consistently treat the NTE as the price — not the maximum.

Most A/E firms choose fee structures based on what the client asks for. The better question is what the project risk requires. Client preference matters — but it should not be the only variable in the decision.

→ Read: Fee Structures for Architecture Firms: Fixed Fee, Hourly, Percentage, and NTE

How Scope Definition Protects the Fee

A fee is only as protected as the scope that surrounds it.

The most expensive word in a fee proposal is "including" when it is followed by a category rather than a deliverable.

"Including all construction documents" is a category. It invites interpretation. It does not define what is included, what phase it covers, how many design iterations are assumed, or what happens when the client asks for a fifth revision to a document set that was priced for two.

A scope that protects the fee does the opposite. It defines:

• What phases are included and what the deliverables are for each
• How many client review cycles are assumed per phase
• What consultant coordination is included — and what falls outside the scope
• What specifically triggers an additional services conversation
• What happens when the construction budget changes significantly after the fee is set

That specificity is not adversarial. It is the foundation of a clear client relationship.

Clients who understand exactly what they are getting and what costs extra are clients who approve additional services invoices. Clients who were told they were getting "full design services" are clients who dispute every invoice for work outside the original budget.

The scope of services is not a formality at the back of the proposal. It is the document that determines whether the fee holds.

→ Read: Defining Scope of Services in Architecture: What to Include, Exclude, and Protect

How to Write a Proposal That Wins at the Right Margin

A fee proposal has two jobs.

The first is to communicate the number clearly — what the fee is, what it covers, how it is structured, and what happens when the project changes.

The second is to make the case for why the fee is what it is — what the client is getting, what problems the firm solves, and why the value justifies the investment.

Most proposals do one of these well. Fewer do both.

What the proposal needs to include:

A clear project understanding — restating the client's goals in the firm's own words demonstrates that the scope was heard, not assumed.

Phase-by-phase scope of services — specific enough that inclusions and exclusions are unambiguous, organized in a way the client can follow.

The fee by phase — broken down at the phase level so the client can see where the investment goes, and so scope changes in one phase don't require renegotiating the entire fee.

The fee structure rationale — a sentence or two explaining why fixed fee, hourly, or NTE was chosen for each phase. Clients who understand the rationale are less likely to push back on the structure.

The additional services process — a brief, clear statement of what triggers an additional services conversation and how it will be handled. This is not a legal disclaimer. It is a shared operating agreement.

What the proposal should not include:

Vague scope language that seems comprehensive but commits to nothing specific.

A single lump-sum fee with no phase breakdown — this invites the client to negotiate the total without understanding what any portion covers.

A fee that was not validated against the cost floor — if the number is below the minimum profitable fee, the proposal should not go to the client until the scope or the rate is adjusted.

→ Read: How to Write an Architecture Fee Proposal

Using Historical Performance to Price More Accurately

The most accurate fee proposals use two data sources: current cost data and historical performance data.

Current cost data — overhead factor, billing rates, target multiplier — establishes what it costs to deliver work today.

Historical performance data answers the harder question: how much work does this type of project actually require?

Most A/E firms have years of completed project data. Very few have organized it in a way that informs the next proposal. Segmenting past projects by type, client, delivery method, and project manager reveals patterns that change how future fees are built:

• Which project types consistently require more coordination than estimated
• Which phases are chronically under-scoped
• Which client types generate scope changes that absorb additional services revenue
• Which delivery methods produce the strongest multipliers for the firm's team

A firm that knows its K-12 education projects consistently run at 2.6 multiplier while its commercial tenant improvement work runs at 3.4 has information that should change both how it pursues work and how it prices it.

→ Read: How A/E Firms Identify Their Most Profitable Projects and Clients

→ Read: Calculate True Project Cost with Your Overhead Factor

The Go/No-Go Decision

Not every project should be pursued.

That statement is easy to agree with in principle and difficult to act on in practice — especially when the pipeline is thin, the client is familiar, or the project type is interesting.

But the go/no-go decision is where proposal discipline starts. A firm that writes a careful, well-calculated proposal for the wrong project at the wrong fee is still writing the wrong proposal.

A structured go/no-go evaluation considers:

• Does the project type historically produce acceptable margins for this firm?
• Is the client type one that generates manageable scope changes and prompt payment?
• Is the timing compatible with current staff capacity?
• Can the fee be built to the multiplier floor at a rate the client will accept?
• Does the project advance the firm's expertise in a niche it wants to grow?

A no on two or more of these questions is not a reason to automatically decline — but it is a reason to price the risk accurately rather than optimistically.

Firms that win every proposal they submit are not successful firms. They are firms that are underpricing the work. A healthy win rate for most A/E firms is somewhere between 40–60%. Below that, rates or positioning need attention. Above 70%, the firm is almost certainly leaving money on the table.

How Proposals Connect to Every Other Part of the Firm

A fee proposal is the first operational decision of every project.

Everything downstream depends on whether it was right.

Billing — the fee structure determines how invoices are generated, how additional services are tracked, and whether billing reflects the work delivered or requires reconstruction at month end.

Project management — the phase structure and budget allocations in the proposal become the project plan. A phase under-scoped in the proposal is a project manager problem from day one.

Time tracking — logged hours only mean something when they're measured against a phase budget. If the proposal didn't create one, time tracking has no baseline to compare against.

Resource planning — the staffing committed in the proposal creates a capacity obligation. A proposal that assumes senior staff at full availability without checking the resource plan is setting up a delivery problem.

Financial metrics — the net multiplier, realization rate, and operating profit that appear in financial reports are all downstream effects of how the fee was built. A firm with consistently weak metrics almost always has a proposal problem, not a billing problem.

When the proposal is built correctly — from real cost data, with specific scope language, in the right fee structure — every other system in the firm has better inputs to work from.

When it is not, the damage runs through every downstream system simultaneously.

Proposals & Fee Structures Deep Dives

These articles break down each component of a strong fee proposal — with formulas, examples, and practical guidance for applying them to real A/E projects.

Fee Structures for Architecture Firms: Fixed Fee, Hourly, Percentage, and NTE
‍The four fee structures A/E firms use — what each one protects, what each one exposes, and how to decide which one fits the project type, client, and scope risk you're actually taking on.

How to Price Architecture Services: A Bottom-Up Approach
‍How to calculate a fee from your actual overhead factor, billing rates, and target multiplier — so the number on the proposal reflects what it actually costs to deliver the work profitably.

How to Write an Architecture Fee Proposal
‍What to include, how to structure the scope, how to present the fee, and how to make it easy for the right client to say yes — without making it easy for the wrong one to renegotiate.

Defining Scope of Services in Architecture: What to Include, Exclude, and Protect
‍How a clearly written scope of services protects the fee, prevents scope creep before it starts, and creates the foundation for billing additional services when the project changes.

Choosing the Right System Matters

Fee proposals are only as accurate as the data behind them.

Overhead factor, billing rates, utilization, historical project performance — none of these can be tracked manually across a portfolio of active projects without the data becoming stale, inconsistent, or wrong.

The right A/E software makes these inputs current, accurate, and connected — so the next proposal is built from real numbers, not last year's assumptions.

Explore:

• Best Software for Architecture and Engineering Firms (2026)
• Compare A/E Software Side-by-Side
• Buyer Guides by Discipline

The Firms That Win the Right Work Aren't the Ones Who Bid the Most

They are the ones who know their cost floor and hold it.

They calculate fees based on the overhead factor and the target multiplier — not on what competitors charge.

They choose fee structures based on project risk — not client preference.

They write scopes that define deliverables — not categories.

They have a clear additional services process, so scope expansion becomes revenue instead of absorbed cost.

They use historical performance data to price future work, so the same mistakes don't repeat on every project of the same type.

These are not complex practices.

They are disciplines that compound over time — turning every proposal into a more accurate financial commitment and every project into a more predictable margin outcome.

That is what a strong proposal system looks like in a small A/E firm.