09 —The plan
Phases, milestones, deliverables.
Five months, three phases
The final delivery: 17 pages, rebuilt — the most important pages of the site first (the 5 industry pages, the 8 product pages, plus Home, Pricing, Support and Contact). A new front-end of React components and shared design settings, each page redesigned by the new system, ready for your engineers to validate and put live. The connections behind it (the content system, translations, account, integrations) stay untouched. The rest of the site is decided afterwards — your team, or a later phase — once the approach is proven here. Each phase ends with something running, not something promised, and phase 1 is where we validate the timeline together. What keeps the scope defensible: same pages, same content, built on components that already exist on the live site today.
Setup & design direction
The design direction and the rules of engagement, agreed before anything is built. Your team decides where the design goes; we bring options and lock the technical scope alongside engineering.
Deliverables
- → Access to your codebase, the working setup, and how changes get reviewed — agreed with your front-end team
- → Getting up to speed on your setup: your standards, shared styles, how content and translations work
- → Scope locked: the 17 pages we rebuild first (5 industry pages, 8 product pages, plus Home, Pricing, Support and Contact) and the components they require — with a written definition of how each component works (its settings, content, translations, and behaviour)
- → Design direction agreed: the shared design settings — type, color, spacing — the components will follow
Execution
We build the system, following the design and engineering criteria your team set in phase 1. Nothing ships without your review.
Deliverables
- → Components redesigned and built in code from proven, ready-made building blocks, keeping each component working exactly as it does today so the connections behind it stay untouched
- → Pages and templates composed from those components — product, industry, editorial
- → A working preview of the new pix4d.com: real content, all languages, all 17 pages in this first scope
- → Every component is reviewed and approved by your team before it goes in
Integration & launch
Your engineers put the finished front-end on the live site — you launch only once we've validated together that everything is correct. We're alongside for review and enablement. Because every component still works the same way, plugging it in is direct: same connections, new front-end.
Deliverables
- → A final engineering review of the whole system, in your codebase, on your standards
- → Your team plugs it in and puts it on the live site; we validate and support alongside
- → Documentation right where it lives: how each component behaves, its settings, variations, how it maps to content, and what it depends on
- → Enablement: pairing until your team extends the system without us; Figma library generated from the code as the lasting view
Next
That is the plan — three phases, each ending with something delivered. What it costs, and what the cost buys, is next.