Webflow subscription vs retainer vs hourly. What you actually pay for.

The short answer

Pay hourly when the work is small and unpredictable. Pay a retainer when you want a set block of hours reserved for you every month. Pay a subscription when you have a steady stream of Webflow work and want one flat price, with no hours to count. For a single new site, a fixed-price project beats all three.

All four models can buy the same Webflow work. What changes is who carries the risk of the work taking longer than expected, and how much you pay when the month is quiet.

Hourly range: theCSS Agency's 2026 Webflow cost guide. Retainer range: Branded Agency's guide to Webflow pricing models. Links at the end.

Hourly: simple to start, hard to predict

Hourly billing is the easiest model to agree on. You describe the task, the developer tracks time and you pay for the hours used. theCSS Agency's 2026 guide puts Webflow freelancer rates at about $50–$150 an hour, and some agencies charge more.

The weakness is that you carry all the risk. A "quick" change that turns out to touch three templates costs three times as much. Most teams end up asking for estimates before every task, which slows small work down.

Choose hourly when

• You need a few hours of help a month, at most.
• The tasks are small and hard to scope in advance.
• You don't mind approving estimates task by task.

Retainer: reserved hours at a monthly price

A retainer reserves a block of a team's time for you each month. Branded Agency's guide says most Webflow retainers run $2,000–$6,000 a month, and gives an example of $3,000 for 20 hours, which works out to $150 an hour if you use every hour. The same guide notes that a retainer does not automatically include unlimited requests or immediate turnaround.

Retainers suit teams that can forecast their hours. The risk moves to you in quiet months: depending on the contract, unused hours may expire. In busy months, work over the block is usually billed extra.

Choose a retainer when

• You know roughly how many hours of Webflow work you need each month.
• You want the same people on your account over time.
• Your contract says clearly what happens to unused hours.

Subscription: one flat price, no hours to count

A Webflow development subscription charges a flat monthly fee for access to a queue. You add requests, such as a page, a section, a CMS collection or a set of fixes, and the team builds them in order. Nobody counts hours, so a task that takes longer than expected costs you nothing extra.

The trade-off is pace. To keep the price flat, subscriptions work on a set number of requests at a time. At ManyBuilds, Pro builds one request at a time for $1,995 a month, and Team builds two at a time for $3,450, with Figma design included. You can add as many requests as you like and reorder them whenever priorities change.

Quiet months matter here too. A good subscription lets you pause instead of paying for capacity you won't use. On ManyBuilds plans, pausing is free and unused days carry over to when you come back.

Choose a subscription when

• Your Webflow site changes every week.
• You want one predictable cost and no estimates per task.
• You can work with a queue: the top request goes next.

Fixed price: best for one defined build

When the job is a new site with a finished design, a fixed price is usually the cleanest deal. You agree on the page list and the price before work starts, so the total does not move. ManyBuilds' Figma to Webflow build, for example, starts at $2,450 for up to 8 pages, with extra pages at $150 each.

Fixed price stops making sense after launch, when the work turns into a stream of small changes. That is where teams usually switch to a subscription or a retainer.

What a typical month costs

Here is one month of ongoing work priced three ways, using the published figures above. Your real numbers depend on how much work there is.

Hourly wins in a quiet month. A flat price wins when the work is steady. In a busy month, a subscription costs the same but works through the queue one or two requests at a time, so plan your priorities.

Questions to ask before you sign

1. What counts as one unit of work? An hour, a request, a deliverable? Get examples.
2. What happens to unused time? Does it expire, roll over, or can you pause?
3. How many things are worked on at once? This decides how fast a full backlog moves.
4. Is there a minimum term? Month to month, or a 3, 6 or 12-month contract?
5. Who owns the work? Your Webflow site and files should be yours when you leave.

Questions people ask

Is a retainer the same as a subscription?

Not quite. A retainer buys a set number of hours each month. A subscription buys access to a queue of requests at a flat price, with no hours counted.

Which is cheapest?

It depends on your month. For a few hours of fixes, hourly is cheapest. For steady weekly work, a flat subscription usually costs less than the same hours billed one by one.

Can I switch models later?

Usually, yes. A common path is a fixed-price build to launch, then a monthly plan for the changes that follow.

Sources

• theCSS Agency: Webflow agency cost (2026): freelancer hourly rates.
• Branded Agency: Webflow agency pricing models: retainer range and the $3,000 for 20 hours example.
• ManyBuilds pricing: Star, Pro and Team plans, pausing and terms.