The Tepid Toys Web Developers Hand You (And the Bliss You Didn’t Know You Were Missing)

I’ve been building websites in Charlotte since 1998. Long enough to have shipped sites on platforms that no longer exist. Long enough to have watched at least four “this changes everything” technologies show up as the future and leave as a punchline. And in twenty-eight years, I’ve learned one thing almost nobody in this industry will say out loud.

The tool barely matters.

Ask ten web developers what they build on, and you’ll get ten sermons. One swears by a custom React front end. One won’t touch anything but Shopify. One’s got a page builder they bought in 2019 and have been defending ever since, the way people defend a bad tattoo. They’re all convinced their toy is the one true toy.

I used to be in that room. I’m not anymore. Because I’ve built fast, durable, genuinely pleasant websites on almost every platform you can name. And I’ve cleaned up slow, brittle nightmares built on those exact same platforms. The logo on your dashboard is a starting point, not a verdict. What decides whether you love your site or quietly resent it is not the software. It’s whether anyone thought about you while they were building it.

Most of the time, nobody did. I’ve spent a good chunk of my career being the guy who finds out.

The tepid toy isn’t the tool. It’s the handoff.

Let me describe a scene I’ve watched play out for two decades. Not because I do it. Because I keep getting hired to undo it.

The site goes live. Everyone claps. The developer sends a login and a PDF nobody will ever open. Then they’re gone, off to the next project, and the client is sitting there holding a machine they don’t understand and are a little afraid to touch.

So the client does the rational thing. Nothing. The hours page goes stale. The team photo still shows three people who left last spring. The blog stops dead at the launch announcement, frozen in time like a museum exhibit called “The Day We Had Energy.” And every time they actually need a change, they go back to the developer, swipe the card, and wait three days for something that should’ve taken ninety seconds.

That’s the tepid toy. It was never the software. It’s the relationship. A website you can’t run yourself isn’t an asset. It’s a subscription to somebody else’s calendar.

I’ve sat across from too many business owners who’d just accepted that. They thought it was normal. The dread, the invoices, the waiting. They figured that’s just how websites are. It made me a little angry, honestly, because I knew the other version existed. I’d been building it for years.

Build to last, or build to placate

After this long, I can spot the difference on day one. The client can’t, because both versions look great at launch. That’s the trap.

The first kind is built to placate the moment. It looks sharp in the proposal mockup. It photographs well for the developer’s portfolio. It checks every box on the kickoff call. And whether anyone admits it or not, it’s built to keep the client dependent. The structure’s clever in ways only the developer understands. The content got poured in once, as an event, not as a system. It’s a stage set. Gorgeous from the front row. Plywood and duct tape behind the curtain.

The second kind is built to last. I build with the assumption that you’ll outlive your relationship with me. That you’ll need to run this thing for years, probably after I’m long out of the picture. So the back end gets organized around your content, not my mental model. The stuff you’ll change constantly is easy to find and hard to break. The stuff you should never touch is tucked away where you can’t accidentally light it on fire. Adding a service page, a staff bio, a portfolio piece doesn’t need me. It needs you, five minutes, and zero courage.

One of those approaches gets a developer a nice screenshot. The other gets you a website you still respect in year four. I’ve made my whole career on the second one, and I’ll tell you plainly, it’s the harder one to sell, because the value doesn’t show up until later. But it’s the only one I can stand behind after twenty-eight years of watching the first one rot. If you want to see what that looks like in practice, it’s most of the web design work we do in Charlotte.

It’s not the tool. It’s how you implement it.

Here’s where I part ways with the platform zealots for good.

I don’t have a sacred toy. Some clients are best served by a flexible front-end builder where they drag, drop, and watch changes happen live as they type. Others are far happier with a stripped-down custom admin where every field is labeled in plain English and there’s exactly one right way to do everything. Both are correct. The right call depends entirely on who’s going to be sitting in that chair after I leave.

I learned this the slow way, and it lines up with what decades of usability research from the Nielsen Norman Group keep proving: people don’t want power, they want to not feel stupid. A busy nonprofit director who updates the site between meetings does not want infinite flexibility. She wants three obvious boxes that say “Event Title,” “Event Date,” and “Event Description,” and a save button that never lies to her. Hand her a wide-open page builder and you’ve handed her anxiety. Meanwhile a marketing team that publishes every week wants the exact opposite. They want room to build and rearrange and experiment without calling me. Give them the locked-down version and you’ve put them in a cage.

Most agencies pick one and force every client into it. Not because it’s right. Because building it once is cheaper than building it right. I get the math. I just refuse to run my shop that way. I build it for the person. That’s the whole trick, and there’s no secret sauce in it. It’s just the boring discipline of asking who actually uses this thing, and then customizing the tool until it fits their hands instead of mine. Whether that’s a custom WordPress build or something else, our Charlotte WordPress work starts from that same question.

A page builder set up thoughtfully is a joy. The same page builder dumped on a client with the defaults still showing is a trap. Same tool. Completely different life. The difference is the labor almost everybody skips. I don’t skip it. That’s most of what you’re paying me for, even though it’s the part you can’t see in the mockup.

Twenty-eight years is a long time to be wrong in public

I want to be honest about where this conviction comes from, because it didn’t arrive in a flash. It came from being around long enough to live with my own decisions. You can read the longer version of that story on our about page, but the short one is this.

I’ve maintained the same client’s site across three redesigns and two decades. When you do that, you stop being impr

essed by clever. Clever breaks. Clever needs its inventor in the room, and its inventor took another job in 2021. The sites that survive are the boring, well-organized ones a normal human can run without a manual. Longevity isn’t a feature you bolt on at the end. It’s a habit you build into the foundation, and the only way to learn it is to stick around long enough to eat your own cooking.

I’ve eaten a lot of my own cooking. Some of it I’d do differently now. That’s the point. Most of the shops competing with me in this city are younger than my oldest client relationships. I don’t say that to brag. I say it because that gap is exactly the thing that taught me what I’m telling you. You can’t shortcut it. You either watched websites age or you didn’t.

The story

I’ve built for this city, my home city of NYC, and with great honor, for clients globally.  The whole time, and Charlotte doesn’t let you hide behind a pretty site that doesn’t work. This is a referral town. A reputation town. A South End boutique, a Ballantyne law office, a contractor out of NoDa, a nonprofit near Uptown. These businesses live or die on whether the right person in the right neighborhood finds them and trusts them in the same afternoon.

A website you can’t update kills that quietly. The new location never gets added. The award goes unmentioned. The service you just launched stays invisible because updating the site felt like too much hassle. And meanwhile the competitor down the street, with a site that honestly looks worse than yours but that they can actually update, looks more alive. I’ve watched Freshness beat Poland more times than I can count. It’s not close.

Over the years we’ve built and maintained sites for Charlotte organizations including Roof Above, Camp North End, Dilworth Church, Touchstone Family Law, and McFarland Construction. Different sizes, different needs, different people sitting in the editor’s chair. There’s no template connecting them. What connects them is that each one got built so the people who own it can actually run it. A church volunteer and a construction company’s office manager do not need the same tool. They need the same outcome. Control.

Content that performs instead of just sitting there

Here’s something twenty-eight years taught me that I wish I’d understood at year two. Your website is not a brochure you print once. It’s where your best work is supposed to do something. And most sites fumble this badly. The portfolio’s buried. The testimonials get dumped into one gray block nobody reads. The case study that should be closing deals is a PDF link that opens in a new tab and dies there.

Showing off your work well is half design, half plumbing. The design half is obvious. Your strongest proof should be the easiest thing on the site to find, framed so a stranger understands why it matters in about four seconds. The plumbing half is the one people miss, and it’s the half I care about most. If adding a case study is painful, you won’t add it. If publishing a project needs a developer, your portfolio’s going to be a year out of date forever. So the content system has to be built for frequent, painless updates, or the design doesn’t matter at all. A gorgeous showcase you never touch is just a better-looking version of stale. You can see how we handle that on our case studies, which exist precisely because the work should be easy to add and easy to find.

The build I’m proud of connects the two. Easy on the back end, strong on the front end, so your newest win lands on the site the same week it happens instead of next quarter when somebody finally opens a ticket. That’s what I mean when I say I build sites that bridge form and function. The pretty part and the working part aren’t two decisions. They’re the same decision, made twice.

What the bliss actually feels like

Strip the philosophy out and here’s the plain version, the thing I want every client to feel.

You stop thinking about your website as a problem and start treating it as a tool you own. You add a team member without an invoice. You announce the new office the day you sign the lease. You fix your holiday hours before the holiday, not three days into it. You publish the case study while the client’s still happy enough to be quoted.

None of that is glamorous. It’s the unglamorous daily reality of a website that works for you instead of the other way around. And it’s the exact thing you can’t picture until you have it, because the alternative, the friction and the waiting and the small humiliations of asking permission to edit your own site, feels completely normal right up until it stops.

That’s the bliss you didn’t know you were missing. It was never a prettier homepage. It’s the quiet confidence of being in charge of your own thing. I’ve handed that feeling to enough people over the years to know it’s the part they remember.

So is your website a tool, or a hostage situation?

Try this. When you need a change to your site, what’s your honest first reaction? If it’s “give me five minutes,” good. Somebody built you something that respects you. If it’s a flicker of dread, a mental note to email the developer, a sigh about what it’ll cost, then you’re renting access to your own business. And I’ll tell you straight, no platform on earth fixes that. Only a better build does.

There’s a reason the platform debate stays so loud, by the way, and I figured this out about ten years in. It’s a useful distraction. As long as everyone’s arguing over WordPress versus Webflow versus custom, nobody has to talk about the real variable: effort. Picking a platform is a decision you make once. Implementing it well for a specific human is work you do every single time. The first is cheap to argue about. The second is expensive to actually do. So the industry argues, loudly, about the cheap thing. I stopped joining that argument a long time ago.

Want a real test of whoever built your current site? Pick the most routine update you can think of. New phone number. New team photo. One line in your hours. Now try to do it yourself, right now, without calling anyone. How long it takes, and how many times you flinch, is your real review. It’s more honest than any award badge in your footer.