How General Contractors Should Structure BD Commission Software

QuotaPath's approach is a fixed, agreed split between estimator and BD lead, set once per project type and applied consistently, for example an estimator getting a smaller flat share and the BD lead getting the larger share on every won bid. It is easy to explain to the team and quick to run, but every exception, a project where the estimator did unusually heavy preconstruction work, has to be handled as a manual override.

CaptivateIQ's approach lets you build an approval step into the plan itself, where a project's split can be adjusted by a manager before it locks, and that adjustment is logged rather than handled in a side conversation. That is more setup, but it removes the manual override problem entirely.

Commercial construction revenue is recognized as the project progresses, with a portion of the contract value held back as retainage until closeout. A commission plan that pays on the full contract value at award, before any of that revenue is actually billed, creates a cash timing mismatch that finance teams dislike. Both tools can tie commission to billed revenue rather than contract award, but it takes deliberate configuration either way, it is not the default behavior in either one.

A change order that adds real scope to a project should generate incremental commission on that added value, credited the same way the original award was credited. The tradeoff here is that CaptivateIQ can represent a project as a base contract plus a running list of change orders inside one commission record, while QuotaPath typically treats a meaningful change order as a smaller, separate commission event, which works fine as long as your team tracks which change order belongs to which original project.

A contractor running a handful of active pursuits at a time, with a stable, agreed split between estimating and BD, does not need CaptivateIQ's approval-hierarchy overhead. A contractor running many concurrent bids across multiple offices, where splits genuinely vary project to project and someone needs to approve exceptions before payout, will spend less time on manual corrections with CaptivateIQ.

Regardless of which tool you pick, decide up front whether commission pays out at contract award or as retainage is released at closeout, since this is a policy decision, not a software feature, and both tools will do whatever you configure. CaptivateIQ vs QuotaPath vs Spiff has more detail on how Spiff's real-time tracking compares if your BD team wants visibility into pipeline value as bids move through preconstruction.

The most common failure mode is not the software, it is the handoff: an estimator finalizes a winning bid in your estimating software, and by the time that award actually reaches whoever runs commission, days or weeks have passed and small details, the final negotiated split, whether a preconstruction fee was included in the award value, have gotten fuzzy. Build a simple, written handoff step: the moment a bid is awarded, someone records the award value, the estimator and BD lead of record, and the agreed split, in one place, before it goes anywhere near a commission tool.

This matters more for a growing contractor than for an established one, since a small team can often rely on everyone just remembering the details of a handful of active pursuits. Once you are running enough concurrent bids that no single person holds the full picture in their head, that informal handoff becomes the actual source of commission disputes, not whichever tool you eventually chose.

Before running your first real commission cycle in either tool, pull three or four recent won bids with genuinely different characteristics, one straightforward single-estimator deal, one with a split, one with a change order, and calculate what each should pay by hand using your documented rules. Then run the same deals through the tool's configuration and compare. Any mismatch tells you exactly where your configuration does not yet match your intended policy, while the stakes are still zero because no real payout has gone out yet.

This test-case approach catches far more configuration mistakes than reading through settings screens, since a rule that looks correct in the abstract often behaves differently once it meets a real, messy deal with a change order and a disputed split. Keep those test cases on file too, since they double as documentation the next person configuring the system can check their own understanding against.

A pre-payout test using real won bids:

1. Pull three or four recent won bids with genuinely different characteristics, such as one simple single-estimator deal, one split, and one with a change order.
2. Calculate what each bid should pay by hand, using your documented commission rules.
3. Run the same bids through the tool's configuration and compare its results with your hand calculations.
4. Investigate every difference before the first live commission cycle, since it points to a rule that was configured wrongly or never documented.