Why Teaming Agreements Don't Fit Inside a Commission Portal

A teaming agreement, where a prime firm and one or more subconsultants jointly pursue a public infrastructure contract, is structured around scope split and fee allocation for a specific project, not an ongoing commission on introduced business. Standard Form 330, used on federal architect-engineer procurements and often mirrored on state and local ones, asks you to identify key team members and consultants and their roles, which makes the relationship documented and contractual rather than the informal referral arrangement PartnerStack's registration model was built around.

Before approaching a potential structural or geotechnical teaming partner, it helps to know which developers, agencies, or general contractors that firm already has active relationships with. Crossbeam's account comparison surfaces exactly that, without either firm handing over its full client list. A civil firm deciding which structural engineer to approach for a joint pursuit can use that overlap to identify a partner whose relationships complement rather than duplicate its own, which matters more for winning the next bid than any commission tracking would.

Once a project is won, the prime firm manages subconsultant agreements, scope, fee splits, invoicing, through project accounting rather than a partner portal, and that relationship is governed by the teaming agreement signed at pursuit stage, not by ongoing deal registration. Neither PartnerStack nor Crossbeam is built for that phase. It belongs in the project accounting and contract management systems the firm already uses for every job, teamed or not.

Engineering firms with in-house business development staff, rather than purely principal-led pursuit, deal with the same reality most B2B sales organizations do: only about 22% of individual sellers hit full quota in a given year¹. For firms where pursuit success depends heavily on relationships built years in advance, that number is a reminder that a formal partner network, teaming or referral, tends to outperform cold pursuit of new agency relationships built from scratch.

Not every relationship in this industry is a teaming agreement. A firm might refer a client to a specialty consultant, environmental permitting, traffic engineering, outside its own service line, and receive a referral fee for that introduction. That narrower case is closer to what PartnerStack was built for, and it's worth tracking separately from teaming relationships rather than trying to force both into the same system, since the governance, disclosure, and payment structures differ.

Start by mapping which relationships in the firm's pipeline are teaming agreements, disclosed on the qualifications package, versus informal referral relationships that involve a fee. For teaming relationships, invest in project accounting and disclosure tracking, not partner software. For the smaller set of genuine referral relationships, PartnerStack becomes worth considering once volume grows past what a spreadsheet handles cleanly, and Crossbeam becomes worth considering once the firm regularly needs to identify new teaming partners rather than relying on the same two or three it's always used.

A practical order of operations for most firms:

1. Map every relationship in the pipeline as either a teaming agreement disclosed on the qualifications package or an informal referral that involves a fee.
2. For teaming relationships, invest in project accounting and disclosure tracking rather than partner software.
3. For the smaller set of genuine referral relationships, consider PartnerStack to record introductions and pay the fees.
4. Before approaching a prospective teaming partner, use Crossbeam account comparison to see which agencies or developers they already work with.

Many engineering firms pursue every teaming opportunity with the same one or two trusted structural or geotechnical partners, which works until that partner is unavailable, overcommitted on another pursuit, or the relationship changes. Expanding the roster of potential teaming partners, and knowing in advance which ones already have relevant agency or developer relationships, reduces that dependency. This is where a broader account-mapping habit, even without formal software, starts paying off during a busy bid season.

Resist the urge to route project-level subconsultant management, scope changes, fee amendments, invoicing, through a partner platform built for deal registration and commission payouts. That work belongs in project accounting and contract administration systems designed for it. Mixing the two creates confusion about what each system is actually the source of truth for, and it's a common mistake firms make when they try to get more value out of a platform they've already invested in setting up.