When Does Lead Gen Billing Actually Start — and When Does the Work?

You signed on a Monday. The payment cleared on Tuesday. It is now the Thursday of the following week, not one prospect has been contacted, and you are eleven days into a month you have already paid for. Nobody has done anything wrong. The list is being built, your messages are sitting in your inbox waiting for approval, and a sending number is somewhere in a carrier registration queue. But you are paying, and the outreach has not started, and nobody warned you that this would be the shape of the first stretch.

This is the most common unpleasant surprise in an outbound engagement and it is almost never a scam. It happens because two different clocks start on two different dates, and only one of them appears on your invoice. Vendor sites will tell you what a service costs. A few of the better ones will tell you to expect a ramp. Not one of them tells you which date the money keys off, which date the work keys off, and what you should do about the distance between the two.

That distance is the subject of this article. It is usually short — days to a few weeks — but it produces more avoidable disputes than anything else in the first quarter of an engagement, because it is the only period where you are paying full price for something you cannot see. The fix is not to negotiate the gap out of existence. It is to name it, bound it with a date, and know which of the two clocks each promise in your contract is actually running on.

Two clocks, and only one of them is on the invoice

The money clock starts on a contract event: a signature, a card charge, the first of a calendar month. It is administrative, it is instantaneous, and it is completely knowable before you sign anything.

The work clock starts on a readiness event: the moment a real message reaches a real prospect. It depends on decisions getting made, assets existing, accounts being connected, and — in text and email outreach especially — on third parties like carriers and mailbox providers who answer on their own schedule and offer neither of you a service level.

Every vendor page you have read collapses these into a single date, because from a marketing standpoint they genuinely are the same day: the day you became a client. From your standpoint they are not remotely the same day, and the interval between them is what you are really asking about when you ask when this starts.

So ask the question twice, in these two forms, and require two separate answers. When does billing start? And: on what date does the first message reach a real prospect? If both questions come back as one sentence, you have been given a sales answer rather than an operational one.

The four dates a contract can bill from

There are only four realistic candidates, and the choice between them is not a detail. Each one silently assigns the cost of a slow launch to somebody, and each one creates a specific failure mode that the other three do not.

Most agreements in this market bill from signature or from payment. That is the default rather than a trick, and a vendor proposing it is not telling you anything about their character. But it is a default, which means it was chosen by the party that wrote the paperwork, and it is negotiable in the ordinary way that terms are negotiable.

One distinction is worth drawing before it causes confusion. This is the date the engagement starts billing. It is a separate question from what triggers each individual charge once the engagement is running — whether an appointment counts when it is scheduled, when it is held, or when it is qualified, which is the per-appointment billing trigger and a different negotiation entirely. A contract can be perfectly clear about the second and silent about the first, and most of them are.

The start date decides who pays for a slow launch

Here is why this deserves a conversation rather than a shrug. Whichever date you land on, somebody is buying the onboarding period, and that is not a neutral allocation.

Bill from signature, and the vendor has no financial reason to hurry. Their month is running whether or not a message has gone out. That sounds like the case against signature billing, and it half is — but only half, because the same structure removes a real hostage problem in the other direction. Under first-send billing, a client who takes three weeks to approve a message set has, without meaning to, put the vendor on an unpaid retainer. Signature billing is partly a defense against that, and the delay it is defending against is a common one.

Bill from first send, and the vendor eats their own delays, which sounds obviously correct until you look at what it rewards. A vendor whose revenue begins when the first message goes out has a direct incentive to get a message out. Not a good message to a well-built list — a message. The pressure it creates lands precisely on the two things that decide whether the campaign works at all: the quality of the list and the quality of the copy. That is a bad place to apply financial pressure.

So the productive move is not to hunt for the fair date. It is to take whichever date you agree on and pair it with the term that neutralizes its specific failure mode. Signature billing needs a launch-by date. First-send billing needs a written definition of what a launch consists of. Either one, agreed in a sentence before signing, prevents the argument that otherwise arrives in week three.

Your guarantee is running on a third clock

Now the part that costs buyers the most and is almost never checked. If the engagement carries a performance guarantee — a number of appointments inside a window, or you do not pay — that window is running on its own clock, and it is not automatically the billing clock.

A thirty-day guarantee counted from signature and a thirty-day guarantee counted from first send are different promises wearing identical words. The difference between them is exactly the length of your onboarding. If onboarding takes ten days, the first version is a twenty-day guarantee with a thirty-day label on it, and the shortfall lands in the period least likely to produce results, since the campaign was not running for a third of it.

The consequence is that two vendors can advertise the same guarantee, in the same words, and be offering materially different protection — and nothing on either website reveals which is which. That is why how the guarantee is actually structured matters more than the headline number attached to it, and why the start date belongs in the same conversation. Ask which date the guarantee counts from as a question of its own, separate from which date billing counts from. They are frequently not the same, and the pairing to watch for is billing from signature with the guarantee also running from signature.

The wait is not one wait — it is three

Buyers tend to treat the pre-launch period as a single block of vendor slowness. It is actually three distinct waits stacked on top of each other, owned by three different parties, and only one of them is compressible by the vendor.

The part you owe

These are decisions, not tasks, which is why they take longer than anyone expects. Who exactly should be reached — industry, geography, size, and the categories you want excluded. What you are actually offering, in a sentence a stranger can act on. What disqualifies a prospect before they reach your calendar. What your real availability looks like. And approval of the actual messages, which is the single most common place a launch stalls. None of it is hard. All of it is blocking, and the list you approve shapes the results far more than the copy does — which is why the filters you set on the list are worth spending the extra day on rather than rushing to unblock a launch date.

The part they owe

A built and validated target list, drafted messages, and working infrastructure: sending numbers or domains, registration with carriers or mailbox providers, and connections into your calendar and CRM. Some of this is genuinely quick. Some of it sits in a third-party queue that neither you nor the vendor controls and that no amount of urgency accelerates. A vendor who tells you a registration timeline is out of their hands is usually telling the truth — but they should be able to tell you what is queued, with whom, and what the typical wait runs. What is bundled into the build versus billed separately is worth settling in the same conversation, because setup work is where scope tends to be least explicit.

The part nobody owns

Market latency. Once the first message lands, the clock is in the hands of people who did not ask to hear from you and are under no obligation to answer promptly. Neither party controls it, no vendor can compress it, and it is the wait that surprises people most because it arrives after everything visibly went right.

Even a perfect launch cannot produce an instant appointment

Work the chain forward from the day the first message goes out and the reason becomes obvious. The message has to land. It has to be read, which for a business owner holding the phone all day can be minutes and for one who checks it between jobs can be two days. It has to be replied to. The reply has to survive a qualifying exchange, because a reply is not yet interest and interest is not yet a fit. And then a specific time has to be found that suits two calendars, which is very rarely this week.

So the honest earliest date for a first booked appointment is later than first send by the length of that chain, and the honest earliest date for a first held appointment is later again, because booked and held are different events and only the second one is worth anything. None of this is in the contract, and none of it is in the vendor's control.

Which explains a pattern worth recognizing in yourself: buyers negotiate hard on how fast a vendor can start, while what they actually care about is when an appointment appears. Those are two questions separated by a chain nobody wrote down. Negotiating the first one aggressively and leaving the second one unspoken is how a perfectly normal engagement comes to feel like a failure in week two.

The part of the delay that is genuinely yours

It is worth saying plainly, because the framing so far has been about protecting you and the honest accounting does not run entirely in your favor. In a large share of slow launches, the blocking item is sitting in the client's inbox.

Outbound is marketed as hands-off, and the ongoing running of it largely is. The start of it is not, and the effort profile is heavily front-loaded — a concentrated burst of decisions in the first week or two, then very little. That is the honest shape of it, and where the done-for-you boundary actually sits is worth understanding before you sign rather than discovering in week one when four approval requests arrive at once.

The practical consequence: if you know a busy fortnight is coming, do not start the engagement at the front of it. A billing clock that started while you were unavailable for approvals is a bill you effectively wrote yourself, and no contract term protects you from it. Clearing two hours in the first week is worth more to the outcome than anything you will negotiate on the start date.

What to pin down before you sign

Five items, each of which fits in a sentence and none of which a reasonable vendor will object to. Send them as a single message and keep the reply.

1. The named billing date. Which of the four dates does the invoice key off — signature, payment, a defined onboarding milestone, or first send? Get the word, not the implication.
2. A launch-by date, and what happens if it slips. Not a promise to be quick. A date, plus what specifically happens to your billing if the delay is theirs. This is the single term that makes signature billing safe.
3. What “launch” means. A campaign being built is not a launch. A campaign being switched on is not a launch either if the list is empty. Define it as messages delivered to real prospects, and say how many constitutes the start.
4. Which date the guarantee counts from. Ask separately from the billing question, because the answers differ more often than buyers expect, and this is where a thirty-day promise quietly becomes a twenty-day one.
5. What you can see during the pre-launch period. The list, the messages, the qualification rules, the routing. These all exist as artifacts before anyone is contacted. A vendor who cannot show you one of them a week in has not started.

That fifth item is the one buyers leave out, and it is the one that resolves the anxiety the other four only manage. The reason the pre-launch period feels like paying for nothing is that nobody showed you the something. It exists. Ask for it.

Worth noting that a separate setup or onboarding fee, where one exists, is a different thing again and does not answer any of the five questions above. It prices the build; it does not tell you when the recurring clock starts, and a contract can carry a setup fee and still bill the first full month from signature. How the various charges are typically structured is the wider version of that question, and it is the one to settle before you get to dates.

Measure from first contact, not from signature

One last thing, and it applies after you have signed. When you eventually judge the engagement, date everything from first contact rather than from signature, or you will be scoring the vendor on your own onboarding speed and drawing conclusions from it.

This matters most in a comparison. If you are on your second vendor, the second one will look faster than the first almost regardless of merit — your ideal customer is already defined, your offer is already written, your approvals are quick because you have done them before, and your calendar is already connected. That is a real advantage to you and a false advantage to them, and diagnosing how the last vendor actually failed is a better guide to the next one than a stopwatch that started before either of them existed.

Keep three dates from day one: signature, first send, first held meeting. The interval between the first two is the onboarding you paid for, and it tells you whether the launch-by term was worth having. The interval between the second and third is market latency plus qualification, and it is the number to carry into your next campaign budget so the following engagement is planned against a real timeline rather than a hopeful one. Neither number is knowable in advance. Both are knowable after one engagement, and almost nobody writes them down.

None of this makes the wait shorter. It makes the wait expected, which is most of the problem — the gap between paying and seeing anything is survivable when it was described honestly and corrosive when it arrives as a surprise. A vendor willing to give you two dates and a definition is a vendor who has run this before, and that is worth more than the dates themselves. If you want to see what the build looks like before any clock starts, what a done-for-you outbound program involves is a reasonable place to begin, and the demo shows the list and the messages before there is anything to invoice.

Frequently asked questions