What should I prepare before monthly Webflow support starts?
Gather site access, final assets, and a prioritized first queue before monthly Webflow support starts on an existing site.
Prepare access to the existing Webflow site, final copy and assets, and a written list of the first requests in priority order. The plan is $999 per month with 10 hours included. Extra hours are $75 and start only after you approve a written estimate. Communication is written only. A new website or a full redesign is a separate project. Your Webflow subscription stays in your account.
Start from the existing site
Monthly support is for a Webflow site that already exists. A new website or a full redesign is a separate project, with its own scope and quote. Before the first request, name the live site and say that the work stays inside the current design unless a separate project covers a redesign.
The plan is one price for every existing Webflow site: $999 per month, including 10 hours of Webflow work. There is no second package and no custom quote to join. 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.
Unused hours expire at the end of each monthly billing period and do not carry over. Plan the first month around work you actually need in that period. Hours you do not use do not move into the next one.
Keep the Webflow account in your name
Your Webflow subscription and hosting stay in your own account. Keep that subscription active and paid. The membership does not replace the Webflow bill, and it does not move the site into another account.
Give access with the permissions needed for the work. Copy changes may need a narrower seat than layout changes. Say which workspace holds the site, and say who on your side confirms a publish. You review changes and confirm when they are ready to go live.
Example: 'The site is in our workspace under the name Northwind. Use the access we added. Leave the Site plan and the domain as they are. We will confirm before anything is published.'
Send final copy, assets, and the right to use them
Provide clear requests and final, approved content and assets. Make sure you have the rights to the content, images, and other materials you ask me to use. A file that is still in review should stay labeled as a draft. An unlabeled folder is hard to place on the right page.
For each asset, include the page or CMS item it belongs to. For an image, include the alt text. Say whether the file replaces something that is already live. If brand or legal review is still open, say the file is not final.
Example: 'Replace the team photo on /about. Use the attached image. Alt text: Northwind studio team in the office. This file is final.'
Write the first queue in priority order
Ten hours is the included capacity for the period. Put the first requests in a list, most important first. Each line needs a URL or a CMS item name, and a description of what done looks like on desktop and on a phone. One bounded request is easier to place in the hours than a note that says the whole site needs a refresh.
Separate a content edit from a layout change. A sentence swap on a live page is a different job from a new page, even when the new page follows the current design. If you already know a request may pass the included hours, say so. That is the point where a written estimate comes before extra time starts.
The update brief is the closer checklist for a single request. This page is the packet to gather before that first request goes in.
Send it on the written channel
Communication is asynchronous and written only, through a shared task board and an agreed written channel. There are no calls or meetings, including at the start. Put the access note, the assets, and the ordered queue in that channel.
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 completion deadlines. The first queue uses the same windows.
Memberships cannot be paused. If you are not ready to use a month, wait to subscribe. If you already have, 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. You can ask to rejoin later, subject to availability.
When that packet is in one thread, I can work from it. The Webflow retainer is the plan this preparation is for. The retainer guide explains which work belongs in the month.
Questions & answers
Do I need to move the site into a new Webflow account?
No. Your Webflow subscription and hosting stay in your own account. Give access with the permissions the work needs, and keep the subscription active and paid.
Can the first conversation be a call?
No. Communication is asynchronous and written only. There are no calls or meetings. Send the access note, the assets, and the queue in writing.
Can the first month include a full redesign?
No. A new website or a full redesign is a separate project with its own scope and quote. The monthly plan is for an existing Webflow site.
What if the copy is still a draft?
Say that it is not final, and do not ask for it to be published. Send approved copy and assets when you want them used on the live site.
Need a hand with your Webflow site?
View membership
View membership