I'm learning that teaming on a set-aside pursuit is as much about relationships as it is about strategy. The teams that seem to win aren't always the biggest — they're the ones that actually make sense together.
Pick partners for what they bring, not their name. Your team should fill specific gaps tied to the evaluation criteria. If a partner doesn't actually move the score, do they really belong there? I'm still learning how to evaluate this, but it's getting clearer every time I review a pursuit.
Lock things in early. Teaming agreements written at the last minute rarely survive contract award. I'm learning to get workshare, exclusivity, and dispute terms on paper early — before anyone gets too emotionally invested in winning. Sounds obvious, but it happens all the time.
Communication cadence matters more than I thought. Running weekly syncs during the pursuit sets the rhythm. And honestly, the rhythm you set in the proposal phase is usually the rhythm you inherit once the work starts. I'm building that habit now so it feels natural later.
I'm actively building a bench of subs across the capabilities I prime. If you're interested in teaming, the partners page is the fastest way to connect.