Proposals, Pitches & Competitions

When a client issues a request for proposals (RFP) or a brief, the document in front of you is only half the story. It lists deliverables, timelines and selection criteria, but underneath it sits a real, often unstated question: 'Can I trust these people with my money, my time and my ambition?' The proposals that win are the ones that answer that human question, not merely the procurement checklist. This is why a technically compliant but generic proposal loses to one that clearly grasped the client's specific situation.

Structure a proposal to reassure, in the client's language. Open by demonstrating that you understood the brief and the deeper goal behind it - reflecting back the problem better than they stated it is astonishingly persuasive. Then set out your approach: how you will run the project, the stages, the team who will actually do the work (not a roster of names who will vanish after signing), and the directly relevant experience that proves you have done this before. Address risk honestly - programme, budget, approvals - because naming the risks and how you will manage them signals competence, whereas pretending there are none signals inexperience. Only then the fee and terms, tied clearly to scope and stages (Lesson 3.4).

Make it easy to say yes and easy to compare you favourably. Answer every stated selection criterion explicitly, in the order the client asked, so an evaluator scoring you can find each point without hunting. Be concrete: named references, real timelines, specific methods. And write it for the actual reader - a homeowner, a facilities committee, a government tender board and a developer each need a different register. A proposal is not a brochure about you; it is a tailored argument that you are the safe, capable, understanding choice for this particular client and this particular project.

A strong written proposal often earns a shortlist interview or pitch, and here the dynamics shift entirely. In person, the client is no longer evaluating a document; they are evaluating whether they can work with you for the months or years the project will take. Chemistry, clarity and confidence now matter as much as content. Many a technically superior practice has lost the pitch because it was arrogant, unprepared or simply hard to imagine spending a year with.

Prepare relentlessly and specifically. Research the client, the site and the project so you can speak to their situation, not deliver a canned pitch. Bring the people who will actually run the job, and let them speak - the client is buying that relationship, so hiding your project lead behind a charismatic principal backfires. Rehearse, keep to time, and design the session as a conversation rather than a monologue: the best pitches feel like the first working meeting of a team that has already started solving the problem together. Anticipate the hard questions - fee, programme, a difficult constraint - and answer them straight; evasion reads as weakness.

Above all, listen and respond in the room. A rigid, over-produced pitch that ploughs through forty slides regardless of the client's reactions loses to a team that reads the room, picks up on what the client cares about, and adjusts. Show, don't just tell: a sketch drawn live in response to a client's worry, a crisp answer to their real concern, a moment of genuine insight about their problem - these are what people remember and what tips a close decision. The pitch is not a test of how impressive you are; it is an audition for a working relationship, and the practice that feels like the safest, most understanding partner usually wins.

Architectural competitions are a distinct route with their own economics and mythology. In an open competition, anyone may enter; the field is huge, the odds long, and the work is almost always speculative and unpaid. In an invited (or limited) competition, a handful of practices are selected to compete, often with a modest honorarium, giving far better odds and usually a more serious client. A third variant, the two-stage competition, uses an open or expression-of-interest first round to shortlist, then a paid second round - combining wide access with fairer economics.

The romance of competitions is real: they can launch a young practice, deliver a landmark commission, and offer a rare chance to design free of an established client relationship. History is full of practices made by a single competition win. But the economics are brutal and must be faced honestly. An open competition may draw hundreds of entries, so any single entry's probability of winning is very low, while a serious entry can consume weeks of unpaid studio time. Multiply the cost of entry by the number of entrants and you see the uncomfortable truth: as a field, entrants collectively donate enormous quantities of free design work, and only one is paid - which is why speculative competitions are a genuine and long-running ethical debate in the profession.

Decide with a clear head, not with hope. Estimate the true cost of a credible entry in staff-days and rupees; estimate your honest probability of winning given the field and the fit; and weigh what a win, a place, or even a strong published entry would actually be worth to you (a real commission, a marketing asset, a portfolio piece, or nothing). Enter invited and paid competitions readily when they fit; enter open speculative ones selectively and deliberately, treating them as a marketing and creative investment with eyes open, never as a reliable way to win work. In India, refer to the Council of Architecture's competition guidelines and current regulations for the conduct and conditions expected of a properly run competition.

Competitions are only the most formal kind of speculative work - work done in the hope, not the certainty, of payment. The everyday version is subtler and more dangerous: the client who asks for 'just some initial sketches so we can see your thinking' before committing, the developer who invites four practices to produce concept designs unpaid as a 'design bid', the friend-of-a-friend who wants a free 'quick idea'. Each asks you to give away the very thing you sell - design thinking - on spec.

The discipline here is to distinguish reasonable pre-commitment effort from being farmed for free ideas. It is normal to invest in a proposal, to meet, to discuss approach, even to show relevant past work - that is business development. It is not normal, and rarely wise, to produce bespoke design for a specific site unpaid on the mere hope of selection, because you are then doing the paid work of Stage A or B for nothing, often alongside competitors doing the same, in a race the client has structured to extract free design from the whole field. The more you give away, the more you signal that your expertise is not worth paying for.

Set a clear line and hold it politely. Offer to demonstrate capability through relevant completed work, references and a rigorous approach, and offer a paid initial engagement - a feasibility study, a concept sprint, a paid first stage - for clients who want to see design thinking on their specific project. A serious client will respect a professional who values their own work; a client who insists on free bespoke design as the price of consideration is usually either not serious or not the kind of client you want. Knowing when to walk away from unpaid design is one of the quiet marks of a practice that will still be solvent in ten years.

Because proposals, pitches and competitions all cost real time, the practices that stay profitable make a deliberate go / no-go decision before pursuing each one, rather than reflexively chasing everything. The questions are simple and should be answered honestly, ideally with more than one partner in the room: Do we genuinely want this project and can we deliver it excellently? Do we have a real chance - is the fit strong, or is there an incumbent already favoured and we are 'column fodder' to make the process look competitive? What will it truly cost us to pursue, in staff-days and cash? And what is the opportunity cost - what better-odds work are we not chasing while we chase this?

Saying no to the wrong pursuits is as valuable as winning the right ones, because every proposal you write for a job you will not get, or do not want, is time stolen from one you would. A practice that wins one in three of the proposals it chooses to write, by choosing carefully, is far healthier than one that writes twice as many and wins one in ten while exhausting itself. Track your win rate by type of pursuit; it will teach you where you are strong and where you are wasting effort.

Finally, build reusable infrastructure. Much of a proposal - practice profile, team CVs, methodology, quality and safety approach, relevant project sheets - is common across pursuits, so maintain a well-organised, up-to-date library from which each specific proposal is tailored, not written from scratch at midnight before the deadline. This lets you spend your limited proposal time on the part that actually wins: the tailored understanding of this client's problem. Do a short win/loss review after each outcome - ask winning clients why they chose you and losing ones why they did not - and feed what you learn back into the next pursuit. Winning work, like design, improves with deliberate iteration.