02 —Planning
The four phases, from setup to hand-off.
Four phases — July to October
Four phases, from setup to hand-off. The design is yours — every style and visual decision; our work is to build it into a working component system and the pilot pages, and to set up the way of working around them. The knowledge transfer is documented as we go — written guides and recorded walkthroughs — with check-in sessions to answer questions once your team has read it; by September/October they work with the system on their own. Each phase lists what we need from you and what we deliver — and the durations are indicative, confirmed together at the start.
Setup
Everything we need to start — access, your standards, and the design itself. This phase is inputs and alignment; we don't hand over anything yet.
What we need from you
- → Access to your codebase and environment, and the people who own the front-end and Contentful
- → Your standards and conventions — how you build, review and deploy today
- → The components and page types to cover, confirmed
- → The visual direction — style, UI and brand — with type, color, spacing and the key screens or references (these design decisions are yours)
What we deliver
- → Nothing to hand over yet — phase 1 is inputs and alignment: together we lock the setup, the component architecture and the workflow
Initial design
We take the design you handed over and set it up in code, and build one full pilot page with its components — so you can validate the styles and the whole look and feel before we apply it across the other four pages. The design stays yours throughout.
What we need from you
- → Feedback as we set up your design in code
- → Validation that the page and its components match the look you want
- → Sign-off on the look and feel from Marketing and DBP
What we deliver
- → Your design set up in code as shared settings (type, color, spacing) — the foundation the components follow
- → One full pilot page and its components, built to your design — to validate the given styles and the whole look and feel
- → A validated look and feel to carry across the other four pilot pages
- → Any gaps or conflicts in the design flagged early, for you to decide
Execution & delivery
With the look and feel validated, we build the full component system and the remaining four pilot pages, reviewed together as we go, and deliver a working result.
What we need from you
- → Timely answers on design questions as they come up during the build
- → Review and approval on each component before it goes in
- → Real content and translations for the pilot pages
What we deliver
- → The full reusable component system (~22 React components) and the remaining four pilot pages, built to the validated look and feel
- → A working preview of the five pilot pages, to validate the result together
- → Basic system documentation as the components are built
Documentation & hand-off
Hand the system over so it stays inside Pix4D — to your developers to keep building, and to the company to own and run on its own. The knowledge transfer is documented, produced by us; the sessions with your team are to answer questions and clarify.
What we need from you
- → Your team to read and validate the documentation as it's produced
- → Availability for check-in sessions to go through questions
- → Where the documentation and repository live long-term, confirmed
What we deliver
- → Hand-off to your developers: documentation, the repository, and the workflow to keep building
- → Knowledge transfer, documented — written guides and recorded walkthroughs of the key processes
- → Check-in sessions to answer questions and clarify, once your team has read the material
- → Everything captured so the team runs the system on its own by September/October
Next
That’s the plan — four phases, each ending with something delivered. What it costs, and what’s optional beyond it, is next.