Architecture Proposal Template: How Firms Package Scope and Fees

Oil painting of an open proposal booklet on a walnut table with a fountain pen, soft lamplight, and architectural drawings beneath
Package scope and fees with clarity clients trust
By Sofia Serrano  ·  

An architecture proposal is a decision document. It tells a client what you will do, how you will work, what it costs, and where the boundaries sit. A strong template does not invent a new personality for every pursuit. It gives the firm a reliable structure so each proposal can be tailored quickly without losing accuracy or tone. Weak proposals bury fees, leave scope ambiguous, or read like a brochure with a price attached. Clients compare them side by side. Clarity wins more often than length.

This guide outlines a practical architecture proposal template for firms that want to package scope and fees with the same care they give drawings. It is a business instrument, not a marketing monologue. For how proposals sit inside a wider practice growth system, see our work with architecture practices.

What the proposal must accomplish

A proposal should make three things obvious: the problem you understand, the services you will provide, and the commercial terms. Everything else supports those three. Clients should finish reading with fewer questions, not more. If a section does not help a decision-maker approve or decline, cut it or move it to an appendix.

Tone should match the firm: precise, calm, and specific. Avoid superlatives about your own excellence. Show understanding of the site, program, and constraints instead. Name the client's stated goals in their language. A proposal that proves you listened often outranks a proposal that only shows past work.

Recommended structure

Use a consistent order so internal teams can assemble packages under deadline and clients learn your rhythm. A proven sequence:

Keep the main narrative short enough to read in one sitting. Move extended resumes, full project sheets, and legal boilerplates to appendices when needed. Decision-makers skim; give them a clean path to the fee and the scope boundary.

Scope of services by phase

Break services into phases the client can map to decisions and cash flow: pre-design or feasibility, schematic design, design development, construction documents, bidding or negotiation support, and construction administration, adjusted for your market and project type. For each phase, list primary tasks and primary deliverables in plain language. If you use percentage-of-construction or fixed fees, state the basis clearly. If the program is incomplete, say what assumptions you are pricing against and what triggers a revision.

Client responsibilities belong in the scope section. Approvals, surveys, geotechnical reports, existing drawings, and decision timelines affect your ability to perform. Writing them down protects both parties and reduces later friction. The same is true for consultant coordination: name which consultants you will manage, which the client engages directly, and how information flows.

Fees, expenses, and commercial clarity

Present fees in a table when possible: phase, fee, and billing timing. State whether amounts are fixed, hourly with a cap, or percentage-based, and what happens if the project pauses or restarts. Expense policy should be explicit: reimbursables, travel, printing, models, and third-party costs. Ambiguity here generates more conflict than almost any design disagreement.

Optional services deserve their own line items: renderings beyond an agreed set, extra meetings, value-engineering rounds, or extended CA. Pricing options up front is cleaner than absorbing scope creep later. If you offer alternate fee structures, present them as clear choices with trade-offs, not as a dense paragraph of conditions.

Exclusions and risk language

Exclusions are a service to the client. List what is outside this agreement: certain consultants, permitting fees paid to authorities, hazardous materials, furniture design, or post-occupancy services if not included. Soft language that only implies exclusions creates disputes. Direct language prevents them.

Reference the form of agreement you intend to use and note that full terms govern. Do not try to litigate the entire contract inside the proposal. Do flag material commercial points: ownership of instruments of service, limitation themes your counsel requires, and payment terms. Align proposal language with the contract template so you never promise something the agreement later withdraws.

Team, experience, and proof without padding

Introduce the people who will actually work on the project. Clients distrust bait-and-switch bios. Select two or three relevant projects with short captions that map to this pursuit's typology, scale, or constraint. Full portfolios belong on the website; the proposal needs proof of fit. Link to project pages when helpful rather than pasting every image into a forty-page PDF.

If the pursuit is competitive, address differentiators only where they are factual: prior work with the same building type, a specific technical method, or a delivery approach suited to the schedule. Empty claims of superior service weaken the document.

For public or institutional pursuits, map the proposal sections to the scoring criteria in the RFP. Make it easy for a selection committee to find responses to each requirement. A beautiful narrative that ignores their checklist still loses to a clearer, if less elegant, competitor package.

Production standards and template hygiene

Build the template in a tool the office will maintain: InDesign, a well-structured Word system, or a controlled Google Docs master with locked styles. Enforce typography, margins, and image rules from the brand system. Version the template. Archive winning and losing proposals so you can refine language that works. Train staff on how to customize without breaking the structure.

Before sending, run a short internal checklist: client name spelling, fee math, phase totals, exclusions, schedule assumptions, and who signs. A single wrong number can undo months of relationship work. For firms refining the full client journey from site inquiry to signed agreement, Nakada Design supports architecture practices on materials, site, and follow-up systems. See our architects page or inquire when you want that sequence tightened end to end.

Common questions

What should an architecture proposal template include?

A clear understanding of the project, phased scope and deliverables, schedule assumptions, fees and expenses, exclusions, team and relevant experience, and a clean next step. Legal detail belongs in the agreement, summarized where needed in the proposal.

How long should an architecture proposal be?

Long enough to define scope and commercial terms without forcing a decision-maker to hunt for the fee. Many successful proposals keep the core narrative short and move extended credentials to appendices.

Should fees appear early or late in the document?

Fees should be easy to find and supported by the scope that precedes them. Burying fees or scattering numbers across pages creates distrust. A clear table after the scope is usually the most respectful structure.

How often should firms update their proposal template?

Review the template at least annually, and after any repeated client confusion or lost pursuit where structure was a factor. Update fee language, phase names, and exclusions when practice methods change.