What to Expect in a Webflow Site Handoff
A Webflow handoff should end with your team publishing new pages without calling the agency. Three things have to arrive together for that to be true: the site transferred into your own workspace, edit access scoped to the right people, and a CMS built around how your team actually works, plus documentation and a live training session. If the handoff is a login and a folder of files, it is not a handoff, it is an invoice.
What you actually receive
Goodthings, a Webflow design agency that hands off every build it ships, transfers the project into your own Webflow workspace so the asset and the billing are in your name. That transfer includes the Designer project, every CMS collection and its items, the component library, the style system built on reusable classes rather than one-off overrides, page-level SEO fields already filled in, and any custom code documented where it lives. Nothing important stays in our account after the transfer completes.
Who should have which permissions
Most of your team does not need Designer access, and handing it out broadly is the fastest way to break a design system. Webflow's Editor lets marketers change copy, swap images, and add CMS items without touching layout or styles. We set this deliberately: Editor for everyone publishing weekly, Designer access for one or two named owners, and a written rule about which changes get a second pair of eyes. Six months later this is the difference between a site that still looks like itself and a site with fourteen shades of your brand blue.
The CMS is the real deliverable
A site is a snapshot. The CMS is the thing that keeps earning. Collections should be structured so that adding a case study, a job posting, or a team member takes ten minutes and produces a page that is automatically laid out, linked, and included in the sitemap. That means reference fields connecting related content, conditional sections that hide cleanly when a field is empty, and required fields on anything that would break a layout if left blank. When SCALA.AI launched, the CMS was scoped before the visual design, which is why their team could publish independently the week after go-live.
Training and documentation
Expect a recorded walkthrough of your specific site, not a link to Webflow University. Ours covers publishing, adding a CMS item, editing a page, swapping an image, and the two or three things on your build that are genuinely non-obvious. Alongside it you get a short written doc: what each collection is for, which fields are required and why, how to add a new page that inherits the right template, and who to call when something looks wrong. Recorded and written both, because the person who needs it in month four was probably not on the call.
Hosting, domains, and billing
Get this in writing before launch. Webflow site plans are billed per site and the plan needs to match your traffic and CMS item count. The custom domain lives in your DNS, not ours, and the records should be documented so a future change does not require an archaeology project. Decide who owns the Webflow subscription: we recommend you do, with your own payment method, so nothing about your live site depends on an agency relationship continuing.
The support window
Things surface in the first few weeks that no amount of QA catches, usually browser quirks, an unexpected content length, or a form integration behaving differently under real traffic. A reasonable handoff includes a defined window of included fixes after launch, typically 30 days, with a clear line between a defect and a new request. Ask where that line sits before you sign, not after you find a bug.
Questions worth asking before you sign
Will the site be transferred to our own Webflow workspace? Who holds Designer access afterward? Is training recorded and documented, or live only? What is included in the post-launch window and for how long? Are the styles built on a reusable system, and can you show me the class list? If the answers are vague, the handoff will be too. For what these engagements typically cost and what drives the range, see how much a Webflow website costs. If publishing capacity is the real question rather than the build itself, the math in fractional versus in-house is the more useful place to start.
The short version
A good handoff transfers ownership, not just files. Your workspace, your billing, your domain, scoped permissions, a CMS someone can actually use, and documentation that outlives the people who were on the launch call. Everything else is polish.
