What counts as an hour of monthly Webflow support?

An hour is time on a written request

The membership includes 10 hours of Webflow work each month, on one plan: $999 per month for an existing Webflow site. Those hours are time spent working on the requests you send. They are not a promise of a fixed number of pages.

The time covers looking into the cause of a problem, building or changing pages, updating CMS content, and checking the result before you approve it. Scope and the time spent stay clear in writing on the shared task board, so you can see where the month's hours went.

Example: you ask to replace the first paragraph on the services page with the approved text, and to check that paragraph on a phone. The hours are the time spent making that change and checking it. They are not a flat charge of one hour because one page was named.

What those hours can be used for

The membership is ongoing work on an existing Webflow website. The hours can cover maintenance, content updates, bug fixes, improvements, and new pages within the existing design. A new page that follows the current design uses the same hours as a smaller fix. It is not a separate package.

These sit outside the membership:

• Building a new website or a full redesign. Those are separate projects with their own scope and quote.
• Your Webflow subscription, hosting, domains, and third-party apps or services, which remain in your own accounts and at your own cost.

You review changes and confirm when they are ready to publish. The hours cover the work on the request, including checking the result before you approve it.

Extra time is still measured in hours

Additional work is $75 per hour. Before work exceeds the included 10 hours, I share a written estimate for the additional time and ask for your written approval. Additional work only begins after you approve it. Time past the included hours is not added after the fact.

If four hours are left and the next request is larger than those four, the estimate covers the additional time at $75 per hour. You can approve it, narrow the request so it fits the hours that remain, or leave the extra work unstarted. The extra hours guide is that decision on its own.

Unused hours expire at the end of each monthly billing period and do not carry over. A quiet week does not make a later request free, and it does not change what an hour means in the next period. The next period starts again at 10 hours.

A pickup window is not an hour of work

Urgent requests are reviewed and picked up within 24 hours. Other requests are reviewed and picked up within 48 hours. These are initial response and assessment times, not completion deadlines. A 24 hour window is not a charge of 24 hours. The hours that count are the time spent on the request, and the window does not promise that the live site will already be changed when it ends.

Communication is asynchronous and written only. There are no calls or meetings. A call is not how an hour is defined, and it is not how extra time is approved.

For a larger task, an estimated delivery time is shared after the scope is reviewed. That note is about when the work can be done. It does not replace the hourly measure, and it does not start hours past the 10 without your written approval.

Write the request so the time is clear

Name the page or the CMS item, attach the final copy or the file, and say what done looks like on desktop and on a phone. 'Make the homepage better' does not describe the time. 'Replace the team photo on /about with the attached image. Alt text: the studio team in the office. Check the same block on a phone.' does.

There is one plan for every existing Webflow site. The price does not change because the site has fewer pages. The Webflow retainer is that plan, with 10 hours included. The retainer guide explains which ongoing work belongs in the month.