Case study one
Zossoz ran its own playbook on itself.
Before Zossoz sold anyone a rebuild, it needed one. In August 2026 the studio tore down its own site, zossoz.com, the same way the free teardown tears down yours, then rebuilt it with the exact four-step process it sells.
This page is the honest version of that story: what the old site actually looked like, the decisions that replaced it, and a set of receipts you can check from your own browser in the next few minutes.
The before
First, we ran the teardown on ourselves.
Every Zossoz engagement opens with a teardown of the client’s site. Ours opened the same way, except the client was us. Some of what that teardown found on the old zossoz.com, documented before any of the rebuild began:
The old site ran on Duda. The free offer was an automated tool called the Website Visibility Scan, gated behind a five-field form that asked for a phone number. Fifty-two blog posts sat behind it.
The glossary’s own H1 read “Glossary Overview: Navigate Essential Branding and Web Terms with Ease,” precisely the kind of SEO-stuffed heading a Zossoz teardown flags on someone else’s site. The privacy policy described data the site never collected: Social Security numbers, payment cards, rental applications.
That old form’s address, /free-website-visibility-scan, still resolves. It just lands somewhere else now.
- PLATFORM
- Duda
- OFFER
- automated scan, 5 fields, phone required
- BLOG
- 52 posts
- PRIVACY POLICY
- described data never collected
- SUBJECT
- zossoz.com (that’s us)
The decisions
What actually changed, in order.
Some of it you can see. All of it is dated, because a rebuild without a timeline is just a claim.
- Aug 9
Off Duda, onto a system
zossoz.com was rebuilt as a Next.js visibility system on Vercel, under an owner-selected direction called Ocean Drive Noir. The same day, the free offer changed: the automated scan became a free human teardown, the form dropped from five fields, phone included, to three, and real client testimonials, pulled from an existing SocialJuice export, went live sitewide.
- Aug 13
Consent that can be taken back
Session recording became opt-in everywhere, not only where regulation requires it. Analytics went consent-gated in the EEA, UK, and Switzerland. Every choice stayed withdrawable from the footer, and the privacy policy was rewritten against what the codebase actually does.
- Aug 15
Mail that doesn't leak
TLS became required on outbound SMTP, and form delivery got hardened, so a teardown request has fewer ways to go missing between a visitor's browser and a human's inbox.
- Aug 19
Fewer identical pages
A honeypot field, timing checks, rate limits, and content heuristics went in against form spam. The same pass ran an editorial variation across the /for and /vs page fleets, so sibling industry and comparison pages stopped reading like one template with the names swapped.
- Aug 27
Content off the deploy pipeline
Every post, and the entire content-ideas backlog, moved into a headless system. A post published there now goes live in about five minutes, with no deploy required.
Verify it yourself
Four things you can check before you finish this page.
None of this asks you to take our word for it. Each one takes under a minute, using nothing but your own browser.
Right now, on this page
Structured data you can read yourself.
This page ships breadcrumb schema. Sitewide, the same system adds ProfessionalService with a real name, address, and phone, FAQPage wherever a page carries FAQs, and Review markup built from actual client quotes.
Check it: View source, search for application/ld+json.
140
pages in the sitemap
Every service, industry, comparison, location, glossary term, and blog post gets its own URL. This number comes from the same list that builds the real sitemap, so it can’t drift out of sync with this sentence.
Check it: Open /sitemap.xml and count them.
Bottom of every page
A consent banner with nothing to hide.
Open “Cookie settings” in the footer. The accept and reject buttons are identical in size, weight, and position. Equal prominence is a legal requirement here, not a style choice.
Check it: Footer of any page, Cookie settings.
~5min to live
from published to public, no deploy
Posts and ideas now live in a headless system outside this codebase. A published post reaches /blog on its own, without anyone redeploying the site you’re reading right now.
Check it: Visit /blog. Nothing there required a new build.
The honest part
What this case study doesn’t show.
There is no before-and-after traffic chart on this page, and no ranking graph. That is not an oversight. The rebuild above shipped across a few weeks in August 2026. Organic traffic, keyword position, and AI citations are the numbers that actually matter, and every one of them takes quarters to mean anything. A chart built from three weeks of data would be noise dressed up as proof, which is the exact kind of score theater the free teardown promises it will never run.
What you can check today is everything above: the markup, the sitemap, the consent banner, the publishing pipeline. None of it needs a quarter to prove itself. It is either true right now or it is not.
One more honest note. Most of the client proof behind this whole site, including the testimonials over on /work, is heaviest in property management and real estate: the industries Zossoz has gone deepest in so far. The teardown, blueprint, rebuild, care system runs the same regardless of industry, but right now the receipts mostly come from where the studio started.
This is case study one. Two more are coming, each with a client’s actual numbers attached, once those numbers are theirs to publish.
Next step
Want the same teardown pointed at your site?
The free teardown is the same starting point this rebuild started from: a human review, delivered async, no sales call, no phone number required. If you already know you want the deeper version, the Rebuild Blueprint turns the findings into a sitemap, a page plan, and a price before anything gets built.
No commitment. No sales pitch. Just the same process you just read about, run on your site instead of ours.