It’s Saturday night. The dinner you made got cold an hour ago. You’ve got a YouTube tutorial paused at the 14-minute mark and a notepad with three things crossed out and rewrote. The website is open in another tab, and it still doesn’t look right.
This is not a hypothetical.
Business owners end up here more often than you’d think — not because they want to be their own web person, but because at some point the frustration hit a temperature where something shifted. Screw it. I’m going to do it myself. And so Saturday becomes the day you learn what a plugin conflict is, or why the text on mobile looks like it belongs on a different page, or what happens when you save over something you didn’t mean to save over.
It doesn’t happen often that people admit doing this. There’s something about it that feels like confessing you don’t have things under control. But the DIY website fixes pattern is real, and what it costs is almost never calculated correctly.
The hauling company in Indianapolis — and the assistant who saw it for what it was
One of the clearer versions of this story came from a cold call, years ago, to a hauling company based out of Indianapolis.
The business owner ran it. She was sharp, capable, the kind of person who figures things out. But the website was one more thing in a very long list of things. Not her priority. Not her expertise. Just something that needed occasional attention and never got the right kind.
She had an executive assistant who absolutely crushed it. Not a partner on paper, but partner-level thinking — the kind of person who evaluates what’s coming in, figures out what the owner needs versus what she’s told herself she needs, and gets things done.
When we made that cold call, it didn’t reach the owner first. It reached the assistant. And she didn’t see an interruption — she looked at it as an opportunity to not be doing these things along with everything else she was doing. The website burden was one item in a stack she’d been watching. When someone called offering to take it off the plate entirely, she paid attention.
By the time the owner heard about it, the groundwork was already laid.
It was a big relief to her, the business owner. Not just the website — the whole idea that this was now someone else’s job. This was back when our pricing was less — one of the benefits of starting with an awesome company early on. They got a killer deal. They’ve been with us ever since.
The story isn’t about a great assistant. It’s about what the pattern looks like from the outside. Someone had to absorb the website burden. The owner was doing it herself — until someone with partner-level thinking recognized that “absorbing it yourself” and “this is being handled” are not the same thing. That’s the difference between doing it yourself and having a hands-off setup where someone else carries the weight.
What business owners try to fix — and why those fixes look easy
The things people attempt themselves are almost always the things that look simple. Hours. Maybe some text. The footer. A photo swap. A phone number that changed.
These feel approachable because they’re visible. You can see the text, so you figure you can change the text. You can see the image, so you figure you can swap the image. The logic holds for about three minutes — until the text is the wrong size on mobile, or the image distorts when the page loads, or changing the footer somehow altered the spacing on a page you didn’t touch.
If you’re trying to do a DIY website fix on a GoDaddy site, a Wix site, even a WordPress site you didn’t build — it’s not easy. You have to have some experience. And the experience isn’t just knowing where the buttons are. It’s knowing what you’re affecting when you press them.
The visible part of a website is a fraction of what exists. Everything from keyphrase density to compelling headlines to how mobile breakpoints are handled — all of it lives in the back end, out of view, being quietly affected by things you never intended to touch. How are you going to do it all unless you know?
You’re not. Most of the time you’re not even trying to. You’re just trying to update the phone number. But the site doesn’t know that.
DIY website fixes — what goes wrong and what it costs
The mobile thing is the most common consequence and the hardest to catch yourself.
If someone pulls up your site on their phone and the text is all wrong — too big, too small, off the edge of the screen, not formatted for that size — it’s embarrassing. That’s not the desktop version you were looking at when you made the change. That’s what their phone renders. And if it looks dumb, it looks dumb for them. Not for you. For the customer you were trying to impress.
You can lose business. And reputation-wise, it’s just not worth the small savings.
The calculation that happens in most business owners’ heads is: web company costs money, doing it myself costs nothing. Savings. But the real math includes things that don’t make it into that first version.
It includes your time, priced at what your time is worth. If you’re running a $75-an-hour operation, two hours on a Saturday fixing a mobile layout is $150 in lost earning potential — minimum. If the fix doesn’t work, and the first attempt usually doesn’t, you’re doubling that before Sunday.
It includes what breaks while you’re fixing. Every web platform is an interdependent system. The visible change you’re trying to make has invisible connections to other parts of the site. You successfully update your hours and might also, without knowing it, affect the CSS that controls text size on mobile, or trigger a caching behavior that means customers are seeing an outdated version for the next three days. No alarm goes off. These aren’t dramatic failures. They’re invisible ones.
And it includes the reputational exposure during the window between “I tried to fix this” and “this is fixed.” That window can be days. In that window, every person who lands on your site sees the version you left it in. The phone that didn’t ring, the form that wasn’t filled, the person who clicked away — those don’t generate error messages. They just don’t generate calls.
How it works when something needs fixing — one message
You reach out. We handle it. That’s the structure.
The details underneath matter, though, because how the request gets to us affects how well we can execute it. We go with the way the client likes to communicate — that’s the general rule. If someone’s a phone person, we’re a phone company. If someone wants to email, we prefer that anyway for anything that involves specific content, because it’s not efficient to copy and paste from text threads into a website. Email is easier to work from directly. The content comes over clean, the formatting is intact, and there’s a record of exactly what was requested.
Text is fine for short things — a quick question, a heads-up. But for anything that involves content changes, we’ll redirect toward email. Not because of a policy. Because it produces a better result. And people are very reasonable when you explain to them the reason why.
Photos are where it gets specific. If you take a photo on your phone and send it over text, that image has been compressed by your phone, then compressed again by the messaging platform. Something that started at 2000 by 1600 pixels — acceptable for a full-page image — is suddenly 800 by 600. We put that on your homepage, the banner’s going to be totally grainy and not look good. It’s going to be a bad representation of your business.
When we explain that, the response is always the same. They’ll be like, “Oh, well I’ll just email it over — I’ll send the full version.” They get it. It just has to be explained.
That’s one of the things broken about the industry at large. Things are not explained well enough to help people do things the right way — the right way that’s best for them, not just easiest for the company. When someone doesn’t know why email works better than text for content changes, they keep texting. When they understand why, they stop. Simple. It just requires someone to explain it once.
About that Saturday night YouTube tutorial
If you’ve spent a Saturday night watching tutorials on how to update WordPress plugins — or fix a mobile layout, or figure out why a button broke, or troubleshoot an error message that means nothing to you — here’s the question worth sitting with before the next one.
Why? Why are you doing that? What’s wrong with the site?
Because the answer determines whether the Saturday night is worth spending.
If you’re updating plugins on a website that’s six, seven years old — maybe it needs a refresh. Maybe it needs a new brand positioning. Maybe it was never built right in the first place, and that’s the problem. Not the plugins. Not the layout. Not the specific thing that’s visibly broken today. You just need someone to analyze it and see if it’s even worth the time and effort you’re putting forth.
There’s a real difference between a website that needs a fix and a website that needs a conversation. A fix is: the phone number changed, the photo is outdated, the hours are wrong. Those are legitimate, quick, and should be handled by whoever manages your site — not you on a Saturday.
A conversation is: the site isn’t getting calls, nobody fills out the form, you’ve been making changes but nothing’s landing. That’s a different diagnosis. There’s a lot that has to get done right for Google to see a site, but also for your customers to want to click buy or call or fill out a form. You’ve got to compel people to do these things. It can’t just be black text on a white background with no images.
That’s a site working against the business. And no amount of plugin updates is going to fix that. What fixes it is stepping back and asking whether the Saturday nights are being spent on the right problem.
Usually they’re not. And if you find yourself in a cycle where you’re managing the technical side of a website you don’t fully understand — that’s not what you signed up for, and it’s not what should be required of you.
The clients who’ve been with us longest stopped thinking about their websites a long time ago. Not because nothing ever changes. Because the path from “this needs handling” to “this is handled” is one message. No tutorials. No Saturday nights. No hoping the plugin update doesn’t break anything.
If your current web company has you Googling your way through it at 11 PM — that’s not a website problem. That’s a web company problem.
Frequently asked questions
What kinds of changes should my web company handle versus things I can do myself?
All of them. Not because you’re not capable, but because it’s faster when someone who built the site makes the change, it’s done right the first time, and it protects the site from the kind of cascading effects that DIY edits tend to cause. Even something that looks simple — a text change, a photo swap — can have downstream consequences on mobile formatting, caching, or page structure. Send the change. Let the person who knows the site handle it.
What’s the best way to send a website change request?
Email is usually best, especially for anything involving specific content — text, copy, images. It keeps things clean, avoids the compression issues that happen when photos go through text messaging, and gives us something to work directly from. For quick questions, text works fine. For content changes, email gets it done faster and better. People are very reasonable about this when someone explains why.
What if my website is old and needs more than just fixes?
That’s worth a real conversation, not a patch job. If a site was never built well — or was built correctly but has aged out structurally — updating plugins and fixing individual elements isn’t going to move the needle. We’d rather tell you that directly than take your money for fixes on a foundation that’s not worth building on. A free audit is the right first step. It tells you what you’re dealing with before anyone talks about what to do next.
How do you handle image quality when clients send photos?
We’ll tell you if an image isn’t going to work before we use it. Texted images are often compressed to the point where they can’t be used for hero banners or full-page sections — a photo that started at 2000 by 1600 pixels can arrive at 800 by 600, and that looks grainy at scale. When that happens, we ask for the original. Email it over or share from a Google Drive link. A short back-and-forth beats a photo on your site that doesn’t represent your work.