Image Lab — site for a medical AI company
A site for a maker of AI products for healthcare: three products, a custom development service, and a clear line between them.
- Each product gets its own page rather than a line in a shared list
- Two different sales separated: a finished product versus custom development
- Fast static output with no CMS or database — nothing to break, nothing to administer
The problem
The company has three products for healthcare institutions plus a custom AI development service. On a single page that blurs into mush: a visitor cannot tell whether they are buying a box or a project, and leaves.
How it works
A separate page per product, another for the development service, and an explicit card linking out to the product that has a life of its own. Content lives in code: for a site this size a CMS adds more work than it saves.
The hard part
The main difficulty was editorial rather than technical: medical products get described in language that is clear to an engineer and opaque to a hospital buyer. Every page was rewritten from the question 'what does this change on the ward' instead of from a feature list.
Evidence
- Six pages built and wired together by navigation
- The product with its own separate site is linked, not duplicated
- No database and no CMS: deploying is publishing static files