“If I hand this over to an agency, do I lose control of my own website?”
That’s the question that quietly delays this decision for months.
Because your website isn’t just another asset, it’s tied to revenue, campaigns, brand perception, and growth. The idea of giving someone external access feels risky. And honestly, it can be, if you do it wrong.
If you’re also evaluating whether bringing in an agency even makes sense, it’s worth understanding what you’re actually paying for, see How Much Does Webflow Maintenance Cost.
Here’s the part most teams don’t realize:
Handing off your Webflow site does not mean giving up ownership. But the way you structure access, documentation, and responsibilities determines whether this becomes a smooth partnership or a slow, expensive mess.
To hand off your Webflow site to an agency, you add them as a guest collaborator in your Workspace, they get access to build and edit, and you retain ownership. You don’t transfer your site or lose admin rights. Share your style guide, CMS structure, active integrations, and a clear scope of what they own. You stay in control.
Where most teams go wrong is in one of two ways:
- They give too much access, admin rights, full control, and even transfer the site
- Or they give too little context, no documentation, unclear ownership, scattered requests
Both lead to the same outcome: confusion, delays, and loss of control, the exact thing you were trying to avoid.
This guide fixes that.
It’s a step-by-step blueprint for handing off your Webflow site the right way, so an agency can actually do their job, while you stay firmly in control of your site, your brand, and your growth engine.
First, You Don’t transfer your site; you invite the Agency
Your site stays in your Workspace. You own it. You control access. The agency is a guest.
This is the most important thing to understand before you do anything else.
In Webflow, your site lives inside your Workspace, and that Workspace belongs to you. When you bring in an agency, you are not handing over your site; you are simply inviting them in as a collaborator.
That distinction changes everything.
Here’s how it actually works:
- You add the agency as a guest collaborator to your Workspace
- They get access to design, build, and update the site
- You retain full ownership, including billing, hosting, and control
- You can remove their access at any time, instantly
At no point does the agency “own” your site unless you explicitly transfer it, and that is a completely separate action.
And this is where a lot of teams get tripped up.
There are two very different things in Webflow:
- Inviting a collaborator, which gives access without ownership
- Transferring a site to another Workspace, which changes ownership entirely
Only you can initiate a transfer. An agency cannot take your site from you, and a legitimate maintenance partner will never ask you to.
If they do, that’s not a process requirement; that’s a red flag.
The right setup is simple: your site stays exactly where it is, inside your Workspace, and the agency works within that environment under the access you control.
Once you understand this, the entire handoff process becomes a lot less intimidating, because you’re not giving something away, you’re just letting someone help you manage it.
Webflow Access Levels, What to Give and What to Keep
This is where most handoffs go wrong.
Not because teams don’t trust agencies, but because they don’t fully understand what each level of access actually allows. So they either over-share and lose control, or restrict access so much that nothing gets done efficiently.
Webflow keeps it simple. There are three access levels that matter. The key is knowing what to give, when to give it, and what to never give at all.
Editor Access
What they can do:
Update CMS items, edit text, swap images, publish content changes
What they cannot do:
Touch layouts, styles, classes, interactions, or custom code
Best for:
- Internal teams managing content
- Agencies handling blog uploads, landing page copy updates, or CMS changes only
Editor access is safe and limited. It’s designed for content workflows, not design or development.
If your agency is only updating blog posts or making copy changes, this is enough.
Designer Access
What they can do:
Full access to the Webflow Designer, layouts, styles, classes, interactions, and custom code
What this enables:
- Building new pages
- Fixing layout issues
- Improving UX and responsiveness
- Implementing integrations and scripts
Best for:
Any agency responsible for ongoing maintenance, design updates, or development work
This is the access level where real work happens.
But it comes with responsibility.
Before granting Designer access, you should be confident in:
- Their process and quality standards
- How they manage changes and approvals
- Whether they document what they ship
Because with this access, they can change how your site looks and behaves.
Admin Access
What it controls:
Billing, plan upgrades or downgrades, workspace members, permissions
What to do:
Do not give this to an agency
There is no valid scenario where an external agency needs admin-level control of your Workspace.
Giving this away means giving control over:
- Your subscription and billing
- Who else can access your site
- Your overall Workspace structure
This should always stay internal.
Access Levels at a Glance
The rule is simple:
- Editor access keeps things safe but limited
- Designer access enables real work but requires trust
- Admin access stays with you, always
If you get this right, you create a setup where the agency can move fast, without ever putting your ownership or control at risk.
What to Prepare Before the Agency Touches Anything
This is where most handoffs quietly break.
Not because of access, but because of a lack of context.
An agency can have perfect Designer access and still struggle if they don’t understand your brand system, your CMS structure, or what’s already in motion. That’s when things get rebuilt unnecessarily, integrations break, or worse, live campaigns get affected.
A clean handoff isn’t just about permissions; it’s about giving the agency enough clarity to move fast without guessing.
Here’s what you should have ready before they touch anything:
Brand and Design Assets
This defines how your site should look and feel. Without it, every update becomes subjective.
Include:
- Your current style guide, typography, color system, spacing, and component usage
- Logo files and brand assets in an organized folder, Figma, or Google Drive
- Fonts, where they’re sourced from, and any licensing notes
If this is missing or outdated, expect inconsistencies almost immediately.
CMS Structure Documentation
Your CMS is the backbone of your site. If an agency doesn’t understand how it’s structured, they will either avoid touching it, or break it.
Include:
- A map of all CMS collections and their fields
- Notes on naming conventions or content relationships that aren’t obvious
- Current CMS item count, important for Webflow plan limits
This saves hours of reverse engineering.
Integrations Inventory
Most Webflow sites are connected to multiple tools, and this is where things often break during handoffs.
Include:
- A list of every active integration, including HubSpot, Salesforce, Marketo, Intercom, analytics, and chat tools
- Who owns or manages each integration
- Any API keys, embed codes, or automations running via Zapier or Make
If an agency doesn’t know something exists, they can’t protect it.
Active Campaigns and Locked Pages
Not every page should be touched.
Some pages are tied directly to revenue, and even small changes can impact performance.
Call out clearly:
- Pages currently used in paid campaigns that should not be changed without approval
- Any pages involved in A/B tests
- Seasonal or time-sensitive landing pages
This prevents accidental disruptions.
Ongoing Tasks and Open Requests
You’re not handing off a static site, you’re handing off a moving system.
If you’re not sure what should actually be in that backlog, this Webflow Maintenance Checklist: What to Do Every Month breaks down the exact tasks teams should be tracking consistently.
Give the agency a clear starting point.
Include:
- Your current backlog of website requests
- Known bugs or broken elements
- Pages that are planned but not yet built
This helps them prioritize and get momentum immediately.
Pre-Handoff Checklist
If you skip this step, the agency will spend the first few weeks figuring things out instead of actually improving your site.
If you get it right, they can start delivering value almost immediately.
How to Structure the Agency Relationship So You Stay in Control
Access and documentation set the foundation, but structure is what keeps things running smoothly over time.
Without clear rules, even a good agency relationship starts to drift. Requests get lost in Slack, priorities get misaligned, and changes go live without proper review.
Control doesn’t come from restricting the agency, it comes from setting clear operating rules from day one.
Here’s what that looks like:
1. Assign a Single Point of Contact
One person on your team should own the relationship.
Not three people. Not “whoever is available.”
This person:
- Submits requests
- Clarifies priorities
- Approves work
It keeps communication clean and avoids conflicting instructions.
2. Standardize How Tasks Are Submitted
Pick one system and stick to it.
Not email, Slack, and random calls all at once.
Whether it’s ClickUp, Asana, or another tool, every request should:
- Live in one place
- Be clearly described
- Be trackable from start to finish
This creates visibility and accountability on both sides.
3. Define Turnaround Expectations
Not everything is urgent, but if everything feels urgent, nothing moves efficiently.
Set clear expectations:
- What qualifies as urgent
- What falls under standard requests
- Typical turnaround times for each
This prevents last-minute pressure and keeps delivery predictable.
4. Establish an Approval Process
Nothing should go live without clarity on who signs off.
Define:
- Who reviews design or structural changes
- What requires approval versus what doesn’t
- How approvals are given, tool, comments, or staging review
This protects your brand and avoids unnecessary rollbacks.
5. Use Staging for Structural Changes
For anything beyond small content edits, changes should be reviewed before going live.
This includes:
- New page builds
- Layout changes
- Major design updates
A staging or preview step ensures you see exactly what’s changing before it impacts users.
6. Set a Monthly Check-In Cadence
Even with a task system, you need a rhythm.
A monthly check-in helps:
- Review what was completed
- Align on priorities for the next cycle
- Catch issues before they compound
Without this, small misalignments turn into bigger problems over time.
Amply uses ClickUp for all task submissions. Every request is visible, tracked, and auditable. Your PM owns the queue.
When these rules are in place, the dynamic shifts.
You’re won’t be chasing updates or reacting to changes, but operating with a system where the agency executes, and you stay in control of direction, priorities, and outcomes.
What a Good Agency Handoff Document Looks Like
If your handoff lives across Slack messages, email threads, and scattered docs, it’s not a handoff, it’s a liability.
A strong setup starts with one living document that both your team and the agency rely on. This becomes the single source of truth for how your Webflow site is structured, managed, and updated.
Here’s what that document should include:
- Site Overview
What the site does, key sections, primary goals, and any critical flows or user journeys - Access Levels Granted
Who has Editor, Designer, and Admin access, and why - Brand and Design Assets
Links to style guide, Figma files, logo assets, typography, and design system - CMS Structure Map
List of all collections, fields, relationships, and any naming conventions - Integrations Inventory
All connected tools, ownership, API references, and automation notes - Locked Pages and Campaign-Sensitive Areas
Pages that should not be edited without approval, active campaigns, A/B tests - Ongoing Tasks and Backlog
Current requests, known issues, and planned builds - Escalation Contacts
Who to reach for urgent issues, approvals, or blockers - Billing and Plan Details
Webflow plan type, limits, renewal dates, and ownership
This document should be shared, accessible, and continuously updated, not something created once and forgotten.
If you don’t already have this structured, you can use Amply’s Webflow client handoff toolkit as a starting point.
When this exists, everything changes.
The agency doesn’t need to guess, chase context, or reverse engineer your setup. And you don’t need to worry about things slipping through the cracks.
You’re both working from the same system, which is exactly what keeps control where it belongs, with you.
Red Flags: What Bad Agency Handoffs Look Like
Not every agency setup is built to keep you in control.
And the problem is, most of these issues don’t show up immediately. They surface weeks later, when something breaks, goes live without approval, or no one can explain what changed.
If you see any of the signs below, it’s not just a process gap, it’s a structural problem.
1. They Ask for Admin Access
There is no valid reason for an external agency to control your billing, plans, or workspace permissions.
This is about control, not capability.
2. They Ask You to Transfer the Site to Their Workspace
This is the biggest red flag.
If your site lives in their Workspace, you no longer own it. Getting it back becomes a process, not a decision.
A legitimate agency works inside your Workspace, not the other way around.
3. No Project Management System
If tasks are being tracked across emails, Slack messages, and calls, things will get lost.
You’ll have no visibility into:
- What’s in progress
- What’s blocked
- What’s been completed
And accountability disappears quickly.
4. No Staging or Review Step
If changes go straight to live, you’re taking unnecessary risks.
Even small layout changes can break sections, affect responsiveness, or impact conversions.
There should always be a review step before anything structural is published.
5. They Can’t Explain What Changed
If you ask, “What was updated?” and get a vague answer, that’s a problem.
Every change should be:
- Documented
- Trackable
- Easy to understand
If it isn’t, you’re operating in the dark.
6. No Defined Approval Process
If there’s no clarity on who approves what, things will either:
- Go live without review
- Or get stuck waiting indefinitely
Neither is acceptable.
A clear approval flow is non-negotiable.
These issues aren’t edge cases, they’re common.
And they’re exactly why so many teams feel like they’ve “lost control” after bringing in an agency.
The difference comes down to structure.
At Amply, everything is built to prevent this:
- Tasks are tracked in a single system
- Changes are visible and documented
- Nothing goes live without a defined process
- And most importantly, your site stays in your Workspace, always
That’s what a controlled handoff actually looks like.
What Happens When You’re Ready to Part Ways
This is the question most teams think about, but rarely ask upfront.
“What happens if we want to stop working together?”
If your setup is correct, the answer is simple.
You remove the agency’s access, and that’s it.
- Your site stays in your Workspace
- Your CMS, designs, and custom code remain untouched
- Nothing needs to be transferred, reclaimed, or rebuilt
There’s no dependency, no lock-in, and no cleanup required just to regain control, because you never gave it away in the first place.
This is exactly why the structure of the handoff matters.
If an agency owns your Workspace or controls critical assets, leaving becomes complicated. If everything is set up under your ownership, leaving is just an access change.
Amply doesn’t own your site. You do. Our 30-day cancel notice exists so you have time to plan a transition, not because we’re trying to hold you.
A good agency relationship should feel easy to continue, not hard to exit.
If you can’t leave cleanly, you were never fully in control.
Final Thoughts
Handing off your Webflow site feels risky for a reason.
You’re trusting an external team with something that directly impacts revenue, campaigns, and brand perception. If the setup is wrong, that risk becomes real.
But if the setup is right, the opposite happens.
You get speed without chaos. Execution without constant oversight. And a system where the agency can move fast, without ever taking control away from you.
The difference isn’t the agency alone, it’s how you structure the handoff:
- Your site stays in your Workspace
- Access is intentional, not excessive
- Documentation removes guesswork
- Processes keep everything visible and controlled
Do this well, and you’re not “giving your site away.” You’re building a system where experts can improve it, while you stay in control of direction and outcomes.
If handing off your site has felt risky until now, it’s because most teams were never shown how to do it properly.
Now you have the blueprint.
.png)
.avif)