Operating ProcedureExecution layer

Framer Client Site Handoff and Domain Cutover (Delivery)

A sequence with 8 steps: Duplicate the approved client project inside the Framer workspace so the production file is frozen before handoff.

By InnovaAI ResearchPublished

What are the steps?

sequence

Framer Client Site Handoff and Domain Cutover (Delivery)

  1. 01

    Duplicate the approved client project inside the Framer workspace so the production file is frozen before handoff

    Keep the working file for revisions and move only the duplicated project into delivery. This prevents late design edits from landing on a site that is already connected to a live domain.

  2. 02

    Assign the client's custom domain under Project Settings, then publish to Framer's global CDN

    Framer hosting carries a 99.99% uptime guarantee. Confirm the domain resolves before you touch DNS records on the client's registrar, and note that client sites stay on Framer infrastructure, so plan the migration conversation before the retainer starts.

  3. 03

    Verify CMS collections match the sold scope: 2 collections on Basic, 10 on Pro

    If the client bought a blog plus service listings, that is 2 collections and Basic covers it. A third collection forces a plan upgrade, so reconcile the count against the signed scope before publishing.

  4. 04

    Configure SEO metadata and site redirects on every page, then run a crawl to confirm no 404s

    Site redirects are a Pro-tier feature. If the client is on Basic, map old URLs manually or flag the gap in the handoff doc rather than promising redirect coverage you cannot deliver.

  5. 05

    Connect Slack, GitHub, or Claude Code so the client's team can trigger content updates from their existing tools

    This is the handoff lever that reduces post-launch support tickets. Document which integration the client owns and which credentials stay with the agency.

  6. 06

    Record the CMS editing workflow in a short screen capture and attach it to the handoff doc

    The Starter Site Launch offer includes this documentation step. Clients who can edit their own CMS collections stop filing retainer requests for copy changes.

  7. 07

    Set the client as the billing owner on their Framer plan and remove agency payment methods

    Basic runs $10/month and Pro runs $30/month. Decide at contract stage whether the client pays Framer directly or you bill it through the retainer, and write that choice into the handoff doc.

  8. 08

    Schedule a 30-day post-launch check on bandwidth usage and AI credit consumption

    Basic includes 50 GB bandwidth and Pro includes 100 GB. A traffic spike on a launch campaign can push a client past their tier, so catch it before Framer throttles the site.