Most SaaS products ship with the right features but the wrong experience. Users drop off, support tickets pile up, and the team keeps patching symptoms instead of fixing the root.

I start every project by finding where the real friction is. Not by guessing, but by looking at how users actually move through your product. Then I design screens that fix it, with full Figma files and documentation your engineers can build from.

At SalesHandy I took a 2.5-star product to 4.5 stars without adding a single feature. At Amagi I led design from MVP to final product for a MediaTech unicorn. The work speaks for itself.

Here is the complete description, section by section. Update each part separately in Contra.

Most SaaS products ship with the right features but the wrong experience. Users drop off, support tickets pile up, and the team spends months patching symptoms instead of fixing the root.

I start every project by finding where the real friction is. Not by guessing, but by looking at how users actually move through your product. Then I design screens that fix it, with full Figma files your engineers can build from without asking questions.

At SalesHandy I took a 2.5-star product to 4.5 stars without adding a single new feature. At Amagi I led design from MVP to final product for a MediaTech unicorn. At VenueVista, booking-related support calls dropped 60% after launch.

If your product works but does not perform, that is exactly the problem I solve.

Before I open Figma, I need to understand your users, your business goals, and where the current experience is breaking down. This happens through a briefing call, a short questionnaire, or a review of any existing documents you have. You will walk away from this phase with a shared understanding of what we are solving and why.

I turn everything from discovery into a clear written document. It covers the must-have features, user roles, key workflows, and the success metrics we are designing toward. This becomes the single source of truth for the project so no one has to guess what we agreed on.

You will get a realistic project timeline with milestones and review checkpoints before any design work starts. No surprises. You will always know what is being worked on and when to expect it.

This is the main deliverable. High-fidelity screens built in Figma, including interactive prototypes, annotated components, and all assets ready for development handoff. Every screen covers the key states: empty, loading, error, and filled. Your engineers will not have to guess what anything is supposed to do.

A full guide covering every component, color, typography style, spacing rule, and interaction pattern used in the product. This means your team can build new screens later without starting from scratch or breaking what already exists.