Whether to add a freelance rates page to your website divides freelancers almost as reliably as the question of fixed versus hourly pricing. Both sides have real arguments, both depend on context, and both miss the more useful question: if you do publish rates, what should you actually put there? A rates page that’s been thought through properly does more than disclose numbers. It pre-qualifies clients, filters out the wrong inquiries, and positions the conversation before a prospect ever reaches out.
The Case For Publishing Rates
Published rates save time, yours and the client’s. A prospect who sees your starting rate and self-selects out has spared both of you an inquiry, a call, and a polite decline. At higher rate levels, this filtering is genuinely valuable. If your day rate is $1,500 and a client’s budget is $400, neither of you benefits from discovering that on a 30-minute call.
Published rates also signal confidence. A freelancer who states their rates clearly is not apologizing for what they charge. That posture is itself a credibility signal, particularly for clients at the premium end of the market who associate hedging and vagueness on price with freelancers who don’t have enough work to be selective.
For freelancers with consistent, well-defined services, a copywriter who offers a service package, a developer who charges a fixed project discovery fee, a designer with defined deliverables, published rates work especially well because the price is attached to a concrete scope. The client knows what they’re getting and what it costs. There’s no ambiguity to negotiate.
The Case Against Publishing Rates
Publishing rates creates a ceiling. If a client arrives expecting your stated rate and the project warrants more, the conversation starts from the wrong place. Value-based pricing, which calibrates the fee to the specific value a project delivers, is incompatible with a public rates page that implies all projects of a given type cost the same.
Highly variable project types are hard to price publicly. A development project could cost $3,000 or $30,000 depending on scope, integration requirements, and deadline. A brand strategy engagement could run anywhere from a two-week sprint to a six-month project. Putting a number on that, any number, is either too low (leaves money on the table), too high (repels clients whose projects would have been profitable), or qualified with so many caveats that the number communicates nothing.
Large organizational clients often can’t act on published rates anyway. Their procurement process involves budget approval cycles that aren’t responsive to a rate card. For these clients, the rate is a starting point for a negotiation that will happen regardless. Publishing it doesn’t change the conversation; it just anchors it.
What to Put on a Freelance Rates Page That Converts
If you decide to publish rates, the page needs to do more than state numbers. Numbers without context create anxiety, not confidence. A rate that the client can’t evaluate against what they’re getting reads as arbitrary, and arbitrary prices invite pushback.
Starting rate or range, not a single number. “From $X per day” or “projects typically start at $X” is more honest than a fixed number for anything that involves variable scope. It filters by budget floor without implying that all projects cost the same. A range gives sophisticated clients room to estimate fit without committing either party to a specific number before scope is defined.
What the rate includes. This is where most rates pages fail. A day rate without context, what’s included, how many revision rounds, what the process looks like, is a number floating in a vacuum. Spell out what you actually deliver: revisions included, discovery process, whether project management is part of the fee, typical project timelines. The client is pricing an experience, not a number, and the rates page should tell them what that experience looks like.
What you don’t do. Scope boundaries on a rates page pre-empt the conversations that waste time post-inquiry. “I don’t take on projects under $X” is more useful than leaving budget floor implicit. “This rate covers X deliverables; additional requests are scoped separately” is clearer than discovering after the fact that client and freelancer had different expectations about what was included.
Social proof near the number. A testimonial or case study result that sits near the rates information reframes the rate as a value statement, not just a cost disclosure. Freelance testimonials that convert explains what makes a testimonial specific enough to do that work. “Clients typically see X outcome” or a brief quote from a satisfied client at that investment level changes what the number means to a prospect who’s evaluating whether it’s worth it.
What Creates Friction Instead
Vague rates create more friction than no rates at all. “Rates vary by project, contact me for a quote” on a dedicated rates page is worse than not having a rates page, because the prospect clicked through expecting to find something and found nothing. If you’re not going to publish rates, don’t have a rates page.
Long disclaimers undermine confidence. If the rates section requires three paragraphs of qualifications before the number appears, the message the client receives is that the freelancer isn’t sure what they charge. Qualifications are legitimate, but they should be brief and specific: “Rates vary for projects requiring travel” is a qualification. “Please note that rates can vary considerably depending on many factors including complexity, timeline, and other considerations” is a hedge that signals uncertainty.
Hourly rates invite micromanagement. Publishing an hourly rate, especially a low one, signals a transactional relationship and invites clients to think about time rather than outcomes. If you charge hourly, consider whether presenting your services as packages or project fees on the public page, with a note that hourly arrangements are available on request, better serves the kind of client relationship you want.
The Freelance Rates Page as a Positioning Tool
The way you present your rates tells a client something about how you think about your work. A rates page that lists a day rate with no context says “I sell time.” A rates page that describes what you deliver, what clients get from working with you, and what the engagement typically produces says “I sell outcomes.” That distinction matters at every price level, but it matters most when you’re positioning yourself for higher-value clients who are buying judgment and results, not hours.
The test for whether your rates page is working: are the inquiries you receive from people who have read it better qualified than the ones you got before? If the quality of inquiry has improved, fewer budget mismatches, more clients who understand the scope and accept the rate without negotiation, the page is doing its job. If the inquiries are worse, or you’re getting fewer when your pipeline was already thin, the rates page may be filtering more aggressively than your current volume can absorb.
Connecting rates to the value of the work is a separate skill from simply disclosing a number. Understanding how to price a freelance project before you decide what to publish is worth doing, because a poorly calibrated rate on a public page is harder to walk back than one that only appears in a proposal.