What the block actually is
Most Webflow maintenance and support is sold as a feeling — peace of mind, we've got you covered, sleep easy. Those are not things you can hold anyone to. A number of hours is. Here is exactly how the block behaves, including the parts that usually only surface when you try to leave.
The question
The usual retainer
Here
What you are actually buying
“Support”, undefined, priced monthly.
A named number of hours, agreed before you pay for them.
Who does the work
Whoever is free. Often a different person each time, re-learning your build.
The same developer every month, who already knows how your site is put together.
Unused hours
Gone at midnight on the last day of the month.
Roll over one month, then expire. And if you keep not using them, we will tell you to drop a tier.
Going over the block
A surprise line on next month's invoice.
We stop and ask. Nothing above the block is billed without your yes, in writing, first.
What counts as an hour
Rounded up, per ticket, by someone you never meet.
Tracked per task in six-minute units and itemised in the monthly log.
Getting out
Three months' notice, or a twelve-month lock-in.
Thirty days. The Webflow project is yours, the account is yours, and nothing is hosted by us.
Why the rollover stops at one month
Because an unlimited rollover is a trap for both of us. It becomes a bank of forty unused hours that you eventually want cleared in a fortnight, and a month where we owe you a week of work we have not scheduled. One month of carry is enough to absorb a quiet August without turning into a debt. If you are rolling over every month, the honest answer is not a bigger bank — it is a smaller tier, and we will say so.