When a Webflow retainer is cheaper than a project

Most people arrive wanting a project. It is the familiar shape: a scope, a number, a date, and then it is done. For a site that is genuinely finished on launch day, that is the right instinct.

Very few marketing sites are finished on launch day.

What each one actually buys

A project buys a defined thing built once. From $5,000, agreed in writing, twelve to fourteen days for a full multi-page build. Scope is the point: it is what makes the price hold, and it is also what makes every change after it a new conversation.

A retainer buys capacity rather than an artefact. $2,500 a month, unlimited requests worked one at a time, typically two to three days each, no minimum term. Nothing is scoped because the scope is "what you need this month".

$90 an hour exists for the case neither covers: one fix, on a site that does not need anybody retained.

The break-even, honestly

Work it out in requests rather than money.

One or two requests a month. Hourly is cheaper, and I would tell you so.

Three to five. Roughly even. Pick on whether you would rather have the queue or the invoice.

Six or more. The retainer wins clearly, and the gap widens every month.

At $90 an hour, three or four substantial requests in a month already approach the retainer. Past that the retainer is simply cheaper, and it is cheaper in a way that compounds, because the thing that makes hourly work expensive is not the rate, it is the overhead of scoping and quoting each piece before anyone starts.

The part that does not show up in the arithmetic

Three things a retainer buys that an hourly arrangement does not, and they are usually what actually decides it.

No estimate before small work. A half-hour change costs a half-hour. Under an hourly arrangement it costs a half-hour plus the exchange about whether it is worth a half-hour, which is frequently longer than the change.

Someone who already knows the site. The second month is faster than the first, and the sixth is faster again. That compounding is real and it is entirely lost when a site is handed to whoever is available.

Things get fixed before you ask. A broken form, a slow page, a redirect that stopped resolving. Under a project nobody is looking. Under a retainer somebody is, and that is most of the value on a site that matters.

When a project is genuinely right

I would rather say this than sell the wrong thing.

A rebuild with a real finish. A site being replaced, launched, and then left alone for a year. That is a project, and paying monthly for it afterwards is waste.

A fixed budget that has to be fixed. Some approvals need a number that cannot move. A project gives you one; a retainer does not pretend to.

Nobody internally to feed it. A retainer only earns its money if there is a stream of work. If nothing is queued in month two, you are paying for availability you are not using, and I will say so rather than let it run.

How to tell which you are

One question: how many times did you want to change the site last quarter, and how many of those actually happened?

If the answer is "several, and most of them did not", that gap is the retainer's whole case. The changes you skipped because getting a quote was more effort than the change is worth are the ones it is for.

If the answer is "once, and it happened", buy a project, or an hour.

The rates page has what each includes.