How to Write an Architecture Fee Proposal:
The Document That Sets Every Project's Profitability
Most architecture fee proposals do one job reasonably well — presenting a number. The best proposals do three jobs simultaneously: they communicate what the client is getting, establish the boundaries that protect the fee, and make it easy for the right client to say yes. Here's how to write one that does all three.
A Fee Proposal Is Not a Sales Document. It's a Financial Agreement.
Most A/E firms treat the fee proposal as the closing document in a sales process. Present the credentials, describe the services, name the number, and hope the client says yes.
That framing misses what the proposal actually does.
A fee proposal is the first financial agreement of the project. Every commitment the firm makes about what is included, what costs extra, how billing will work, and what happens when the scope changes originates here. If those commitments are vague, the firm will spend the rest of the project negotiating what they meant.
A proposal written with precision does four things simultaneously:
- It communicates the value of the services clearly enough that the fee makes sense to the client
- It defines the scope specifically enough that boundaries are visible to both parties
- It structures the fee in a way that matches the project's risk profile
- It establishes the additional services process before scope changes occur — not after
Most proposals do the first passably. Very few do all four consistently.
The Cost of a Weak Proposal
A vague proposal does not just create friction. It creates specific, recurring costs.
Every hour of work that falls into the gray zone between "included" and "additional" is a billing conversation that the firm will either win at the cost of the client relationship or lose at the cost of its margin. Firms that write vague proposals are not saving time on the front end. They are trading a few hours of careful scope writing for months of billing uncertainty on every project.
A well-written proposal takes longer to produce. It returns that time many times over in fewer write-offs, fewer scope disputes, and fewer billing conversations that should never have been necessary.
The hours spent writing a precise proposal are the cheapest hours the firm will spend on the project.
Every ambiguity in the proposal becomes a conversation later. Some of those conversations go well. Many don't. A scope paragraph written carefully at proposal time eliminates dozens of billing disputes that would otherwise accumulate across the life of the project.
The Seven Components of a Strong Fee Proposal
1. Project Understanding
The proposal should open by restating the client's goals, program, and project context in the firm's own words.
This is not a summary of the RFP. It is evidence that the firm listened — that the scope of services that follows was built around this specific project, not copied from the last proposal.
A strong project understanding section demonstrates:
- Comprehension of what the client is trying to accomplish
- Awareness of the project's constraints — budget, timeline, site conditions, regulatory context
- Any risks or complexities the firm has identified that the client may not have fully considered
Clients who feel understood are more likely to accept the fee. They are also less likely to dispute scope later, because the proposal demonstrated from the start that the firm grasped what the project required.
2. Team and Qualifications
A brief introduction to the project team — who will lead, who will manage, who will produce — with specific relevant experience.
The goal is not to list credentials. It is to show the client that the team has done this before and that the people named will actually be on the project. Proposals that name principals in the qualifications section and deliver junior staff on the project are a common source of client dissatisfaction and scope disputes.
3. Scope of Services — Phase by Phase
This is the most important section of the proposal.
The scope of services defines what the firm will deliver, organized by phase. It is the document that determines whether the fee holds — not the fee number itself.
A scope that protects the fee is specific about deliverables, not just activities. The difference:
Activity-based scope: "Prepare construction documents"
Deliverable-based scope: "Prepare a construction document set including architectural drawings, specifications, and coordination with structural and MEP engineers of record. Assumes two client review cycles per phase. Additional review cycles billed as additional services."
The deliverable-based scope defines what is included, how many iterations are assumed, and what explicitly falls outside. The activity-based scope invites the client to define "construction documents" in whatever way is most favorable to them at billing time.
Every phase of the scope should include:
- The deliverables the firm will produce
- The number of review or revision cycles assumed
- What consultant coordination is included
- What is specifically excluded or listed as an additional service
→ Read: Defining Scope of Services in Architecture: What to Include, Exclude, and Protect
4. Fee by Phase
The fee should be presented by phase — not as a single lump sum.
A phase-by-phase fee breakdown serves multiple purposes. It shows the client where the investment goes. It makes the total fee easier to understand and accept. And it creates a structure that protects the firm when scope changes in a single phase — a change to the construction documents phase does not require renegotiating the entire fee.
Each phase entry should include:
- The phase name and brief description
- The fee for that phase
- The fee structure for that phase (fixed fee, hourly, NTE)
- Any phase-specific conditions (e.g., "Assumes construction budget of $X. Significant changes to program or budget may affect this fee.")
5. Additional Services
Every proposal should include a clear statement of what constitutes additional services and how they will be handled.
This is not a legal disclaimer. It is a shared operating agreement that both parties review before the project starts. Its purpose is to make scope expansion recognizable — so when additional work occurs, both the firm and the client understand what is happening and what the process is.
An effective additional services clause:
- Defines the categories of work that fall outside the scope (redesign after approved documents, extended construction administration, third-party coordination not listed in the scope)
- States how additional services will be authorized (written approval before proceeding)
- States how they will be billed (hourly at the rates listed, or as a fixed fee for defined tasks)
Firms that include this language clearly in every proposal find that additional services conversations are shorter, less adversarial, and more often successful. The client was told from the start how this works.
6. Reimbursable Expenses
Define what reimbursable expenses are and how they will be billed.
Typical reimbursables: printing, travel, permit fees paid on the client's behalf, subconsultant markups. Define what is included in the fee and what will be billed at cost or cost-plus-markup.
Proposals that leave reimbursables undefined create invoice disputes on almost every project. The client assumes printing is included. The firm assumes it is reimbursable. That conversation is entirely avoidable with a single paragraph in the proposal.
7. Schedule and Terms
A brief statement of the anticipated project schedule, billing cadence, payment terms, and what the firm needs from the client to begin and maintain progress.
Billing cadence matters: monthly billing with net-30 terms is the standard. Proposals that establish this upfront create the expectation rather than negotiating it later.
A single lump-sum fee with no phase breakdown is an invitation to negotiate the total.
Clients who see a lump sum focus on the number. Clients who see a phase breakdown focus on the value of each phase. The same total fee presented by phase is consistently easier to accept — and significantly harder to renegotiate piecemeal.
How to Present the Fee
The way a fee is presented affects whether it is accepted — not just the number itself.
Lead with value, not scope.
Most proposals present the scope first and the fee last. The client reads through pages of deliverables and then encounters the fee as a conclusion. A stronger approach leads with what the client cares about — their goals, their problems, what the firm will accomplish for them — and positions the scope as the explanation of how that outcome will be delivered.
The fee then follows not as a price tag but as the investment required to achieve the outcome the client has just read about.
Contextualize the fee without apologizing for it.
Firms that present fees tentatively — with hedging language, excessive caveats, or preemptive discounting — signal that they are not confident the fee is justified. That signal invites negotiation.
A fee presented directly — with a clear explanation of what it covers and why it reflects the work required — communicates confidence. Confidence does not mean inflexibility. It means the firm knows what the work costs and has priced it accordingly.
Address the obvious questions before they are asked.
Most clients reviewing a fee proposal are asking some version of three questions: What am I getting? Why does it cost this much? What happens if the project changes?
A well-written proposal answers all three before the client has to ask. The scope of services answers the first. The fee breakdown and bottom-up rationale (summarized briefly, not presented as a spreadsheet) answers the second. The additional services clause answers the third.
Present options where appropriate.
For some clients and project types, presenting two or three clearly defined scope options — a comprehensive scope at the full fee, a reduced scope at a lower fee, and an expanded scope at a higher fee — can significantly improve win rates. The client is no longer deciding between this proposal and a competitor's. They are deciding which version of this proposal fits their budget and needs.
This approach works best when the scope differences between options are genuine and clearly explained — not when the lower option is the same scope with the fee arbitrarily reduced.
What not to include:
Vague scope language included to make the proposal look comprehensive while committing to nothing specific. Clients notice this eventually, usually at billing time.
A fee that has not been 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 is reduced or the rate is adjusted.
Excessive credentials that are not relevant to this specific project. Qualifications should be specific to the project type, not a general firm portfolio.
A fee presented with confidence and a clear rationale closes faster and negotiates less than a fee presented tentatively.
Hedging language, preemptive discounts, and excessive caveats signal that the firm is not sure the fee is justified. That signal is an invitation to push back. Know the cost floor, price above it, and present the fee as what it is — an accurate reflection of what the work requires.
The Proposal Review — Before It Goes to the Client
Every fee proposal should be reviewed by a second person before it leaves the firm.
Not for grammar. For financial integrity and scope accuracy.
The review should confirm:
Fee integrity:
- Has the fee been calculated against the cost floor using current overhead factor and billing rates?
- Does the fee by phase add up correctly?
- Is the fee structure for each phase appropriate for the scope clarity of that phase?
- Have reimbursables and additional services been addressed?
Scope accuracy:
- Is the scope specific enough at the deliverable level to make additional work recognizable?
- Are the number of revision cycles and review rounds clearly stated?
- Are consultant inclusions and exclusions clearly defined?
- Is there anything in the scope language that a client could reasonably interpret as including work the firm intends to bill as additional?
Client and project fit:
- Does the project type historically produce acceptable margins for this firm?
- Does the client type generate manageable scope changes and prompt payment?
- Is the timing compatible with current staff capacity?
This review is not a formality. Proposals that pass this check produce better projects. Proposals that skip it are where the billing problems that show up six months later begin.
After the Proposal Is Accepted
A signed proposal is the foundation of the project — but it is not the end of the scope conversation.
As the project progresses, the scope of services in the proposal should be referenced actively: in project kickoff meetings, in phase transitions, and whenever client requests fall outside what was defined. The proposal is not a document filed away after signing. It is a working reference that protects both the firm's margin and the client's expectations throughout the project.
Firms that treat the proposal as a living reference — and that have the additional services conversation early when scope expands — consistently outperform firms that treat it as a closing document and never look at it again.
Cut Your Billing Time by 60% Within 90 Days — Or We Refund Every Penny
We're so confident BaseBuilders will transform your billing process that we're putting our money where our mouth is.
BaseBuilders’ easy-to-use software is specifically designed to help small to mid-sized firms track time, manage projects, stay on top of expenses, and more. We’ll handle the invoicing for you so you can focus on growing your firm and designing wonderful spaces.