HelpSite is knowledge-base software: public help centers, private SOPs, and an AI chatbot that answers from your own articles. It needs a marketing site that grows a page every time the product does.
What we did
We rebuilt it as a static Next.js site where the design lives in code and the content lives in plain files. Adding a feature page now means writing one file with a title, a description, and a few sections. The build turns it into a page with the right headings, meta tags, share images, and structured data. Nobody can accidentally move a button.
The bigger change was the words. The old site listed features. The new one starts from the problems people arrive with, answering the same questions twice, support tickets that shouldn't exist, docs that go stale, and shows the feature as the fix. And instead of describing search, the home page lets you use it: type a question and watch the right article come back.
What changed
Feature pages can now follow a repeatable publishing process. The static build, reusable layouts, and clear answers give the team a stronger foundation for keeping the site useful as the product grows. This case study describes the implementation; it does not claim a measured increase in search traffic or conversions.
