DEV Community

аЛЕКС ЛИР
аЛЕКС ЛИР

Posted on

18 Years, 235+ Sites: What Running a Small WordPress Studio Actually Taught Me

I run a small web development studio in Ukraine. We've shipped 235+ projects over 18 years — mostly WordPress sites, landing pages, and small e-commerce stores for local businesses. No VC funding, no SaaS growth chart, no "we scaled to 10M users" story. Just a lot of repeat, unglamorous client work.

I want to share what that work actually taught me, because a lot of it cuts against what gets upvoted on dev-focused platforms.

  1. The stack doesn't matter as much as you think

I know Elementor gets side-eye from "real developers." Page builders are heavier than hand-rolled markup, they come with plugin dependencies you have to actively manage, and they're not what you'd reach for on a resume project.

But here's what they buy me on client work:

Fast turnaround. A landing page ships in 2–3 days instead of 2–3 weeks.
Client-editable handoff. Someone with zero dev background can update their own copy and images later, without filing a ticket with me.
Predictable cost. No custom component library to maintain for a client who needs five pages, total.

Custom code earns its place when a project genuinely needs it — complex business logic, third-party integrations, real scale. The mistake I see junior devs make (and one I made early on) is defaulting to the "impressive" stack regardless of whether the project needs it. Most local-business sites don't. Matching the tool to the actual requirement, before you touch a single line of config, has saved me more time than any framework migration ever has.

  1. Pricing transparency filters leads better than good code does

Most agencies in this space hide pricing behind "contact us for a custom quote." We do the opposite — published price ranges by package, with what's included and how long each takes:

Package Range What it covers
Landing page $200–400 Single page, AI-assisted base copy, standard sections
Business site $400–800 Multi-page, custom copy edits, basic SEO setup
SEO-optimized site $800–1,500 Full on-page SEO, content strategy, analytics setup
Individual scope $1,500+ Custom requirements, integrations, ongoing support

It felt risky the first time we published this — competitors could undercut us on paper alone. In practice, it does something more valuable: it filters out mismatched leads before the first call. Someone who needs a $5,000 custom build doesn't waste our time or theirs booking a consult for a $250 landing page. That's not a marketing trick, it's just fewer bad-fit conversations per week.

  1. Being upfront about AI-generated copy isn't a red flag anymore

Two or three years ago, telling a client "the base copy in this tier is AI-generated, and you'll edit it yourself" might've read as cutting corners. Now it's just accurate. Nobody realistically expects hand-crafted copywriting bundled into a $250 landing page. Naming that upfront — instead of quietly doing it and hoping nobody notices — removes friction later, when the client is reviewing drafts and wondering why the tone feels generic. Set the expectation at scoping, not at delivery.

  1. Trust signals you don't control beat the ones you do

Every site has a testimonials section. Most of them are quotes the business itself selected and typeset, which readers correctly discount. What's worked better for us is linking out to review verification on a third-party freelance platform — reviews we don't get to curate or edit. It's a small structural choice, but it changes how much weight a skeptical visitor gives the social proof.

  1. Unglamorous work still rewards getting the fundamentals right

None of the above is a technical breakthrough. But there's a pattern I keep noticing: a lot of developer discourse treats "boring" tech stacks and "unsexy" niches (small-business sites, local service companies) as not worth optimizing for. In practice, this space rewards the same fundamentals as any other kind of software work — clear scoping, honest communication about tradeoffs, fast and predictable delivery — just without the framework debates.

If you're a dev considering freelance or small-agency work on the side, my honest take: the technical bar is lower than you'd expect, and the business-judgment bar is higher. Knowing when not to reach for the impressive solution is the actual skill.

Happy to go deeper on any of this — pricing structure, when a page builder is genuinely the wrong call, or how we handle client handoff and maintenance long-term. Drop a comment.

Top comments (0)