Paying Seller-Doer Engineers Without Discouraging Billable Work

A principal who spends a week pursuing a new municipal contract is a week they did not spend billing hours on an active project, and if the firm's only measure of performance is utilization rate, that principal looks worse on paper for doing exactly the business development work the firm needs. A commission or bonus structure that offsets some of that opportunity cost is not a luxury, it is what keeps senior staff willing to pursue new work at all instead of retreating entirely into billable delivery, where their individual performance metrics look cleaner.

This pattern is specific to firms where the technical staff and the business developers are the same people, which describes most civil and structural practices below a certain size. A firm large enough to run a dedicated business development function faces a different, simpler problem: paying that function is a normal sales comp question. The seller-doer tension only exists where those two roles have not been separated.

Many engineering firms land on a simple rule: a fixed percentage of a project's fee goes to whichever principal originated it, paid once the contract is signed, with no attempt to net that against the originator's own utilization. QuotaPath can track that cleanly, one project, one originating principal, one bonus calculation, without much configuration. It is a reasonable choice for a firm that has decided origination credit and utilization tracking should stay separate rather than combined into one formula.

Some firms want a single calculation that credits origination while also accounting for the fact that the originating principal's billable hours dropped during the pursuit, effectively paying a bonus that reflects the true net value of winning the work. That requires pulling both project fee data and timesheet or utilization data into one formula, which is exactly the kind of multi-source calculation CaptivateIQ's engine is built for and QuotaPath's template-based builder is not.

Suppose a principal spends roughly three weeks pursuing a municipal infrastructure contract, time that would otherwise have been billable, and then wins it. A flat origination bonus rewards the win but ignores the utilization cost of the pursuit itself, which is fine if the firm has decided that trade-off is acceptable and does not want to complicate the formula. A netted calculation instead credits the origination bonus against a rough estimate of the billable hours lost during the pursuit, which more accurately reflects the project's true value to the firm but requires timesheet data most firms are not used to feeding into a comp calculation. Neither approach is wrong; the choice depends on whether your firm's leadership wants that added precision badly enough to build and maintain the data pipeline it requires.

If your firm is comfortable paying a flat origination bonus and treating utilization as a separate performance conversation, QuotaPath will track the bonus side cleanly with little setup. If leadership wants one number that reflects both origination credit and its utilization cost, CaptivateIQ's formula engine can build that, but budget real time to get the timesheet integration right before trusting the output.

Use these criteria to choose a platform:

• Choose a flat origination bonus in QuotaPath if leadership is comfortable treating utilization as a separate performance conversation.
• Choose a netted calculation in CaptivateIQ only if leadership wants one number reflecting both origination credit and its utilization cost, and budget real time to build it.
• Confirm your project accounting system can supply clean fee and timesheet data, so principals never log business development hours in a second system.
• Check who will maintain the data pipeline after setup, since a netted calculation is only as good as its inputs.

Most engineering firms already run project accounting software separate from any commission tool, tracking billable hours, project phases, and fee burn against budget. Whichever commission platform you pick has to pull clean data from that system rather than duplicating it, since asking principals to log business development hours in a second system just to feed a comp calculation is the kind of friction that quietly kills adoption. Confirm the integration works against your actual project accounting platform before committing, not just against a generic CRM connector that may not map cleanly to how engineering firms structure project codes.