Landing page retainer or one-off project

Buy a one-off project when the landing page is a bounded job with a launch date at the end of it. Buy a retainer when you will really ship pages, new versions or big edits at least twice a month, every month. What decides it is how much work you will actually feed the arrangement, and most teams get that number badly wrong.

Count what you will ship, honestly

Open the last twelve months and count. How many new landing pages went live, and how many test versions? How many times did a campaign stall because nobody could build the page? Write down the real numbers rather than the ambitious plan. Under one page a month, a retainer sits half used while you resent the invoice. Two or more a month with ad spend behind them, and a retainer is cheaper per page and a lot faster.

What a one-off is good at

You get a fixed scope, a fixed price and a clear finish line. You know what you are buying and when it ends. It fits a launch, a new offer or a first paid traffic test. Use it when you need to prove the channel works before you commit to a monthly bill. It also suits teams whose design needs are lumpy, seasonal or genuinely hard to predict.

The cost is restart friction. Every new project means briefing again, quoting again, explaining your customers again and waiting for a slot in someone's calendar. Do that six times a year and you have paid for the same ramp up six times over.

What a landing page retainer is good at

You get momentum. The person already knows your offer, your objections, your brand files and your analytics, so a new version starts on day one instead of week two. You hold a slot in their calendar that you never have to negotiate for. Testing becomes routine instead of a project with its own approval cycle, and routine is the only way testing ever happens at a small company.

How retainers go wrong

Retainers fail in three ways. You buy capacity you never use, which is the most expensive line item in agency work. The scope stays vague, so the word included turns into an argument every single month. Or the work quietly drifts into small edits and admin, and nobody is doing the strategic work you signed up for. All three are avoidable if you write down what one month contains before you sign anything.

What to ask before signing

What is the monthly capacity in concrete terms, in pages or active requests or hours? How many things can be in progress at once? What is the turnaround on a single request? Does unused capacity roll over, and for how long? What is the notice period, and is there a minimum term? Who exactly does the work, and what happens when they take a holiday? A retainer with no numbers in it is a subscription to hope.

Ours, as one data point

A single landing page sprint with us is 2,400 USD, live in five working days. The retainer is 4,800 USD a month for continuous design and build work. Break-even sits at roughly two pages a month, and that is the honest threshold. Below it, buy sprints and keep your flexibility. We say this to prospects who would happily hand over a retainer today, because a half used retainer ends in a cancellation and a bad taste.

Start with a project, then decide

Almost nobody should sign a retainer first. Run one paid project. You learn how they think, how fast they reply, whether they push back on bad ideas, and whether the page performs once it is live. Move to a retainer only if the volume is really there. Ask for a one month notice period on the first agreement rather than a six month lock. Anyone confident in their work will agree to that without a fight.