Freelancer or Agency? Who Should Build Your Website

When you decide to get a website built, the first split usually comes down to price. The freelancer a friend recommended looks affordable; the agency looks expensive. Yet the complaints we hear from business owners a few years later rarely concern the amount they paid. What we hear instead is: I can't reach the person who built my site, and they have all the passwords.

So it makes more sense to compare the two by how you will live with the site over the next three to five years, not by the quote.

A quick comparison

• Upfront cost: A freelancer usually quotes lower. An agency price often includes project management, testing and post-launch support.
• Availability: A freelancer is one person. A holiday, an illness or a big new client can put you in the queue. At an agency, someone else can usually pick up the work.
• Range of skills: A good freelancer can be excellent in their field, but design, development, SEO and copywriting rarely live in one person.
• Continuity: A freelancer may take a full-time job; an agency may change hands or close. Either way, what matters is that the code and access are yours.
• Communication: With a freelancer you talk directly. An agency puts a project manager in between, which sometimes slows things down and sometimes brings order.

Working with a freelancer

The advantages are real. No middleman, quick decisions. Without agency rent and staff costs, they can do the same work for less. They are flexible and may fix a small issue on a Saturday morning.

Most of the risk comes from depending on one person. A situation we see often: the site was built by a freelancer two or three years ago, the hosting and domain sit in their account, and nobody at the business knows the admin password. The freelancer now works at a company and replies to messages weeks later. There is no bad intent; life moved on. But before you can update or move the site, you have to regain access, and that alone can take days.

The second risk is scope. A freelancer may write solid code while mobile testing, page speed, basic SEO settings or the cookie notice get skipped simply because nobody asked. A written scope prevents this.

When evaluating a freelancer, look at their live sites and call one of those site owners to ask whether they could still reach the freelancer after launch. A five-minute phone call tells you more than portfolio screenshots.

Working with an agency

The biggest thing an agency brings is process. Quote, scope, design approval, testing and handover follow defined steps. Even if someone leaves the team, the project files and notes stay with the agency. A designer, a developer and someone who knows SEO sit at the same table.

There are risks here too. A small job can slide down a big agency's priority list. Planning every job as a from-scratch build can push a five-page brochure site to a budget far beyond what it needs. And even with an agency, ownership problems happen: accounts opened in the agency's name, source code never handed over. We listed the questions to ask an agency in a separate article; it is worth a look before the first meeting.

What fits which project

For a single campaign page or a personal portfolio, a freelancer whose work you can see is usually enough. If the budget is in the 6,000 to 15,000 TL range and you don't plan frequent changes, you don't need an agency structure.

For a 5 to 10 page business site, both paths work. The deciding factor is who looks after the site afterwards. If you will only touch a few texts a year, a freelancer makes sense. If you plan a regular blog, SEO work and campaign pages, a team is safer.

For e-commerce, booking systems or anything with integrations, choose an agency or at least a small team. When the checkout fails at 11 p.m., having more than one person to call matters.

There is a middle path as well. Having a ready-made site adapted to your brand is one way to get an agency workflow for close to a freelancer budget. At Kodyva we offer this model too: since design and infrastructure already exist, the cost goes down, while support follows an agency workflow. You can also have a freelancer build the site and hand maintenance to an agency. The only condition is that the code and access are yours from day one.

Whoever you choose, put this in the contract

• Domain, hosting and email accounts are opened in your name and the passwords are handed to you.
• Whether source code and design files are delivered, and on what terms, is written down.
• The scope is written down: number of pages, languages, which forms and integrations are included.
• The number of revision rounds is stated, along with the price of extra ones.
• The free bug-fix period after launch (30, 60 or 90 days, for example) is clear.
• Payments are tied to delivery milestones.

We covered each of these in detail in our article on website contracts. If you work with a freelancer, this list matters even more, because the contract often ends up being a handful of WhatsApp messages.

When you decide, ask yourself one question: will this person or team be reachable for me a year from now? If the answer is yes and the accounts are in your name, either option can produce a good site.