In plain English: Nerdy.Money had 39 pages, 13 of them empty. In 72 hours we rebuilt it as a fast static site with 170 pages in two languages, 19 country guides from one data set, four free tools and no cookie banner.
Imagine you're thinking about moving your company to Cyprus. You find a site that promises to explain it. You click on the Cyprus guide. It's empty. You click on Portugal. Also empty. The page that is written quotes a Cyprus tax rate that changed with the 2026 reform.
You'd close the tab. So would everyone else.
That was Nerdy.Money in September 2026: a site that helps entrepreneurs and expats move abroad and cut their taxes legally, and whose content is the whole sales pitch. Seventy-two hours later it had 170 pages, 19 country guides, four free tools and no cookie banner.
Full disclosure: Nerdy.Money is co-founded by our founder, Markus Behmann. That made it the perfect guinea pig. We ran our full relaunch process on it, with no discount on rigour, before recommending the same move to anyone else. Here's exactly what we did, and how to tell if your site needs the same.
The Starting Point: A Third Of The Site Was Empty
Nerdy.Money had grown the way many company websites do: WordPress, a page builder (Divi), a stack of plugins and good intentions. The content that existed was good. The problem was everything around it.
- 13 of 39 URLs were empty, and 3 more were placeholders.
- Only one country guide was written (Malta). Seven other country pages were blank, on a site whose core product is country guides.
- Dead ends everywhere. Service buttons led nowhere, the "Optimize tax" and "Protect wealth" sections were empty, and the podcast player was still playing the page builder's demo file.
- Outdated facts, which is dangerous on a tax site. Cyprus was listed at 12.5% corporate tax (it's 15% since the 2026 reform), and Portugal's NHR regime had been replaced by IFICI.
- Heavy, and full of trackers. A cookie tool, an ads tag, an analytics suite, jQuery, reCAPTCHA and a WooCommerce merch shop, all for a site whose job is to be read.
None of this is unusual. It's what happens when a site is built once and then patched for years. But for a business that sells expertise, every empty page quietly says "we don't really know".
Step 1: Inventory Before Demolition
The most expensive relaunch mistake is losing things you didn't know you had: a page that ranks, a paragraph a partner links to, a form someone relies on.
So before we deleted anything, we saved a verbatim copy of every old page, listed every URL and checked every claim. Every outdated number was flagged, every old page worth keeping got a new home, and the merch shop (a business decision to drop it) was redirected to the homepage instead of turning into a 404.
What you can do: export a list of every URL on your site today and mark each one: keep, merge, rewrite or redirect. That list alone will tell you how big your relaunch really is.
Step 2: Turn Content Into Data
This is where most of the 72 hours were won.
We didn't write 19 separate country pages by hand. We turned every jurisdiction into one structured file: tax rates, residency rules, costs, pros and catches. The country pages, the comparison table, the Jurisdiction Finder and the tax calculator all read from that one source.
| Hand-written pages | Content as data | |
|---|---|---|
| Change a tax rate | Edit every page that mentions it (and miss one) | Edit one file, and every page and tool updates |
| Add a country | Design and write a new page | Add one file and the page builds itself |
| Compare countries | Copy-paste into a table | The table is generated |
| Show sources | Rarely done | Every figure links to an official source and shows when it was last checked |
We were also honest about what isn't finished. Countries whose figures are still being reviewed are marked as drafts instead of being passed off as final.
What you can do: look for the content on your site that has the same shape again and again, such as products, locations, services or case studies. That's data wearing a page costume, and it's the first thing worth structuring.
Step 3: Replace Tiles With Tools
The old homepage had static tiles. The new one gives visitors answers before they ever talk to anyone:
- A Jurisdiction Finder: seven questions, then a ranked shortlist with the reasons.
- A tax calculator for corporate and dividend tax across all nineteen jurisdictions.
- A country comparison: up to three side by side.
- A 183-day tracker for tax-residency days.
Plus site-wide search. All four tools run in the visitor's browser, and no data leaves their device, which matters a lot to an audience that cares about privacy.
Tools like these are what people bookmark, share and come back to. They're also the natural bridge to a paid conversation: once someone has a shortlist of three countries, "can we talk this through?" is the obvious next question.
What you can do: find the question your sales team answers ten times a week. If the answer depends on a few inputs, it can be a calculator.
Step 4: Fill The Gaps, In Two Languages
With the structure in place, the content could grow fast: guides on leaving Germany, tax residency, offshore banking, moving abroad and passports and residency, plus insights, a glossary and FAQ sections marked up for search engines. The result was 85 pages in English and 85 in German, and not one of them empty.
The empty service pages became a clear "how it works" partner model, with a multi-step match form that can be pre-filled from any country or service page. The funnel now leads from free content, to a tool, to a paid strategy session.
What you can do: check which pages your best leads visit before they contact you. Those pages deserve the next hour of writing, not the homepage.
Step 5: Delete What Nobody Needs
The fastest code is code you don't ship. We removed:
- the cookie tool, the ads tag and the analytics suite (no cookies, so no cookie banner),
- jQuery and the page builder,
- reCAPTCHA (replaced by quieter spam protection),
- Brevo, since newsletter, double opt-in, welcome automation and lead forms now all run on Resend.
The hero videos were re-encoded from 21.3 MB to 8.9 MB in total. We went through the same exercise on our own site. If you're curious what WordPress was costing us, here are the before-and-after numbers.
What you can do: open your cookie banner's settings and list every tool it's asking permission for. For each one, ask: when did someone last make a decision based on this?
The Result
| Before | After | |
|---|---|---|
| Platform | WordPress + Divi, plugins, jQuery | Static site on Cloudflare Pages, deployed from GitHub |
| Pages | 39, of which 13 empty | 170 (85 EN + 85 DE), none empty |
| Country guides | 1 written, 7 blank | 19 jurisdictions from one data set |
| Tools | None | Finder, tax calculator, comparison, 183-day tracker, search |
| Cookie banner | Yes | Not needed |
| Build time | – | 72 hours |
In Lighthouse on the live site, every page we tested scores 100 for SEO and best practices, 99–100 for desktop performance and 84–96 on mobile, with zero layout shift. A new country, guide or rate change is now a small edit, reviewed and live within minutes. The code lives in the client's own GitHub repository, with no theme licence and no plugin stack to keep patched.
What we can't show you yet is traffic and leads: a relaunch needs a few months before those numbers mean anything. We'll add them here after the first 90 days, including the ones that don't flatter us.
Should You Make The Same Move?
Not every site needs this. If ten people edit your site every day and the setup works, a static rebuild may be the wrong trade. But it's worth a serious look if at least two of these sound familiar:
- Every WordPress or plugin update feels like defusing a bomb.
- There are pages you're embarrassed by, or that are simply empty.
- Your content is your sales team, but it's scattered and out of date.
- You pay for plugins, trackers and tools nobody looks at, plus a cookie banner to go with them.
- You need a second language, and the current setup makes that painful.
The split of work that made 72 hours possible was simple. The client brings the expertise: what's true, what matters, what customers ask. We do the tech wizardry and the heavy lifting: inventory, migration, structured content, tools, forms, e-mail, performance, SEO, hosting and go-live. We work AI-native, which is why a rebuild like this takes days instead of months, and a human checks every fact that matters.
Curious where your own site and processes stand? The free scorecard takes three minutes and tells you where we'd start.