Hiring a Framer Developer: What to Ask Before You Pay

The expensive mistakes happen before the kick-off

Hiring a Framer developer is not hard because good ones are rare - hiring is hard because the first call is a sales call, and everyone sounds competent on a sales call. In practice, the projects I get asked to rescue all failed the same way: money moved before scope, ownership or SEO were ever discussed. The developer wasn't a villain; the contract was just twenty questions short.

I've already written a step-by-step guide to how to hire a Framer developer: where to look, how to read a portfolio on the live sites, how to compare quotes and what the contract must say. This article is the other half of that process: the exact questions to put to the one person you've shortlisted, before you pay a deposit, and the answers that should worry you.

Hiring a Framer developer: seven questions to ask before you pay

Ask all seven, in writing. The answers matter, but the way the questions are answered matters more - a senior developer has heard every one of these before and answers without flinching.

1. What exactly is included in the price? Pages, breakpoints, CMS collections, animations, integrations - itemised, not implied.
2. Who actually does the work? You personally, or a subcontractor I'll never meet?
3. Can you walk me through a live project with custom code components? Links, not screenshots.
4. How will SEO be handled? Redirects, metadata, structured data - and who is responsible for each.
5. How many revision rounds are included - and what counts as a revision?
6. Who owns the Framer project file, the domain and the assets when we're done?
7. What happens after launch? Support window, response time, and the hourly rate for future edits.

For a second opinion from outside the Framer bubble, this short video asks very similar questions of web designers in general: https://www.youtube.com/watch?v=MPySR3Kf9WE

"What exactly am I paying for?"

The most common dispute I see is not about quality - the dispute is about scope. "A website" can mean five pages or twenty-five, three breakpoints or one, a blog wired into the CMS or a static page with fake posts. Get the list in writing: pages, breakpoints (desktop, tablet and phone as a minimum), CMS collections, forms, animations, third-party integrations. If a developer resists itemising, the developer is keeping room to renegotiate later - at your expense.

"Show me real code components"

Framer's visual editor has a high ceiling, but the sites that feel genuinely custom lean on code components - and this is where portfolios lie most often. Ask the developer to open a live site the developer built and explain what the code actually does. If you're wondering how far the platform itself can stretch, I've covered that in Can Framer Handle Custom Code and WebGL? - the honest answer is "further than most developers can". You can also tell a lot from whether someone ships production files publicly at all; I keep my own Framer templates public partly so clients can inspect how my builds are structured before paying for one.

"How will SEO survive the build?"

This question matters even more if an existing site is being rebuilt. Moving platforms without a redirect map is how rankings die quietly over a quarter - I've documented the safe process in my Webflow to Framer migration guide, and the same logic applies from WordPress, Wix or a custom stack. A serious answer names specifics: 301 redirects mapped URL by URL, per-page titles and meta descriptions, structured data, image alt text, and a Search Console check after launch. "Framer handles SEO automatically" is not an answer; that line is a warning.

"Who owns the file when we're done?"

You should own the Framer project, the workspace the project lives in, the domain and every asset - full stop. The healthy pattern: the site is built in your Framer workspace (or transferred into that workspace at handover), billing sits on your card, and the developer keeps edit access only as long as you want the developer to. When a developer insists the project must stay in the developer's account "for maintenance reasons", your monthly bill has become the developer's retention strategy.

A deposit buys work, not promises. Every question you ask before paying is one you won't be asking a lawyer afterwards.

What a fair Framer quote looks like in 2026

Prices vary with seniority and geography, but after ten years of quoting - and being quoted against - these are the honest ranges for freelance Framer work:

Two caveats. First, a quote far below these ranges is usually a template reskin sold as custom work - sometimes perfectly fine, but you deserve to know which of the two you are buying. Second, platform choice changes the maths: if you are still weighing Framer against the alternatives, my Framer vs Webflow comparison breaks down where each platform actually earns its cost.

Red flags that should end the conversation

• Full payment upfront, or pressure to pay before a written scope exists.
• No live Framer links - only screenshots, Dribbble shots or "NDA'd" work.
• "SEO is included" with no mention of redirects, metadata or structured data.
• Evasiveness about who actually does the work.
• The project will live in the developer's account indefinitely.
• Revision terms that appear only after you have paid.

None of these makes someone a scammer. Each one makes your project the place where you find out.

Want the answers in writing before you pay anything?

Pavlo Zhydkykh is a senior Framer developer with 8+ years in web design and 50+ custom builds shipped. Every project starts with a written scope that answers all seven questions above - pages, ownership, SEO plan and support terms included - before any deposit is requested. If that sounds like the right way round, get in touch.