11 —Why now

For the Pix4D team

This is an ambitious proposal — on purpose. It answers the brief, and it goes one step further: it sets up a new way of working, closer to what users and customers actually see. That closeness is where the savings come from — fewer handovers, faster rounds, decisions made on the real thing.

What Pix4D gets is a redesigned pix4d.com — starting with its 17 most important pages — and underneath it, the library the brief asked for: design settings, the basic building blocks, and full components, living in your team's own codebase, plugged into the same connections that run the site today. Not a picture of the system. The system itself.

Figma stays, as the view it should be — a view of the code, generated from it, always up to date, never a second copy to maintain. The two-versions-drifting problem isn't managed. It's gone.

And your team keeps the way of working itself: designers shaping components directly in the system, engineers reviewing every change, the system enforcing its own rules. A way of working that keeps paying off after the project ends — because it lives in your team's own codebase, reviewed and owned by them.

Because what you get isn't just the site. It's the way of working: designers and code in the same place, Figma as a view of it.

The next step is a kickoff: one week, together, confirming the audit and the component list — then we start building. The first components can be live before the first Figma library would even have been finished.