What a Designer-Built Framer Site Actually Ships With
I'm Sterre van Dijk, founder of Seven Purple Mangos. I have watched too many Framer sites launch with a lovely homepage and no way for the marketing team to add a case study. The framer website builder is only worth the money when the build leaves you with an editable, fast, measurable site.
That is why I judge every handover by what still works a year after launch. Below I walk through what a designer-built Framer site actually ships with. You will learn how to read framer website examples as a handover checklist, what a CMS your marketing team can add to looks like, and how forms and tracking should be wired before handover.
I also cover motion that does not slow the page, speed checks you can run yourself, and breakpoints that match your buyers' phones and laptops. I finish with where Framer design stops and your edits begin, what the last day contains, questions to ask about any Framer build, and a one-minute handover test.
Judge a Framer build by what still works a year after launch
A Framer build is easy to admire on launch day. The real test comes six months later, when a price changes or a paid campaign needs its own landing page.
What you walk away with is the handover inventory. That means the CMS collections, form routing, tracking, motion settings, breakpoints and the design files behind the build.
I judge every page by the job a design has to do after it goes live. Your marketing changes week to week, so the site has to keep up with you. A page that only looks finished on delivery day is not finished.
You get a fixed price before you decide anything. The list of what is included is agreed before I open Framer, so nothing depends on guessing later.
If the site cannot be edited by the person running the ads, you have bought a picture of a website.
Reading framer website examples like a handover checklist
Framer website examples are great research, and most people study the hero image and stop there. Open a few on your phone first. If the text is tiny or the menu fights your thumb, the breakpoints were never tested, and WCAG 1.4.10 reflow asks for content that works at 320 CSS pixels without sideways scrolling.
Find the blog or the work page next. If the newest item is dated a year ago, either the brand stopped publishing or nobody there can add one.
Send the contact form and watch what happens. A thank-you page gives your ad platform a URL to count, which an on-screen message does not.
Ask which parts of those pages are fed by a collection and which were placed by hand. That answer tells you how much you will be able to edit later. I ask the same questions of any build I review.
The CMS your marketing team can add to without me
Collections decide how much you can edit without me.
Repeatable content belongs in collections: blog posts, team members, case studies, FAQs. The layout pulls from the fields, so adding one item updates every place it appears.
Then ask this. Can you add a post, fill in the fields and publish it yourself? If every new item goes through me, the CMS is decoration.
Field planning decides whether your edits stay tidy. Title, slug, image, alt text and a short summary need to exist before launch, or new posts publish with broken previews. Alt text is a text alternative for images, and WCAG 2.1 requires one at Level A.
What breaks a Framer CMS is content typed straight into the page instead of pulled from a collection. The list page and the item then drift apart.
Test it in your own hands before you sign off. Add one draft item, change its title, publish, then check the list page, the mobile view and the search result.
Forms and tracking that are wired before handover
Once your CMS is settled, the next question is where a form submission lands. Ask for a specific answer: an inbox, a Google Sheet, your CRM, or a mix of those. "It goes to the site" is not one.
A thank-you page gives your ad platform a URL to count, which an on-screen message does not.
Before launch, I wire four events: form submit, thank you page view, clicks on your main call to action, and a hidden field that captures UTM values. That last one tells you which campaign brought the lead.
Then test on the live site, from a phone. The email has to arrive, the sheet row has to appear, and the conversion has to show in your ad platform after the test completes.
Add a consent line that records what the person agreed to. Documented consent means holding a record of what they were told and when. A honeypot field cuts spam without asking anyone to solve a puzzle.
How a framer website builder runs motion without slowing the page
A form can land correctly and the page can still stutter, which is why motion is something I check before launch.
Entrance animations, scroll reveals and hover states earn their place when they point to the next action, such as the form or the pricing table. If an animation points at nothing, I cut it.
Cheap motion animates transform and opacity, keeps entrances short, and starts after the content is visible.
Costly motion looks like a full screen video on the first screen, four scroll effects stacked on one page, or animation that starts before the headline has painted.
Set a reduced-motion version so anyone whose system requests less animation still gets a readable page.
Open the finished page on a real phone over a normal connection. If the scroll stutters, the motion is doing too much.
Speed you can check yourself after launch
Motion is settled, so now the numbers. In a Framer build I control four things that move speed: image sizes and formats, lazy loading for anything below the first screen, how many fonts load, and how many third party scripts you add.
Metric names and thresholds live in Google's own Web Vitals documentation. Check that page for the current figures instead of trusting a number you read somewhere.
After launch, run PageSpeed Insights on the live homepage and one paid landing page. Then watch the Core Web Vitals report in Search Console over the next few weeks. Field data comes from real visitors, so it lags a live test.
No build scores the same on every page. A heavy hero video on the first screen can drag load time down for everything else, and so does a chat widget you add three months later.
When something is slow, fix it in this order: compress the largest image, remove or delay the worst third party script, then look at fonts.
Breakpoints that match the phones and laptops your buyers use
Speed is half the story. The other half is how the page holds up on the screen your buyers hold.
I build three layouts: desktop, tablet and phone. Each needs designing, because scaling a desktop layout down drops text sizes and spacing in odd places. That is where responsive design across devices stops being a checkbox.
On the phone layout, check four things:
Headings that still read
Tap targets a thumb can hit, 24 pixels minimum under WCAG 2.2
Form fields big enough that the page does not zoom on focus
A menu that opens on tap
A page built only at desktop width can look stretched in the middle range, where many buyers browse. The same design principles for accessibility apply at every width.
I open the breakpoints on real devices before launch. Open the same pages on your phone after publish, because your browser, cookies and connection differ from mine. A layout that never left the Framer canvas is a guess.
What you can edit yourself, and what still needs me
Once breakpoints pass on real devices, one thing left to settle is who owns which change.
Safe on your own: text on a page, text inside a collection item, a swapped image, a new testimonial, reordering sections built to move, publishing a drafted post.
Still design work: a section that does not exist yet, a new page layout, a change to the grid, a new form field that alters where submissions go.
If a change is copy or content, make it without me and the layout should hold. I set fields up so a longer headline wraps instead of breaking the page.
For anything needing design, weekly check-in and fixed delivery days give your edit a slot instead of leaving it in a queue.
I write down which changes are yours and which come to me, so nobody has to remember a conversation from handover day. That note sits with the project files you get on handover day.
Where framer design stops and your edits begin
Framer design covers the layout, the type scale, the spacing and the components. Your edits all happen inside that frame.
A component with properties gives you a menu of safe choices. Change the label, the image or the link and the shape stays as designed. No nudging, no broken alignment.
What the handover contains on the last day
On the last day, you leave with:
Framer project access at editor level, plus the published site. You log in, open the project and change a page yourself.
Every CMS collection, with its fields named in plain words. Title, image, alt text, summary. Nothing cryptic.
Form destinations, the analytics property, conversion events and ad platform tracking, all wired and tested before handover. The analytics and ad pixels fire only after the visitor makes a choice, and every third party receiving data is listed.
The Figma file: brand colors, type styles, logos and the fonts used, with a note on where the license sits.
A short written guide on what you can change, what comes to me, and how to check speed and form delivery after launch.
From the first call to the last file, this list is agreed before work starts. You know what ships with the site.
Questions to ask about any Framer build
Once you know what should be in the handover, ask for it before you sign. Here are five questions that work on any Framer build.
Can I add a CMS item and publish it without you? Ask to see the fields during the build, not after. The field names should say what each one does.
Where does the form go, and what fires the conversion in my ad platform? Get a named destination and an event you can watch. An on-screen thank you gives your ads nothing to count.
Which breakpoints were designed, and were they checked on a real phone? Desktop, tablet and phone each need their own layout.
What loads and what animates on the first screen? Then ask how it behaves on a slow connection. A heavy hero video on the first screen can drag load time down for everything else.
On handover day, do I get the Framer project itself? And what does a change cost me a month later?
Ask all five while a fix is still cheap.
The handover test, in one minute
Those questions narrow to one test. Run four checks in one sitting. Add a post to the CMS, send the form, watch a conversion land in your ad platform, then change a headline and publish.
If you can do all four without me, the build did the job a design has to do. If one of them needs a developer, that is the question to answer before the final invoice.
Framer suits a growing brand that wants to move quickly with someone who already knows your brand. Judge it on the handover, because that is what you live with.
Conclusion
A Framer build is only as good as what still works a year after launch. Designed breakpoints for desktop, tablet and phone matter. So does getting the Framer project itself on handover day. That is the job a design has to do.
A build from someone who already knows your brand should hand you the keys and leave you running it. The handover is what you live with.
Frequently Asked Questions
How can I tell if a Framer website is built to last after launch?
Judge the build by what still works about a year after launch, not by how it looks on launch day. The handover inventory should cover the CMS collections, form routing, tracking, motion settings, breakpoints and the design files. Ask whether the person running your ads can edit the site, because if they cannot, you have bought a picture of a website.
What should I check on a Framer website example before hiring someone?
Open a few examples on your phone first to see whether the text is readable and the menu is easy to use. Then find the blog or work page and check how recent the newest item is. Send the contact form to see where it goes, and ask which parts are fed by a collection and which were placed by hand.
What do I need in a CMS so my marketing team can publish without the designer?
Repeatable content such as blog posts, team members, case studies and FAQs should live in collections, with fields like title, slug, image, alt text and a short summary set up before launch. Your team should be able to add a draft item, fill in the fields and publish it themselves. Content typed straight into the page instead of pulled from a collection causes the list page and the item to drift apart.
How should forms and tracking be set up before handover?
Ask for a named destination for form submissions, such as an inbox, a Google Sheet, your CRM or a mix of these. Use a thank-you page URL as the conversion your ad platform counts, rather than an on-screen message. The post recommends wiring form submit, thank-you page view, main call-to-action clicks and a hidden UTM field, then testing from a phone to confirm the email arrives, the sheet row appears and the conversion shows in your ad platform.
What does the handover include, and what can I change myself afterward?
On the last day you should receive editor-level Framer project access, every CMS collection with plainly named fields, tested form destinations and tracking, the Figma file with brand assets and a written guide. Copy changes, collection items, swapped images, new testimonials and publishing drafted posts are safe to do yourself. Changes to layout, the grid, a new section or a new form field that alters where submissions go are still design work.
