The ask behind the ask
A pattern that’s become common at pre-seed: a founder likes a vendor, doesn’t have the cash to pay full freight, and asks for a discount. Increasingly, that ask has changed shape. Instead of “can you cut your rate,” founders are asking “can you take a piece of what this generates instead of a flat fee.” It shows up with outbound agencies, fractional CROs, recruiters, even some dev shops. The framing is usually the same: we’re pre-revenue or barely post-revenue, we don’t want to burn runway on a fixed retainer, so let’s align incentives and you get paid when we get paid.
It’s a reasonable instinct. It’s also a request that most vendors, including outbound agencies, are structurally unable to say yes to in the form founders imagine. Understanding why matters more than the ask itself, because it explains what a workable version actually looks like.
Why founders are asking now
Pre-seed rounds have gotten smaller and slower to close in many categories, and the founders raising them have absorbed two years of advice about capital efficiency. A $150k check that has to last 12-18 months doesn’t leave room for a $6-10k/month outbound retainer that may or may not produce pipeline in the first 90 days. Revenue share feels like it solves the cash problem and the risk problem at once: no cash out the door until there’s cash coming in.
There’s also a generational effect. Founders who’ve watched SaaS pricing shift toward usage-based and outcome-based models expect vendors to price the same way. If Stripe takes a cut of the transaction instead of charging a subscription, why shouldn’t a growth vendor take a cut of the deal?
Why it rarely works as pitched
The math breaks down for a few structural reasons that are worth naming plainly, because a founder who understands them negotiates better.
Attribution is messy. A revenue share deal requires agreeing on what counts as “revenue from this vendor’s work.” If an outbound agency books a meeting, an AE closes it four months later after three product demos and a security review, and the buyer also saw a LinkedIn ad and talked to a friend who’s a customer, whose revenue is it? Founders and vendors will disagree on this constantly, and disputes over attribution are one of the most common reasons revenue share arrangements sour.
The vendor doesn’t control the close. An outbound agency, recruiter, or lead-gen shop influences the top of the funnel. It doesn’t run your demo, doesn’t price the deal, doesn’t handle procurement, and has no say over whether your product actually solves the problem. Asking a vendor to take payment risk on a process they don’t control is asking them to underwrite your sales execution, not just their own work.
Pre-seed companies are volatile. Pricing changes, ICPs pivot, teams turn over. A revenue share agreement signed in month one against an ICP that gets abandoned in month four leaves both sides holding a contract that no longer maps to reality.
Cash flow timing kills vendors, not just founders. A vendor still has to pay callers, SDRs, or recruiters now, in cash, regardless of when your deal closes. If they’re not getting paid until you get paid, they’re extending you a working capital loan with founder-level risk and vendor-level return. Very few service businesses can carry that on more than a handful of accounts at once, which is why most who “do” revenue share cap how much of their book can be structured that way.
What actually gets negotiated
Given those constraints, the deals that do get done usually aren’t pure revenue share. They’re hybrids, and it’s worth knowing the shapes so you can ask for something a vendor can actually say yes to:
Reduced base plus a bonus or kicker. A lower monthly fee that covers the vendor’s hard costs, plus a bonus tied to closed-won revenue or a defined milestone (meetings held, opportunities created, deals closed within a set window). This is the most common landing spot because it caps the vendor’s downside while still rewarding results.
Deferred payment, not contingent payment. The full fee is owed regardless, but a portion is deferred 60-90 days. This helps cash timing without asking the vendor to bet on your close rate.
Performance-based pricing on a metric the vendor controls. Pay-per-meeting is the clean version of this. The vendor is paid for the thing they actually produce, a qualified meeting, not for a downstream outcome shaped by your product, your pricing, and your closing skills. It aligns incentives without asking the vendor to absorb risk they can’t manage.
Equity or warrants as a small kicker, not the core structure. Some vendors will take a small equity component alongside a reduced cash fee, especially for a founder they believe in. This should be a sweetener, not a substitute for a real cash mechanism, because equity doesn’t pay a caller’s salary next Tuesday.
If you’re a founder making this ask, come with a proposal, not just a constraint. “We can pay X now and Y as a bonus on closed revenue in the first 6 months, capped at Z” is negotiable. “Take a cut of everything and we’ll figure out attribution later” usually isn’t, because it asks the vendor to trust a process it can’t see.
Where a pay-per-meeting model fits
This is worth being direct about, because it’s easy to conflate revenue share with performance pricing: they’re not the same thing, and the distinction matters for pre-seed founders specifically.
A pay-per-meeting model, which is how Nurturance is structured, already solves the core problem founders are reaching for with revenue share, without the attribution disputes or the multi-month cash lag. You pay for meetings that get booked and held, not for a subscription regardless of output, and not for a slice of revenue the vendor has no control over. If you’re pre-seed and weighing whether to build outbound in-house, hire a fractional SDR, or go the DIY tooling route with a sequencer and a list, the honest answer is that DIY can work if you have someone internal who’ll own it daily and you’re prepared for a slow ramp. A managed pay-per-meeting service tends to be the better fit when you need pipeline on a specific timeline, don’t have bandwidth to manage callers or tooling yourselves, and would rather pay for a concrete, countable output than negotiate a revenue share structure that’s hard to write cleanly into a contract at this stage.