One Time vs Recurring: How to Price and Bill Agency Work

What actually changes inside your CRM when an offer bills once instead of every month, and the automation each shape needs.

One Time vs Recurring: How to Price and Bill Agency Work

The one time vs recurring question is usually argued as a pricing debate, which is why it keeps producing bad operational decisions. Pricing is the smaller half. The larger half is that the two shapes create different objects inside your CRM, fail in different ways, and need different automation behind them. Switch an offer from a single charge to a subscription without changing anything else and you have not built a retainer. You have built a payment that will silently stop working in about eleven months, when the first card expires.

Here is what actually differs, and how to decide per offer rather than as a blanket policy.

What changes inside the system, not the price list

A one-time charge is an event. It happens, it succeeds or it does not, and the record is closed. The only follow-up states worth modelling are refund and dispute, both of them rare and both of them handled by a human.

A subscription is a lifecycle. It has a start, a billing anniversary that recurs indefinitely, a payment method that decays on its own schedule, a set of failure and retry states, an optional pause, a cancellation that may be effective immediately or at period end, and an access grant that has to be revoked when it ends. Every one of those is a state your automation can be asked about, and every one of them is a place where a studio quietly loses money by not modelling it.

The practical consequence: a recurring offer needs someone to own the failure path. A one-time offer does not.

The comparison

The four shapes agencies actually use

The one-time project fee

Correct for genuinely finite work with a defined deliverable and an end: a brand identity, a site build, a migration. Trying to force this into a subscription to make the reporting look tidier produces an offer clients cancel the moment the deliverable lands, which is worse for the relationship than an honest project fee.

The pure retainer

Correct when the value is ongoing and roughly even: hosting and maintenance, managed campaigns, a support commitment. The requirement it carries is that the client must be able to see what they received this month, or the renewal conversation becomes an argument about whether anything happened.

Setup fee plus recurring

The hybrid, and the most common shape for agency work with real onboarding cost. It solves a specific problem: the first month of a retainer costs several times what the fifth month costs, so a flat monthly rate either overprices month five or loses money in month one. Charging the build once and the ongoing work monthly matches the billing to the work.

The trap is that this is two products, not one, and they must be modelled as two. If the setup fee and the first subscription payment are collected as a single charge, the subscription amount your reporting shows for month one is wrong, and any automation keyed on the payment amount will behave differently in month one than in every subsequent month.

Usage pass-through

Ad spend, message volume, and per-seat costs that vary. Best kept as a separate line rather than folded into the retainer, because a variable amount inside a fixed subscription is the single most common source of billing disputes.

The failure path is the part that gets skipped

A card expires. That is not an edge case, it is a certainty on a long enough timeline, and it is the largest cause of subscriptions ending without anyone deciding to end them. The path needs four things defined before you launch the offer.

• Retry schedule. How many attempts, spaced how far apart, before the subscription is treated as lapsed.
• Notification sequence. A short series to the client that stops the moment the payment succeeds. The mechanics of building one, including where these sequences silently pause, are covered in the guide to email sequences setup.
• An exit condition. A successful payment mid-sequence must pull the contact out immediately, which is exactly what a goal event is for; the setup and its skip-ahead behaviour are described in the walkthrough on goal events.
• A grace period. Decide whether access continues during retries. Cutting a client off on the first decline over an expired card is a support problem you created yourself.

Re-entry: why month two does not behave like month one

This is the defect that catches most people converting an offer to recurring. A subscription payment fires its trigger every cycle, but a workflow will not necessarily run again for a contact that has already been through it. Whether the second month’s payment starts the fulfilment workflow, or does nothing at all, depends on a single setting, and the behaviour is explained in the note on why a workflow will not refire.

Get this wrong in the direction of no re-entry and the client is billed monthly while the monthly work is never queued. Get it wrong in the other direction on a one-time offer and a refunded, re-purchased client runs the onboarding twice.

What it changes for referral partners

Commission structure is downstream of this choice and is frequently left on a default that does not match the offer. A one-time product pays a partner once. A subscription can pay per cycle for the life of the account, pay for a fixed number of cycles, or pay once on the first payment only. All three are defensible; picking one by accident is not, and the triggers available for each are set out in the guide to affiliate manager triggers.

The related question is what happens to commission when a subscription is refunded or charged back. If that is not defined, it becomes an awkward conversation with a partner rather than a rule.

Choosing per offer

1. Ask whether the work genuinely continues. If it stops, bill once. Manufacturing a subscription around finished work produces cancellations, not retention.
2. Separate the onboarding cost from the ongoing cost, and bill each in the shape that matches it.
3. Define the failure path before launch: retries, notifications, exit condition, grace period.
4. Check the re-entry setting on every workflow the recurring payment touches, then verify by watching the second cycle rather than assuming.
5. Set the commission rule and the refund rule for partners at the same time as the price.
6. Decide what access is revoked on cancellation, and confirm the revocation actually happens.

One time vs recurring is really two questions wearing one name. The pricing question is answered by the shape of the work. The operational question is answered by whether anyone owns the lifecycle, and a subscription with nobody watching the failure path is not a retainer at all. It is a payment that will stop, on a date you did not choose, without telling you.

Frequently Asked Questions

Should an agency put every offer on a subscription?

No. A subscription should match work that genuinely continues. Wrapping finished work in a monthly charge invites cancellation as soon as the deliverable lands, and it makes the renewal conversation harder than an honest project fee would have been.

Why does my recurring workflow only run in the first month?

Almost always the re-entry setting. A subscription fires its trigger on every billing cycle, but a workflow can be configured to ignore a contact that has already been through it. Check that setting and confirm by watching the second cycle, not by assuming.

Can I charge a setup fee and a subscription together?

Yes, and it is the most common agency shape, but model them as two products rather than one combined charge. Folding both into a single transaction makes month one report a different amount from every later month and breaks any automation keyed on that amount.

What is the most common reason a subscription stops paying?

An expired or replaced card, not a deliberate cancellation. This is why the retry schedule, the notification sequence and the grace period need defining before the offer launches rather than after the first decline arrives.

Should access be cut off the moment a payment fails?

Usually not. A grace period covering the retry window prevents a client losing access over a card the bank reissued. Define how long that window is and what happens at the end of it, so the decision is a rule instead of a case-by-case judgement call.

How do referral commissions differ between the two?

A one-time product pays a partner once. A subscription can pay every cycle for the life of the account, pay for a capped number of cycles, or pay only on the first payment. Choose deliberately, and define what happens to commission on a refund at the same time.

How should usage costs like ad spend be billed?

As a separate line rather than inside the fixed monthly amount. A variable figure hidden inside a subscription is the most frequent cause of billing disputes, because the client sees a changing charge without a changing explanation.

Can an existing one-time product be converted to recurring?

The product can be recreated as a subscription, but existing purchasers are not migrated by changing the setting. Treat it as a new offer with its own workflows, its own failure path and a deliberate plan for what happens to people who bought the old one.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.