The architect's proposal framework: five pillars that make a fee feel worth it

Search for an architectural proposal and you find the same thing again and again: a list of phases, a payment schedule and a page of exclusions. Those parts matter. Without them you are exposed on scope, on fees and on liability. But they describe a contract, not a choice. A homeowner or developer comparing practices reads that page last, after they have already decided who they trust.

The proposals that feel considered do something else first. They show the client their own project, understood better than they could put it themselves. Then they show how the practice thinks. Only after that do they lay out what gets delivered, when and for what fee. The order is the argument: judgement first, deliverables second, paperwork last.

This is also the practical answer to how to structure a proposal for a project. The brief comes first because it earns attention. Thinking comes second because it earns trust. Scope and price come next, when the client is ready to judge value rather than cost. Acceptance closes the document, so the decision and the action sit on the same page.

Compare that with a standard fee letter, which opens with the practice's services and closes with a signature block. It answers the question "what do you do?" when the client is asking "do you understand what I need?"

The executive summary is the page clients read in full, so give it real work to do. Open with their goal in their own vocabulary. If they said "more light in the kitchen and somewhere for the kids to do homework", say that, not "enhanced daylighting and flexible living space". Then add the thing they did not mention: the north-facing garden that makes a rear extension darker than they expect, or the conservation area that shapes what the roof can do. That paragraph is where the client decides you are worth the fee.

Next, show a point of view before any fees appear. A site analysis sketch, a massing diagram or a pair of precedent images can carry more weight than a page of text. Use visuals to show thinking, not to decorate. Every image should answer a question: why this orientation, why this height, why keep that wall.

The firm profile belongs here too, but cut it down. Pick the past projects closest to this brief in type, scale and constraint, and name the people who will actually run the job. A long list of awards and sectors reads as a brochure. A short, relevant selection reads as evidence.

Phases give a client something they rarely get from professional services: a map. Use the names they will hear from builders and planners, and explain each in a sentence. Schematic design settles the big moves. Design development fixes materials, structure and services. Construction documents produce the drawings a contractor prices and builds from. Bidding helps the client compare tenders. Construction administration covers site visits, queries and sign-off while the build happens.

Tie a fee to each phase and a payment to the end of each, so the client pays for things they can see. Whether you charge a fixed fee per phase or a percentage of construction cost, show how the total breaks down. Clients accept a higher number more easily when they can see what each part buys.

Construction administration deserves its own line. Many practices price it separately, as a time-based fee, because nobody knows yet how long the build or the contractor will take. Saying so up front avoids an awkward conversation halfway through the job.

Write exclusions as sentences, not legal fragments. "Planning application fees are paid by you directly to the council" is clearer than "Statutory fees excluded". Name the additional services a client is likely to need, such as a structural engineer, a party wall surveyor or a cost consultant, and say how you charge if they ask you to arrange them. Then add a short contingency note: a margin on time and cost for things nobody controls, like weather, material prices and planning decisions.

Illustrative example: a couple want a 180 m² family home extended at the rear, with a larger kitchen and a ground-floor home office. The fictional practice writes the brief reframe like this.

Brief reframe: "You want a kitchen the whole family can use at once, and a quiet room for working from home. Your garden faces north, so we will bring light in from above rather than from the back wall, and keep the home office at the front where it is calmest."

Notice what that paragraph does. It uses the client's words, adds a site insight and previews a design move without drawing anything yet.

Terms protect you, so keep them, but write them for a client to read. Cover client responsibilities such as information, access and timely decisions. Cover delays outside your control, rising material prices, insurance on site and what happens if the project pauses. A page of short paragraphs beats a dense legal schedule, and you can link to full terms for anyone who wants them.

Then remove every step between "yes" and a signed agreement. This is where Formlio fits. You build the proposal from blocks: the brief, a gallery of sketches, a timeline of phases, a pricing block with the fee by phase, and an agreement block where the client signs with an e-signature or a Slide-to-Approve button. It opens as a web page on any device, in your own fonts and colours.

A PDF goes into a black box. A Formlio document reports back: who opened it, what they read, when they signed. You get a notification when the client opens the proposal and can see which sections they spent time on. If they lingered on the fee table, call about the fee. If they went straight to the sketches, talk about the design. Follow up when they are reading, not a week later.

As for AI, treat it as an editor. It can help you turn rough notes into clean paragraphs or suggest a clearer order for your terms. It cannot read a site, weigh a planning risk or decide what your time is worth.