01A file that cannot be built
Figma makes it easy to draw a screen and show it. It also makes it easy to forget what turns it into an interface: states, content limits, breakpoints, focus, keyboard and the difference between what is seen and what can be built.
An approved file is not a finished interface. If the empty, error, loading and mobile states are missing, someone invents them during implementation. That is not a design detail: it is debt that appears in QA and support.
The problem is not Figma. It is using Figma as a gallery of screens instead of a system of decisions.
A file that does not say what is reused, what changes and what is out of scope is not ready to build. It is ordered before it reaches code.
02When it helps and when it does not
It can help
- There are several screens or flows, not just one marketing page.
- Design and development have to work from the same system, not from loose screenshots.
- The brand or product already exists and needs judgement: colour, type, spacing and states.
- A flow or an idea has to be validated before investing in implementation.
- The Figma file exists, but production has drifted away from it.
- Accessibility is meant to be decided in design, not patched at the end.
It does not help
- You only need a landing page or a corporate page: that is Web design and landing pages.
- There is no product, brand or decision to order: the problem comes first.
- You want a mock-up to show, not to build.
- You need large-scale user research or testing: that is scoped separately and does not always fit.
- No one can validate the work and there is no implementation destination.
- The team already has a working system and only needs one new screen: reuse it, do not rebuild it.
The four decisions
-
01
Keep and audit
If the file already works, the gap with production is reviewed and what fails is fixed. A system that only needs order, states or handoff is not rebuilt.
-
02
Order a system
When every screen is drawn from scratch, the system is defined: components, tokens, states and rules. It has the most upfront work and prevents the same problem on the next screen.
-
03
Handoff only
If the design is resolved and what is missing is that development can implement it, the file is prepared: tokens, measurements, states, content and acceptance criteria. No redesign by inertia.
-
04
Do not use Figma
If it is a simple page, the theme and HTML/CSS solve it sooner with less maintenance. Figma is not added as a ceremonial requirement.
03What we do in Figma
Figma is not the deliverable. The deliverable is a system that can be used to build and maintain the interface.
-
01
Inventory of existing flows, screens and components.
Go to UI/UX and branding -
02
Visual system: colour, type, spacing and states.
Go to UI/UX and branding -
03
Reusable components and variants in Figma.
Go to UI/UX and branding -
04
A prototype to validate the flow, not to decorate.
Go to UI/UX and branding -
05
Accessibility in the file: contrast, focus, targets and content.
Go to UI/UX and branding -
06
Tokens and handoff to the product stack.
Go to Custom web development -
07
Usage notes and limits.
Go to UI/UX and branding -
08
Visual QA against production.
Go to Custom web development
04From file to production
A design does not reach production by exporting a PDF. It reaches production when the team can implement it without asking and check that it matches the approved file.
What can be measured
- Colour contrast and focus states in the built interface.
- Keyboard navigation and reading order.
- 200% zoom without losing content or controls.
- Component coverage: which screens use the system and which do not.
- Differences between Figma and production at the agreed breakpoints.
What cannot be promised
- Conversion, retention or sales: design supports the result, it does not guarantee it.
- “Pixel perfect†if the file changes every week or has no defined states.
- That a design is accessible just because it is in Figma: it has to be reviewed and tested.
- A fixed date before seeing how many screens, flows and components there are.
Maintenance
A system drifts. Someone has to own it, components have to be versioned and tokens have to be reviewed when the brand changes. If no one maintains it, the file separates from production again within weeks.
Price and delivery
Quoted after the inventory. It depends on flows, screens, components, branding, the implementation part and documentation. There is no fixed rate before reviewing the case.
See UI/UX and branding05Proof: declared capability
Declared capability. We do not publish cases, conversion metrics or “designs that work†without permission.
The evidence is the system, the documentation and the correspondence between Figma and production. If there are publishable cases, they will appear with source and date; until then, they are not invented.
This page explains when Figma fits and when it does not. It is not a claim of accredited experience or a promise of results.
See the projects06Frequently asked questions
Does Figma replace the designer or the developer?
No. Figma is a design and collaboration tool: it does not decide the product or implement the interface. It helps order decisions so design, content and development talk about the same file.
Do you only design, or do you also implement?
It depends on the scope. We can deliver the system in Figma with tokens and handoff, or implement the interface in HTML/CSS or WordPress. Full product or app development is a separate service and is quoted separately.
Figma or Framer?
Figma fits interface work, a component system and collaboration. Framer can fit a specific marketing or motion piece. It is not chosen by fashion: it is chosen by what has to be built and who will maintain it.
What do you need to start?
Product or brand, access to the file if it already exists, real examples, one person to validate and the implementation destination. If something is missing, it is logged as a dependency and resolved before design starts.
How much does it cost and how long does it take?
Quoted after ordering flows, screens and components. There is no fixed rate or date before the inventory: the price depends on scope and on whether implementation or only handoff is included.
Is a Figma design accessible?
Accessibility is decided in design but verified in production. In Figma we review contrast, focus, touch targets, hierarchy and content limits; after that it is tested with a keyboard, zoom and real content.
Do you work with an existing Figma file?
Yes. We audit it, order it and decide what to reuse and what to retire. We do not rebuild by default or deliver a new sheet if the problem was the system or the handoff.