DEV Community

Cover image for How we redesigned our own studio's pricing page — and what it taught us about client psychology
аЛЕКС ЛИР
аЛЕКС ЛИР

Posted on

How we redesigned our own studio's pricing page — and what it taught us about client psychology

A few months back we rebuilt the pricing section on our own site, webmaster.co.ua, after years of running it as "contact us for a quote." Here's what changed and why.

We split price into named packages instead of a single custom quote. The old flow funneled every lead into a call before they saw a number. Now the site lists four tiers — a $200–400 landing page, a $400–800 business site, an $800–1,500 SEO-focused build, and a $1,500+ custom tier — each with what's actually included. Conversions from "just browsing" to "sent a message" went up, but more importantly, the messages themselves got more specific. People arrive already knowing which tier fits, so the first message is "I need the business tier, here's my situation" instead of "how much would a website cost."

We stopped hiding that the base tier uses AI-generated placeholder copy. This was the part we debated longest — does saying it upfront make the cheap tier look cheap? It didn't. It made expectations match reality, which meant fewer clients arriving at review stage disappointed that the copy wasn't hand-written. Naming the tradeoff at the pricing page did more for satisfaction than trying to overdeliver on copy quality would have.

We linked reviews out to a third-party platform instead of only showing curated quotes. Testimonials on your own site are testimonials you selected. Ours now link to verified reviews on an external freelance platform alongside the on-site quotes. Visitors don't have to trust our curation — they can check the source.

None of this required new tech. The whole rebuild happened inside our existing WordPress + Elementor setup — no framework migration, no rebuild from scratch. The lesson wasn't technical at all: the pricing page was doing less work than it could, and fixing the information architecture mattered more than fixing the stack.

If you run a services site and you're still hiding pricing behind a contact form, it's worth testing the alternative on a subset of traffic before assuming transparency will scare people off. For us, it filtered the leads instead of losing them.

Top comments (0)