Process breakdowns

Design-to-build handover without the rework

The gap where most agency projects lose two weeks, and the handover format that closes it.

5 min read

The gap: most agency projects lose real time in the handoff between finished design files and the first line of code, not because the design is wrong, but because a static mockup doesn't specify things a browser actually needs to know, how a component behaves at every breakpoint, what happens on hover versus focus versus active states, what the loading and error states look like when nobody designed them because they're not the happy path.

What closes it: a handover format that ships alongside the visual design, not after it, covering the states a Figma file doesn't show by default: every interactive element's full state set, spacing and type as tokens rather than eyeballed pixel values, and a written note on intended behavior anywhere the design implies motion, transition, or a decision the file itself can't fully express.

Where this comes from: Bona's own build process treats design and development as one continuous handoff rather than two separate phases with a wall between them, the same instinct behind embedding brand identity directly into product builds like Rising Collectively rather than layering it on afterward. A handover document is really just that same principle, written down.