Why RFP Quota Credit Is a RevOps Problem, Not Just a Sales Argument
When a rep asks whether an RFP win counts toward quota, the question sounds like a compensation dispute. Underneath it is a data modelling problem that belongs to RevOps. Quota is meant to measure whether an individual’s activity converts into revenue. If an RFP win and a self-sourced outbound win land in the same attainment bucket with no distinction, the number stops telling anyone what actually drove the result. A sales leader looking at 110 percent attainment cannot say whether that came from prospecting skill, from a procurement team choosing to run a tender, or from a partner introduction that happened to close in the same period.
This matters most in capacity planning. Territory and headcount models are built on an assumption of how much pipeline a rep can generate independently in a year. If half of a rep’s number in fact arrived through an inbound tender that a BDR, a partner, or a procurement portal surfaced, next year’s hiring plan will overestimate what a newly hired rep in that territory can produce alone. The distortion does not show up immediately. It shows up two or three quarters later, when a new hire with no inbound RFP flow misses a number that was calibrated against someone who had it.
The same distortion reaches compensation design, forecasting, and even promotion decisions, because all three lean on the same attainment figure as a proxy for selling skill. Getting the RFP question right is therefore less about being fair to one rep in one quarter, and more about keeping every downstream model that depends on quota data honest.
The Case for Full Quota Credit on RFP Wins
The strongest argument for crediting RFP wins at full value is that the effort involved often matches or exceeds an outbound deal of similar size. A formal enterprise or public-sector RFP response typically pulls in sales engineering for a technical demonstration, product management for a roadmap commitment, legal for contract redlines, and security or compliance staff for a questionnaire that can run to dozens of pages. The rep owns coordinating all of that against a fixed submission deadline, while also managing the buyer relationship. That is not a passive inbound lead being handed a proposal template.
There is also a behavioural argument. If RFP-sourced revenue counts for less than outbound revenue, reps respond to the incentive rationally: they deprioritise the RFP whenever it competes for time against an outbound deal that pays full quota credit. Complex tenders with internal review cycles, security questionnaires, and legal negotiation are exactly the deals most likely to stall if the rep chasing them has no reason to push procurement, deal desk, and legal to move faster. A channel that management wants to grow can end up starved of attention purely because of how the comp plan is written, independent of the actual revenue opportunity it represents.
Full credit also simplifies communication. A single attainment number, with no asterisks, is easier for a rep to trust and easier for a manager to explain in a one-to-one. Where the RFP channel is a small share of total pipeline, that simplicity can outweigh the precision lost by not adjusting for effort differences.
The Case for Discounting or Excluding RFP Wins
The counter-argument starts from where the opportunity originated rather than how much work followed it. Many RFPs arrive because a buyer already decided to run a tender, often triggered by a procurement mandate, an incumbent contract expiring, or a compliance requirement rather than any prospecting activity by the rep. In that scenario the rep is responding to demand that already existed, not creating it. Crediting that response at par with a self-sourced outbound deal rewards administrative diligence and proposal quality as if they were prospecting skill, which distorts what attainment is supposed to measure.
This becomes acute in portfolios where a large share of the pipeline is inbound tender flow, such as public-sector-facing SaaS vendors responding to formal procurement processes. UK public bodies run much of that flow through a central tendering channel, documented on the government’s own Find a Tender service, and a rep working that channel is fundamentally doing a different job to one building an outbound pipeline from cold outreach. If both count identically toward quota, territory design starts to assume every rep can replicate that inbound flow, and capacity planning collapses the moment a territory without an active tender pipeline is staffed the same way.
There is a second, quieter risk: if RFPs count fully and are also easier to forecast (a tender has a published deadline and a known evaluation process), reps and managers alike gravitate toward RFP pursuit as the safer route to quota, even where the underlying deal is smaller or lower margin than an outbound alternative the rep could have chased instead. Excluding or discounting RFP credit is one way to keep that incentive from quietly overriding good deal selection.
Building a Weighted Quota Model That Splits the Difference
Most RevOps teams that have argued through both positions land somewhere between full credit and exclusion: a weighted model, where RFP-sourced revenue counts toward quota but at a fraction of its face value. The appeal is that it acknowledges the real effort involved in a serious RFP response without letting inbound tender volume mask a rep’s independent prospecting output.
Setting the Weighting Band
Rather than picking a weighting figure because it feels reasonable, anchor it to something measurable: compare the average internal effort consumed by a typical RFP response against the average effort consumed by an outbound deal of a similar contract value, using whatever unit is already tracked internally, such as internal working days logged against the opportunity or the number of internal stakeholders pulled in. If an RFP of a given size consumes roughly two thirds of the internal effort of an equivalent outbound deal, a weighting close to that ratio is defensible in a compensation review in a way an arbitrary round number is not. One organisation might land on a weighting around a third; another, with heavier internal RFP overhead, might land closer to two thirds. What matters is that the figure can be traced back to an effort comparison rather than asserted as policy.
Guarding Against Gaming the Weighting
Any weighting scheme creates an incentive to reclassify deals to whichever side of the line pays better. A rep on a quarter where outbound is falling short may push to have a borderline inbound enquiry logged as prospected; a rep with a strong RFP quarter may resist reclassifying a deal the other way. Guard against this by keeping the classification decision out of the rep’s hands entirely. Deal desk or RevOps, not the account owner, should approve the source tag, based on documentary evidence such as a tender reference number, a formal RFP document, or a portal submission record attached to the CRM record. Where that evidence does not exist, the deal defaults to outbound.
CRM and Pipeline Structure for Tracking RFP Wins Separately
None of the above works without a CRM structure that can hold the distinction cleanly. Most teams get this wrong not because the concept is hard, but because they try to reuse a field that already means something else.
Custom Fields and Source Tagging
A platform’s native lead source or original source property, such as the one HubSpot’s object and property model exposes on contacts and deals, is built to capture marketing channel attribution, not deal-classification for compensation purposes. Overloading that field to also mean “this is an RFP” tends to break the marketing reporting it was designed for the moment someone edits it for a comp reason. Build a dedicated deal property instead, for example a picklist covering outbound prospecting, inbound RFP or tender, partner referral, and renewal or expansion, with a required linked field for a tender reference number or an attached RFP document wherever the inbound RFP value is selected. The requirement to attach evidence does double duty: it feeds the compensation dispute record and it forces the classification through deal desk rather than being set casually by the rep at deal creation.
Automating the Handoff Without Losing Data
Manual classification drifts. A rep tags a deal correctly at creation and then forgets to update it when the deal’s nature changes, or a manager bulk-edits a view and accidentally overwrites the field. Where RFPs arrive through a predictable channel, such as a tender portal notification or a dedicated inbound form, automation tools like those documented at n8n’s workflow documentation can apply the source tag and attach the reference document automatically at the point of deal creation, before a human has the chance to skip the step. That does not remove the need for deal desk approval on ambiguous cases, but it removes the much larger volume of clear-cut cases from manual handling, and it produces an audit trail: a timestamped log of who or what applied the tag and when, which becomes the evidence base if a rep disputes their attainment at quarter close.
Where the Weighting Actually Lives in Compensation Plans
Deciding on a weighting figure only solves half the problem; the plan also has to specify mechanically where that weighting applies, and the three common options behave quite differently in practice.
The first option applies the weighting at the deal-value level: an RFP-sourced deal’s contract value is multiplied by the weighting factor before it ever enters the attainment calculation, so a single blended attainment percentage is all anyone sees on a leaderboard. This is the simplest option to communicate but it hides the split from finance and from the rep, who cannot easily see how much of their number came from which source without pulling a report.
The second option leaves the full contract value counting toward attainment and forecasting, but pays a different commission accelerator rate on RFP-sourced revenue. This keeps forecasting and pipeline reporting undistorted, since the true contract value is what finance sees, while still adjusting the rep’s actual payout for the effort differential. It requires a payroll or commission engine capable of applying rate differences by deal source, which not every stack supports out of the box.
The third option tracks RFP-sourced revenue as a separate sub-quota with its own target and its own attainment percentage, reported alongside (not blended into) the main outbound quota. This preserves the clearest visibility of the three, at the cost of asking every rep to understand and track two numbers instead of one.
Whichever mechanism a plan chooses, lock the classification logic and the weighting figure before the compensation period begins, and never apply a definitional change retroactively mid-period. Changing how a deal type is weighted after reps have already closed deals under the old assumption rewrites attainment history that comp and payroll have already relied on, and it is the fastest way to turn a design disagreement into a formal pay dispute.
Common Failure Modes When Rolling Out an RFP Quota Policy
Three patterns account for most of the disputes that surface after a weighted RFP policy goes live. The first is a mismatch between the written plan document and what the CRM and commission engine actually calculate. A plan can state a clear weighting rule, but if deal desk applies manual overrides in a spreadsheet that never gets reconciled against the CRM’s automated calculation, two numbers exist for the same deal, and whichever one payroll uses becomes the one the rep disputes.
The second is an undefined threshold for what counts as an RFP in the first place. A one-page inbound pricing enquiry and a forty-page formal government tender are both, technically, requests for a proposal, but they involve wildly different effort. If classification is left to rep judgement rather than tied to an objective marker (a formal tender portal submission, a procurement reference number, a signed NDA covering a competitive bid process), reps will classify identical deals inconsistently across a team, and the weighting logic misfires on cases it was never designed to handle.
The third is a systems gap between where the classification happens and where compensation is calculated. RFP tagging done cleanly in the CRM never reaches the commission engine if the two systems are not integrated, and the weighting policy ends up existing on paper without ever affecting an actual payslip. This is the failure mode that RevOps is best placed to catch, since it is the team most likely to be looking at both systems at once.
Related Reading
Frequently Asked Questions
Should RFP wins always count toward quota at full value?
Not automatically. Full credit is defensible where the internal effort on the RFP genuinely matches an outbound deal of similar size, but many teams find that a weighted model, where RFP revenue counts at a fraction of face value, better reflects the difference between inbound tender response and self-sourced prospecting.
How should a RevOps team decide on a weighting percentage for RFP deals?
Anchor it to a measurable effort comparison, such as internal working days or stakeholders involved, between a typical RFP response and an outbound deal of similar contract value, rather than choosing a figure because it feels fair. That gives the weighting a basis that holds up in a compensation review.
What CRM fields are needed to track RFP wins separately from outbound deals?
A dedicated deal source picklist covering categories such as outbound prospecting, inbound RFP or tender, partner referral, and renewal or expansion, plus a required linked field for a tender reference number or attached RFP document wherever the RFP value is selected.
Who should be allowed to classify a deal as an RFP for quota purposes?
Deal desk or RevOps, not the account owner, should approve the classification, based on documentary evidence attached to the CRM record. Leaving classification to rep judgement alone creates an incentive to reclassify borderline deals whichever way pays better in a given quarter.
Where in the compensation plan should RFP weighting be applied?
At one of three points: the deal value itself before it counts toward attainment, the commission rate paid on the full contract value, or as a separate sub quota tracked alongside the main outbound quota. Each has a different trade-off between simplicity and visibility, and the choice should be locked before the compensation period begins.
For more on this, see more RevOps strategy posts, including Developer-First SaaS Sales: PLG, GTM, and RevOps Strategies, 5 RevOps Mistakes You Should Avoid for Seamless Scaling, and Building a Resilient and Scalable RevOps Tech Stack for B2B Growth.
Leave a Reply