Handover & Training

What do you get at handover?

Everything your team needs to run, change and extend what we built, without having to call us:

• A Figma library with the components, variables and styles used in the product
• Clean code in your own repository, with the components and any custom logic documented
• Short recorded walkthroughs of your own site or product, not generic tutorials
• A live training session with the people who will do the day-to-day work

A good handover means you only call us because you want to, not because you have to.

Can another developer or designer take over?

Yes. We build with that in mind from the first day:

• The same names for components in Figma and in code, so designers and developers talk about the same thing
• Consistent, readable code without hidden dependencies on us
• Tokens in one place, so a new designer can change the brand safely

What does the process look like?

1. Plan it early. We agree at the start who will own what after launch, and design the handover around those people.
2. Document as we build. Documentation is written alongside the work, while the decisions are fresh.
3. Train on your real product. Sessions use your own pages and features, recorded so new joiners can watch them later.
4. Stay reachable. A short support window after launch for questions, then help only when you ask for it.

What is the most common mistake?

Treating handover as the last day of the project. When it is an afterthought:

• The team inherits something they are afraid to touch
• Small changes turn into expensive agency requests
• The product slowly drifts away from the design it launched with

Handover is the moment a project becomes yours. We plan for it from day one.