For agencies · Design delivery

Your design, built as drawn.

The fear every design agency has about handing work to a developer is that it comes back approximately right. Spacing that drifted, type that was substituted, the interaction that was quietly dropped.

Figma, Sketch or XD Built to the design Problems raised, not hidden Your brand throughout
The handover problem

Approximately right is the usual outcome.

A design agency sells judgement. The spacing is deliberate, the type scale is deliberate, and the reason one element sits slightly off the grid is deliberate. Then it goes to a developer who treats the file as a suggestion, and it comes back with the type substituted, the rhythm gone and nobody quite able to say why it looks cheaper.

Most of that is not laziness. It is a developer meeting something genuinely difficult to implement — a layout that breaks at an awkward width, an animation that will fight the browser — and solving it silently rather than coming back to ask.

Our rule is that we raise it instead. If something in the design will cause a problem once it is real, you hear about it while there is still time to decide, and the decision stays yours. That is slower than quietly simplifying and it is the only way the thing you drew is the thing that ships.

How we work with you

What handover actually looks like.

From your files

Figma, Sketch, XD or a written brief. We work from what you have rather than asking you to redo it in our preferred tool.

Type and spacing honoured

The scale you set, not approximated. If a typeface cannot be licensed for web we tell you before the build rather than substituting it.

Problems raised early

A layout that breaks at 900px, an interaction that will be painful on a phone. You hear about it while it is still cheap to change.

Responsive decisions shared

Designs rarely cover every width. Rather than invent the in-between states we agree them with you.

Built to be edited

So your client can update content without the design falling apart, which is what protects your work after handover.

Nothing branded by us

No credit in the footer, nothing in the code, nothing in the documentation. Your client sees your agency.

Straight answers

Where we will push back.

When a design will not survive content

A layout that works with the ideal heading breaks with a real one. We will show you where, and suggest how to hold it.

When something is very expensive

Some effects cost ten times what they look like they should. We will tell you the price rather than absorb it or drop it silently.

When accessibility is at risk

Contrast below AA, or an interaction that cannot be used by keyboard. We will say so, and propose an alternative that keeps the intent.

Questions

What design agencies ask.

Will you change our design?
Not without asking. Where something will cause a real problem we come back with the issue and a suggested alternative, and you decide. The failure mode we are avoiding is a developer who silently simplifies and presents it as finished.
What if the design does not cover every state?
Most do not, and that is normal. We list what is missing — error states, empty states, awkward widths — and either you design them or we propose something and you approve it. What we will not do is invent them and hope.
Do you need designs in a particular format?
No. Figma is easiest because we can read the actual values rather than measuring, but Sketch, XD or a well-written brief all work.
Can you join client calls?
If it helps, as part of your team and under your brand. Plenty of agencies prefer the technical answers coming straight from the person who built it. We do not contact your clients independently.
Next step

Send us a design and we will tell you what it involves.

Including the parts that will be awkward and what they would cost. We would rather have that conversation before you have quoted your client than after.