What we checked first on an outdated company website, the choices we made and how we changed it safely — shown as a case. It follows the same steps we use in consulting.
We defined the business lines to show and separated what visitors (owners, investors, partners) look for from what should not be published.
We ordered the menu by what visitors look for, not by how the company is organized.
The first screen shows at once what the company does and what it has done.
We compared a full rebuild with reusing the existing system on cost, time and risk.
We kept existing functions such as news, careers and inquiries, and changed the screens first.
Less development scope and risk, with no loss of existing functions.
We checked company details against the corporate register and business registration, removed wording we could not legally use, and backed up all files and source before editing.
No internal information that could affect security goes on public pages.
We could always return to the state before the work if something went wrong.
AI produced drafts; people reviewed and revised them, repeatedly. Approved drafts were built and checked on both desktop and mobile.
Mobile was designed on its own — swipeable cards and a fixed contact bar — rather than a shrunken desktop page.
Sixteen photos total about 0.8 MB, so pages open quickly on phones.
We deployed to the server and checked HTTPS, certificate renewal, logs and storage.
Keeping the site up matters more than building it, so we set a checklist.
With a checklist, recurring problems can be caught early. In progress
We are still collecting data on time and cost savings and will publish real figures here once measured.
For security, system architecture and technologies are not published on public pages. We explain them directly to invited guests along with the demo system.