Should you publish your prices?
Yes. Put at least a starting price on your page. It answers the first question every client has before they ask it, turns away the people who could never pay it, and lets everyone else arrive already decided.
Picture the visitor. They found you, they like what they read, and then the page goes quiet on the one thing they need to decide. So they do the polite thing. They leave, meaning to write later. Later doesn’t come.
| A full price | A starting price | On request | |
|---|---|---|---|
| Works for | Sessions, packages, anything with a fixed shape | Projects that vary in size | Work that’s different every time |
| What the client knows | Exactly what they’ll pay | What it costs at the least | Nothing, until they ask |
| What it costs you | Nothing | One short conversation about scope | A conversation with everybody, including people who can’t afford you |
Yes, it scares some people off
It scares off the people who were never going to pay it, before they’ve taken an hour of your week. The ones who write have already said yes to the number.
When “on request” is right
When the price depends on something you can’t know until you’ve talked: the size of a team, the state of a codebase, a house you haven’t seen. Even then, give a range. “Most projects land between $3,000 and $8,000” answers the question without committing you to either end.
Check your booking page reads your page the way a client first meets it and tells you whether there’s a price on it.
A price is a filter. Let it do its job.
Checked 2026-10-10.