Price Your Project: Free Tutorial by Carlos Geronimo

Marketplace Tutorials Categories Business

Stop leaving money on the table. Here's the framework I use after four years of client work.

Introduction

Pricing is the part of freelancing nobody teaches you.

You learn Framer. You build great sites. And then a client asks "how much does this cost?" and you freeze — or worse, you make up a number that feels safe and immediately regret it.

I've been there. For the first two years of my freelance career, I undercharged consistently. Not because I didn't know my work had value — but because I had no system. I was guessing every time.

This guide covers the framework I use now to price every Framer project. It won't give you a magic number. But it will give you a process that makes sense — and a starting point you can actually defend.

1. Understand what you're actually pricing

Scope is not just a page count.

The most common mistake when pricing a Framer project is treating it like a flat fee per page. Five pages, multiply by X, done.

That ignores everything that actually takes time.

Here's what I factor in before quoting any project:

Complexity of the design: A marketing site with static sections is not the same as a product site with interactive demos, scroll animations, and custom code components. The visual complexity directly impacts build time.
CMS requirements: A blog with three interconnected collections — articles, authors, categories, all cross-referenced — is a different project than a simple page with no dynamic content.
Custom code components: Anything that goes beyond Framer's native capabilities adds time.
Integrations: Forms, analytics, third-party tools. Each integration adds setup time and testing time.
Revisions and feedback rounds: More on this later — but the expected number of revision rounds should always factor into your quote.

2. Choose your pricing model

There's no universally right answer — but there is a right answer for your situation.

There are three main models for pricing Framer projects. Each has tradeoffs.

Fixed price: You quote a number upfront based on the full scope. The client knows exactly what they'll pay. You take on the risk if the project runs long.

Best for: well-defined projects with a clear brief and experienced clients who know what they want.

Hourly rate: You charge by the hour and track your time. The client pays for exactly what you work. You take on less risk — but clients often feel less comfortable with open-ended costs.

Best for: ongoing work, maintenance, or projects with undefined scope.

Packaged pricing: You define fixed service tiers, each with a set scope and price. Clients choose the package that fits.

Best for: positioning yourself clearly and reducing back-and-forth on scope.

I use a combination: fixed price for new client projects, packaged options for repeat clients and agencies.

3. Estimate your hours honestly

Most freelancers underestimate. Always.

Before setting a price, estimate the hours. Not what you hope it will take — what it will actually take, including the things you always forget to account for.

Add those up. Multiply by your hourly rate. That's your floor — never quote below it.

Then add a buffer. I’d add 15-20% to every estimate to cover the things that always come up: a section that needs rebuilding, a client request that wasn't in the brief, a third-party integration that takes twice as long as expected.

4. Factor in the feedback phase

Unlimited revisions is not a strategy. It's a liability.

One of the most common ways freelancers erode their margins is through unstructured revision rounds. The client sends feedback through three different channels, you lose track of what's been addressed, and the project drags on two weeks past the agreed deadline.

I cap revision rounds at two in my contracts, and I run them through a structured process — the client reviews the live site, leaves feedback directly on the page, and I work through it item by item. When everything is marked resolved, the round is closed.

If you want to tighten up this part of your process, ClientFlow is a Framer plugin I built specifically for this — it lets clients leave feedback directly on the live site, and you manage it all from inside Framer.

The point is: revision rounds have a cost. Build that cost into your quote — or define what happens when the client exceeds the agreed number.

5. Validate your number before you send it

The price should feel slightly uncomfortable. That's usually right.

Before sending a proposal, I run my number through three quick checks:

Does it cover my hours? Take your estimated hours, add the buffer, multiply by your rate. If the quote is below that number, something is wrong.

Does it reflect the value delivered? A site that generates leads, represents a brand to the world, and runs without a developer — that's not a commodity. Price it like a product, not a service.

Would I do this project at this price without resenting it? If the answer is no, the price is too low.

If you want a starting point before going through this process manually, I built a free Framer Project Calculator — you answer a few questions about the project and get a personalized estimate in your inbox. It won't replace your judgment, but it gives you a number to react to.