Change graph
All system objects, functions and the connections between them — clearly visualised. Click a node to see details, change history and who made each change.
Platform AI is an operating system for a business. It connects the ERP, CRM, spreadsheets, BI, maps and messaging a company already runs. AI agents build and operate the processes on top. We designed and built the site: twenty pages, one design system.
The product was never the hard part. Explaining it was. The brief: understand the platform within two screens, and never read more than you came for.

The site answers four questions, in order. What the platform is. What it sits on top of. What you can build. What it costs. One question per section.
Nothing competes for attention. A section makes its point, shows it, hands the reader on. Ease of reading was the brief, not a polish at the end.

One point per section, one block per point. Twenty-eight blocks carry twenty pages. A new page is a running order, not a new design.
The forms repeat, so the site is learned once. A claim sits where claims sit. A proof looks like a proof. Recognition does the work explaining would otherwise have to do.

The site splits by reader, not by subject. Light and orange for outcome, cost and time. Dark for how the platform is built. Same blocks, same type scale, two rooms.
Neither reader wades through the other's half. The way across is a link, placed where the question arises.




Sections arrive in reading order, a beat apart. Thirty-three groups, four easing curves. Motion here is pacing, not decoration.
Complex inside, simple outside — the product's own promise. The illustrations are where the site keeps it. They move on long, quiet cycles and rest on the values they were drawn with.
All system objects, functions and the connections between them — clearly visualised. Click a node to see details, change history and who made each change.
Try changes on a copy of the system before they touch production. Test, compare, then deploy.
One page holds the library: twenty-eight sections, what each is for, where each is used. Every new page starts here.
The system lives on a page, not in a document. So it is looked at before anything new is drawn.
The same twenty-eight sections carry a landing page, a module page for developers, a customer story, a pricing table. The running order changes. The design does not.
This is the case for a library over a folder of layouts. A new page inherits every fix the others already had. The work goes into what it says.



