A straight conversation about your program. No hard sell, and no obligation to work together.
THE DEFINITION
What Affiliate Marketing Lead Generation Is
Affiliate marketing lead generation is a performance model in which an advertiser pays approved partners for a defined lead or downstream conversion event rather than for traffic. The partner sends a prospect, the advertiser validates the submission against agreed qualification rules, and payment follows only for events that pass those rules.
That last clause is where most programs come apart. Paying for a defined event means you first have to define it, and the definition has to survive contact with your sales team.
Six events get loosely called “a lead”, and they aren’t interchangeable:
- Raw inquiry: a form submission. No qualification applied.
- Marketing-qualified lead (MQL): meets your fit and intent criteria on paper.
- Sales-accepted lead (SAL): sales has reviewed it and agreed to work it.
- Sales-qualified lead (SQL): sales has made contact and confirmed need, authority and timing.
- Opportunity: a live deal with a value and a close date.
- Closed customer: signed and paying.
A lead generation affiliate is compensated for whichever of those you nominate. Before a single partner is recruited you need four things in writing: the payable event, the qualification criteria, the rejection criteria, and the validation window in which you’re allowed to reject. Programs that launch without all four end up litigating each invoice.
THE OPERATING MODEL
Affiliate Lead Generation
Affiliate lead generation is the complete loop from recruiting a partner to paying them for a validated outcome. In a B2B or SaaS context that loop has to close through your CRM, because the affiliate platform on its own can’t tell you whether a lead was any good.
The sequence I work through when designing one:
- Define the conversion event. Pick the furthest-downstream event you can track reliably. Paying on raw inquiries is simplest and produces the worst partner mix.
- Establish qualification and rejection criteria. Write them as rules a third party could apply without asking you. If two people on your team would score the same lead differently, the rule isn’t finished.
- Model the allowable CPL from gross margin, not from what competitors pay.
- Choose a payout model. Each shifts risk differently.
- Recruit partners whose audiences match the ICP. Fit first, volume second.
- Configure tracking and lead-status feedback. The platform needs to receive qualification outcomes, not just send clicks.
- Validate and deduplicate submissions against each other, your CRM, and your existing customer base.
- Approve or reject inside the stated validation window, with a reason code attached.
- Optimize partners on downstream quality and revenue, not on submission counts.
Steps six through nine are the ones that get skipped, and they determine whether the program is profitable. Lead gen affiliate marketing is the same channel discipline you would apply to any considered purchase. It simply has more places to leak.
LEAD QUALITY
Affiliate Marketing Leads
Lead count and lead value are different numbers, and treating them as the same one is the most expensive mistake in this channel. A partner who submits four hundred inquiries a month and produces no opportunities isn’t a high-volume partner. They’re a cost.
Affiliate marketing leads should be assessed on ICP fit, role and purchasing authority, product use case, intent, lead source and promotional method, duplicate status, existing customer status, sales acceptance, and finally opportunity creation and closed revenue. The last two settle every argument the others start.
Qualified versus unqualified, in practice
| A qualified affiliate lead | An unqualified affiliate lead |
|---|---|
| ✓Company matches your ICP on size, sector and region | ✗Sole trader, student, or an unreachable company |
| ✓Contact has budget influence or is the buyer | ✗No purchasing role, often no role stated |
| ✓Stated need maps to a product you sell | ✗Generic interest, or a use case you don’t serve |
| ✓First appearance in your CRM | ✗Already in pipeline via sales outreach or paid search |
| ✓Contact details verify and respond | ✗Bounced email, disconnected number, fabricated fields |
| ✓Reached you through a disclosed, approved placement | ✗Arrived via incentivized traffic or an unapproved method |
| ✓Sales accepts and works it | ✗Sales rejects on sight, repeatedly, from the same partner |
The right-hand column isn’t hypothetical. It’s what arrives when you pay a flat rate per form fill and publish no rejection rules.
WHERE THE RISK SITS
Payout Models for a Lead Generation Affiliate Program
Every model below is legitimate. They differ in who absorbs the risk of a bad lead, and how much tracking infrastructure they demand.
| Model | Payment triggers on | Who carries more risk | Tracking required | Use when | Common failure |
|---|---|---|---|---|---|
| CPL (cost per lead) | Any valid form submission | Advertiser | Click-to-form tracking only | Short cycles, high volume, cheap products | Rewards volume over fit; attracts incentivized traffic |
| CPQL (cost per qualified lead) | Submission passing your MQL rules | Shared | Lead status returned to the platform | Defined ICP, agreed qualification rules | Rules drift; disputes if criteria are vague |
| CPSAL (cost per sales-accepted lead) | Sales accepts the lead | Shared, tilted to partner | CRM feedback loop | Sales team with disciplined acceptance logging | Slow sales follow-up starves partner earnings |
| CPO (cost per opportunity) | Opportunity created with value | Partner | Full CRM matchback | High ACV, long cycles, mature sales ops | Payment delay too long for most partners to fund |
| CPA (cost per acquisition) | Closed and paid | Partner | CRM matchback plus revenue data | Self-serve or fast-closing products | Partners won’t promote if the cycle is 90+ days |
| Hybrid | Small payment on lead, larger on downstream outcome | Genuinely shared | Both lead tracking and CRM matchback | Long B2B cycles where partners need cash flow | Complex to configure and to explain to partners |
For most SaaS and fintech programs I would start with a hybrid. A modest validated-lead payment keeps partners funded while they wait out your sales cycle; the larger payment on opportunity or closed revenue keeps their incentives pointed at quality. Pure CPA looks safest on a spreadsheet and quietly kills recruitment, because a partner can’t run a business on revenue that arrives four months after the work.
The cheapest CPL is rarely the most profitable. A partner charging $40 per lead with a 5% acceptance rate costs $800 per accepted lead. A partner charging $150 with a 70% acceptance rate costs $214. Judge cost per accepted lead, and eventually cost per opportunity, never the headline rate.
THE ARITHMETIC
SaaS and Fintech Lead Economics
Before negotiating any rate, calculate what a lead can be worth to you. The arithmetic isn’t complicated; the discipline is in doing it before launch rather than after.
The equation:
Gross profit per customer = ACV × gross margin % Accepted lead to customer = lead-to-opportunity rate × opportunity-to-close rate Expected value per lead = gross profit per customer × (accepted lead to customer) Allowable CPL = expected value per lead × target acquisition share
Worked example: hypothetical, not a client result
All figures below are modeled illustrations. They aren’t client results and not industry benchmarks. Use the structure; substitute your own numbers.
A B2B SaaS product with a $12,000 ACV and an 80% gross margin produces $9,600 in first-year gross profit per customer. The business is willing to spend 30% of that on acquisition, giving an allowable CAC of $2,880.
Historically, 25% of accepted leads become opportunities and 20% of opportunities close, so an accepted lead converts to a customer 5% of the time.
- Expected gross profit per accepted lead: $9,600 × 5% = $480
- Maximum sustainable CPL on accepted leads: $2,880 × 5% = $144
If 40% of raw submissions get rejected, and you choose to pay on raw leads instead of accepted ones, the same economics support only $86.40 per raw lead. The rejection rate isn’t an administrative detail. It’s a direct multiplier on what you can afford to pay.
Why a $400 lead can be cheap and a $40 lead expensive
Run the same equation on an enterprise product at $120,000 ACV and 80% margin: $96,000 gross profit, and if a demo request closes 10% of the time, each one carries $9,600 in expected gross profit. At a 30% acquisition share, $400 for that demo request is inexpensive.
Now run it on a small e-commerce offer with a $60 order value at 40% margin. Gross profit is $24, so a $40 lead is unprofitable before sales even calls. Same channel, opposite conclusion, which is why generic CPL benchmarks are worse than useless.
Differentiated rates
Once the model holds, stop paying one flat rate. Rates should vary by lead status, geography, customer segment, partner type, verified quality, pipeline contribution and closed revenue. Paying an enterprise-focused partner the same as a long-tail directory listing is how good partners get poached.
THE HARD PART
B2B Attribution Across Long Sales Cycles
A lead arrives in March and closes in July. Between those dates the prospect visits three times from two devices, attends a webinar, gets an outbound email, and eventually converts through a branded search. Who gets paid?
For a ninety-day cycle this is the whole game, and it’s the part neither competing page addresses seriously.
The pieces you have to reconcile:
- Cookie duration. A thirty-day window is fine for retail and structurally wrong for B2B. Against a ninety-day median cycle it systematically underpays partners and understates the channel.
- First-touch versus last-touch. Affiliate platforms overwhelmingly pay last-touch. Your CRM often reports first-touch. Both are internally consistent and they won’t agree.
- Cross-device activity. Research on a phone, purchase from a work laptop. Click-based attribution loses this unless identity is stitched.
- Self-reported attribution. A “how did you hear about us?” field is imperfect and still one of the most useful B2B signals available, because it captures influence no cookie sees.
- CRM matchback. Reconcile platform events against CRM records on a stable identifier. This is what turns affiliate activity into pipeline you can defend in a board meeting.
- Offline and sales-assisted conversions. Deals closed by a rep still need their originating partner credited.
- Existing-account and existing-opportunity exclusions, plus duplicates across affiliates and paid media. Nobody should be paid twice, or paid for a company already in pipeline.
- Retroactive status updates. Leads get requalified weeks later, and your payment logic has to accommodate that.
The flow to instrument:
Affiliate click → landing page → form submission → tracked event → CRM record → qualification → opportunity → closed revenue → partner-quality feedback
The final arrow is the one nearly everyone omits, and it’s the one that makes the program improve.
Two attribution questions, not one
Keep these separate and say so in your program terms. Payment attribution is a contractual rule: simple, published, consistently applied and auditable. Partners are entitled to know exactly how credit is assigned. Analytical attribution is an internal question about incrementality and channel contribution, and it can be as sophisticated as you like.
When the two disagree, and they will, you pay according to the contract and you argue about the analysis internally. Retrospectively rewriting payment rules because a multi-touch model produced an inconvenient number is the fastest way to lose the partners worth keeping. If the payment rule is genuinely wrong, change it going forward, announce it, and honor the old rule for work already done.
A PROCESS, NOT A PROMISE
Lead Validation and Scrubbing
“Lead quality matters” isn’t a process. This is a process.
- Capture a stable identifier at submission: an account ID, a normalized email, or a company domain. Everything downstream depends on it.
- Check required fields and formatting. Valid email syntax, deliverable domain, plausible phone format.
- Verify geography and ICP criteria against the rules in your program terms.
- Check for duplicates across partners, across channels, and against prior submissions.
- Check for existing customers and open opportunities. Suppress, don’t pay.
- Screen for bots, fabricated data and incentivized submissions. Look at submission timing, field patterns and traffic source.
- Apply sales-acceptance criteria: the point at which a human agrees to work it.
- Assign a standardized rejection reason to everything you decline.
- Return the status to the affiliate platform so partners see outcomes, not silence.
- Update partner quality scores from downstream results, and act on them.
Example rejection reason codes
A schema you define and publish, not a platform default:
| Code | Reason |
|---|---|
| DUP-01 | Duplicate of an existing lead or partner submission |
| GEO-02 | Outside approved geography |
| ICP-03 | Company size, sector or use case outside ICP |
| CUST-04 | Existing customer or open opportunity |
| DATA-05 | Invalid or unreachable contact details |
| ROLE-06 | No purchasing influence |
| FRAUD-07 | Suspected fabricated or incentivized submission |
| TERMS-08 | Promotional method breached program terms |
On validation windows. State the window before launch, keep it as short as your process honestly allows, and hold to it. A partner can plan around a fourteen-day validation period. They can’t plan around reversals that arrive whenever someone gets round to the queue. Enforce rejection rules identically across every partner, including the ones you like. The moment enforcement becomes discretionary, your best partners assume the program is arbitrary and go elsewhere.
TRIGGERS, RULES AND ACTIONS
Configuring a Lead Program in PartnerStack
PartnerStack builds program logic from triggers, which its documentation describes as if-this-then-that statements made of an Event, a set of Rules, and an Action. Triggers are created under Advanced Settings, and the trigger types are Offer, Drip Offer, Group Move and Apply Tag.
The events relevant to a lead program include A customer is created, A lead is qualified, A lead is closed, A lead stage changes, A customer is updated and A deal stage changes. Lead-level rules can target Lead Stage Status, Lead Stage Name, Lead Stage API Name and Date submitted.
Minimum viable setup
- Record the lead event. PartnerStackJS sends signups from your front end: populate growsumo.data.name, growsumo.data.email and growsumo.data.customer_key, then call growsumo.createSignup().
- Use a stable customer_key. Your own account ID is better than an email address, because emails change and duplicate.
- Build one Offer trigger on A customer is created, with a flat commission. PartnerStack’s percentage commission type requires a Transaction Created event, so lead payouts are flat by design.
- Write the offer description in partner-facing language. Partners never see trigger names or rules.
Stronger setup for a long B2B sales cycle
- Trigger on qualification rather than creation. A lead is qualified or A lead stage changes lets you pay for a validated outcome, with rules targeting the specific stage.
- Use A customer is updated for CRM-driven qualification. It fires when a customer property referenced in its rules changes, for example a Customer Status moving to Qualified. Note the documented behavior: it fires once per customer, which is a useful guard against paying twice for the same account.
- Use a Drip Offer where you need a delay or a cancellation period before commission accrues.
- Delay approval, not just payment. Commissions arrive in the partner’s dashboard as pending and require your team’s approval before they’re invoiced, so the review step is native.
- Differentiate rewards using partnership rules (Group, Tier, Tag and Partner Key) so enterprise-focused partners are on different terms from long-tail ones.
- Set Trigger Evaluation Order deliberately. PartnerStack’s own documentation shows how the wrong order pays two commissions for one event.
- Test the whole journey end to end before recruiting anyone. Click a partner link, submit a form, watch the event land, run it through qualification, confirm the commission fires once.
EVENT TYPES AND ACTION LOCKING
Configuring a Lead Program in impact
impact organizes tracking around Event Types, each with a unique ID (an EventTypeId, also called an ActionTrackerId). The relevant one here is Online Lead, documented as tracking the Customer ID and email of a prospect. An Action is a tracked conversion credited to a partner, and it moves through a documented life cycle.
- Confirm your Online Lead Event Type and its ID. Event Types are typically configured with impact rather than self-served.
- Choose a tracking method. The Universal Tracking Tag (UTT) with a trackConversion call covers browser-side tracking; API tracking is the server-to-server, cookie-less route; FTP submission matches on ClickID.
- Pass a unique identifier on every action. Oid is documented as your own unique identifier for the order or event, and it’s the field any deduplication logic has to be built on. CustomerId and CustomerStatus carry the account context.
- Set the Action Locking period to cover your validation window. Locking can be a fixed duration of up to ninety days, or a dynamic Month + Day configuration. Actions can only be modified or reversed before the locking date, so a locking period shorter than your qualification cycle removes your ability to correct anything.
- Reject invalid events by reversing them before they lock. Actions move from PENDING to APPROVED or REVERSED; a reversed action voids the cost and pays nothing. Batch Modifications & Reversals handles this at volume.
- Use SharedId to carry partner-level or campaign-level context through to reporting.
- Reconcile against your CRM on a fixed cadence, using Oid and CustomerId as the join keys.
- Test the edge cases, not just the happy path: a duplicate submission, a reversal before locking, an action that should have been suppressed as an existing customer.
Confirm current field names and locking options with impact during implementation. Platform documentation changes, and the setup above should be validated against your own account rather than assumed.
PartnerStack or impact
| PartnerStack | impact | |
|---|---|---|
| Native fit | SaaS and B2B, partner-type breadth built in | Broad: retail, B2B, and large mixed programs |
| Lead handling | Explicit lead and deal objects with stage-aware triggers | Lead handled as an Online Lead Event Type in a general action model |
| Validation control | Commission approval step plus Drip Offers | Action Locking window with modification and reversal |
| Reward logic | Trigger builder with grouped AND/OR rules | Contract terms and payout rules per event type |
| Leans toward | Software companies wanting reseller, referral and affiliate partners in one place | Programs needing granular action-level financial control at scale |
Neither is universally better. Programs already running B2B partner motions with deal registration tend to settle on PartnerStack. Programs needing action-level financial control across a large, mixed partner base tend to settle on impact. I don’t take referral commissions from either, so the recommendation depends on your operating context, not on my relationships.
QUALITY OVER COUNT
Recruiting Partners Who Can Deliver B2B Leads
Partner count is a vanity metric. Ten partners who understand your category will out-produce two hundred who signed up because your program appeared in a directory.
Partner types worth pursuing for B2B and SaaS lead generation: niche publishers with genuine category authority; educators and subject-matter experts whose audiences trust them; consultants already advising your buyers; integration and technology partners whose customers overlap with your ICP; agencies implementing in your category; review and comparison sites; professional communities; newsletter operators with tight, targeted lists; and existing customers or advocates, where a referral arrangement is appropriate and disclosed.
Partner qualification checklist
- Does their audience match your ICP on sector, seniority and geography?
- Do they have credibility in the subject, or only traffic?
- Does their content reach buyers with intent, or only researchers?
- Can they explain a considered purchase, or only transactional offers?
- What promotional methods will they use, and are all of them approved?
- What is their compliance history with other programs?
- What lead volume is realistic, and at what expected quality?
- Will they accept a validation window and a rejection process?
The last question is the useful filter. A partner who objects to any lead validation at all is telling you what their leads are worth.
Not sure whether your lead economics support a partner program? That’s the first thing I would look at, usually as an Affiliate Growth Audit.
WHAT GOES WRONG
Fraud, Compliance and Privacy
Lead-based payment attracts a specific set of abuses. The ones I watch for: duplicate submissions and form stuffing; fabricated contact details; incentivized leads from users paid to submit; brand-bidding violations on your own terms; self-referrals; existing customers resubmitted as new; leads from outside approved geographies; bot-generated activity; misrepresentation of your offer in partner copy; and unauthorized use of creative or claims.
Most of this is prevented by writing things down before launch rather than detecting them afterwards:
- Written program terms stating exactly what is permitted
- An approved list of promotional methods, with everything else requiring prior sign-off
- Documented qualification rules the partner can read
- Standardized rejection reasons applied consistently
- A fixed validation window
- Audit trails on every approval, rejection and reversal
Consent and privacy deserve particular care here, because you’re receiving personal data collected by a third party. Where the partner collected it, what the person consented to, and whether that consent covers contact from you are questions to settle before the first submission, not after a complaint. Get your own legal and privacy review of your program terms and data flows. I can tell you where the operational risks sit; I’m not a lawyer and this isn’t legal advice.
TWO KINDS OF NUMBERS
Measuring and Optimizing the Program
Split your metrics into two groups and never let the second group drive a commercial decision.
Commercial outcome metrics (what the program is worth): accepted-lead rate, cost per accepted lead, sales-qualified lead rate, opportunity rate, pipeline generated, closed revenue, customer acquisition cost, payback period, and gross profit by partner.
Diagnostic metrics (where it’s breaking): click-to-lead rate, landing-page conversion rate, duplicate rate, rejection rate, time to qualification, partner activation rate, lead velocity, reversal rate, and sales follow-up time.
Optimizing for raw lead volume or the lowest headline CPL rewards exactly the wrong partners. The partner sending three hundred cheap unqualified submissions looks like your best performer on a volume dashboard and your worst on a gross-profit-by-partner report.
What downstream outcomes should change: partners with strong opportunity rates get rate increases, exclusive offers and direct attention. Partners with volume but weak acceptance get specific feedback and a defined window to improve. Partners with persistent duplicate or rejection rates get removed. That last decision is harder than it sounds when the partner is producing visible dashboard activity, which is exactly why it needs to be governed by numbers agreed in advance.
BEFORE YOU COMMIT
When This Model Works, and When It Doesn’t
| Best fit | Not a good fit |
|---|---|
| ✓Proven product-market fit and a repeatable sale | ✗Pre-revenue, still testing the offer |
| ✓A defined ICP you can express as rules | ✗No agreed definition of a good lead |
| ✓Meaningful customer value relative to lead cost | ✗Margin too thin to fund partner payment |
| ✓A functioning sales process with capacity to follow up | ✗Leads sitting untouched for days |
| ✓Reliable CRM ownership and clean data | ✗CRM nobody maintains |
| ✓Willingness to return lead-status feedback to partners | ✗Unwilling to share outcomes |
| ✓Competitive partner economics | ✗Expecting partners to work for below-market rates |
| ✓Clean, tested tracking | ✗Tracking already known to be broken |
| ✓Patience for a channel that compounds | ✗Expecting immediate scale |
If several items in the right-hand column describe your situation, the honest answer is that affiliate lead generation isn’t your next move. Fix the funnel, the qualification process or the tracking first. A partner program built on a sales process that doesn’t convert simply distributes the problem to people you now have to pay.
FOUNDER-LED, SINCE 2005
A Platform Records Events. It Doesn’t Run the Program.
PartnerStack and impact are both good at what they do, which is recording events, applying rules and moving money. Neither one recruits a partner, reads an application, judges whether a commission structure protects your margin, notices that one partner’s acceptance rate has quietly halved, reconciles the platform against your CRM, enforces your terms when a valuable partner breaches them, or decides which three partners deserve your attention this quarter.
That work is judgement, and it’s continuous. It’s also where most lead generation affiliate programs fail, not because the partners were wrong, but because nobody was doing the operational work of running the channel.
I’ve been managing affiliate programs since 2005, and I do this work personally. There’s no account team and no handoff to a junior manager. If you engage me, the person modelling your lead economics, writing your qualification rules and having the difficult conversation with an underperforming partner is the same person you spoke to on the first call.
QUICK ANSWERS
Affiliate Lead Generation FAQs
What is affiliate marketing lead generation?
It’s a model in which an advertiser pays approved partners for defined lead or downstream conversion events instead of for traffic or clicks. The advertiser sets the payable event, the qualification rules and the validation period, and pays only for submissions that pass.
How does a lead generation affiliate program work?
A partner promotes your offer through an approved method and sends prospects to a tracked landing page. Submissions are recorded as events in an affiliate platform, validated against your qualification and duplicate rules, then approved or rejected within a stated window. Approved events generate a commission, and downstream CRM outcomes feed back into how each partner is managed.
How much should an affiliate be paid for a lead?
Work backwards from gross margin. Multiply gross profit per customer by your accepted-lead-to-customer rate to get the expected value of a lead, then pay a defined share of that. A rate that works for a $12,000 ACV product will be wrong for a $120,000 one and catastrophic for a $60 order.
What makes an affiliate marketing lead qualified?
ICP fit, purchasing authority, a genuine use case, real intent, verifiable contact details, no duplicate or existing-customer conflict, and acceptance by your sales team. Qualification has to be written as rules before launch, or it becomes an argument at invoice time.
How do you track affiliate leads through a long B2B sales cycle?
Extend the cookie window to match your actual sales cycle, capture a stable identifier at form submission, add a self-reported attribution field, and reconcile the affiliate platform against your CRM on a regular cadence. Then feed opportunity and revenue outcomes back to partner-level reporting.
Can PartnerStack manage a lead generation affiliate program?
Yes. PartnerStack supports lead and deal objects with stage-aware triggers, including A lead is qualified and A lead stage changes, so you can pay on a validated outcome rather than a raw submission. Commissions require approval before invoicing, which gives you a native validation step. Confirm current capabilities against PartnerStack’s documentation during setup.
Can impact track and validate affiliate leads?
Yes. impact uses an Online Lead Event Type, and every tracked action passes through a documented life cycle from PENDING to APPROVED or REVERSED. The Action Locking period defines how long you have to modify or reverse an action, which is the mechanism a lead gen affiliate program uses for validation. Set that window to cover your qualification cycle.
How do you prevent duplicate or fraudulent affiliate leads?
Capture a stable identifier on every submission, deduplicate against other partners and your existing CRM records, suppress current customers and open opportunities, screen for bot and incentivized traffic, publish standardized rejection reasons, and enforce them identically for every partner. Consistency matters more than sophistication.
Request a Free Affiliate Growth Audit
Most affiliate programs don’t fail because affiliate marketing doesn’t work. They fail because the program is passive, poorly recruited, overexposed to low-value partners, or missing operational fundamentals. The audit identifies the bottlenecks before you commit to anything. Need a narrower diagnostic? See the affiliate program fraud audit and affiliate compliance audit.
Free 30-Minute Audit
Paid In-Depth Audit: $1,000
What the Audit Covers
Request Your Audit
Short form, about 30 seconds. Prefer to give more detail? Complete the full audit request form →
I’ll only use this to review your program and reply directly. No spam. No hard sell. Practical recommendations whether we work together or not.
READY TO START
Build a Lead Generation Program You Can Account For Commercially
If you’re considering paying partners for leads, or you already are and the numbers aren’t adding up, the useful next step is a conversation about your actual economics. I’ll look at your lead economics, your tracking setup, your current program or your launch plan, and tell you where the risk sits. If affiliate lead generation isn’t the right channel for you, I’ll say so.
Direct with me, not an account team. No hard sell.