The Framer Expert badge tells you someone can build a site that survives review. It does not tell you whether the file they hand back will survive your team touching it. I went through the application, and I have since worked on 25+ Framer projects across AI SaaS, healthcare, fintech, and entertainment. Here is what I would actually check before hiring anyone, including me.

What the application actually involves

You submit three to five sites you have built. They get reviewed in detail, by a person, not a checklist. Responsiveness across breakpoints. How the file is structured underneath. Whether layers are named properly. Whether the animations are doing a job or are just there. If something does not fit, they catch it.

For me the wait was around two to three weeks. That was early in the programme, so treat the timeline as indicative rather than current; how they assess applications has almost certainly moved since.

The useful thing to understand is what the review actually screens for: construction, not decoration. Which is why the badge is a real floor. It is also only a floor.

What actually goes wrong in Framer files

The most common broken file I see is not from another agency. It is from the founder who built it themselves, and the failure is always the same shape.

People who have not built in Framer before do not have a mental model for relative versus absolute positioning. So elements get placed by eye instead of by structure. Alignment is approximate. There are no proper stacks holding anything together. The desktop view looks fine, so it ships.

Then you open the tablet and mobile breakpoints and there is nothing there. Not broken exactly, just never structured. The layout was assembled until it looked right on one screen and published.

The second failure comes later. The founder goes in to make a small change, and because nothing is structured, the change propagates somewhere unexpected and breaks something else. Then they change more to compensate. That is usually the point at which I get the email.

Rebuilding is usually faster than fixing, and that surprises people

Founders assume inheriting a half-built site saves money. In my experience the opposite is true: it is generally easier to rebuild a badly structured Framer file from scratch than to repair it.

The reason is that Framer's strengths work against you in a bad file. Text styles and colour styles are global by design, which is exactly what you want in a clean build. Change a heading style once and it updates across every page. But in a file where nothing was set up as a style in the first place, and elements were positioned individually, every correction you make either fails to propagate or propagates somewhere it should not. You end up chasing the file rather than fixing it.

A clean file has a real type hierarchy, proper H1 and H2 structure for SEO, and styles that cascade predictably. Change one thing and the site stays consistent. That is the whole point, and it cannot be retrofitted cheaply.

So if you are getting quotes to fix an existing build, be suspicious of the cheapest one. It probably means patching, and patching a structurally broken file is money spent on a problem that comes back.

When I tell people to buy a template instead of hiring me

Most people who come to me with an existing Framer file bought a template. They want it to stop looking like a template, rebranded, with new sections and pages for what they actually do.

That is good work and I am happy to do it. But here is the part that is against my own interest: if your budget is tight, buying a template and paying me to build on top of it is usually the better purchase than commissioning a site from scratch. You get further for less. A custom build from zero is worth it when your brand needs to be genuinely distinctive and you have the budget for that to matter. If you do not, a well-chosen template plus real customisation will serve you better than a thin custom site.

Anyone who never recommends the cheaper path is optimising for their invoice.

The check I run on every project now

Before anything else: is the copy ready?

This is the single biggest cause of missed deadlines in website projects, and almost nobody scopes for it. If the copy is not written, either the founder writes it while I am designing, or I work through it with them. Both take time that was not in the estimate. Design decisions cannot be finalised against placeholder text, because the length and hierarchy of real copy changes the layout.

So if you are hiring and the designer does not ask about copy in the first conversation, you are going to have a timeline conversation later.

What to actually check before you hire

Ask for a screen-share of a real client file and look at the layer tree. You do not need to know Framer to tell the difference between organised and chaotic. Open three of their live sites on your own phone, cold, not the case study video. Ask how they would structure your CMS before they design anything, because badly modelled content is the most expensive mistake in a Framer build and you will not discover it until you have fifty items in. Settle project ownership and transfer in writing before kickoff, not after final payment.

And hire the one who pushes back on your brief. Production is cheap to buy. Judgment is the thing you are actually paying a senior rate for. If you are still weighing what a startup website should cost, start there.