It's the question nobody dares ask out loud. The one that stops conversations in meetings, the one SME owners whisper after seeing a technical presentation: "If this agency disappears tomorrow, what do I do with my website?" Jean-Marc is 50. He runs an accounting firm in Sion. He's always had WordPress. He can change a comma at 10pm. And now someone's asking him to change everything. What follows is a real dialogue — the questions a business owner asks when they're afraid of being trapped, and the answers an honest agency should give.
The scary question
Jean-Marc: "Camilo, I saw your presentation. It's impressive, green scores everywhere, fast loading... ok. But I'm 50, I've always had WordPress. Everyone knows WordPress. If I want to change a comma or a photo at 10pm, I know how. Your 'Next-js-thing', if you disappear tomorrow or go raise goats in Chile, what do I do with my site? Am I stuck?"
It's the most honest question a client can ask. And it's where most agencies lie.
They say "WordPress is freedom." But they hide that this freedom comes with 50 updates per month, plugins that break each other, and a site that gets hacked the moment you miss a patch. WordPress freedom is the freedom to manage everything yourself.
What you actually own
Jean-Marc: "Explain it to me. If you're gone, who can touch the site?"
Two things.
First, your content. Your texts, your images, your data stay yours — not locked in a proprietary database whose access we control, but stored in versioned, open-format text files. If OSOM disappears, your content isn't captive to anyone: it can be exported, reclaimed, reconnected. It's the opposite of the WordPress model, where your data lives in a database that belongs to your provider.
Second, the source code. Your site's engine. We deliver it on a GitHub account in your name. That's the global standard in software. If tomorrow you want to work with another agency in Lausanne or even New York, they take the code, they read it, and they continue.
You're not married to OSOM. You own your own intellectual property.
How many WordPress agencies deliver the source code on your own repository?
The myth of the local handyman
Jean-Marc: "Yeah, well, any small freelancer around here can manage a WordPress. Your 'Next.js', am I going to need a NASA engineer for every change?"
Quite the opposite.
A WordPress site is like an old car where the engine has been tinkered with for 10 years: every mechanic will say "Oh boy, who did this?". Twenty plugins installed, three themes stacked, custom code injected into functions.php. Every intervention is a risk.
A Next.js site is a standardised, clean, documented architecture. It's the most-used framework in the world for new web projects. Every developer graduating in 2026 can read Next.js. Not all of them can untangle a WordPress that's been patched for 8 years.
And above all, Jean-Marc, the real question isn't "who can tinker with this site?" but "what is it built on?".
WordPress is about 40% of the web: a massive base, but often weighed down by years of stacked plugins. A Next.js site rests on a standardised, documented architecture that search engines — and now AI engines like ChatGPT — read more easily. Where WordPress carries its debt, Next.js starts clean.
Analytics without the lies
Jean-Marc: "And for analytics? I'm told that on WordPress you can see everything, install all the stats plugins you want. With you, am I going to be blind?"
It's the opposite.
WordPress stats plugins slow your site down and are often inaccurate because of ad blockers. Each plugin adds JavaScript. Each script slows loading. Every second lost means visitors leaving.
At OSOM, we use server-level analysis (Edge Analytics). You see everything, in real time, without slowing the site by a single millisecond. No cookies. No blockers. Accurate data.
And most importantly, we build you a dashboard that tells you what actually matters: "How many people called me?" rather than "How many useless clicks did I get?".
Anyone can inflate visitor numbers. Conversion numbers don't lie.
The world changing while you hesitate
Jean-Marc: "Last thing... what's this GEO story? Why should I care? Google works just fine for me."
Google is changing. Not in 5 years. Now.
Tomorrow, your clients won't click on 10 blue links. They'll ask their phone: "Find me the best accounting firm in Sion for a tax audit."
If your site runs on WordPress with heavy code, plugins stepping on each other, and a structure that even Google struggles to read — AI won't be able to parse it. It won't cite you. You'll be invisible.
GEO (Generative Engine Optimization) is the insurance that your business still exists in the world where people don't search on Google but ask AI. A Next.js site with clean structured data, sub-second loading, and semantically rich content — that's exactly what AI engines can read.
A site an AI can't read is a site it won't cite. It's that simple.
The 3 truths nobody tells you
After this conversation, three realities remain that most agencies prefer to hide:
1. Technical sovereignty
GitHub is a global standard. The client isn't "trapped" by OSOM. They own their assets on neutral, open, lasting platforms. It's the opposite of the WordPress model where your site lives on hosting you don't really control, with a database only your provider knows how to export properly.
2. The end of technical debt
WordPress demands constant maintenance: plugins to update, vulnerabilities to patch, compatibility to verify. A Next.js site deployed on Vercel is static, pre-rendered, nearly invulnerable. Maintenance goes from 10 hours per month to near zero. That freed-up time goes into what generates revenue: content and strategy.
3. Investment vs expense
A site that generates zero leads, whatever its price, stays an expense. A site that captures AI traffic and asks a fraction of a WordPress in annual maintenance is a different calculation. The real question isn't "how much does it cost" but "what does it return, and for how many years".
And the goats?
Jean-Marc chose Next.js.
Not because we convinced him that one tech is "better" than another. But because he understood he'd depend on nobody: his data is his, his code is his. Even if Camilo left to raise goats in Chile, his site would keep running and making him visible.
Real freedom isn't being able to tinker yourself. It's depending on no one.
As for the goats — it was Argentina in the original question, but Chile is better. Better wine.
Key takeaways
Your content in open files + your code on GitHub = you depend on nobody.
WordPress covers about 40% of the web, but often at the cost of accumulated technical debt.
WordPress maintenance costs 10h/month. A Next.js/Vercel site: near zero.
GEO (Generative Engine Optimization) is tomorrow's SEO. WordPress isn't ready.
The real question isn't "how much does it cost" but "how much does it return".