Do you do design-only engagements, or only alongside development?
Both. We run standalone design engagements, Figma files, prototype, handoff documentation, for teams that have their own engineers. We also run design-and-build projects where the same studio handles both. The second is smoother because the designers and engineers work in the same sprint cycle with the same Slack channel.
What do you deliver, and in what format?
Figma files with organised layers, auto-layout components, design tokens and Dev Mode annotations. A prototype for user testing (Figma or Protopie). A handoff doc covering responsive breakpoints, motion specs and component states. Optional: a Storybook integration walkthrough with your front-end team. Everything is in Figma, shareable with a link, no licence required on your end.
How do you handle design changes during engineering?
We stay available throughout the build for implementation questions and design tweaks. Ambiguity discovered during engineering is resolved in the Figma file and documented as a change, not handled verbally and forgotten. We batch small changes into weekly design reviews rather than trickling them in through Slack, which keeps the engineering rhythm intact.
Can you work with an existing brand and design system?
Yes. We adapt to your existing tokens, components and brand guidelines. We also audit existing design systems for inconsistencies and missing components before starting new work, so we're building on a solid foundation rather than silently extending a broken one.
Do you do accessibility?
Yes, WCAG 2.2 AA compliance is a baseline requirement on every project, not an add-on. Colour contrast, keyboard navigation specs, focus states, screen-reader annotations and ARIA label guidance are included in every handoff file. We test with VoiceOver and NVDA before handoff on critical user flows.