How to Write a Fee Proposal for Architectural Services

Key takeaways

• A complete fee proposal for architectural services has seven sections: scope summary, fee structure, phase-by-phase services, assumptions, exclusions, schedule, and payment terms.

• Choose between lump sum, hourly with a not-to-exceed cap, or percentage of construction cost based on how well the scope is defined and how fixed the budget is.

• Break the fee into SD, DD, CD, permitting, bidding, and CA so the client sees what each dollar buys and change orders have a defensible basis.

• When a client pushes on price, trade scope before cutting your rate, because a discounted rate resets every future negotiation.

• Once signed, a fee proposal becomes a project budget: track hours against each phase fee so overruns surface before invoice time.

A strong fee proposal for architectural services names the fee structure (lump sum, hourly, or percentage of construction cost), scopes services phase by phase, and lists exclusions and assumptions before the client can argue about them. This guide walks through each section, then prices the same 4,000 sq ft commercial fit-out under all three structures with the math shown.

What should a fee proposal for architectural services include?

A fee proposal for architectural services needs seven sections: scope summary, fee structure, phase-by-phase services, assumptions, exclusions, schedule, and payment terms. Miss any one and you invite scope creep or a fee negotiation you can't win, because the client has nothing to point to except your number.

The copy-ready structure: seven sections in order

1. Scope summary. Two or three sentences naming the project, site, and what you will deliver. No marketing language.

2. Fee structure. Lump sum, hourly, or percentage of construction cost, stated once with the basis made explicit. Architectural institutes such as the RAIC and AIA describe these three structures as the common bases, with the choice depending on project type and how well scope is defined. If your basis is a percentage, say what cost it applies to, because construction cost, construction budget, and net construction cost are three different numbers and clients will assume whichever one is smallest.

3. Services by phase. List each phase, what you deliver at its end, and the fee allocated to it. This is what you will fall back on during additional-services discussions.

4. Assumptions. What you expect to be true: number of revisions, client decision timelines, approvals already in hand.

5. Exclusions. What you will not do: permit fees, FF&E procurement, CA site visits beyond a stated number, survey, structural engineering.

6. Schedule. Your timeline and the client obligations it depends on.

7. Payment terms. Invoicing cadence, retainage, and what happens on suspension.

What belongs in each section (and what doesn't)

Keep sections 1 through 3 concrete and sections 4 and 5 blunt. Anything you would argue about in month six belongs in writing in month zero. Once a proposal is accepted, every phase deliverable, assumption, and exclusion becomes a tracked obligation against your project forecast, which is why we keep proposal scope and delivery in one relational system rather than a document folder (see FAQ — Systems for Architects | Househouse Systems).

Which fee structure should you propose: lump sum, hourly, or percentage of construction cost?

Lump sum: when a fixed fee protects you and when it doesn't

A lump sum gives the client cost certainty and gives you the upside if you deliver efficiently. It protects you only when scope is defined by phase and exclusions are tight; on vague scope with a hands-off client, you absorb every revision. Use it for well-briefed commercial work where you control the deliverables list.

Hourly with a not-to-exceed cap

Hourly billing pays for every hour, including scope creep, which is why clients distrust it on its own. Adding a not-to-exceed cap converts it into something a client can approve while you still track time honestly. It fits early-stage work, feasibility studies, and projects where the client keeps changing the brief.

Percentage of construction cost: the math and the risks

A percentage fee scales with the build, so a costlier project pays you more without renegotiation. The risk runs both ways: if construction cost drops, your fee drops even though your hours don't, and if the client inflates the budget, you look expensive. It works best when the construction budget is fixed and credible before you propose.

Worked example: one project, three structures

Say a 12,000 sq ft office fit-out has a $2.4M construction budget and you estimate 900 hours at a $125 blended rate.

Whichever structure you pick, the proposal you send should carry the same phase-by-phase math. A tool that generates the fee table as a clean PDF (PDF Studio for Architecture Firms | Househouse Systems) keeps the numbers consistent between the estimate and the document the client signs.

How do you scope architectural services phases in a fee proposal?

Break the fee into Schematic Design, Design Development, Construction Documents, permitting, bidding, and Construction Administration so the client sees what each dollar buys. The AIA B101 standard form defines these phases and its additional services language, which gives you a defensible baseline when a client asks why permitting costs what it does.

Phase-by-phase fee allocation with illustrative percentages

A typical split for a commercial fit-out might look like: SD 15%, DD 20%, CD 35%, permitting 10%, bidding 5%, CA 15%. These are illustrative, not benchmarks. Adjust for project type: a heavy CA building like a restaurant tenant improvement shifts weight toward Construction Administration, while a design-forward retail concept shifts it toward DD.

Scoping FF&E, specs, and deliverables per phase

Name the deliverable each phase produces: SD ends with a concept package, DD with coordinated drawings and outline spec, CD with full specs and FF&E schedules. State explicitly whether FF&E procurement and spec writing sit inside the base fee or ride as additional services, because that ambiguity is where change orders and resentment start.

Track those phase budgets against hours actually spent once the proposal is accepted, so your next fee proposal for architectural services is priced from evidence. We built Househouse Systems for exactly that: one relational database underneath projects, phases, and deliverables, where you enter data once and everything updates. See how firms use it at Custom Apps for Architecture Firms | Househouse Systems.

What exclusions and assumptions belong in an architect fee proposal?

Assumptions that set the baseline

State what you priced against: one round of client revisions per phase, decisions made within five business days of each submission, and a single point of contact with authority to approve. Add site assumptions too, such as existing conditions being as shown in the documents you received. If any assumption breaks, the fee becomes negotiable, and you have the paragraph to point to.

Exclusions that protect the fee

List in plain language: FF&E procurement beyond specification, landscape and interior design by others, permits and expediter fees, multiple renderings or marketing imagery, and attendance at more than a stated number of site visits per phase. Client-readable beats lawyerly. A principal can hand this list to a client without translation.

How to price additional services and RFI/CA overage

Define additional services as anything outside the stated scope, billed hourly at named rates, with written authorization before work starts. Cap RFI responses and CA reviews in the base fee; overage triggers the hourly rate. Track which assumptions broke and which exclusions got tested in one place, like the Internal Dashboard for Architecture Firms | Househouse Systems, so your next fee proposal prices the risk you actually absorbed.

How do you justify your fee when a client says it's too high?

Trade scope, not margin

When a client pushes on price, cut deliverables before you cut your rate. Dropping your hourly rate resets every future negotiation with that client; removing a phase or narrowing a deliverable keeps your economics intact. Make the trade explicit: "We can bring the fee to $X by moving FF&E selection to a time-boxed allowance." That converts a discount conversation into a scope conversation, which you control.

Anchor the discussion in market reality. Median compensation data from the AIA Compensation Survey shows what architects at your staff's experience levels actually cost to employ, before overhead and profit. If your rate sits within that range, say so.

Showing the client what each phase buys

Break the fee down by phase so "too high" becomes "which part?" Clients rarely object to construction documents priced against a $4M build; they object to an opaque lump sum. Itemized phases also give you a defensible basis for change orders during CA.

Tracking that breakdown against hours actually spent is where spreadsheets break. We built AI Workflows for Architecture Firms | Househouse Systems around one relational database so fee proposals, project forecasts, and delivered hours stay connected, and you can see per-phase margin while the project is still running.

How does a fee proposal differ from a proposal for design services?

A fee proposal is a commercial document: price, payment schedule, phase scope, exclusions, assumptions, and validity period. A proposal for design services sells your approach, team, and design thinking, and usually appears earlier, in RFPs or interviews, before a client has picked you.

Clients expect both at different moments. Design services proposals win the shortlist; the fee proposal closes it. In practice many firms merge them, but keep the commercial terms in their own section so a client's procurement team can extract numbers without reading your design narrative. If a client asks for "a proposal," ask which one they mean.

When should you walk away from a project instead of sending a fee proposal?

Some projects cost you money even if you win them. Walk away when the client refuses to share a budget, because you'll price blind and anchor to their guess anyway. Walk away when the brief keeps expanding before you've signed: a "small renovation" with a full FF&E package, a rezoning application, and CA attendance is a different fee, and a client who won't acknowledge that now won't later.

Also reconsider when the RFP is clearly a three-bid price check with no interview stage, or when the construction budget is half of what the scope implies. One test: if you'd resent the fee at hour ten, the proposal isn't worth writing. Purpose-built practice management tools exist because firms learned this lesson through lost margins; don't relearn it per project.

How do you track accepted fee proposals against actual project delivery?

From fee proposal to project forecast

The moment a client signs, your fee proposal stops being a sales document and becomes a budget. Each phase line is now a spending limit: if CA is running long and RFI volume is climbing, you need to see it against the phase fee before you've burned through it. Tracking that in spreadsheets means copying the proposal into a new file, then reconciling timesheets against it by hand every month. Firms that skip this step usually discover the overrun at invoice time, when it's too late to manage.

One source of truth for fees, phases, and deliverables

The fix is keeping the signed fee breakdown, actual hours, and deliverables in the same place, so the forecast updates as work happens. That's the problem Househouse Systems is built for: one relational database underneath projects, phases, fees, and deliverables. Enter it once; everything updates. A principal can open a project and see the fee proposal, hours burned per phase, and what's outstanding without opening email or folders. The practical payoff shows up at renewal and renegotiation: when a repeat client asks for a proposal on a similar building, you price it from the recorded hours and margin of the last one rather than from memory, and the assumptions that broke last time become explicit line items this time instead of silent losses buried in your rate.

To be fair about where it falls short: Househouse is a custom system, not off-the-shelf software like Monograph or Programa, so there's an implementation cost ($9,000 base plus $200/user/month for six months) and no public product tour to click through. If you want a tool you can buy this afternoon, those products exist. If you want the forecast, the fees, and the FF&E schedule in one system you own, that's the trade.

FAQ

How much should an architect charge as a percentage of construction cost?

There is no universal percentage; it varies by project type, scope clarity, and how much of the build you are responsible for. In the worked example above, a 12,000 sq ft office fit-out priced at 4.5% of a $2.4M construction budget. Treat any percentage as illustrative and always state which cost figure it applies to.

Do you include reimbursables and consultants in an architect fee proposal?

No. List reimbursables such as printing, travel, and permit fees, plus consultant fees for structural, MEP, and survey work, as separate line items outside your base fee. State whether you mark up reimbursables and whether you carry the consultant contracts or the client engages them directly.

What is a typical hourly rate for architectural services in 2025?

Rates vary widely by market, experience level, and overhead, so quoting a single number invites a bad anchor. The worked example above uses a $125 blended rate for a commercial fit-out, which is illustrative rather than a benchmark. Price from your actual staff costs plus overhead and profit, then check against published compensation data.

Should a fee proposal include a payment schedule tied to phases?

Yes. Tie invoicing to phase completion or monthly progress, state retainage terms, and specify what happens if the project is suspended. A phase-tied schedule gives you leverage: if the client stalls during Design Development, the unpaid milestone signals the cost of delay without you having to argue it.