Notes from the pursuit.

Most small businesses approach teaming as a networking outcome: meet enough primes, trade enough capability statements and eventually someone will call. At VA, where small business participation matters and primes are building teams early, that approach leaves good companies on the outside. Here are four patterns worth fixing.

1. Showing up after the team is set

By the time a final RFP is released, most serious teams are already formed. If your first conversation with a prime happens after release, you are competing for the few open slots left. Track the forecast, and start partner conversations while the requirement is still being shaped.

2. Leading with everything you do

A prime is solving a specific problem: a capability gap, a small business goal or a past performance weakness. A capability statement that lists twelve services makes them do the work of finding the fit. Lead with the one or two things that close their gap on this pursuit.

The best teaming pitch answers one question: what does this team lose if you are not on it?

3. Treating workshare as an afterthought

Small businesses often agree to join a team before anyone has defined their workshare. Talk about scope, labor categories and how work will flow before you sign, and get it in writing where it makes sense.

4. Spreading across competing teams

Joining every team that asks can feel like hedging, but it signals a lack of commitment and can create real conflicts. Pick the team you believe in, commit to it and build a reputation as a partner primes can trust.

Agency forecasts are a starting point, not a promise. Lines slip, change scope or quietly disappear. Before you commit pursuit budget, look for signals that the requirement has real momentum.

1. It keeps showing up. A requirement that appears across consecutive forecast updates with consistent details is more likely to move than one that appears once.
2. Market research has started. A sources sought notice or RFI on SAM.gov means the customer is actively shaping the acquisition.
3. There is an incumbent contract ending. Recompetes tied to a known period of performance end date tend to have firmer timelines.
4. The details are specific. A clear contract type, vehicle, set-aside and estimated value suggest the acquisition team has done real work.
5. Industry is talking about it. Industry days, partner conversations and prime team-building are strong signs that others see it as real too.

No single signal is proof. Two or three together usually justify a closer look, and a structured bid or no-bid decision before you spend serious time.

Growth teams are measured on wins. Delivery teams are measured on performance. When the two do not talk early, the proposal promises a staffing plan the program cannot actually execute, and the customer notices in the first ninety days.

Write the staffing plan you can run

Key personnel, labor categories, clearance requirements and start dates should be tested against the real talent market before they go into the proposal. If a role is hard to fill, plan the pipeline or the partner who can fill it now.

Bring partners in for delivery, not just for the bid

A teaming partner chosen only to check a box on the proposal can become a delivery gap after award. Choose partners who strengthen the program you will actually run.

Hand off with context

The capture team knows why the customer chose you. Make sure the delivery team hears it directly, along with every commitment made during the pursuit.

Winning is the start. Thinking about delivery from day one is how a single award becomes a lasting relationship.