Spend time in any freelancing subreddit and pricing comes up constantly. Someone posts their quote and asks if they’re charging too much or too little. Someone else describes an underpriced job that turned into a nightmare. The experienced voices in those threads have been giving consistent advice for years — and most of it holds up.
The core Reddit consensus on pricing
Across r/freelance, r/webdev, r/graphic_design, and dozens of other communities, the same themes appear repeatedly:
Stop pricing by the hour, start pricing by value. “If you can build something in two hours that saves a client ten hours a week, charging $150 for your time is leaving enormous value on the table.” This appears in some form in nearly every pricing discussion. The implication: your rate should reflect the outcome you’re delivering, not the time it takes you to deliver it.
Double your first instinct. Newer freelancers consistently report that their initial pricing felt too high and turned out to be too low. Many experienced freelancers advise new ones to take their first number and multiply it. Not always literally, but the principle holds: beginner quotes are almost always underpriced.
The client who balks at your rate is often the client you don’t want. The ones who spend the most time negotiating your price tend to create the most scope issues, the most revision requests, and the most payment problems. Clients who approve a fair rate without fuss tend to be better clients.
If you lower your price to win work, you attract clients who made their decision based on price. That’s the client you’ll be undercharging for the entire project.
Build the estimate from the ground up
Regardless of how you present the final number, the calculation should start from a detailed time estimate. Reddit’s experienced freelancers are consistent on this: vague gut-feel pricing leads to underpriced projects.
Their typical process:
- List every task and phase
- Estimate hours for each, including communication, revisions, and admin
- Multiply by your target hourly rate
- Add hard costs (tools, assets, subcontractors)
- Add a contingency buffer (15-25% for unknown factors)
- Decide whether to present as fixed price or estimate
The fixed-price version is usually more palatable to clients — it gives them certainty. But it should be based on this bottom-up calculation, not a guess.
Price to your target client, not the market average
One of the most practical pieces of advice from freelance forums: know who you’re trying to work with, and price for them.
If you want to work with small startups on tight budgets, your pricing needs to reflect that. If you want established businesses and agencies, your pricing needs to reflect that credibility. Trying to be competitive with every segment simultaneously usually means you’re not optimal for any of them.
The implication for quotes: the way you present the price matters as much as the number. A clean, professional quote with detailed line items and clear terms positions you differently than a quick email with a lump sum. The same $5,000 price feels different depending on how it’s presented.
Common pricing mistakes from the forums
Patterns that come up repeatedly as cautionary tales:
- Not charging for revisions beyond the included rounds — scope creep kills margins
- Including unlimited revisions — never do this
- Quoting before understanding the full scope — leads to repricing conversations
- Discounting to win the job — sets a precedent and attracts price-sensitive clients
- Not increasing rates — your rates from two years ago should not be your rates today
The through-line is the same: treat your freelance business like a business. That means pricing deliberately, protecting your scope, and building systems — like proper quoting with tools like Waco — that let you operate professionally at scale.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
