Every architecture firm knows the feeling. An RFP drops with a tight deadline, and within hours you're scrambling to assemble a team — structural, mechanical, electrical, civil, landscape, maybe a specialist or two. You reach out to the firms you've worked with before, hope they're available, and paste their credentials into your submission.
It works. Until it doesn't.
Most firms pick subconsultants the same way every time: the principal or project manager pulls from a mental shortlist of "people we've worked with." There's rarely a structured record of which subconsultants were teamed on which proposals, what they cost, or how the project turned out.
This creates three problems that directly affect your win rate:
1. You default to the same partners regardless of fit.
When time is short, you go with who you know. But the structural engineer who was perfect for your last healthcare project may not be the right fit for a K-12 school with a tight budget. Evaluation committees notice when your subconsultant team doesn't match the project scope — it signals that you assembled the team quickly rather than strategically.
2. You lose institutional knowledge when people leave.
If the associate who manages your subconsultant relationships leaves the firm, those relationships — and the context around them — walk out the door. Who did we use for the Halton school board project? What did the MEP consultant charge last time? Were they responsive during construction administration? That knowledge evaporates.
3. You can't demonstrate teaming track record.
Some RFPs explicitly ask for evidence that your proposed team has worked together before. If you can't quickly show which past projects involved the same subconsultant lineup, you're leaving points on the table. Evaluation committees value teams that have a demonstrated working relationship — it reduces their risk.
When a selection committee reviews your subconsultant page, they're looking for three things: relevance (does this firm have experience with this project type?), capacity (can they actually take this on?), and chemistry (has this team delivered together before?).
The firms that win consistently aren't necessarily teaming with the most prestigious subconsultants. They're teaming with the right ones for each specific opportunity, and they can prove it with project history.
The fix isn't complicated, but it does require moving beyond spreadsheets and memory. Firms need:
We've been building these capabilities into ArchFP — from a searchable partner directory and proposal shortlisting to automatic CV extraction and an AI assistant that can answer questions like "which structural engineers have we teamed with on school projects?" using your firm's actual data.
If your firm's teaming decisions are still driven by who the principal remembers from the last project, book a quick demo and we'll show you what a data-driven approach looks like.