How Should You Price a Webflow Retainer?

How Should You Price a Webflow Retainer?

Price the outcome, not the hours. Decide what the site must keep doing every month, work out what that genuinely takes, and quote a fixed monthly number for it. Hourly retainers look fair and quietly reward the slowest possible version of every task, which is the opposite of what anyone wants.

We get asked about this a lot, usually by founders who have been burned by a retainer that became a slow drip of small tickets. The failure is almost never the rate. It is that nobody agreed what the retainer was for.

This is how we think about it, including the parts that are uncomfortable to say out loud.

What Is a Webflow Retainer Actually For?

Keeping a site useful after launch. A website is not a deliverable that stays finished. Content goes stale, standards move, platforms change their defaults, and the business the site describes stops matching the business you now run. A retainer is the budget for that drift.

Most retainers get sold as an insurance policy against breakage, which undersells them badly. Very little breaks on a well-built Webflow site. What happens instead is slow decay: pages that no longer match the pitch, a blog nobody prunes, and a conversion path designed for a product two versions ago.

If you describe the retainer as maintenance, you will get maintenance-sized budget and maintenance-sized results. If you describe it as ongoing improvement with a named goal, it is a different conversation entirely.

Why Do Hourly Retainers Go Wrong?

Because they price the wrong thing. An hourly retainer makes efficiency a cost to the studio and a benefit to nobody. The faster and better you get at a task, the less you earn for it, which is an incentive structure no honest person should want to sit inside.

They also create the worst possible conversation. Every month someone reconciles a timesheet against a feeling, and the client ends up auditing minutes rather than judging outcomes. We have never seen that discussion improve a website.

The third problem is the leftover hours question. Unused hours either roll over, which turns your retainer into a growing liability, or they expire, which feels like theft even when it was in the contract. Both endings are bad, and neither has anything to do with the work.

What Work Genuinely Recurs Every Month?

Less than agencies claim and more than clients expect. Content changes are the reliable core: new pages, updated case studies, pricing edits, campaign landing pages. Then there is the quieter category of keeping the site aligned with standards that keep moving.

Those standards are real and measurable, which makes them good retainer material. Google's web.dev documentation sets Interaction to Next Paint at 200 milliseconds or less for good at the 75th percentile, Cumulative Layout Shift at 0.1 or less, and suggests aiming for a Time to First Byte of 800 milliseconds or less. A site that met those at launch will not automatically meet them in a year.

Then there is platform drift. Infrastructure defaults change without asking you, and September 2026 was a good example: Cloudflare changed its crawler defaults on 15 September 2026, including for existing free customers who had never touched their settings. Somebody has to notice things like that, and that somebody is what a retainer buys.

How Do You Size a Retainer Without Guessing?

Run the first month as a fixed scope, then measure. Pick the three or four things that must happen every month, do them once properly, and note what they actually took. The number you get is far more honest than any estimate made before the work existed.

We prefer to size around a small number of named commitments rather than a pool of capacity. Two new pages, one performance review, one content refresh cycle, and a monthly report is a retainer someone can evaluate. Ten hours of Webflow support is not, because nobody can tell whether it went well.

Build in a review at three months and mean it. The right retainer size in month one is rarely the right size in month six, and a contract that cannot change is one that quietly stops being worth it for one side or the other.

Should the Retainer Include Strategy or Only Execution?

Include enough strategy to make the execution correct, and no more. A retainer with no thinking in it produces a series of well-built pages that do not add up to anything. A retainer that is mostly meetings produces slides.

The practical split we like is a short monthly decision conversation and a written record of what changed and why. Thirty minutes deciding what matters this month saves several days of building the wrong thing, and it is the cheapest part of the whole arrangement.

Be honest about who holds the strategy, though. If the client has a strong marketing lead with a clear plan, a strategy-heavy retainer is duplication they will resent paying for. Our piece on Webflow agency against in-house covers where that line usually sits.

What Should Never Be Inside a Retainer?

Anything with a hard deadline attached to a launch, and anything big enough to eat the whole month. A product launch page due on a fixed date is a project with a scope and a quote, not something to squeeze into ongoing capacity while the regular work waits.

Rebuilds belong outside too. When the answer to a request is a new template, a new content model, or a new navigation system, that is a project. Doing it inside a retainer means doing it in slices over months, which is the most expensive way to build anything.

The rule we use is simple. If it changes the shape of the site, it is a project. If it changes the contents of the site, it is retainer work. That line is easy to explain and it holds up under pressure.

How Do You Know a Retainer Has Gone Stale?

When the monthly report stops containing decisions. A healthy retainer produces arguments about priorities. A stale one produces a list of completed tickets that nobody reads, and an invoice that gets approved out of habit because cancelling it would take a meeting nobody wants to book.

Two other signals are worth watching. If the same request keeps coming back, the underlying problem was never fixed, usually because a structural change kept being deferred as too big. And if nobody on either side can name what the site is meant to improve this quarter, the retainer has become a subscription.

The honest response to either is to pause and rescope, even when that means a smaller number. A retainer that both sides quietly resent is worth less than a clean project quote every six months.

What About Handover and Lock-In?

A good retainer should be leavable at any point without damage. That means documented conventions, a style guide page that reflects the build, and CMS structures a new team can read without a call. If leaving is painful, the retainer is being held together by dependency rather than value.

We treat that documentation as part of the work rather than an exit deliverable, because it also makes the ongoing work faster. The same notes that let a new agency take over let a new person on our side pick the site up in an afternoon.

If you are currently inside a handover, our guide to Webflow client handoff covers what a complete one should include.

How Do We Actually Do It?

We quote fixed and we scope first. Our published model is three tiers, Launch, Growth and Scale, with a fixed quote after a short scoping call rather than surprise hourly bills. Build timelines run four to eight weeks from kickoff to launch, with focused marketing sites at three to four weeks and larger builds with custom CMS and automations at six to ten.

Ongoing work follows the same logic. Name what recurs, price it as a number both sides can judge, and review it often enough that neither side is stuck with a shape that stopped fitting. That is less clever than most retainer models and it argues less.

If you are trying to work out whether your site needs a retainer or just needs a project, we are happy to talk it through honestly, including when the answer is neither. You can find us at phoenix.studio, and the cost of that conversation is one call. Our notes on what a Webflow website costs cover the project side of the same question.