How Pay-Per-Qualified-Lead Pricing Works

Who this guide is for

This guide is for buyers, finance teams, procurement reviewers, revenue operations owners, and implementation teams evaluating a pay-per-qualified-lead offer. It explains SellersGPT mechanics in plain language. It is not an order form, legal advice, tax guidance, or a substitute for the terms effective for a specific customer.

Contents

1 Start with the billable unit 2 How SellersGPT applies the model 3 Use the Billable Event Ledger 4 Resolve the exact effective price 5 Separate controls that look similar 6 Handle disputes without premature deduction 7 Itemize follow-up separately 8 Recalculate a symbolic scenario 9 Compare risk allocation 10 Common mistakes 11 Limits and publication controls 12 Frequently asked questions 13 Sources and methodology

1. Start with the billable unit

Every pricing model allocates risk around a defined unit. A subscription charges for access or time whether or not a particular outcome occurs. Pay per lead charges for a captured record under a lead definition. Pay per meeting moves the unit downstream to a calendar or attendance event. Pay per Qualified Lead charges when a record passes an agreed qualification rule. The phrase qualified lead is not self-defining. Under SellersGPT, the unit is the SellersGPT Qualified Lead: an evidence-backed lifecycle state created under a specific rule version. It is not a marketing-qualified lead by default, nor does it prove budget, authority, need, timing, a meeting, opportunity, or purchase. HubSpot's scoring documentation illustrates why fit and engagement inputs need an explicit combination rule. HubSpot, "Understand the lead scoring tool" It does not define the SellersGPT billable state or product price. That unit should appear identically in the product, invoice explanation, evidence page, dispute process, and reporting export. If the operational system says one thing and the commercial page says another, the buyer cannot reconcile charges. Advertising metrics remain upstream and separate. Google Ads defines average CPC as click cost divided by clicks and average CPA as conversion cost divided by configured conversions. Google Ads Help, "Average cost-per-click (Avg. CPC): Definition" Google Ads Help, "Average CPA: Definition" These definitions make clear why an advertising CPC or lead-action CPA is not a Qualified Lead product price.

2. How SellersGPT applies the model

The SellersGPT mechanism has nine controlled steps: 1 A customer has an eligible, funded account arrangement under the applicable commercial terms. 2 The approved ICP and qualification rule define the required evidence and exclusions. 3 An eligible event creates or updates a Lead record. 4 The system evaluates fit, identity, completeness, evidence, and hard stops under the effective version. 5 A passing record enters the Qualified Lead state. 6 The pricing service resolves the exact unit price effective for the tenant, industry, currency, and product version. 7 A traceable billable-event record is linked to the qualification and price records. 8 A timely dispute, when permitted, opens an evidence review; the disputed fee is not deducted while that review remains open. 9 At clear or solved status, a rejected dispute posts in the resolution month, while an upheld dispute is not charged if it has not posted. A linked account credit is used only if an already-posted charge requires correction under the applicable rule. Optional follow-up fees remain separate. This sequence protects two kinds of truth. The evidence packet explains why the unit exists. The pricing record explains which amount applied. Neither should be reconstructed from the other.

3. Use the Billable Event Ledger

The Billable Event Ledger is the minimum reconciliation record. Field Required content Why it matters Billable unit Qualified Lead ID and state-created event Prevents billing against a click, score, or unverified record Qualification rule Version and effective time Makes the criteria reproducible Evidence packet Criterion results, evidence references, hard stops Enables review without exposing unsupported claims Price key Tenant, industry, currency, product/version key Identifies the applicable commercial record Effective unit price Exact value read from pricing system Prevents benchmark-based inference or manual retyping Charge event Amount, currency, posting time, ledger ID Records a clear, non-disputed, or rejected-and-resolved financial entry Exclusion controls Existing Customer and other applicable blocks Shows why a record was or was not billable Dispute state Filed time, reason, evidence, reviewer, decision, clear/solved time Separates allegation from outcome and governs posting month Adjustment event No-charge decision or, only when needed, amount, currency, time, and related posted charge Prevents premature deduction and corrects an already-posted charge without deleting history Follow-up ledger Eligible unit, calendar month, stop event, Keeps optional service economics separate fee The display should let a customer trace from a billable event to evidence, see whether a dispute is pending, and trace any posted charge or later correction to its resolution. It should not expose sensitive internal logic or data beyond the authorized scope.

4. Resolve the exact effective price

The actual Qualified Lead unit price must come from the pricing system at the event's effective time. The lookup should use the governed key fields, such as tenant, SGT industry, currency, product variant, price version, and effective interval. Where a tenant-specific override or contract term applies, the authorized precedence rule must resolve it. Do not:

• use the USD 5.10 portfolio mean advertising CPC as a Qualified Lead price;

• divide a lead-action CPA by a conversion rate to create a product price;

• average product prices across industries or tenants;

• round the price with the benchmark's nearest-USD-5 rule;

• copy a current web-page value into a historical charge;

• replace a missing lookup with the nearest industry value. If price resolution fails, the safe outcome is an exception state, not an invented number. The event and qualification can be retained while the commercial operation waits for a valid pricing record. The public 2026 benchmark has a mean advertising CPC of USD 5.10, a public mean lead-action CPA of USD 71, and a modeled mean cost per MQL of approximately USD 229. Those are three planning metrics with three denominators. None is the actual Qualified Lead unit price.

5. Separate controls that look similar

Existing Customer Under the approved SellersGPT rule, an Existing Customer block prevents outreach and billing for the covered relationship. The evidence should show the relationship, scope, source, observation time, and applicable rule. A stale name match is not sufficient; identity and scope still matter. Suppression Suppression blocks outreach within its defined scope. It can apply to a contact, account, domain, campaign, or channel. Suppression alone is not the billing control and does not imply that a charge occurs. A suppressed contact could also be an Existing Customer, but the two facts should remain separate because they support different decisions. Duplicate and invalid records A duplicate should not create a second distinct Qualified Lead merely because another event arrived. The deduplication rule should define person, account, pursuit, and time boundaries. Invalid or ambiguous identity should enter review rather than be forced into the billable population. Pre-funded balance A pre-funded balance is an account funding and ledger control. It is not the lead's price, an outcome guarantee, or a subscription. The interface should distinguish available balance, reserved or pending amounts where applicable, posted Qualified Lead charges, follow-up charges, and any linked corrections.

6. Handle disputes without premature deduction

A dispute tests whether the record passed the rule that governed the charge. It should not ask whether the lead later bought or whether a salesperson liked the lead. The minimum dispute packet includes:

• Qualified Lead and charge identifiers;

• qualification and pricing-rule versions;

• the specific disputed criterion or exclusion;

• customer evidence and submission time;

• original evidence packet;

• reviewer, decision, reason, and time;

• billing outcome at clear or solved status, including any linked correction to an already-posted charge. Where the approved product rule applies, the current public workflow uses a five-day dispute window. That timing must be bound to the actual rule version and effective date displayed for the customer; it is not presented here as a universal legal right or a substitute for binding terms. Because reviewer and binding product-version fields are not populated in this draft, publication must keep the article in ready_for_review until that control is satisfied. The latest effective SellersGPT decision states that a disputed fee is not deducted while review remains open. If the dispute is rejected, the fee is billed in the month the case is cleared or solved. If the dispute is upheld before a charge posts, the disputed fee is not charged. If an applicable correction is required after a charge has already posted, append a linked account-credit entry rather than rewriting history. Do not apply both a no-charge outcome and a credit for the same amount. Preserving the Qualified Lead event, dispute, decision, posted charge if any, and linked adjustment keeps gross creation, dispute rate, and net billing reconcilable. The source archive labels implementation of this lifecycle NOT VERIFIED, so publication must not imply that the production system has been validated until QA supplies evidence. FTC business guidance supports the general publication principle that objective marketing claims should be truthful and evidence-based. U.S. Federal Trade Commission, "Advertising and Marketing Basics" It does not approve SellersGPT commercial terms or determine a dispute.

7. Itemize follow-up separately

Optional follow-up is priced separately at USD 3 per eligible Qualified Lead per calendar month when the service applies. It is not the Qualified Lead unit price, a fixed monthly platform fee, or a subscription. Use the formula: follow-up service cost = eligible Qualified Leads x billable calendar months x USD 3 Because leads may enter, stop, transfer to human ownership, or leave the eligible service at different times, calculate lead-months rather than multiplying one month count by every lead automatically. Qualified Lead Eligible calendar months Stop or ownership event Follow-up cost QL-A 3 Human takeover after month 3 USD 9 QL-B 1 Stop rule during month 1 USD 3 QL-C 2 Service completed after month USD 6 This fictional table totals 6 lead-months x USD 3 = USD 18. It says nothing about conversion. Operational rules determine eligibility and stop timing.

8. Recalculate a symbolic scenario

Illustrative scenario - explicitly fictional. Let P be the exact Qualified Lead unit price returned by the effective pricing-system record. A closed monthly cohort creates 8 gross Qualified Lead state events. Seven are clear and one timely dispute is upheld before its fee posts. Five eligible QLs receive follow-up for one calendar month, three continue for a second, and one continues for a third. 1 Gross Qualified Lead state events: 8. 2 Clear posted Qualified Lead charges: 7 x P = 7P. 3 Upheld disputed item before posting: 1 x P is not charged, so account credit is 0. 4 Net Qualified Lead charges: 7P. 5 Follow-up lead-months: 5 + 3 + 1 = 9. 6 Follow-up service cost: 9 x USD 3 = USD 27. 7 Net program ledger total for these units: 7P + USD 27. If the effective price lookup returns a value, insert it for P without rounding or changing currency. The scenario remains reproducible without publishing or inventing a product price. If the eighth charge had already posted under an applicable earlier state and then required correction, the alternative ledger would show 8P posted and a linked P credit, also producing 7P; it must not also record the item as uncharged. The scenario keeps dispute treatment and follow-up service visible rather than hiding either inside a blended average. If the buyer wants its complete internal cost per net Qualified Lead, it may add its separately defined internal handling costs and divide by 7 net units. That customer-side cost is not the product price.

9. Compare risk allocation

Pay per Qualified Lead shifts the vendor's unit beyond a raw click or captured lead, but it does not transfer all commercial risk. The buyer still controls or influences offer, response process, sales capacity, pricing, technical validation, procurement, and closing. The provider does not promise meetings, opportunities, or revenue merely because the unit sits further downstream. Evaluate:

• how precise and testable the qualification definition is;

• which research, media, systems, and operations are included;

• whether volume is committed, capped, or variable;

• how duplicates and Existing Customers are treated;

• what evidence is available with each unit;

• how dispute holds, resolution-month billing, and any later corrections work;

• whether follow-up is included or separately priced;

• which downstream work remains with the customer.

10. Common mistakes

• Comparing only the headline unit price.

• Treating USD 5.10 advertising CPC as a Qualified Lead price.

• Billing against a score without an evidence packet.

• Manually retyping a price into content or operations.

• Confusing Suppression with the Existing Customer billing block.

• Judging disputes by later sales outcome instead of the effective qualification rule.

• Deducting a disputed fee while review is open, or applying both no-charge and credit treatment to the same amount.

• Hiding the USD 3 follow-up fee inside the Qualified Lead unit price.

• Calling a funded balance a subscription.

• Promising a meeting, opportunity, revenue, or ROI.

11. Limits and publication controls

This article explains SellersGPT product mechanics in a non-binding way. The applicable order form, price record, qualification rule, dispute policy, tax treatment, and legal terms control a specific transaction. Product rules can change by version and effective date. No unit price appears because the provided benchmark data does not contain the authoritative customer billing value. Publication should resolve price dynamically where approved, never from this article. No result downstream of qualification is guaranteed.

12. Frequently asked questions

Am I paying for clicks? No. Under this model, a click is an upstream advertising or engagement event. The billable unit is a record entering the SellersGPT Qualified Lead state under the applicable rule. Is the Qualified Lead price the same as cost per MQL? No. Cost per MQL is an acquisition-cost measure or model. The Qualified Lead price is an exact product price from the effective pricing-system record. What happens when a dispute is resolved? No disputed fee is deducted while review is open. A rejected dispute is billed in the month it is cleared or solved. An upheld dispute is not charged if it has not posted; if an already-posted charge requires correction under the applicable rule, a linked account credit preserves the audit trail. Does Suppression prevent billing? Suppression blocks outreach in its scope. It is not, by itself, the billing control. Existing Customer is the stated control that blocks outreach and billing under the approved rule. Is the USD 3 fee a subscription? No. It is a separate follow-up service fee per eligible Qualified Lead per calendar month when that service applies.

Sources and methodology

The Billable Event Ledger, symbolic price P, dispute hold and resolution-month treatment, conditional account-credit correction, Existing Customer and Suppression controls, five-day conditional workflow, and USD 3 follow-up rule are SellersGPT product-specific. They must be reconciled to the effective commercial and product version before publication. The archived billing decision marks implementation NOT VERIFIED. External sources support only metric and claims boundaries. 1 LE-01-INTERNAL-DEFINITION - SellersGPT Knowledge, "What Counts as a Qualified Lead?". Internal definition used by this release; not an external benchmark. 2 LE-03-INTERNAL-PRODUCT-RULES - SellersGPT product-rule controls summarized in this guide. Reviewed for the Module 05 production specification on August 25, 2026. Binding version and effective date must be populated before publication. 3 DEF-01 - Google Ads Help, "Average cost-per-click (Avg. CPC): Definition". Accessed August 25, 2026. Defines CPC; does not support a Qualified Lead price. 4 DEF-03 - Google Ads Help, "Average CPA: Definition". Accessed August 25, 2026. Defines CPA arithmetic; does not define the SellersGPT billable unit. 5 QUAL-01 - HubSpot, "Understand the lead scoring tool". Accessed August 25, 2026. Supports fit and engagement scoring distinctions; does not support SellersGPT pricing. 6 GOV-04 - U.S. Federal Trade Commission, "Advertising and Marketing Basics". Accessed August 25, 2026. Supports evidence-based public claims; does not approve commercial terms.