The IPs don’t match anything. Not the old server. Not the new server. Something else entirely different.
That’s where this story starts — not at the end, not with the punchline, but right in the middle of a migration that had just gotten very interesting. We’ll get back to it.
First, let’s talk about what really happens when you hire us.
That first call — and why it feels different
There’s a specific shift that happens on the first call after someone becomes a client. Not a prospect anymore. A client. And if you’ve just been through a web design build with us, you already know why that call feels the way it does.
The build process is collaborative in a way that’s hard to fully describe until you’ve been through it. We ask questions. You give us input. We take that input — your goals, your preferences, what you care about — and we build something from it. Something that didn’t exist before. That process unites people. It’s a very cool collaborative process that unites people, and by the time the site is live, we’re not strangers.
So that first client call? It’s like talking to a friend. Yes, there’s a monetary arrangement. We work for you, you pay us. That’s real. But beyond that, we are invested in your success. We get edits right because we care about your success. We make suggestions that are grounded in principles because we care about your success. That first call, when the site is live, is a wonderful thing.
That tone doesn’t fade. It’s the baseline — not the honeymoon phase. And it’s the best answer we can give to the question of what to expect after hiring a web designer.
Meanwhile: I’m staring at these IPs and they don’t resolve to anything I recognize. Not the old server. Not the new one we spent weeks building out. Something else. Something no one set up — or no one remembers setting up. We’ll get there.
What we need from you to get started — what to expect after hiring a web designer
The single most common fear we hear from new clients goes something like: I don’t have my stuff together enough. I don’t know what I’m going to give you.
Here’s what we’ve learned: we need almost nothing to begin.
We’ve literally built an entire website based on a color. A single color. Not a hex code, which is the exact color down to the exact shade. We’re talking light green. That was the whole brief. From that single color, we built out a full website. We did get images — thank goodness — and we put together a simple text logo, which is included at no extra charge. But in terms of direction, that was it. We got the website up in a little over two weeks.
There’s no doubt that client had the “I thought this would be harder” moment.
That’s not an unusual outcome. It happens often. You’ve been sitting on a web project for longer than you want to admit, partly because you think it requires more from you than it does. The intake process is light on purpose. We know how to work with whatever you can give us — and sometimes the clients who give us the least creative input up front produce the sites we’re most proud of, because we’re not fighting a long list of conflicting preferences. We’re building from instinct and principles.
What do we need? Access to your current site if you have one. A general sense of your services. Some photos if you have them — and if you don’t, we’ll figure that out too. That’s about it. The rest comes out in the first conversation.
This was a migration we’d planned for months. Several clients on multiple servers, all running on operating systems at end of life — meaning no more security updates. It’s like when Windows XP had to be retired. You couldn’t just update it. It had to be replaced entirely with something different. Same thing here. We had to migrate to new servers. Not update. Migrate. We set up the new servers first with an exact copy of everything from the old ones, then planned how we’d flip each client’s domain to point at the new destination. The process itself was clean. The communication was where things got interesting.
Day one: how you know what to expect and how to reach us
On the call where we onboard you, we always make an appointment for the next appointment. That’s a rule, not a preference. Before you hang up, you know exactly when you’ll hear from us next — and how.
This sounds simple, but it’s one of the things that separates working with a company that’s done this a long time versus one that hasn’t. The default behavior for most web companies is to say something like “I’ll reach out when I have an update.” Which means you’re waiting for something to happen. You don’t know when. You don’t know in what form. So you either send a check-in email or you don’t — and either way, there’s low-grade anxiety about whether you’re going to hear from anyone.
We don’t do that.
If it’s late Thursday and we’re scheduling something for the following week, instead of locking in a specific calendar slot that might not hold — because clients are extremely busy, and maybe they don’t know what Wednesday looks like yet — we’ll say something like: “Why don’t I send you a text Monday or Tuesday to see what Wednesday, Thursday, or Friday looks like for you?” That’s not evasiveness. That’s respecting that they need to do their business, we need to do ours, and a hard appointment that has to be rescheduled twice is worse than a flexible one we keep.
Anyone in the trades knows this: you don’t know when an emergency job is going to pop up. Rain hits and suddenly you’re super available because the roof job is paused. We know that. If you know your schedule, great — we lock it down. If you don’t, we work with how you work.
The broader point is this: you won’t spend a single day wondering if we forgot about you.
The first email went out professional. “Here’s what’s happening. Here’s what you need to do. Here are the steps. Or just send me your login and we’ll handle it.” Literal words from the email. We didn’t get a single response. Not one. After thirty years in customer service, I knew to build in lead time on something like this — so we had almost three weeks. Still. Not one reply.
What a typical month looks like — from your seat
Here’s the honest answer: most months, nothing happens from your perspective. That’s not a failure. That’s the goal and that’s Yeetish working in the background, always on the ready, always knowing the next steps.
The maintenance work runs in the background. WordPress core updates, plugin updates, theme updates, security monitoring — none of that requires anything from you. You never see it and you never think about it. If something needs attention, we handle it. If something breaks at 2am, we find out before you do. That’s what a maintained site looks like from the client’s seat: quiet.
We have a pest control client — he started with us about three months ago. He came to us from a previous company that had been stringing him along and still charging full price for nothing delivered. The experience of that first few months with us, compared to what he’d just gone through? He’s paying over 50% less than what he was paying the other people — who had never delivered. His website uptime is essentially 100%. And in the last thirty days, he’s locked down a couple of large commercial clients.
Now look — we’re not claiming full credit for that. He moved from a W2 job to starting his own pest control company just a year ago, and his business is already doing better than his previous salary. He’s hustling. He’s boots to the ground, getting it done. But isn’t that freaking cool? A website that works, a price that doesn’t hurt, and a platform that lets a guy who just bet on himself compete. That’s what a good month looks like from the client’s side — even if neither of us is thinking about the website at all.
Second email. Subject line: “URGENT: Your Website Will Go Down Next Wednesday.” A few people opened it. A few replied. But it was like the Sahara Desert around here. Time to start dialing. We were down to eight clients who hadn’t responded at all. I called. Left voicemails. Obviously, we’d done a ton of work leading up to this — tracking which clients had already made the switch, which domains were in-house, what was still pending. But those eight people? Who knows. They might have been sick, out of town, slammed. So we kept going. One by one, they came through, trickling down to the last wire.
What “we handle it” means in practice — not the promise, the story
Every company says “we handle it.” Most of them mean “we’ll send you a tutorial.” Here’s what it looked like in practice.
The migration had a drop-dead date. In reality, that Wednesday date had a built-in buffer — the real cutoff was Friday. We were down to two clients who hadn’t made the switch. One of them had a domain through a registrar we’d worked with plenty of times. We got them on the phone, got the login, went into the DNS to update the A record — the thing that tells the internet which server to point the domain at, like updating your address when you move from one street to another.
What causes all this to work is the domain. It looks at a certain server and then the website appears. Change the A record from the old numbers to the new ones and you’re done. Should have taken two minutes.
The IPs don’t match anything. Not the old server. Not the new server. Something else entirely different.
We dug deeper. What the hell is this? The domain was running through some sort of CDN, a security layer. We don’t remember setting it up. A long-time client — probably set up by a previous provider years ago, probably an upsell. Fine. We bypass it entirely, point it straight to our server, update the A record and everything else that needs updating. Then we wait.
Network Solutions — that’s where the domain was registered — takes about two hours to propagate a DNS change. So we wait. And while we’re waiting, we start looking around the account.
What we found was a full audit’s worth of waste. A website security scan product costing a couple hundred dollars a year. Some web hosting package. Multiple extra domain extensions — .net, .org, the whole row — all adding up to over a thousand dollars a year in charges nobody knew about. One small DNS update turned into a full account audit. By the time the propagation finished and the site was live on the new server, we’d identified years of unnecessary charges that could now be eliminated.
That’s what “we handle it” means. Not just the task we were called to do. The whole account — because we were already in there, and it involved our clients. It was kind of mind bending at times, keeping track of all this, multiple spreadsheets, multiple tabs, but it was all very, very important because it involved our clients. You don’t shortcut that.
If you want to understand what the ongoing web design relationship is supposed to look like — full engagement, not just the minimum the ticket requires — that account audit is the answer.
Now saving the best for last. One client left. Long-time client, usually super responsive. We sent the first email back when this whole thing started. Nothing. Sent the urgent one. Nothing. Called — voicemail, and not even a way to leave a message. Super weird. I’m thinking: are they out of business? Whatever. Sent a final notice. Called again and again. Four emails. Five calls. I finally said out loud, “I’m done. I’m not going to bug them anymore — I don’t want to be a pest. I’m trying to help them.” And then we ran out of road. Or so I thought.
What changes between month one and month six
When someone first comes on as a client, even after a successful build, there’s still hesitation. That’s normal. When they first pay, they’re still scared they made a mistake — because you don’t know what you don’t know. They made a decision. They signed up. But proof takes time.
What builds trust isn’t a presentation or a portfolio. It’s follow-through. At Yeet Websites, we follow through. Simple as that. Every time we say we’ll do something, we do it. Every time there’s an issue, we handle it. Over months, that accumulates into something the client can feel: the absence of disappointment.
John Gottman, the psychologist who spent over four decades studying what makes relationships succeed or fail, described this dynamic in an article for UC Berkeley’s Greater Good Science Center. He was writing about interpersonal relationships — but it’s exactly how we operate:
“What I’ve found through research is that trust is built in very small moments, which I call ‘sliding door’ moments. In any interaction, there is a possibility of connecting with your partner or turning away from your partner.”
— John Gottman, Ph.D., Professor Emeritus of Psychology, University of Washington. Source: greatergood.berkeley.edu
At month one, there’s hesitation. By month six, there’s so much trust that clients can basically tell us everything. Not just the website stuff. The business. The challenges they’re running into. What competitors are doing. What they want to change about their model. That’s not information they shared in month one — they were still deciding whether we were trustworthy enough to be looped in.
What that depth of trust makes possible depends on what kind of client they are. If they’re a website-only client, we know everything related to the site — the seasonal patterns, the pages that get traffic, the calls that come through. If they’re an SEO client, we’re digging a lot deeper — figuring out exactly what makes them different, what makes them tick. That’s how we make the articles unique when we go and build links for them. You can’t write a good piece about someone’s business from a questionnaire. You need the relationship.
Month six is not month one. It’s quieter. More efficient. Less explaining required. The clients who stay long-term — and most of them do — will tell you that the relationship feels easier over time, not harder. That’s how it should work. It’s also how a website built to grow with a business is supposed to function — not a thing you launch and forget, but a platform that compounds.
Then the hosting company came through with a 72-hour extension. The Friday deadline just became Monday. One more shot. I called one more time on a Friday afternoon. He freaking answered. It was so great. “Hey, we’re trying to reach you, bro. Your site’s going to go down if we don’t update your domain.” He goes: “Oh yeah, I saw that. Here’s my login.” Fixed in two minutes. GoDaddy propagated instantly.
What it looks like when a client reaches out mid-month
Someone texts or calls or emails on a random Tuesday. They need something updated. What happens next depends on where things are, but the default is: if we’re in between things, we just do it. Done. Fast. No ticket, no queue.
There’s a step most clients don’t see, and it matters. Something called cache — your computer has a memory. You can request a change and we can make it immediately, but if your browser is showing you the old cached version, it’ll look like nothing happened. That’s frustrating. It’s not the change that failed — it’s the display.
So the process is: make the change, clear the cache on the website itself, clear the cache on the server, and then send you a link. That link has something at the end of it — a forward slash, a question mark, and a no-cache parameter — which forces your browser to go directly to what’s live on the server right now. Even if your computer still has the old memory stored somewhere, clicking that link forces a full refresh. You see exactly what’s there.
That’s the whole process. We do it so that clients aren’t disappointed when we do things quickly. When we say “done,” we mean you can see it right now with your own eyes. Not “done pending your next browser refresh.” Done.
The principle is simple: when a client reaches out, the goal is a complete resolution with zero follow-up needed. No back-and-forth. No “did it go through?” No checking tomorrow to see if it looks right. Done means done.
I promise you — no one. No company. No one is going to care as much. Is anyone else going to do all of that for one client? That guy’s site was going to go down. It would have been down for weeks. And he’d have called someone eventually and said, “What the hell, man? Why didn’t you let me know?” Four emails. Five phone calls. A 72-hour extension from the hosting company. For one client. The result? Every client migrated. Zero downtime. Nobody called us freaking out about their site being down. That’s the only metric that matters.
The no-contract thing — and what it doesn’t do to how we work
People sometimes expect us to say something meaningful about how the no-contract model changes our accountability. Like we feel pressure because you could leave anytime.
It doesn’t do anything to how we show up every month. Knowing they can walk away anytime doesn’t create urgency that wasn’t already there. The urgency was always there — because doing good work is the point, not the mechanism for keeping someone trapped.
If someone wants to leave, we will be the first ones to pack their bags. Time to go. That’s how we live our entire lives. There’s no guilt trip. No retention call. No “let me see what I can do on price.” You want to leave, we help you leave cleanly.
But the reasoning goes further than that. If you’re doing work based on whether or not someone is locked in — if the contract is part of why you’re showing up — then the entire premise is wrong. The premise should be: I’m going to do my best no matter what, no matter the circumstance. Not: I can lock someone in for twelve months and coast because they can’t leave. That’s a terrible business model and it’s a terrible way to treat people.
Not how we do things. No way, no how.
What you’ll notice — if you stay long enough to notice it — is that month six looks like month one. Same person. Same response time. Same attention. The relationship grows, but the standard doesn’t slip. That’s not because we’re terrified you’ll leave. It’s because it would never occur to us to show up differently.
Ready to see what this looks like from your end? Take a look at what we build, or there’s only one way to really find out.
Frequently asked questions about what to expect after hiring a web designer
What do I need to provide to get started?
Almost nothing. If you have a current website, access to that helps. If you have service descriptions or photos, those are useful. But we’ve built full sites from a color preference and a conversation — so if you feel like you don’t have your act together enough to start, you probably have more than enough. We’ll ask the questions that matter on the first call and go from there.
How will I know what’s happening with my site month to month?
Most months, nothing visibly happens — which means everything is working. The maintenance runs in the background. If something needs your input or decision, you’ll hear from us directly. We don’t send monthly reports full of metrics you didn’t ask for. We communicate when it matters and handle the rest ourselves. When they first pay, new clients are still a little unsure whether that’s true. By month three, they usually stop wondering.
What if I need something changed on a Tuesday afternoon?
Text, call, or email — whichever you prefer. If we’re between things, we do it right then. If we’re in the middle of something, it gets done within hours. We send you a cache-clearing link so you can verify the change is live the moment you click it. The goal is a complete resolution with zero follow-up needed. Not “we’ll get to that” — done.
Is there any situation where the site could go down and I wouldn’t know about it?
We watch for that. Monitoring is part of the maintenance — we’re looking for issues before clients see them. That said, the best demonstration of what happens when something goes sideways isn’t a policy statement. It’s what we’ve done when the situation was out of our hands. See above.
Does the no-contract model mean you’ll disappear once the build is done?
The opposite. No contracts mean every month is a performance review. We can’t coast — there’s no lock-in protecting us from the consequences of showing up differently than we did when you signed on. Clients who’ve been with us since early on describe the experience the same way at year three as they did at month three. Same person. Same speed. That’s not luck. That’s a decision about how to run a business.
How long until the relationship feels comfortable?
Most clients say month three is when the uncertainty fully fades. By month six, the dynamic is different — more efficient, less explaining required, and clients are usually sharing things about their business they weren’t ready to share at the start. We follow through. That’s really it. Follow-through, repeated consistently, becomes trust. And trust makes everything easier for both sides.