There’s a version of this that sounds like a sales line: you focus on your business, we handle the website. Clean. Confident. Easy to say in a pitch.
And there’s a version where a client is in their second year with us, getting a reply within the hour, watching their site get updated and maintained and checked on schedule — and that sentence isn’t a sales line anymore. It’s just a description of what’s been happening all along.
This post is about the second version. We aren’t the kind of company where you worry about managing your web designer, we’re the kind of company where the promise is delivered and it’s real.
The foundation no one sees
When we take on a new client, there’s a layer of work that happens that the client will never see and never think about. The back-end setup. The code structure. What the founder calls “the code gobbledygoop.” All the stuff that’s not the colors or the fonts or the layout — the invisible architecture underneath all of that.
And here’s the thing most people don’t know: a website can work when that foundation isn’t right. It can load, it can display your logo, it can show your phone number. It functions. But functioning and right are different things.
The question we ask is: if you can do it right, why wouldn’t you?
Think about framing a wall in a house. You can frame it dead plumb — perfectly vertical, perfectly aligned, square in all directions. Or you can frame it off by a degree or two. It won’t look wrong. It’ll hold up the ceiling just fine for years. Nobody’s going to notice. But over a very long time, that degree or two starts to accumulate. You get the beginning of a leaning tower of pizza. The deviation was there from day one. It just takes years to show up.
Web builds work the same way. The foundation is the SEO structure — the heading hierarchy, the schema, the way pages reference each other, the speed setup, the code itself. Every one of those elements is either right or it’s off by a degree or two. You don’t see the leaning tower in year one. You see it in year three when the site starts performing exactly like it was always going to perform with a compromised foundation underneath it.
We build it right because we’re going to be the ones managing this site. There’s no build team and support team — one person builds it and one person maintains it, so Yeetish, so absolutely pure, and those are the same person. When the foundation is wrong, we’re the ones who live with it. So we don’t frame the wall off by a degree. Not because it matters on day one. Because it matters in year three.
Websites die without maintenance — and most do
The build is one part of the promise. The ongoing maintenance is the other and if you’re not a web designer why would you want to be googling diy website fixes when someone can do it for you?.
Think about a car. If you don’t change your oil — it depends on what kind of car it is, but it’s going to die. Maybe not this week. Maybe not this year. But the absence of maintenance is a debt you’re accumulating, and eventually the car collects. Same exact thing with a website. If you don’t update the code, do a visual check, make sure things are working right, it will die. Maybe slowly, maybe suddenly, but it will happen.
The plugins fall behind. A theme update breaks something. A widget stops loading. The contact form stops sending. The SSL certificate lapses. Any one of those things happening on a Tuesday morning when you’re supposed to be running your business is a problem you shouldn’t have to deal with — and most clients don’t deal with them because they’re handled before most clients even know there was something to handle.
This is a piece of the promise that doesn’t come up much in sales conversations because it’s not exciting. “We keep your website from dying” isn’t a headline anyone puts on their home page. But it’s real. It’s unglamorous and essential, and it’s the difference between a site that compounds in value over time and one that slowly deteriorates while the client assumes everything’s fine.
A third of our clients came here over simple edits
When clients come to us from other companies, there’s usually a story. About a third of the time, the story isn’t complicated. It’s some version of: I needed a simple edit done and I couldn’t get it done.
Update my hours. Change a phone number. Swap a photo. The unglamorous small stuff that keeps a business’s web presence accurate and functional.
What happened, usually, is it just got ignored and their previous company wasn’t a full service web design company. Or it got lost in the pipeline at the big web company. The request went in, got acknowledged somewhere, and then nothing. Days pass, then a week, and the business owner sends a follow-up, maybe gets a response, and maybe eventually the edit gets done — or it doesn’t. And then eventually they stop asking. Or they switch.
The clients who come to us from that experience aren’t usually blown away when they send us a request and it gets handled the same day. There’s no moment of amazement. It’s more like relief. Like breathing normally again after months of shallow breaths.
That’s the tell. When good customer service feels like breathing — obvious, expected, unremarkable — that’s when you know the standard has been met. It’s only remarkable if you’re in an environment where it doesn’t happen.
Frederick Reichheld, the Bain & Company researcher who created the Net Promoter Score — the most widely used measure of customer loyalty in the world — quantified this gap in a landmark study on what companies believe they deliver versus what their customers experience:
“Most companies assume they’re consistently giving customers what they want. Usually, they’re kidding themselves. When we recently surveyed 362 firms, we found that 80% believed they delivered a ‘superior experience’ to their customers. But when we then asked customers about their own perceptions, we heard a very different story. They said that only 8% of companies were really delivering.”
— Frederick F. Reichheld, Bain Fellow and creator of the Net Promoter Score. Source: bain.com
Twenty years ago, great customer service wasn’t a differentiator. It was the floor. The baseline everyone was supposed to be operating at. The companies that were truly exceptional operated above that floor — and the floor was already high. What’s happened since is the floor has dropped so far that the companies doing what used to be baseline are now the top 1% of everyone doing it. That’s great for us. It’s not great for the trajectory of business — but here we are. We stay on the floor anyway.
What this means in practice is that how we communicate is as much a part of the promise as the technical work. The edit that gets done same-day and the message that gets answered in an hour — that’s the same promise expressed two different ways.
Hands-off website design — when something is outside our control
Here’s the version of the promise that most companies don’t tell you about: there are moments when we can’t fix it. Not because we won’t, not because we’re not trying — but because the resolution is in someone else’s hands.
We’ve had a client waiting on a working payment button for over a year. Over a year. And it is still not resolved. The payment processor company cannot seem to get it done — three legitimate chances at this point, three different coders or timelines or whatever the internal story is, and none of them have produced a working button.
The amount of websites we’ve built since this payment thing started is ridiculous. It is not an exaggeration to say that our output since this saga began would look insane next to the single unresolved task we’ve been waiting on from the processor.
It’s a saga that doesn’t seem to want to die. We want it to die. The owner wants it to die. At this point the likely resolution is that the owner cuts ties with the processor entirely — and the processor will probably scramble and say wait, wait, we’ll get it done. But they’ve had three shots.
Here’s what this story is really about: what do you do when the resolution is out of your hands? What does the promise look like in those moments?
You keep the communication open. You light fires where you can. You do updates where updates are possible. And then there’s the other thing — the part that doesn’t have a task attached to it. You become the shoulder the client can cry on. The person who can listen to the rage and not make it about you at all.
That’s a specific thing to ask of yourself. When a client is frustrated about a problem you didn’t cause and can’t fix on your own timeline, the instinct is to defend your output — to remind them of the websites you’ve built since this started, to create a little distance between yourself and the unresolved thing, to make sure they know this isn’t your failure. That instinct is understandable. It’s also exactly wrong. The moment you redirect the conversation toward what you’ve accomplished, the client stops feeling heard. They start feeling managed. And a client who feels managed in a frustrating moment has just learned something about who you are when things are hard.
What the client needs in those conversations isn’t resolution — they know resolution isn’t coming today. What they need is to feel like the person they hired is still fully present, still fighting even when the fight is stalled, still on their side without qualification. That’s not a performance. You can’t fake it for a year. It’s just the actual posture: this is your problem because it’s their problem, regardless of where the failure originated.
We can’t sign into the payment processor’s backend and build the button ourselves. But we can be present, responsive, honest, and relentlessly on their side. That’s what the promise looks like when the path to resolution runs through someone else’s incompetence. It also says something about how web company communication has to work — not just when things are going smoothly, but when they’re not.
The client who wants to know how it works
In the beginning of most builds, there’s a period where the client wants to be involved. Questions come in and we love it, the questions are what web designers need from clients to have a great website build. Questions like: What about this? What about that? It’s normal. It passes, usually, when they realize they don’t have to manage us — we’ve got it, things are moving.
What’s easy to miss is that wanting to be involved in the beginning doesn’t always mean what it looks like. There was a limo driver out of Connecticut who, early in our relationship with him, was really into it. Wanted to be in on every piece. What I noticed as the build went on was that it wasn’t about control. It wasn’t about not trusting us. He just wanted to understand how the process worked.
He’s probably the kind of person who takes apart electronics on the weekend to see if he can put them back together. But he doesn’t need to know how a website works for us to do a great job.
We always put value judgments on these situations. We say “control freak” or “Type A” and we’ve already decided what we’re dealing with. But maybe that person is just curious. Maybe they like to understand things. Maybe the way they respect a process is by learning how it works first, and then stepping back once they feel the foundation under them.
It’s not always that someone’s a Type A who just wants to control you. And reading that correctly matters — because misreading it creates friction the client doesn’t need. A curious client who gets treated like a control problem ends up in an adversarial dynamic before the build is even finished. Getting the read right, and responding to what’s there instead of what you assumed was there, is part of how the build goes smoothly. We’ve got this includes knowing what kind of presence the client needs from us at each stage. That’s not a small thing.
If you’ve been wondering whether you should be managing your web designer — the answer is no. But understanding why takes some context.
We take liberties — and we’re transparent about it
Content is where the line gets interesting. There’s a version of “we handle everything” that would mean we write every word, make every decision, and hand the client a finished website with no input requested. We can’t do that well. Nobody can.
Here’s what we do: we take liberties. We write copy based on what we know about the industry, the region, the kind of business. And then — every single time — we’re upfront about it in the review meeting.
The framing is always the same: I took some liberties. I’ve got a master’s in English and creative writing, but big deal — I don’t know your business. You know your business. So here’s what I put on the page. I wanted actual words there rather than this Latin that looks dumb on a draft — the filler text that makes everything feel like a wireframe. So there are real words here, some of them might be wrong for your situation, and if they are, you tell me what’s right and I’ll change it.
Then we go through it together. If there’s a long list of content changes, there are options: wait until the site’s live and work through changes in real life — we turn those around same day, so the site isn’t live with wrong content for long. Or do screenshots and go item by item. We give them the choice for how they want to handle it, because some people are visual and some people need to see the actual site.
The point is: the client’s knowledge of their own business is irreplaceable. We can approximate it. We can write around it. We can’t fake it. So the line is: we do everything that doesn’t require being inside the business, and we make it as easy as possible for the client to contribute the things only they can contribute. That’s what full service web design looks like when it’s defined clearly.
Give it back to the client mode — and why we don’t operate that way
There’s a default at most web companies when something unfamiliar comes up. If it’s a weird file, they ask for a jpeg or a PNG. If it’s an unusual logo format, the ticket gets returned: please resend in standard format. If it’s something they don’t recognize, it goes back to the client with a note saying they need to get the right file.
The client, who didn’t know the difference between any of those file types in the first place, now has to figure it out — find an old designer, ask someone, Google what a .ai file even is. They get pulled into a task that has nothing to do with their actual business.
We don’t do that. We don’t hand it back. We pride ourselves on delivering white glove web design services at a price that doesn’t rip you off.
If there’s a weird logo file, there are online tools that convert it. Free. Fast. If it’s a complete hassle, you open it in a viewer, screenshot it, crop it down — and that’s the logo. It’s not transparent so you’d use it on a dark background, but if it doesn’t need to be transparent, it’s fine. Worst case, twenty seconds. Client doesn’t hear about it.
There are so many solutions to fix a problem, and everyone’s stuck in give it back to the client mode. We don’t handle it that way. We don’t do that.
Individually, these moments don’t feel like much. But the accumulation of them is what the promise feels like from the client’s side. They ask for a thing. It gets done. They never hear about the obstacle that stood between the request and the result. That’s the experience of working with a company that handles it — not one that handles it as long as everything is frictionless.
If you’ve been dealing with a company that returns everything complicated to your inbox, you already know what that experience feels like. Here’s what working with a company that doesn’t looks like from the start.
Frequently Asked Questions
What does hands-off website design mean day to day?
It means you don’t think about your website. Maintenance happens. Updates go in. Visual checks get done. If something needs attention, we handle it before it becomes a problem. If you have a request — update my hours, swap a photo, change some copy — it gets handled the same day. You’re running your business. The website is running in the background. Those two things don’t intersect unless you want them to.
What if something goes wrong with my website and it’s not your fault?
There are situations where the resolution lives in someone else’s hands — a hosting provider, a third-party payment processor, a platform doing a forced update. When that happens, we stay on it and keep you updated. We light fires where we can and we absorb your frustration when the timeline isn’t in our control. We don’t disappear, and we don’t pretend the problem isn’t ours just because it didn’t originate with us.
Do I need to be involved in my website build at all?
Yes — for the things only you can provide. Your story, your business, your approvals. We take liberties on content and build from what we know, then walk you through what we wrote and change anything that doesn’t match how you’d describe your own business. The goal is to make your participation as focused and efficient as possible. You’re not project managing. You’re reviewing.
Why do so many businesses end up managing their own web designer?
Because a lot of web companies are set up to build and hand off — not to maintain a relationship. The sales team locks you in, the build team launches the site, and then you’re in the maintenance void where nothing gets done unless you push for it. If you’re sending follow-up emails to get basic tasks done, you didn’t hire a partner. You hired a vendor who already moved on to the next client. That’s not how it should work.
How do you handle content for clients who don’t have any?
We write it. We research your industry, your local market, your competitors, your customer search language — and we build content from the ground up. You review it and tell us what’s wrong. That’s your job in this arrangement. Ours is to produce something worth reviewing in the first place, so the conversation is about refinement rather than starting from scratch.