Answering together is not forbidden: it is provided for, and most buyers explicitly allow it. What blocks companies is almost never the law — it is not knowing who signs, who invoices, who answers for delays, and how to agree before anything has been won.
The offer lead is the client’s single point of contact. They submit, they sign, they invoice, and they are the one called when a milestone slips. Not necessarily the largest partner, nor the one doing the most work: the one who can hold the relationship. Choosing last, “once we know”, is the surest way never to submit.
A teaming agreement that arrives after the win arrives too late: by then everyone knows the amount and negotiates their share against the project. Signed first, it sets roles, each partner’s contribution, confidentiality, and the split — which is then frozen. Uncomfortable for ten minutes; it saves three months of argument.
Each partner’s scope; who leads and what they may decide alone; the price split, as a percentage or an amount, and the moment it is frozen; confidentiality, including what each may reuse afterwards; exclusivity, or its absence, on this specific bid; and what happens if someone withdraws before submission.
That the team covers the whole scope, that they have one number to call, and that every announced capability rests on more than a claim. A capability attested by a third party or confirmed by a previous client weighs more than a brochure — in public procurement it is often the only differentiator you can produce.
Building the team around the people you know rather than around the requested scope. Waiting until you have won to talk about money. And announcing a capability nobody on the team can prove — a buyer who discovers that mid-mandate does not call back.
Startups and SMBs · Networks and ecosystems · Public buyers · Cybersecurity · Artificial intelligence · Clean technologies · Industry and manufacturing · Public-sector teaming