Most losing presentations are not bad presentations. They are careful, well designed, and aimed at the wrong reader. That is what makes these mistakes hard to see from inside the firm: every one of them is the result of a reasonable decision made for a reason that no longer applies.
I have sat on both sides of this. I have presented work I was proud of and watched it go nowhere, and I have reviewed submissions from firms whose design was clearly stronger than the one that won. The pattern is consistent enough to be worth writing down.
None of what follows is about design quality. It is about the gap between what a firm produced and what the client actually experienced.
1. Leading with the firm instead of the client
Open almost any architecture proposal and the first ten pages are firm history, studio photography, awards, and a map of offices.
This happens for an understandable reason. RFPs ask for it, so it goes at the front where it is easy to find. But the first screen or page is the only one you can be confident every reader sees, and spending it establishing that you exist forfeits the one guaranteed moment of attention you get.
The fix. Open with their problem, stated in their language, with enough specificity that it could not be sent to another client. Firm credentials still go in, and still get read by the people whose job is to check them. They just do not need the position of maximum attention. If the RFP prescribes an order, follow the order and use the cover or opening spread to do this work instead.
2. Designing for the room instead of the forward
Firms rehearse the interview. They design the deck for a projector, in a room, with a principal narrating.
Then the file gets emailed. It goes to a finance director who was not there, a board member reading three weeks later, and a procurement officer comparing four submissions in a spreadsheet. None of them get the narration. The deck that worked brilliantly in the room becomes a sequence of beautiful images with no argument attached, because the argument was in the presenter's mouth.
The fix. Produce for the forward, not the room. Every slide or section should carry enough written context to survive without you. If that makes the deck too text-heavy to present live, you have discovered that these are two different artifacts, and the leave-behind is the one that reaches more decision-makers.
3. Treating the fee section as an afterthought
The fee is often a table at the back, formatted differently from everything else, clearly assembled last and by someone else.
Engagement data on proposals is consistently unflattering here: fee and schedule sections get disproportionate time. That should not be surprising. For a large share of the committee, the commercial terms are the part they are professionally responsible for evaluating.
The fix. Treat fee and schedule as designed content with the same care as the design narrative, and make them easy to reach rather than buried. Burying the number does not delay the question, it just makes the reader work and signals that you find the topic uncomfortable. Explaining what the fee includes, and why the phasing is structured as it is, converts a number into a rationale.
4. Showing the process instead of the outcome
Architects are trained in and rewarded for process. Diagrams of iteration, massing studies, and option matrices communicate rigor to other architects.
To a client, a page of twelve massing options frequently reads as indecision. They are not equipped to evaluate why option seven was chosen, and asking them to do so transfers your expertise burden onto them.
The fix. Show the conclusion and the reason for it. One line of reasoning attached to one resolved outcome carries more authority than a grid of alternatives. Keep the process work available for the audience that wants it, in an appendix or a secondary section, rather than in the main line of argument.
5. One proposal for a committee with different jobs
Firms write a proposal as though it has one reader. It does not. A hospital pursuit might route through a facilities director worried about phasing around live operations, a CFO worried about cost certainty, a clinical lead worried about workflow, and a board member who will spend four minutes total.
A single linear document written for an imagined average reader serves none of them especially well.
The fix. Structure so different readers can find their own concern quickly, with clear sections and headings that name the topic rather than being clever. This is one of the concrete arguments for a navigable format over a linear file: it lets the CFO go straight to cost without scrolling past twenty pages of design narrative, and it lets you see afterward which concerns actually dominated.
6. Confusing spatial media with spatial understanding
A fly-through video is watched. It is not explored. The client sees exactly the path you chose, at the pace you chose, looking where you pointed.
For a hero moment that is exactly right. As a substitute for letting someone understand a building, it is weaker than firms assume, because the questions a client actually has are rarely the ones your camera path answers. They want to know what the view is from the corner office, whether the loading dock conflicts with the entrance, how the atrium reads at ground level.
The fix. Use video where you want control of the emotional beat, and use navigable 3D where the client needs to answer their own question. They serve different purposes and are not interchangeable. If you only have budget for one, ask which of those two your specific client needs.
7. Sending a file and calling it delivery
The proposal is exported, attached or dropped into a transfer link, emailed, and then the firm knows nothing. Was it opened? By whom? Did it reach the person who actually decides? Was the version they read the one with the corrected fee table?
Firms accept this blindness because it has always been the condition. Then they follow up with a message that says they are just checking in, which is a message that contains no information because the sender has none.
The fix. Deliver in a form that reports back, so follow-up can reference something real. Failing that, at minimum build a deliberate follow-up sequence with a reason to make contact each time, such as a relevant project completing or a question you genuinely need answered. The goal is to stop sending messages whose only content is that time has passed.
8. Inconsistency that reads as carelessness
Three different fonts because three people assembled sections. A team member listed on the org chart but missing from the bios. A project described as recently completed that finished in 2019. A page number that does not match the contents.
Individually trivial. Collectively they answer a question the client is genuinely asking, which is what it will be like to work with this firm for three years. A submission that shows evidence of poor internal coordination is evidence of poor internal coordination.
The fix. Build the proposal from maintained, reusable content rather than assembling it fresh each time from whatever people have on their drives. Most consistency failures are a content management problem wearing a design costume. A single owner doing a final read specifically for consistency, with no other agenda, catches most of the rest.
9. Ignoring the reading conditions
The proposal is designed on a 27-inch monitor. It is read on a phone, on cellular, in a spare ten minutes.
Small text in a dense two-column layout is unreadable on that device. A 180MB PDF will not open. A ten-second load means the reader gives up and intends to look later, which frequently means never.
The fix. Open every submission on a phone before it goes out. Not as a formality, but actually reading it, on cellular rather than office wifi. It is the single cheapest quality check available and it routinely finds problems that no amount of desktop review surfaces.
The pattern underneath all nine
Every one of these is the same error in a different costume: designing for the presenter's experience rather than the reader's. The firm knows the argument, has the context, controls the pacing, and reads on a large screen. The client has none of that.
The most useful exercise I know is to hand a finished proposal to someone in your own office who has never touched the pursuit, give them four minutes, and then ask them what the client's problem is, why your firm is the answer, and what the fee is. If they cannot tell you, the proposal is not finished, regardless of how it looks.
Further reading
About the Author
Kitae Kim
Architect with 10 years of experience in design and client communication. Co-founder of Foveate, where he builds proposal and presentation tools for AEC firms. Former studio lead who saw too many winning designs lose to worse proposals.
Related Articles
Architecture Business Development: How to Turn Your Portfolio Into a Prospecting Tool
Your portfolio is the most expensive business development asset your firm has ever produced. It's also the most passive. Here's how the firms winning the most competitive work have turned their case studies into an active intelligence system.
What Architecture Presentation Tips Actually Win Projects?
Clients don't buy design. They buy confidence. Your presentation's job is not to show your work—it's to make clients believe you understand their problem, you can solve it, and working with you will be good.