How a $2,000 Freelance Project Should Have Been Priced at $4,500
A realistic pricing teardown for a client who asked for an automation workflow.
The Job Everyone Gets Wrong
Most freelancers don't undercharge because they lack confidence. They undercharge because they only count the hours they know about — not the hours they don't.
A client asks for an automation workflow that integrates their CRM with their email tool. They say their budget is $2,000. You do some mental math: 15 hours × $120/hr = $1,800. You could do it for $1,900.
This is where almost everyone leaves money on the table. And it's not because you're bad at negotiating. It's because you're pricing the wrong thing.
The Project Nobody Should Quote at $2,000
Here's a real project setup:
Client asks for: An automation workflow connecting HubSpot to Gmail, with triggers, filters, and conditional routing. About 15 hours of work.
Their stated budget: $2,000
The $1,800 quote most people give:
15 hours × $120/hr = $1,800
This looks reasonable. It feels fair. Here's why it quietly destroys your business.
Why the Simple Math Is Wrong
What you're actually selling
When you quote by hours, you're treating this like a job. But your client isn't buying your time. They're buying:
- A working system that doesn't break when conditions change
- The peace of mind that the automation handles edge cases
- Someone to call if it stops working at 2am before a campaign launch
- Confidence that the data in their CRM actually matches their email tool
That's not 15 hours of work. That's an operational system with ongoing value.
The hidden complexity
A CRM-email integration that "just works" involves:
- Implementation cost: What you think is 15 hours
- Scope uncertainty buffer: What happens when the client's CRM has custom fields you didn't know about?
- Revision risk: What if the client changes their mind about the trigger conditions?
- Client-side coordination: Will someone be available to approve credentials and test the sandbox environment?
- Communication overhead: How many meetings, Loom videos, and Slack threads does this actually take?
- Delivery confidence: What is it worth to you to guarantee this works before go-live?
If you only charge for the first one, you're subsidizing the rest.
The Correct Pricing Breakdown
Here's what a fair quote looks like when you count everything:
| Component | Cost |
|---|---|
| Implementation (15 hrs × $120) | $1,800 |
| Scope uncertainty buffer (20%) | $360 |
| Revision risk (10%) | $180 |
| Client coordination overhead (5 hrs) | $600 |
| Communication thread cost (3 hrs) | $360 |
| Delivery confidence guarantee (5 hrs) | $600 |
| Total | $3,900 |
Round down to $3,500 for a cleaner number, or structure it as three options.
Three Options Instead of One
Most clients who push back on $3,500 aren't saying the work isn't worth it. They're saying they can't justify the full amount right now. Give them a tiered structure:
Option 1 — The Core ($2,800)
- Standard CRM-email integration
- Basic triggers and filters
- 2 rounds of revisions
- 30-day support window
Option 2 — The Complete ($4,500)
- Everything in Option 1
- Edge case handling for 5 common scenarios
- Full documentation
- 90-day support window
- Priority response within 24 hours
Option 3 — The Enterprise ($7,500)
- Everything in Option 2
- Custom error handling and fallbacks
- Monitoring dashboard
- 6-month support window
- Monthly check-in call
This works because you're not discounting. You're giving them a real choice about scope and risk. The client who takes Option 1 still gets a working system — and the ones who need more pay for more.
Copy This Mini Calculator
Want to reprice your next freelance project? Use this formula:
BASE = hours × your_rate
COMPLEXITY = BASE × 1.25 (if the brief has any ambiguity)
RISK = BASE × 0.15 (if client has a history of changing scope)
COORDINATION = hours_you_estimate × 0.4 × your_rate (meetings, reviews, back-and-forth)
SUPPORT = hours × 0.3 × your_rate (buffer for questions after delivery)
FINAL = BASE + COMPLEXITY + RISK + COORDINATION + SUPPORT
This won't give you a perfect number. It will give you an honest one.
The Real Lesson
The $2,000 budget wasn't the project's value. It was the client's opening offer based on what they assumed your work was worth. Your job isn't to accept or reject it — it's to show them what the actual work costs and let them decide.
If they come back and say it's too expensive, that's when you have a real conversation about scope. But you can't have that conversation from $1,800. You can only have it from $4,500.
Want Me to Tear Down Your Next Quote?
If you're working on a project and want a second pair of eyes on the scope and pricing, I offer $10 quick reviews: paypal.me/cheapuno
Send me the brief, your current rate, and what you're thinking of charging. I'll send back a breakdown of what I'd charge and why — within 24 hours.
Continue Your Pricing Journey
If you want the framework behind this teardown: → The Freelance Scope Estimation Framework — the complete formula (BR × SM × RB)
If you're dealing with a scope change right now: → How to Price a Scope Change Without Losing the Client — specific phrasing and pricing strategy for mid-project changes
If you want a tool that does the math for you: → A 30-Second Pricing Decision Tree for Freelance Devs — answer 5 questions, get a price range
Who Is Actually Getting Burned
This isn't a confidence problem. It's a pricing structure problem.
The freelancers who get burned most are the ones who are competent, careful, and genuinely trying to do good work. They run the numbers honestly. They think: "15 hours at $120/hr = $1,800, I'll charge $1,900 and seem fair."
Here's what they didn't account for:
The client who says "we'll handle the technical details" — and then spends 6 hours in Slack threads coordinating credentials you could have set up yourself.
The project that "should take a week" — but the client's internal review process adds three rounds of feedback you never factored in.
The "simple change" that turns into a full rewrite because the client's original requirements didn't mention the compliance field their legal team added two days before launch.
If you've ever finished a project and thought "I actually lost money on this" — you already know this problem. You just didn't have a system for pricing it correctly upfront.
Self-Evaluation Checklist
Go through each one. If you answer "yes" to 3 or more, your next project is probably underpriced.
- [ ] The brief had any ambiguity — even a little "we can discuss later" in the scope document
- [ ] You've done this type of project before and it always takes longer than the initial estimate
- [ ] The client uses words like "flexible," "we'll figure it out," or "not a big deal" when discussing scope
- [ ] You'd need to schedule more than 2 calls/meetings to align on requirements
- [ ] There are stakeholders besides the person you're directly talking to (designer, manager, legal, etc.)
- [ ] The project has any integration component (APIs, webhooks, third-party tools)
- [ ] The client's industry has compliance requirements (healthcare, finance, legal, education)
If you're at 5+: You need either a scope document with explicit buffers, or you need someone to sanity-check your quote before you send it.
The Outreach Kit Angle
If you're reading this and thinking "I don't need a consultation, I need to know how to price better" — the Freelance Pricing Page Review Kit is a free downloadable resource with the templates and checklists I use when pricing my own projects.
If you've read it and still want a second set of eyes on a specific quote, I'm available for $10 quick reviews: paypal.me/cheapuno. Send me the brief and your current number. I'll tell you what I'd charge and why.
No pitch. No upsell. Just a direct breakdown within 24 hours.
This is part of a series on freelance pricing. If this helped you see your work differently, the best next step is to audit your current pricing formula before your next client conversation.
Top comments (0)