Agency, freelancer or in-house: who should build your site

Three ways to get a website built. What you are really buying in each, how to vet them, and the red flags we get called in to rescue.

Nitesh PadghanNitesh PadghanFounder, Storifex Media
7 min read
On this page (13)
  1. 01The three options
  2. 02What each one really costs
  3. 03When a freelancer is the right call
  4. 04When an agency makes sense
  5. 05When in-house is right
  6. 06How to vet whoever you pick
  7. 07Red flags
  8. 08Who owns what at the end
  9. 09The hybrid that often works best
  10. 10The costs nobody quotes
  11. 11How to compare quotes properly
  12. 12How long each one takes
  13. 13Where we sit

You need a website built. There are three ways to do it, and they are genuinely different jobs with different failure modes.

This is about picking the right one. If you want the money in detail, that is a separate piece: what a custom website actually costs.

Here is how to work out which of the three fits.

The three options

A freelancer. One person, sometimes two working loosely together. You deal with them directly.

An agency. A team with designers, developers and someone running the project. You deal with the agency.

In-house. You hire or already employ the people. The site becomes another thing your staff own.

Each is the right answer for somebody. None of them is the right answer for everybody.

What each one really costs

Rates vary a lot by country and by experience, so treat these as shapes rather than quotes.

Freelancer Agency In-house
Typical build 800 to 6,000 4,000 to 50,000 Salary, ongoing
Time to start Days One to four weeks Months to hire
Design and build Sometimes one person Separate specialists Depends who you hire
If they are ill Everything stops Someone covers Everything stops
After launch Depends on their diary Contracted Always available
Knows your business Learns it Learns it Lives in it

The in-house column is the one people misread. A mid level developer is a salary plus tools plus management time, every year, forever. That only makes sense if you need a site changed constantly, which most service businesses do not.

When a freelancer is the right call

Pick a freelancer when the job is well defined and not very large, when your budget is genuinely tight, and when you can describe what you want clearly.

Good freelancers are often better value than agencies for straightforward work. You are not paying for project management you do not need.

The risks are real though, and worth naming.

One person has one calendar. If they take a bigger project, you wait. If they are ill, you wait. If they change career, you may be left with a site nobody else understands.

Ask before you sign: what happens if you are unavailable, who else could pick this up, and what do I get if you stop working on it.

When an agency makes sense

Pick an agency when the site connects to other systems, when several kinds of work are needed at once, or when a missed date costs you money.

The thing you are paying extra for is not talent. Plenty of freelancers are excellent. You are paying for cover, for a process that does not depend on one person's memory, and for somebody whose job is making sure it ships.

You are also paying for overheads that do not touch your project. That is the honest trade.

The wrong reason to hire an agency is because it feels safer. A bad agency is worse than a good freelancer and costs three times more.

When in-house is right

Rarely, and later than people think.

It makes sense when your website is the product, when you are changing it every week, or when regulation means the work cannot leave your building.

For most consultancies, agencies and professional firms, the site changes a few times a month. That is not a job. That is a CMS and someone who knows how to use it.

How to vet whoever you pick

Same rigour for all three options. Most people do less due diligence on a 10,000 dollar website than on a 400 dollar phone.

Ask for live sites, not screenshots. Anything can look good as an image in a portfolio. Ask for URLs, open them on your phone, and run one through PageSpeed.

Ask what they built and what they did not. Plenty of portfolios include sites where someone did the design and nothing else. That is fine. You just need to know.

Talk to a past client. Ask one question: what went wrong, and how did they handle it? Every project has a problem. How it was handled is the useful signal.

Ask what happens when you disagree. A good answer sounds like a process. A bad answer is "that does not really happen".

Give them a small paid test first if you can. A landing page before a full site. Cheaper than finding out three months in.

Red flags

From projects we have been called in to rescue, the warnings are consistent.

No written scope. If nobody can tell you exactly what is included, the argument later is guaranteed.

A price with no questions. Anyone quoting before understanding what the site must do is guessing, and the gap comes back as change fees.

Hosting they control and you cannot access. This is how people end up held hostage over a domain.

No mention of content. It is the single biggest cause of delay. Silence about it means it landed on you.

Pressure to sign this week. Discounts with a deadline are a sales tactic, not a business reason.

Who owns what at the end

Boring, and it decides how much freedom you have later. Get answers in writing before you pay a deposit.

  • Who owns the design files?
  • Who owns the code?
  • Whose name is the domain registered in?
  • Whose account is the hosting under?
  • If you leave, what do you get, and in what format?

The correct answers are: you, you, you, yours, and everything. Some agencies will push back on the code, especially if they built on their own framework. That may be acceptable. It just needs to be a decision you made, not one you discovered later.

The hybrid that often works best

You do not have to pick one lane.

A pattern we see work well: an agency builds the site, then a freelancer or an internal person handles small changes afterwards. You pay for the heavy lifting once and keep the ongoing costs low.

For this to work the build has to be handed over properly. Documented, on hosting you control, on a platform someone else can pick up. Ask about that before you start, not at the end.

The costs nobody quotes

Whatever you choose, these are usually missing from the number you were given.

Content. Somebody has to write the words and find the photos. If it is not in the quote, it is your job, and it is the thing that delays most projects.

Hosting and domains. Small, but ongoing.

Maintenance. Updates, backups, security. On some platforms this is real work every month.

Changes after launch. There will be some. Ask what they cost before you need one.

Your own time. Feedback, approvals, gathering assets. Budget a few hours a week during the build. Projects stall on the client side more often than the builder side.

Add 20 to 30 percent to any quote for the things above and you will be closer to the true figure.

How to compare quotes properly

When three quotes come back at wildly different numbers, they are not describing the same job.

Ask each one the same five questions.

  1. What exactly is included, page by page?
  2. Who writes the content?
  3. What happens if we need a change halfway through?
  4. What does support cost after launch?
  5. Can I see two sites you built that are still live?

That last one matters most. Anyone can show a portfolio image. Ask for live URLs and open them on your phone.

How long each one takes

Price gets all the attention. Timeline is where projects actually go wrong.

Freelancer. Can often start within days, which is the main advantage. The risk is that your project shares a calendar with three others. Ask what else they are running and when yours gets worked on.

Agency. Usually a wait to start, because good ones are booked. Once it starts it tends to move faster, because several people work at once and someone is paid to keep it on track.

In-house. Hiring takes two to four months before anyone writes a line. Fine if this is a permanent need. Very slow if you just want a site.

One thing worth asking whoever you talk to: what is the date, and what happens if you miss it? A confident answer with a real date is a good sign. Vagueness about timing usually means vagueness about scope.

We work to two weeks, brief to live, and the date goes in the agreement. That is possible because the scope is locked before anything starts, not because anyone is rushing.

Where we sit

We are an agency and we publish our prices, which most do not. A site starts at 4,500 dollars and a site with the systems behind it starts at 7,500. The full breakdown, including what moves the number and the costs that never make it into a quote, is in what a custom website actually costs.

We are not the cheapest option and we do not try to be. If your budget is under a couple of thousand, a good freelancer will serve you better than we will, and we will tell you that on the call rather than shrinking the scope to fit.

The right answer depends on what the site has to do. Work that out first and the choice gets much easier.

Found this useful?
LinkedInX
Nitesh Padghan

Nitesh Padghan

Founder, Storifex Media

I build websites that turn visitors into revenue, and the systems that run everything after. Clients in six countries, most of them shipped in two weeks.

Connect on LinkedIn

Related reading