Maintenance & support

Webflow
maintenance
and support

A block of hours a month, and someone who already knows your site. For teams who depend on a Webflow site and have no developer on staff. You buy the hours, we spend them on whatever the month actually needs, and you get an itemised log showing where every one of them went.

A month on an eight-hour block
Illustrative
New pricing table on the services page
1.50 h
CMS filter broken after a Webflow update
0.75 h
Four blog posts loaded and formatted
2.00 h
Mobile nav overlapping on iOS
0.50 h
Speed pass on the two slowest templates
1.75 h
Backups, plan check, broken-link sweep
0.50 h
Used this month
7.00 / 8.00 h

A made-up month, not an average — yours depends entirely on what you ask for. What is not made up is the log: you get one like this every month, itemised, whether you read it or not.

Webflow Design
Figma to Webflow
CMS Architecture
Migrations
Motion & Lottie
Technical SEO
Integrations
Care Plans
Webflow Development
UX/UI Design
CMS Architecture
Migrations
Motion & Lottie
Technical SEO
Integrations
Care Plans
Webflow Development
UX/UI Design
CMS Architecture
Migrations
Motion & Lottie
Technical SEO
Integrations
Care Plans
Webflow Development
UX/UI Design
CMS Architecture
Migrations
Motion & Lottie
Technical SEO
Integrations
Care Plans
How the hours work

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.

What is covered

Where the hours actually go

Six kinds of work, in roughly the order they come up. Anything on this list comes out of the block without a separate conversation.

01

Edits and content

New sections, copy changes, swapped images, CMS items loaded and formatted so they look like the rest of the site rather than a paste from a document.

The everyday one
02

Things that broke

What worked last month and does not now. A Webflow update, a browser update, or a third-party embed that quietly changed its own markup. Usually nobody did anything wrong.

Regressions
03

Speed

Image weight, render-blocking assets, and templates that got slower as the CMS filled up. Measured on the page, not on a homepage lab score.

Core Web Vitals
04

CMS and structure

New fields, new collections, filters and sorts — the work that stops your team having to ask us for things they should be able to do themselves.

Less dependence on us
05

Forms and integrations

Silent form failures are the single most common thing we find on a site nobody has checked in a year. Wired, tested, and re-checked every month.

Checked monthly
06

The boring monthly

Backups, site plan and billing check, uptime, a broken-link sweep, and a short written log of everything done. Half an hour that pays for itself the first time you need it.

Roughly 0.5 h
Response time

Within 1 business day

We are in Jaipur, and we work 10:00 to 19:00 IST, Monday to Friday. Same business day is a real commitment and it means a real thing — but what it looks like depends on where you are sitting, so the table says it out loud instead of leaving you to find out at six o'clock on a Tuesday.

When our reply lands where you are
10:00–19:00 IST
London · Dublin
Your morning
Berlin · Paris · Amsterdam
Your morning
New York · Toronto
Waiting at 9am
Chicago · Denver
Waiting at 9am
Los Angeles · Vancouver
Waiting at 9am
Sydney · Melbourne
Your afternoon

Monday to Friday. Nothing here is a guess at how fast we type — it is arithmetic on a timezone, and we would rather you did it before signing than after.

10–19
IST, Monday to Friday

Every request gets a real reply inside that window — an answer or an estimate, not an automated receipt telling you we have received your automated receipt. The one exception runs the other way: if the site is genuinely down we answer whenever it happens, out of hours included, and it does not come out of your block.

Straight answers

Four things this does not cover

A maintenance retainer that quietly absorbs project work stops being maintenance and starts being a discount on design. Here is where the line is, written down before you pay rather than negotiated in month three.

Building new pages

Not included

A new page, a new template or a redesign is a project with its own scope and its own price. Taking it out of the block would burn two months of hours on one page and leave nothing for the thing that actually breaks in week three. We will quote it separately and you can decide — and if it is small enough to fit, we will say that too.

SEO and content writing

Not included

Technical problems that surface during maintenance are in: a canonical that broke, a template that got slow, a sitemap that stopped updating. Keyword research, writing, link building and monthly reporting are not. That is the Webflow SEO retainer, it is a different engagement with a different budget, and we would rather you bought the right one.

Webflow hosting costs

Not included

Your Webflow site plan is billed by Webflow, to you, on your own account — and it should stay that way. We are not a reseller and we do not mark it up. If you would genuinely rather we handled the billing we can talk about it, but the default is that you own the account and can lock us out of it in ten seconds.

Third-party tools

Not included

Your CRM, booking tool, chat widget or payment provider are software we do not control and cannot guarantee. We will liaise with their support and we will do the work on our side of the connection. What we promise is to tell you quickly when the problem is theirs, rather than billing you hours to discover it.

You want this page if

You have a site people use

It is built, it is live, people use it, and things keep coming up that nobody internally can fix. You want ongoing Webflow support from a known person, with a known number of hours, rather than a scramble every time.

You want the other page if

You want the site to grow

Keeping it working is not your problem — being found is. That is content, authority and technical SEO run continuously, which is a different engagement with a different budget.

Webflow SEO retainer →
Process

How a month actually runs

No portal to learn, no ticket numbers to quote back at us, and no month that ends without a written record of what you got for the money.

STEP 01

No ticket system

Email, Slack, a shared board, a voice note. We are not going to make you learn a ticket system to ask for a copy change. One inbox, one thread per request, and nothing gets lost because it arrived in the wrong place.

STEP 02

The cost, up front

Before anything starts, not after it finishes. If a request is bigger than it looks, or bigger than what is left in the block, you hear that while you can still change your mind about it.

STEP 03

Staging first

Copy changes go straight in. Anything that touches layout, the CMS or a template happens on a staging copy and gets your sign-off before it reaches the live site.

STEP 04

Published, with a note

What changed, which page or template it lives on, and how long it took. Written so that whoever reads it in six months can tell what happened without asking us.

STEP 05

The monthly log

Every task, every duration, the running total against your block, and what rolled over. A document you keep, not a dashboard you have to log into.

STEP 06

The quarterly check

Once a quarter we look at whether the tier still fits. If you have not touched the hours in three months, we will say so and suggest you drop down. That conversation goes downward more often than up.

FAQ

What clients ask before signing

01

What happens to hours I do not use?

+

02

What actually counts as an hour?

+

03

Will you take over an existing site?

+

04

Is Webflow hosting included in the fee?

+

05

What if the site goes down?

+

06

Do I have to sign a long contract?

+

07

Is this the same as your SEO retainer?

+

Start here

Tell us what keeps breaking

Send the URL and what has broken, changed or nagged at you in the last three months. You will get a recommended tier and a fixed monthly number — and if the honest answer is that you do not need a retainer at all, you will get that instead.

Replies within one business day · US, UK & EU hours covered