Can monthly Webflow support edit code already on the site?

Code that is already on the site can be a request

Monthly support is for an existing Webflow site. The work includes maintenance, content updates, bug fixes, improvements, and new pages inside the current design. A fix to custom code that is already on that site is the same kind of request. It is not a second plan, and it is not unlimited.

The plan is $999 per month and includes 10 hours of Webflow work. There is one plan for every existing Webflow site. There is no custom quote to join, and the price does not change because the site has a snippet in the footer. Additional work is $75 per hour. Before work exceeds the included hours, I share a written estimate and ask for your written approval. Additional work starts only after you approve it.

Example: a booking link in the footer snippet still points at last year's URL. The request is to replace that URL and confirm the booking page opens. The site already exists. The snippet is already there. That is monthly work, inside the hours, or past them only after you approve the estimate.

Name the code, the page, and what done looks like

Write the request the way you would write any other edit. Name the page. Say where the code sits, in words a teammate can find, such as the footer embed or the site head. Paste the current snippet or describe the line that is wrong. Paste the replacement, or describe the result you can see.

Example: 'On every page, the footer embed should load the booking button with this URL. It still uses the old URL. Replace that URL only. Done when the button opens the new booking page and the rest of the footer is unchanged.'

Do not send 'clean up the code' with no page and no result. That sentence cannot be estimated. Split a list of snippets into separate lines if only one of them is blocking a form.

If your own team can already change the copy, keep that edit in-house. Send the request when the work is code your team should not guess at. The team edits guide is that split. The custom code guide is the walkthrough if you are placing the snippet yourself.

A new site is not an edit to old code

A new website or a full redesign is a separate project with its own scope and quote. Calling it a code change does not move it into the month. Rebuilding every page, replacing the layout, or starting from a blank site is that project.

A new page that follows the design you already have can still be monthly work. A one-line fix in an embed can be monthly work. The test is whether you are changing the site you have, or replacing it.

Example: update the chat snippet so it appears on /contact only. That can be a written request. Replace the marketing site with a new design and a new set of pages. That is a separate project, even if some of the old embeds would be copied over.

Unused hours do not become a credit toward that project. Unused hours expire at the end of each monthly billing period and do not carry over.

Code uses the same hours and the same windows

An hour is time spent on the written request: looking into the problem, making the change, and checking the result. A URL swap and a careful pass through several snippets do not take the same time. Ten hours is not a menu of code fixes with a fixed price each.

Urgent requests are reviewed and picked up within 24 hours. Other requests are reviewed and picked up within 48 hours. Those are pickup times, not a promise that the live snippet is already corrected when the window ends. For a larger change, a delivery estimate is a separate note about timing. It is not an approval of extra hours.

Communication is asynchronous and written only. There are no calls or meetings to walk through the snippet. Send the current code and the result you want in the same thread.

If the change would pass the included hours, stop at the estimate. Additional work starts only after you approve it in writing. Declining the estimate leaves that extra work unstarted. Hours still left in the period stay available for other requests.

The account stays yours

Your Webflow subscription and hosting stay in your own account, at your cost. A code request does not move the site, the domain, or the hosting bill. Keep the subscription active. The monthly plan does not replace it.

You review the change before it is published. Say publish or hold in writing, and name the destination. That reply is not the extra-hours approval. If you are unsure which yes you are sending, keep them in separate sentences.

Memberships cannot be paused to wait while someone on your side rewrites a script. You can cancel before the next renewal to stop future billing. Service continues through the paid period, and remaining included hours stay available until that period ends.

The Webflow retainer is the plan this code request belongs to. The retainer guide explains which ongoing work fits the month. Use this page when the thing you want changed is code the site already has, and you need to know it is still the same monthly plan.