The Question Most Checklists Skip

Most guides on hiring a web designer focus on price and portfolio, and those matter, but they skip the question that predicts trouble more reliably than either one. Who, specifically, is responsible for making sure every piece of your site actually works together? Ask about price and you'll get a number. Ask about the portfolio and you'll get a slideshow. Ask who owns the whole picture and you'll find out fast whether you're hiring a team or a hand-off.

If you've already decided you want something built properly rather than assembled from a template, DIY Website Builders vs. a Professionally Designed Site: What Actually Changes covers that decision. This post picks up right after it, once you're ready to vet whoever builds it.

What a Good Technical Eye Actually Catches

A good technical hire catches the problem that falls between two people's areas of responsibility, not just the one inside their own. Years ago, leading a mobile and UI platform team, I watched two other teams each build their own source of truth for the same dataset, one meant to extend the other, but living on separate microservices with separate databases. Every request had to reconcile which version was current, live, while a real person waited on the other end.

That reconciliation alone was adding five to ten seconds of delay on a good connection, even with barely any data in either table. Nobody on either team had done anything wrong in isolation, the problem only existed in the gap between their two pieces, which is exactly the kind of thing an agency that hands your project between disconnected specialists will miss. I ended up advising that both systems get folded into a third one built to be the actual source of truth for both use cases, and the fix held because someone was looking at the whole system, not just their assigned slice of it.

That's the real test for a web designer or developer, not how skilled they are at their individual piece, but whether anyone on the team is actually accountable for how the pieces fit together.

What You Should Own When the Project Ends

You should own your domain, full account access, and the copyright to your website itself, no matter who builds it or what they build it on. Make sure the domain is registered in your name, under your own account, with your own email as the contact. If a designer registers it under their account instead, they can technically let it lapse, transfer it, or hold it over you later, and the same goes for hosting and your CMS admin login. If you've never been handed a username and password for any of the three, that's worth raising before you sign anything else.

Owning the copyright to your website is different from owning the platform code it runs on, and the two get confused constantly. Your content and your design are yours, and a legitimate agency will confirm that plainly rather than dodge the question. The underlying software running the site is a separate matter, especially when it's built on a company's own platform rather than written from scratch, and plenty of legitimate businesses work exactly that way, the same as building on Wix, Squarespace, or WordPress core rather than bespoke code. That split isn't a red flag by itself. What matters is that someone tells you clearly which part is which before you sign, instead of letting you assume you own everything, or nothing.

The Red Flags Worth Taking Seriously

The clearest warning sign is a mismatch between who you met and who actually does the work. If the senior person in your first meeting isn't the same person building your site, and "the team will be assigned" after you sign, you're buying a different service than the one you were pitched. A handful of direct questions tend to surface this fast. Who specifically will be working on this day to day, and is that the same person I'm talking to now. What determines whether this project costs one number instead of a much higher one. What happens to my files and access if we part ways before the project is done. Who owns the domain, the hosting account, and the copyright to my website once I've paid in full.

Vague answers to any of those matter more than the answers themselves. An agency that can't explain its own process clearly probably can't explain yours to a customer either, and that gap tends to surface in exactly the place you can't see it until the site's been live for months. If you'd rather have someone walk through this with you than vet an unfamiliar agency alone, that's what a no-pressure consultation is for.

Your Next Step

Your next step is simple. Ask those four questions before you sign anything, and pay closer attention to how directly they're answered than to how impressive the answer sounds. Reach out when you're ready, we would rather earn the job by answering these questions well than by dodging them.