Inventory ownership and billing
Inventory the domain, business email, forms, scheduling, payments and licensed assets as well as the visual site builder. Record the legal subscriber and the recipient of renewal notices. A single monthly agency invoice can still hide several different ownership and transfer arrangements. Identify what the business can continue using independently and which services require an explicit transfer when the production relationship ends.
Record owner, payer, renewal and support route for each. Inspect each product’s documented transfer or access process rather than leaving the business dependent on a contractor’s personal account or assuming every subscription is transferable.
Assign access by work
Start access decisions from the work performed by each person. A content editor may not need subscription administration, while a billing owner may not need design access. Distinguish routine tasks from emergency authority and use individually revocable access where the platform supports it. The handoff should explain who can grant, review and remove permissions instead of distributing one shared login without an accountable owner.
Check current role entitlements and costs on the actual platform. Use access that can be withdrawn individually, with an assigned offboarding owner, rather than treating one shared owner login as the handoff package.
Have the operator complete one routine update
Ask the receiving operator to correct a phone number, replace an image and review the change before publishing from their own normal setup. Let that person follow the written instructions rather than having the builder perform the actions for them. After publication, verify the intended page and dependent forms. This exercise exposes missing permissions, unclear review steps and undocumented dependencies before the production team becomes unavailable.
Record the reviewer’s checks where approval is required. A useful procedure names the shared elements that should not be changed and the way to reverse a mistake, not only the sequence of interface clicks.
Plan recovery and separation
Separate recovery of visible pages from recovery of the complete service. Stored code or design files do not necessarily reproduce CMS content, search, intake processing or protected pages on another host. Use the platform’s export documentation to identify the boundary, then agree which missing functions would require rebuilding. Include emergency contacts and an alternative intake route for the period when the normal site cannot be used.
Retain contacts, data locations and manual fallback procedures. Export and backup coverage vary; verify what can actually be retained instead of assuming a complete site will automatically run unchanged on another service.
Define acceptance beyond appearance
Acceptance should include a delivered enquiry that the responsible person can find, alongside the visual review. Check licensed material, billing and the route for future change requests. Write down the agreed work and the work outside that scope. This makes it easier to distinguish correcting an incomplete delivery from commissioning a new feature, and prevents an unclear commercial handoff from becoming an operational dependency.
Keep demonstration records distinct from real customer data and review unnecessary access through proper procedures. Document the boundary between builder and operator, including who handles minor changes after launch.
Rehearse the day an operator changes
After the rehearsal, distinguish access that is no longer needed from access required for an agreed maintenance contract. Transfer responsibility at an explicit time instead of removing everything and discovering that nobody can support the site. Assign an owner for the first routine update and the next contract renewal. Handoff quality becomes visible when the new operator can complete those later tasks without reconstructing the original project history.
If granting access, removing obsolete access and paying invoices have different owners, retain a contact for each responsibility.
Demonstrate the tasks through legitimate accounts and permissions, then define the remaining designer-dependent work as the scope of an actual maintenance arrangement.
Official sources
Pricing, availability and feature limits can change. Check the linked official pages before subscribing.
- Framer site plans overviewInformation checked: 2026-10-27
- Webflow Site and Workspace plansInformation checked: 2026-10-27
- Carrd Pro plansInformation checked: 2026-10-27
- Squarespace plan featuresInformation checked: 2026-10-27
- Webflow code exportInformation checked: 2026-10-26
- Framer pricingInformation checked: 2026-10-27
- Webflow Workspace and Site plansInformation checked: 2026-10-26
- Carrd Pro featuresInformation checked: 2026-10-27
- Squarespace pricingInformation checked: 2026-10-27
- Selling on Squarespace website plansInformation checked: 2026-10-27