Most bad website experiences do not start with a bad design — they start with a bad hire. The developer disappears after launch, the contract never mentioned who owns the code, or the “custom site” turns out to be a template with your logo dropped in. Here is how to avoid all three, based on what actually goes wrong.
Ask about your business before your design
A developer who opens with “what colors do you like?” is designing a brochure. A developer who opens with “what do you actually want visitors to do on this page, and what happens after they do it?” is building a system. That question order tells you almost everything about how the rest of the project will go.
Get it in writing: ownership, timeline, revisions
Before any work starts, you should have clear written answers to three things: who owns the final files and domain (it should always be you), how many rounds of revisions are included, and what the delivery date is. Verbal agreements are how projects quietly balloon from three weeks to three months.
Check what happens after launch
This is the question almost nobody asks and almost everybody regrets not asking. Plugins need updates. Forms break. A page speed score quietly degrades over a year. Ask directly: “if something breaks in month six, who fixes it, and what does that cost?” If the answer is a shrug, keep looking.
Look at live sites, not screenshots
A portfolio screenshot hides a lot of sins — slow load times, broken mobile layouts, forms that do not actually send anywhere. Ask for links to live sites and test them on your own phone before you hire anyone.
How I handle this
Every website project I take on starts with a scoped, written agreement covering ownership, timeline, and what post-launch support looks like — because I have seen what happens when that is left vague. You can see real examples of the work in my case studies, or book a free consultation to talk through your specific project first.
Frequently Asked Questions
What is a red flag when hiring a web developer?
A developer who quotes a price before asking about your goals, refuses to put ownership and deliverables in writing, or cannot show you live sites you can test on your own phone.
Should I own my website after it is built?
Yes, always. You should own the domain, hosting account, and all source files. If a developer insists on keeping the site under their own account, that is a serious red flag.
What should be in a website contract?
At minimum: scope of work, number of revision rounds, delivery timeline, who owns the final files, and what post-launch support is included and at what cost.