Most agency case studies talk about the finished product. This one is about a narrower, less glamorous problem: how do you hand a client a marketing site they can actually edit — new pages, new posts, updated copy — without waiting on a developer every time, while keeping the site fast and cheap to run?
That's what we built for Yellow Intelligence, an AI platform that builds custom AI systems for sales teams.
The Problem
Yellow Intelligence needed a marketing site with real content depth — product pages, resources, a blog, a growing team — and all of it was going to keep changing after launch. Two common approaches, both wrong for that:
- A CMS-backed server — works, but adds a runtime server and a database, both things that need patching, monitoring, and paying for.
- A static site with no CMS — fast and cheap to host, but every content change becomes a pull request. Fine for a two-person team; a bottleneck for anyone else.
We needed the editing experience of a CMS with the hosting simplicity of a fully static site.
This isn't a Yellow Intelligence-specific problem — it's the default tension on almost every marketing site we build. The founder wants to ship copy changes the day they think of them. The dev team doesn't want to be the bottleneck for a headline swap. And nobody wants a server bill or a security patch schedule for what is, functionally, a brochure.
The Approach
We built the site as a statically-exported Next.js app — no server running at runtime — paired with a Git-backed CMS, so every edit an editor makes becomes a commit, and every commit triggers an automatic rebuild and deploy. No database to manage, no server process that can go down, and no developer in the loop for routine content changes.
Because the site has no runtime server, we put the effort instead into making sure a broken content edit can't silently ship — the build itself verifies that every piece of content produces a real, working page before anything goes live. That's the part that matters most for a site a non-technical team will be editing long after we're gone: catching mistakes before they reach production, not after.
When This Pattern Makes Sense — and When It Doesn't
Static-export-plus-CMS is the right call when the site is mostly content that changes on a human timescale — pages, posts, product copy, team bios — rather than data that changes per request. It's the wrong call when you need real-time data, user accounts, or anything that has to be computed per visitor; at that point you need an actual server somewhere, and trying to force it into a static export just adds complexity instead of removing it.
The other trade-off worth knowing about up front: a rebuild-on-publish model means a content change takes a minute or two to go live, not zero. For a marketing site, that's a non-issue. For something like a live pricing page that needs to update instantly, it isn't the right pattern.
Working With the Client
This wasn't a one-shot build — the site evolved across multiple rounds of structured revisions as the client refined their messaging and information architecture. That's typical of real client work, and worth saying plainly: the first version is rarely the shipped version. What matters is having an architecture that makes revisions safe to make quickly, rather than risky.
Handover
The project shipped with full documentation and was handed over cleanly to the client's own team — they own the site, the content, and the ability to keep it running and evolving without depending on us.
What This Project Says About How We Build
The Yellow Intelligence site isn't flashy — there's no 3D scene, no experimental animation system. What it demonstrates is the less visible half of good agency work: building content architecture that survives contact with a real, non-technical editor making real changes after launch, on infrastructure that doesn't need a server to babysit.
If you need a marketing or product site your team can actually maintain after we hand it off — not one that quietly breaks the first time someone edits it — get in touch. We build the same way we built this: static where we can, CMS-editable where it matters, verified before it ships.
See our portfolio | Explore our web development services | Get in touch
LSD Dev Studio — Launch Support Develop. We build web apps, mobile apps, animated videos, and digital products. See all our services.