Freelancer vs Agency: Where the Risk Actually Sits
Two quotes, a fourfold gap, and both promise the same website. One comes from an independent designer, the other from an agency. The board asks a fair question: what exactly is that difference buying? 🤷
The usual answer — “an agency has a team” — doesn’t hold up. The real difference is not headcount but where the risk sits. With an independent, most of it stays with you. With an agency, part of it transfers. The price gap is the cost of that transfer.
This article doesn’t compare the two models. It identifies the thresholds at which the model must change, then covers the third option most companies overlook.
Where Does the Risk Sit?
Every web project carries five risks: continuity, scope, quality, schedule and handover. ⚖️ Each rests on a different party depending on the model, and that is what actually produces the price difference.
Where Is the Threshold?
BU BÖLÜMÜN ÖZETİ
- Threshold 1: Twenty pages and six templates
- Threshold 2: Integration or multiple languages
- Threshold 3: A fixed launch date
- Threshold 4: Continuous publishing after launch
“An agency is better” is a false statement: hiring an agency for a ten-page brochure site is waste. 📐 The useful question is which threshold your project has crossed.
Threshold 1: Twenty pages and six templates
Beyond twenty pages and six unique templates, the work becomes a coordination problem. When one person designs and codes, every revision reverses three jobs. Without coordination, schedules slip regardless of talent.
Threshold 2: Integration or multiple languages
ERP links, dealer portals, payment infrastructure or a second language demand separate expertise. Multilingual work is not translation; it requires URL structure, language markup and market-specific content. 🌍
Threshold 3: A fixed launch date
Where a trade fair, launch or season start cannot be missed, continuity risk cannot be carried. There is no backup behind one person. A project with a date needs a team with redundancy.
Threshold 4: Continuous publishing after launch
If regular content, campaigns and updates will follow, the relationship is a subscription rather than a project. Sustaining that rhythm with an independent is difficult; priority will not always be yours. 🔁
The Third Option: A Hybrid Model
BU BÖLÜMÜN ÖZETİ
- Build with an agency, maintain independently
- Advice from an agency, production in-house
- Comparing cost honestly
- Where hybrids fail
The choice is presented as binary, but a third path exists: split the work by layer. 🧩 The agency builds the architecture; an independent sustains day-to-day production.
Build with an agency, maintain independently
The agency establishes architecture, templates and technical foundations; daily content and small fixes pass to an independent. Because the system follows standards, the handover works. One condition: documentation and code standards must be delivered. Without documentation the hybrid model collapses.
Advice from an agency, production in-house
Where the company has its own designer or developer, the agency stays in a directing role: architecture, review, periodic audit. This prevents the in-house team from drifting off standard. 🧭
Comparing cost honestly
The common mistake is placing quote totals side by side. A fair comparison adds the missing layers: performance work, search setup, accessibility, handover documentation. Priced individually and added to the independent’s quote, the gap narrows considerably. 🧮
Where hybrids fail
The single weakness is the boundary of responsibility. When something breaks and no document says who fixes it, the parties point at each other. Define one owner per layer and a response time. A hybrid with written boundaries takes the best of both models.
Quick Summary
- The price gap buys risk transfer, not headcount.
- Five risks: continuity, scope, quality, schedule, handover.
- Thresholds: 20 pages/6 templates · integration or languages · fixed date · continuous content.
- Two thresholds crossed means one person is no longer viable.
- Hybrid is a real option: agency builds, independent maintains.
- Write the responsibility boundary in any hybrid setup.
Frequently Asked Questions
Next Step
Mark how many of the four thresholds you have crossed. 🎯 More than two, and the conversation should be about an agency or a hybrid.
Sık Sorulan Sorular
If an independent falls ill, takes another project or stops replying, the project stops. In an agency the role passes to someone else. On small projects this risk is tolerable. On projects with a fixed launch date, it is not an acceptable line item. ⏱️
A designer delivers the interface; server configuration, performance work, search visibility and accessibility usually fall outside. Adding them afterwards costs more than building them in.
Some independents work to their own conventions, leaving no documentation and following no standard. The system runs but cannot be transferred. An untransferable system means starting from zero at every future upgrade.
In a one-person setup the work reviews itself. In an agency, design sees development and development sees content; faults surface before delivery. That internal review is the least visible but most concrete thing the price buys. 🔎
No. Under ten pages with no integrations, an independent is sufficient. The only requirement is written ownership and handover terms.
Three steps: written scope, staged payments and a handover document. Keep domain and hosting in your own accounts.
No. What matters is process maturity and internal review. An agency without separated roles may underperform an experienced independent.
Undefined responsibility. When nobody owns the fix, the process stalls. Assign one owner per layer.
When the website is a continuously developed product. For a corporate site updated a few times a year, in-house cost is not recovered.
Yes, if the system follows standards. Undocumented, non-standard builds turn a model change into a rebuild.