Architecture and Design Firm Presentation Template

Architecture and interior design firms present at every stage of a project: pursuit of the commission, conceptual design review, design development, construction documentation, and project delivery. Each of these presentations has a different audience and a different objective. The firm that structures its presentations to match these objectives wins more work and keeps clients better informed.

Firm Capability Statement

The capability statement is often the first document a prospective client reviews. It must do two things: establish competence and differentiate the firm.

Firm overview. Founding year, size, practice areas, and geographic reach. Two to three sentences — clients do not need a history lesson; they need to understand what you do and at what scale.

Core practice areas. For a multi-disciplinary firm, segment your work clearly: commercial, residential, hospitality, civic, institutional, mixed-use. Include the percentage of project volume each represents so the client understands your primary focus.

Representative project portfolio. Five to eight projects, with one image per project, a brief project description, project size (square footage or project cost), client name, and completion year. Do not show every project. Show the projects that are most relevant to this client's project type.

Design philosophy. One paragraph describing how the firm approaches design problems — not marketing language, but a statement with a point of view. "We believe buildings should respond to their site" is a philosophy. "We create innovative, client-focused designs" is a platitude.

Key personnel. Principal bios should be brief: education, relevant experience, and three notable projects. Clients want to know who will lead their project, not a full CV.

Past clients. If you can name them, do. A recognizable client list signals credibility more effectively than any other single element.

Project Proposal

The project proposal is the document that wins or loses the commission. It must demonstrate that your firm understands the project scope, has relevant experience, and has a credible plan for delivering it.

Project understanding. Restate the client's program — not the RFP language, but your interpretation of what the client actually needs. Clients respond positively to firms that have clearly read and thought about the brief.

Approach and methodology. How will you approach this specific project? What design principles are most relevant? What site conditions, programmatic constraints, or user needs will define the design direction? This section should be project-specific, not generic process boilerplate.

Relevant project experience. Three to five comparable projects with brief descriptions. Comparable means: similar program type, similar scale, similar client type, or similar site conditions. Show the projects most analogous to the current commission.

Project team. Who will lead the project, who will manage it day-to-day, and who will provide technical oversight. Include the subconsultants you propose — structural, MEP, landscape, civil. Clients want to understand who they are hiring.

Project schedule. A high-level milestone schedule from design kickoff through construction completion. Even if the program is uncertain, showing that you can sequence work credibly demonstrates project management capability.

Fee proposal. Present the fee in phases: schematic design, design development, construction documents, bidding, and construction administration. Break down the fee by phase so clients can understand what they are paying for. A lump-sum fee with no breakdown invites skepticism.

Conceptual Design Presentation

The conceptual design presentation is often the highest-stakes internal milestone: it is the first time the client sees the design direction, and it is where most design directions are either validated or redirected.

Design process. Show the analysis work: site analysis, precedent study, program adjacencies, massing exploration. Clients who understand how you arrived at the design concept are more likely to trust it.

Design concept. Present the organizing idea clearly. What is the concept? How does it respond to the site, the program, and the client's goals? One strong concept presented clearly is more effective than three concepts presented with equal weight.

Massing and siting. Plans, sections, and massing diagrams that show how the building sits on the site and how it relates to its context.

Key program elements. How does the design solve the program? Show that the key spaces — primary entries, primary occupant spaces, service and support — are positioned intelligently.

Visual representations. Perspective views, physical or digital models, or reference imagery. Clients need to see the building, not just read plans.

Open questions. Be explicit about what has not been resolved and what decisions the client needs to make before design development can proceed. Clients respect firms that are clear about the boundaries of the work.

Client Milestone Review

Milestone reviews at design development and construction documents are progress reviews, not design presentations. The client already approved the concept — the milestone review shows execution quality and surfaces issues that need resolution.

Progress against program. Show square footage by space type and confirm that the program is being met. Flag any areas where the design is over or under programmed.

Design coordination status. Have structural, MEP, and other systems been coordinated? What conflicts have been resolved and what remains open?

Budget tracking. Present the current cost estimate against the approved budget. Construction costs change as design is developed — clients who are surprised at bid time are clients who were not kept informed during design.

Decision log. A running list of decisions made at previous reviews and the current status. This creates accountability and prevents decisions from being re-litigated.

Required client decisions. A specific list of decisions the client must make before the next phase begins. Ambiguity here causes schedule delays.

---

Common Architecture Presentation Mistakes

Too many images, not enough structure. Beautiful images do not substitute for a clear narrative about the design.

Generic process descriptions. Clients hear the same process language from every firm. Differentiate by being specific about how you approach this project, not projects in general.

Fee proposals without phase breakdowns. A lump sum with no breakdown invites clients to negotiate without understanding the scope.

Not asking for the commission. Architecture proposals often end without a clear ask. Close with a direct statement about next steps.

---

Build Your Architecture Presentations with slide-deck.io

slide-deck.io generates professional presentations for architecture and design firms — from capability statements and project proposals to design reviews and milestone updates. Apply your firm's brand and export to PowerPoint for client distribution.

Create your architecture presentation