The director called me on a Tuesday in September. His voice swung between irritation and polite disbelief. He had just paid €8,200 to a local agency for a WordPress brochure site. Three months of delay. The result: a $59 ThemeForest theme, two logos moved around, and a contact form that didn't send any email. When he asked for the sources, he received a .zip file and the Gmail address of a developer in Dhaka he had never met.
The agency had a real storefront, a beautiful website full of "values" and "processes", three consultants in suits at the sales meeting. The dev who actually wrote the code never left Bangladesh. Nobody lied to him — they just forgot to mention where the code came from.
Upfront disclosure: I'm a freelancer. What follows is openly biased. But it's also 14 years on the ground, dozens of projects taken back from agencies, and the honest urge to ask the question nobody asks: why is there so much opacity about who actually does the work?
Agency vs freelance: what's the real difference?
On paper, a web agency sells a multi-disciplinary team — project manager, designer, developer, integrator, SEO, sometimes a traffic manager. A freelancer sells one brain and two hands. The apparent difference is structural: the agency covers the chain, the freelancer covers one link.
Except in real life, in Besançon as elsewhere, the split is fuzzier. Most agencies under 15 staff don't have all profiles in-house. They subcontract. Either to French freelancers (often the same ones you could have reached directly), or to offshore platforms. The actual production cost of a brochure site billed €8,000 by an agency is rarely above €1,500 — the rest is margin, sales, management, office space.
The real difference isn't who codes, but who owns the project. The agency promises organization, a single point of contact, a contractual deliverable. The freelancer promises a direct relationship with the person writing the code. Both models are valid — but they don't cover the same needs, and the price doesn't reflect the same thing.
The myth of agency safety
"Going through an agency is safer." That's the number one argument I hear. It deserves a piece-by-piece teardown.
Turnover. The project manager who sold you the project has a non-trivial chance of having left the agency before delivery. The dev assigned to your project has an even higher chance of being gone within 18 months. You talk to a stable salesperson, but the technical team rotates. When you call for a fix six months after delivery, the new project manager opens your file for the first time.
Hidden subcontracting. In 2023 I took over a Symfony project delivered by a Paris agency for €47,000. The code came from a Ukrainian freelancer (excellent, by the way) billed €8,000. The client had never heard of him. When the dev ended up in Lviv in 2022, the agency had nobody left who could maintain the project. Cost to take it back: another €12,000, because documentation was non-existent.
Inflated quotes. An agency bills "man-days" at €800-1,200. A senior freelancer bills between €500 and €700. The difference doesn't go into the code — it pays the structure. That's not illegitimate, but it's rarely explicit. And on projects where the structure adds nothing (a brochure site, a single-developer app), it's money that produces nothing.
"Agency safety" exists — for very large multi-channel projects. For a standard SME web project, it's essentially a marketing argument.
The myth of the fragile freelancer
The symmetrical argument is just as persistent: "if I go with a freelancer, I depend on one person. If he has an accident, I lose everything." True in the abstract, false in practice.
Continuity. A senior freelancer established in Besançon for ten years has a network. If I'm unavailable, I have three peers technically able to take over — and I formalize it. It's rarer than at an agency to see this written down, but it's doable and it's my case. Always ask for the continuity clause in the contract.
Code ownership. With an honest freelancer, you own the code upon delivery. No license, no captive SaaS, no proprietary WordPress theme nobody else can modify. Accessible Git, minimal documentation, hosting accounts in your name. With an agency, you're statistically more likely to end up locked into an ecosystem whose exit costs a fortune.
Maintenance contract. A freelancer can absolutely commit to an SLA. Response within 24 business hours, intervention within 48 hours for emergencies, monthly updates. Flat fee €80 to €250 excl. tax/month depending on criticality. That covers 90% of an SME's real needs — far better than a "premium agency package" at €600/month that only pays for a generic hotline.
When choosing an agency still makes sense
I have to be honest: there are cases where the agency is objectively the right call. If one of these criteria applies to you, skip the rest of this article — call a serious agency.
- Integrated marketing need. You want a website + SEO strategy + editorial content + Meta/Google ads + community management — all coordinated by one team. It's doable by assembling several freelancers, but an agency does it natively.
- Budget above €30,000. At that level, the project justifies a real multi-disciplinary team. Agency margin becomes relatively small compared to the value produced. The risk inverts: a single freelancer can't keep the pace.
- Complex multi-channel. Website + native iOS/Android mobile app + back-office portal + multiple integrations. Too many specialties to coordinate for a single freelancer. Either you assemble a team, or you take an agency.
- Heavy procurement procedures (public sector, large groups). Many IT departments require a supplier with X years of existence, Y staff, ISO certifications. A freelancer doesn't pass the administrative filter, even when technically much stronger.
When a senior freelancer makes the difference
Conversely, here are the cases where a well-chosen senior freelancer statistically buries the agency option — in quality, cost, and timeline.
- Complex tech with a modern stack (Go, Rust, Symfony 7, Vue 3, event-driven architecture). Local agencies rarely staff seniors on these stacks — they do WordPress or Webflow and subcontract the rest. A specialized senior freelancer codes better and faster, because that's all he's done for 10 years.
- Custom business app. Lightweight ERP, custom CRM, internal management tool, customer portal. These projects need deep business understanding and short iterations. A freelancer talks directly to the decision-maker, without the project manager layer filtering information.
- Regulatory compliance (GDPR, AMF finance, healthcare HDS). The legal responsibility granularity works better with a single named contact. See my consulting missions on these topics.
- Long-term partnership (3-5 years and more). The same person on the codebase for five years is worth gold. No turnover, no relearning, no documentation that goes stale because nobody has read it since 2022.
- Stuck project recovery. When a project is in the wall, what you need is a senior dev diving into the code, not a kickoff meeting with four different profiles.
5-question decision grid
When a prospect hesitates between agency and freelance, I ask these five questions. If the majority points to freelance, that's probably the right call.
- Project volume. Less than €25,000 total? Freelance. More than €35,000 with multiple components? Agency or assembled team.
- Technical qualification of the need. Stack identified and stable (PHP, JS, or modern variant)? Senior freelancer. Cross-functional design + dev + marketing need? Agency.
- Level of partnership. You want a partner who understands your business over time? Freelance. You want a contracted deliverable with a single entry point? Agency.
- Continuity guarantee. Ask in writing who codes, where, and what happens if that person disappears. If the agency dodges, that's a red flag. A freelancer who has a backup peer planned in case of unavailability is more reassuring than ten org-chart slides.
- Pricing transparency. Ask for a day-by-day breakdown. If the agency bills 60 days without detail, ask yourself how much ends up with the dev who codes, and how much ends in margin. See my public price grid for comparison.
And in Besançon? The reality of the local landscape
Let's be clear without naming anyone — Besançon is a beautiful city of 116,000 inhabitants, but the local digital landscape is modest. There are a few serious agencies, a number of WordPress integrators calling themselves "agency", and many freelancers of varied profiles.
Senior agencies — those staffing architects, experienced full-stack devs, DevOps — are rare in Bourgogne-Franche-Comté. Most ambitious projects end up in Lyon, Paris, or Geneva. The result is paradoxical: in Besançon, many SMEs pay regional agency rates for subcontracted WordPress production, when a local senior freelancer would deliver better for less.
This isn't a critique of local agencies — it's a market reality. The Besançon area doesn't have the critical mass to staff several senior agencies. For simple needs (WordPress brochure site, territorial communication), local integrators do the job well. For the rest, the gap between what's billed and what's delivered can be uncomfortable.
If you're looking for custom work in Besançon, look first to local senior freelancers, then widen to the whole Bourgogne-Franche-Comté region, and only then consider national agencies. That's the reverse of the usual reflex, but it produces the best quality/price ratio in 70% of cases.
Takeaways
The "agency vs freelance" debate is really an "opacity vs transparency" debate. An agency isn't bad by nature, a freelancer isn't good by nature. What matters is who codes, at what level, with what continuity commitment, and how much margin sits between you and the keyboard.
For a strategic SME project under €30,000 in Besançon, in 80% of cases, a local senior freelancer brings more value than a regional agency. For a multi-channel project at €60,000+, the agency (or assembled team) regains the advantage. Between the two, the question to ask is: how many effectively coded man-days do I get for my budget?
If you're thinking through a project and want an honest opinion on the right format, we can talk it through. I give a frank assessment, even when the answer is "for this specific need, take an agency". It happens more often than people think — and that's what makes the conversation useful.
