Architecture Client Proposals, Contracts, and Closing Strategies for Small Practices
Winning a project starts long before you submit a fee proposal — it begins with the first client conversation and continues through every interaction until a contract is signed. Most architects are technically excellent but commercially undertrained: they underestimate the importance of qualifying prospects, struggle to present fees confidently, and lose projects on avoidable contract negotiation issues. This guide covers the full sales process from initial inquiry to signed contract.
READY TO TAKE ACTION?
Use the free LaunchAdvisor checklist to track every step in this guide.
Qualifying Prospects: Not Every Inquiry Is a Project
The first step in client proposals is qualifying the prospect — determining whether the inquiry can realistically become a project before you invest time in proposal preparation. Four qualification questions:
1. Is the project feasible? Does the client's vision match their budget? A homeowner who wants a $2M custom home on a $500K budget is not a client — they need education, not an architecture proposal.
2. Is the timeline realistic? Projects starting 'someday' are not projects. A client with a genuine motivating event (building permit already filed, lease expiring, school board authorization received) is a real prospect.
3. Is the client decisive? Clients who involve 10 family members in every decision, cannot articulate their priorities, or have already gone through two architects for the same project are high-friction risks.
4. Is the site and scope definable? Can you scope and price this project with reasonable confidence from the available information?
Ask direct questions during the initial conversation: 'What is your target construction budget?' 'When are you hoping to have construction complete?' 'Have you worked with an architect before?' These questions seem blunt but are expected by clients who have hired professionals before. Clients who refuse to answer basic scoping questions are signaling difficult relationships ahead.
Structuring a Compelling Architecture Proposal
An architecture proposal is both a scope document and a sales document. It needs to convince the client you understand their project, demonstrate your qualifications, and present your fee in the most favorable framing possible.
Proposal structure:
1. Project understanding: 2–3 paragraphs showing you listened carefully to the client's goals, constraints, and priorities. Paraphrase what they told you — nothing demonstrates understanding like demonstrating you heard them.
2. Your approach: Briefly describe how you will approach the project — your process, your design philosophy as it applies to this specific project, any relevant experience.
3. Relevant portfolio: 2–4 projects similar to theirs. Include brief project narrative, construction budget, and outcome. Do not show every project you have ever done.
4. Team qualifications: Your biography and any key consultants. Emphasize relevant licensure and experience.
5. Scope of services: A clear list of what is included in Basic Services and what is listed as Additional Services. Clarity here prevents disputes.
6. Fee: Present the fee in the frame that makes it most compelling — percentage of construction cost communicates proportionality; lump sum by phase communicates budget certainty. Include the payment schedule.
7. Next steps: A clear call to action — 'We can have a contract ready within 2 business days of your go-ahead.'
Navigating AIA Contract Negotiations
Most residential clients sign your proposed AIA B101 or B105 with minimal changes. Sophisticated commercial clients — developers, institutions, corporations — often send redlines. Here is how to navigate common negotiation points:
Scope reduction requests: If the client wants to reduce fee by cutting scope (e.g., removing Construction Administration), be explicit about what they are giving up — they take on the risk of construction-phase design decisions without professional oversight. Many architects decline CA scope reductions entirely, preferring to lose the project rather than stake their professional reputation on a project executed without their CA involvement.
Liability cap addition: Many developers request a mutual limitation of liability. This is generally reasonable and protective for both parties. Agree to a mutual cap (applies to both architect and owner) sized at your E&O insurance limit or 2–3x your fee, whichever is greater. Run any LOL language by your E&O carrier.
IP ownership demand: Some clients (particularly technology companies and sophisticated developers) will insist on owning the copyright in the drawings. This is a significant value transfer — price it accordingly (typically 1.5–2x standard fee for IP transfer). Never agree to IP transfer as a routine concession.
Owner redlines removing consequential damage waiver: Resist this strongly. The mutual waiver in B101 Section 8.1.3 is there to protect both parties from outsized liability. If an owner insists on removing it on their side, walk away or significantly increase your fee and insurance limits.
Handling Common Client Objections
Three objections arise in almost every architecture proposal process:
'Your fee is higher than another architect we spoke to': Ask what the other architect's scope includes — often the lower fee excludes CA services, uses less experienced staff, or assumes a simpler specification level. If the scope is genuinely comparable, stand behind your fee and explain what your practice specifically brings to this project. Do not immediately match or beat the competitor.
'We do not know our construction budget yet, so we cannot agree to a percentage fee': Propose a phased approach — a paid programming phase (hourly or small lump sum) to establish the budget and scope before committing to the full project fee. This is standard practice and demonstrates sophisticated client management.
'We have been burned by architects before who did not communicate well': This is an opportunity, not an objection. Describe specifically how your practice communicates with clients — meeting frequency, reporting format, response time commitment. Clients who have had bad experiences with architects become your most loyal long-term clients if you demonstrably deliver what their previous architect failed to provide.
Client Onboarding: The First 30 Days
How you onboard a new client sets the tone for the entire project relationship. A strong first 30 days establishes professional confidence and prevents early misunderstandings:
Week 1 — Contract execution and project kick-off: Counter-sign the agreement, issue the first invoice (retainer), and schedule a project kick-off meeting. At the kick-off meeting, review the project schedule, confirm the program, clarify the owner's decision-making process, and establish communication preferences.
Week 2 — Document and site information gathering: Collect all existing information — previous drawings, surveys, geotechnical reports, HOA requirements, deed restrictions. Conduct a thorough site visit and document existing conditions photographically.
Week 3–4 — Schematic Design initiation: Begin design work. Share preliminary ideas earlier rather than later — clients who see nothing for 4 weeks become anxious. Even rough massing studies or precedent image sharing demonstrates progress and engagement.
Establish from day one: response time expectations (most clients expect 24-hour email response), meeting cadence (weekly or bi-weekly check-ins during active design phases), and your billing cycle (monthly invoicing is standard).
RECOMMENDED TOOLS
AIA Contract Documents
AIA B101 and B105 owner-architect agreements — the industry standard contracts for client proposal and project execution
Monograph
Generate professional client invoices and track project fee progress from proposal through project completion
AIA (American Institute of Architects)
AIA practice management resources including contract negotiation guidance and professional practice standards
Some links above are affiliate links. We may earn a commission if you sign up — at no extra cost to you.
FREQUENTLY ASKED QUESTIONS
How long should an architecture proposal be?
For residential projects: 4–8 pages is typically appropriate. Long enough to demonstrate understanding and present qualifications, short enough that a busy homeowner will actually read it. For institutional and commercial RFQ/RFP responses: follow the agency's specified page limits exactly — exceeding them disqualifies submissions in many public procurements. For commercial client proposals: 6–12 pages. Visual quality matters as much as content length — a beautifully laid-out 6-page proposal outperforms a wordy 15-page document.
Should I require a retainer before starting design work?
Yes, always. A retainer at contract execution is standard professional practice — it confirms the client's commitment, funds your initial work, and filters out tire-kickers who are collecting proposals with no intention of moving forward. For residential clients, 20–25% of the SD fee is typical. For commercial clients, 20% of the first-phase fee. Make the retainer application clear in your B101 — it is typically credited against the final invoice or a specified invoice milestone.
What should I do if a client asks for design ideas before signing a contract?
Politely decline to provide design concepts without a signed agreement and retainer. You can share portfolio images, describe your approach, and discuss the project conceptually — but generating actual design ideas is billable professional service. Clients who ask for free design concepts are either testing your boundaries (often these become great clients once boundaries are established) or planning to take your ideas to a cheaper provider. Either way, professional practice requires a contract before design begins.