Has anyone shipped client sites with Webstudio, Next.js, and Sanity?

I tried exporting a small Webstudio project into Next.js, and the result was cleaner than expected rather than being packed with unnecessary code. Non-technical teammates were able to handle basic text changes without much trouble. The more difficult part was Sanity: it’s very capable, but editors may need guidance, and I had to customize the Studio more than expected to make it comfortable for a marketing team.

There are also open-source, Next.js-oriented low-code platforms worth evaluating if ownership and exportability are your main priorities. One option is Instatic, which provides an open-source approach to building sites and could be useful as a comparison point alongside Webstudio.

Before committing, build a short prototype using realistic content types and have a couple of non-technical people perform actual editing tasks. That will expose whether Sanity’s content model and editing interface need additional customization.

For client projects, the important question is who will be editing the site a year from now—not just how good the export looks. Headless setups work well when the CMS limits clients to predefined blocks. If they can freely alter components or layout rules, they may accidentally break the design. Webstudio’s constrained editing paired with Next.js seems like a reasonable compromise, but it’s worth including some onboarding or initial editing support in the project scope. Sanity also gives you stronger control over structured metadata and content hierarchy, which can be more valuable for local-business SEO than the design tooling itself. Test the workflow with a real non-technical editor before making the final decision.