How to choose who builds your website

The four ways a website actually gets built

Somewhere in your browser right now there might be four open tabs: a do-it-yourself builder's pricing page, a freelancer's portfolio, an agency's homepage, and a template marketplace listing. That's the whole decision, laid out in tabs.

A do-it-yourself builder hands you the tools and expects you to do the building yourself, template and all. Whether that actually saves money once your own time is counted is the DIY-versus-hire decision, and it deserves more than a first glance.

A freelancer is one person handling the design, the code, and every email, alone. An agency splits that same work across a small team, with someone managing the account and others building it. What that team-size difference actually buys you matters more than which one costs less on paper.

A premium template gets you a pre-built structure that someone customizes instead of designing one from scratch. It can look every bit as sharp as a custom build. Where the two genuinely differ is worth understanding before you assume the cheaper option is also the weaker one.

None of the four is a wrong answer by default. Each fits a different mix of budget, timeline, and how hands-on you actually want to be during the build.

Matching the option to your situation, not the other way around

The right option depends on what you're building, not on what worked for a friend's business. A five-page site for a local service does not need the same team as a fifty-page catalog with online ordering behind it.

Think about three things before you pick a lane:

Whether you'll write the site's words yourself or expect the designer to affects the timeline as much as anything on this list. Who actually ends up writing that content is worth settling before the project starts, not partway through it.

If you already have a site and you're weighing whether to patch it or replace it outright, that's a different question. The redesign decision carries its own set of questions, starting with whether a full rebuild is even the right move.

Answer those three points honestly before you talk to anyone. It changes which option even makes sense to pursue first.

What vetting actually looks like before you hand over money

Before any money changes hands, you can confirm someone is who they say they are. A real business has a findable history: a web presence that predates this week, work samples that check out, and people willing to vouch for them by name.

None of that takes long to check. It takes far longer to undo hiring someone who fails that check after the deposit has already cleared and the project has stalled.

Look at how someone answers a direct question, too. A vague reply to a simple one is worth noticing early, before it becomes a pattern.

The full vetting process covers exactly what to look at and in what order, from the first message you send to the final invoice.

What belongs in writing before work starts

A conversation is not a contract. Before you pay a deposit, get the scope, the price structure, the number of revisions, and the handover terms written into one document you both sign.

What that contract actually needs to say is more specific than most people expect going in. It should also spell out who owns the finished site once it's live — the files, the domain, and the login that controls both.

If a designer resists putting any of this in writing, that reluctance is information on its own. A legitimate business has done this before. It already has language for it, ready to send.

The sales language worth being skeptical of

Some phrasing is worth slowing down for. A pitch with a firm delivery date before anyone has scoped the work is a guess dressed up as a fact. A promise of a specific spot in search results is a promise nobody can actually control once your site is live.

An offer that asks for full payment before any design work exists is asking you to trust a stranger completely, on the first date. None of that automatically means the person is dishonest.

It means the claim needs a follow-up question before you act on it, not blind acceptance because it sounded confident on a call. Ask for specifics. A real answer holds up under a second question.

The specific phrases worth doubting when you're hiring go well past the examples above, and they're worth reading before your first real conversation with anyone.

The questions that separate a real answer from a pitch

A specific answer sounds different from a rehearsed one. Ask how someone would handle a page that isn't performing, or what happens if you want a change three months after launch.

A real answer references an actual process, a tool, or a past project it happened on. A rehearsed one changes the subject back to price, or repeats a phrase that sounded good the first time you heard it.

That gap is easy to hear once you're actually listening for it. Bring the same two or three questions to every conversation. Consistency is what makes the comparison mean anything at all.

Where price fits into this decision

Price matters, but treat it as the last filter, not the first. Two designers can quote very different amounts for the same list of pages, and the gap comes down to what's actually included in each one.

How pricing models work, and what actually moves the number up or down is worth understanding before you set one quote against another. A lower number that leaves out revisions, mobile testing, or basic support isn't automatically the better deal.

It's just a smaller number with more missing from it. You often don't find out what's missing until you actually need it, well after the site is live. A specific, itemized quote is worth more than a smaller round one.

More from the blog

All posts