UI/UX design in Figma for websites, SaaS and apps

It depends on the number of screens or page templates, whether research and wireframes are included, the number of user flows, a design system, prototypes and the review rounds agreed. Designing a marketing site is a smaller job than designing a full SaaS product. We quote a fixed price after a call, with the scope written down.

Both. You can hire us for design only, and we hand over developer-ready Figma files with components, styles and specs. Or we design and build, which removes the hand-off gap because the people who designed it are the people who code it. Many clients start with design and continue into development.

The number of review rounds is set in the written scope, usually per stage: wireframes, key screens and the full set. In practice we agree the key pages first, then roll the approved style out to the rest, which keeps revisions focused and avoids redesigning everything late in the project.

Yes. We start with a UX audit of the current product: analytics, support tickets, usability issues and user feedback. Then we redesign the highest-impact flows first, such as onboarding, checkout or the main dashboard, so improvements reach users sooner instead of waiting for a complete redesign.

You get the Figma files with organized pages, components, variants, styles and tokens, an interactive prototype of the key flows, exported assets and handoff notes for developers. The files and all assets are yours to keep and edit, and we walk your team or developers through them.

In Figma, using comments directly on the screens, plus short review calls at each stage. We present designs with the reasoning behind them, collect your feedback in one place and confirm the changes in writing, so everyone knows what was decided and what comes next.