How a UX Design Agency Works: The Process From Discovery to Launch

A UX design agency engagement follows five phases: discovery and research, strategy and architecture, design and iteration, handoff and implementation support, and design QA. Each phase produces specific deliverables and informs the next. The quality of the first phase determines the accuracy of every design decision that follows. Most failed design engagements skip or compress the first phase to start producing screens faster. This guide explains what actually happens inside each phase, what you as a founder should be doing at each stage, and how the embedded model changes this process for the better.

What Are the Five Phases of a UX Design Agency Engagement?

A UX design agency engagement follows a consistent sequence regardless of the specific product or scope. The phases are: discovery and research, strategy and information architecture, design and iteration, handoff and implementation support, and design QA and launch review. Some agencies compress these into fewer phases or rename them, but the underlying work is consistent across any engagement that produces high-quality outcomes.

Understanding the sequence helps you evaluate agencies more accurately. An agency that proposes skipping discovery to start producing screens in week one is proposing to design without insight into your actual users. An agency that ends the engagement at handoff is proposing to let engineering resolve all the implementation questions the handoff file cannot answer. Both are warning signs that the engagement will produce lower-quality shipped outcomes than the designs promise.

What Happens During the Discovery and Research Phase?

What Does a UX Design Agency Do in the First Week?

Discovery begins with a kickoff session where the agency develops a detailed understanding of the product, the business context, and the design problems to solve. This is not a sales meeting: it is a structured information-gathering session covering the product's current state, the user types it serves, the metrics that define success, and the specific flows or screens that are the highest priority for the engagement.

Following the kickoff, a discovery phase for a SaaS product typically includes user interviews with five to eight current or target users. The Nielsen Norman Group's research on user testing established that five users identify approximately 85 percent of usability problems in a product, making this a cost-effective research investment even for early-stage products. Interviews explore what users are trying to accomplish, where they currently struggle, and what would make the product significantly more useful in their workflow.

Discovery also includes review of existing product analytics to understand where users drop off, which features are underused, and which flows have the highest task completion rates. Even basic analytics data (page views, session recordings, funnel drop-off percentages) provides directional insight that prevents designing solutions to problems that users do not actually have.

What Does the Discovery Phase Produce?

Discovery produces a research report documenting key findings from user interviews and analytics review, a user journey map showing the current experience and its friction points, a list of design implications (what the research says the design should address), and a prioritized list of design problems for the engagement to solve. The research report is the foundation on which all subsequent design decisions are built. If the design decisions later prove incorrect, the first place to look is the discovery work that preceded them.

What Happens During the Strategy and Architecture Phase?

How Does a UX Design Agency Define the Product Structure?

After discovery, the agency defines the information architecture: how the product is organized, what navigation hierarchy it uses, how users move between sections, and how content is grouped and labeled. Information architecture decisions happen before any screen is designed and determine whether users can find what they need without asking for help. A poorly structured product produces support tickets, user frustration, and churn from users who could not find a feature they needed. A well-structured product feels intuitive because the structure reflects the user's mental model of the tasks they are trying to accomplish.

For SaaS products with multiple user roles, the strategy phase also defines the role-specific navigation: which sections each role sees, what each role's landing state looks like after login, and how the product presents different content to different users. For how the SaaS product design process integrates strategy and architecture decisions with the full design workflow, the SaaS product design process guide covers the complete framework from discovery through delivery.

What Does a UX Design Agency Produce in the Architecture Phase?

The architecture phase produces a sitemap or navigation map documenting the product's organizational structure, user flow diagrams showing how each user type moves through the key journeys, and a content inventory defining what information appears at each screen and in what hierarchy. These deliverables are reviewed with the founding team before any wireframing begins. Structural changes are fast and cheap at this stage. They are expensive and disruptive after engineering has built screens based on an architecture that later proved incorrect.

What Happens During the Design and Iteration Phase?

How Does a UX Agency Move From Structure to Design?

With architecture approved, the design phase begins with wireframing: structural blueprints for each key screen that show layout and hierarchy without visual styling. Wireframes let you evaluate the logic of each flow quickly and make structural changes before the cost of visual design is invested in the wrong direction.

After wireframe review and approval, the agency builds an interactive prototype: a clickable simulation of the core user flows that can be tested with real users. Prototype testing is one of the highest-return investments in any design engagement because it identifies flow logic problems and user comprehension gaps before engineering time is spent building the wrong thing. A single usability test session with five users before development begins is faster and cheaper than a sprint of engineering rework after launch.

Following prototype validation, the agency produces high-fidelity design files: the final visual design for every screen in scope. High-fidelity designs cover all interactive states for every component (default, hover, focused, loading, error, success, disabled), all empty states for new users, and all responsive breakpoints for mobile and tablet where relevant. For how high-fidelity wireframes and designs are organized for maximum engineering clarity, the high-fidelity wireframes guide covers the file organization and component documentation standards that make handoff reliable.

What Does a UX Agency Do When the Initial Design Direction Does Not Work?

Good UX design agencies expect this and have a clear process for it. When user testing shows a design direction is not working (users are confused by the navigation, cannot complete a task, or misunderstand the product's value), the agency goes back to the research findings to identify which assumption was incorrect. It re-frames the design problem with the new insight and iterates on the direction. This might mean revising the wireframes, restructuring the flow, or rethinking the information architecture. It does not mean starting over from zero: the research and the structural thinking remain valid even when the first design execution of that structure proves incorrect.

An agency without a defined process for handling a wrong initial direction has not thought through what happens when design gets hard. Ask every agency you evaluate: what do you do when user testing shows the first design direction does not work?

What Happens During the Handoff and Implementation Phase?

What Should a Complete UX Design Handoff Include?

A complete developer handoff is significantly more than a shared Figma link. It includes annotated design files with spacing and sizing specifications using design tokens, documented interaction behavior for all animations and state transitions with specific timing values, responsive breakpoint specifications for every screen, accessibility annotations covering ARIA attributes, keyboard behavior, and focus management requirements, a component library mapped to the engineering codebase, and a written document explaining any design decisions that required judgment calls the engineer should preserve during implementation.

The annotations are what make the difference between an implementation that matches the designs and one that approximates them. An engineer who sees a specific animation timing value (150ms ease-in-out) can implement it precisely. An engineer who sees a description ("the dropdown opens with a subtle animation") implements their interpretation of subtle, which may or may not match the designer's. Precision in handoff annotations directly determines precision in implementation.

How Should a Founder Stay Involved During Engineering Implementation?

During implementation, the founder's job is to create the conditions for the designer to stay involved. This means including the designer in engineering standups where implementation decisions are made, setting the expectation with engineering that design questions should be brought to the designer immediately rather than resolved independently, and ensuring the designer has access to the staging environment throughout the build period so they can catch issues early rather than in a single QA session at the end.

In the embedded model, this involvement is built into the structure of the engagement. The designer is already in the standup, already in Slack, and already available for real-time questions. In a project-based engagement, this involvement requires intentional management from the founder to bridge the gap between design and engineering teams that would otherwise be separated.

What Happens During Design QA and Launch?

Why Is Design QA the Most Commonly Skipped Phase?

Design QA requires time from both the designer and engineering after a build is complete, which puts it directly in competition with the next sprint's feature development. The natural pressure of a fast-moving startup is to ship and move on. This pressure is what causes design QA to be skipped most often, and it is also what causes products to accumulate visual and interaction inconsistencies over time.

A single design QA pass before a major feature ships takes one to two days and catches the gaps that would otherwise reach users. The most common gaps found in design QA: spacing values that are close but not correct (8 pixels instead of 12, visible in density comparisons with the design), interactive states that were built for the default case but not for all states (a focused input field without the correct focus ring, a button without its loading state), and empty or error states that were not in scope and were therefore not built. Each of these gaps individually is minor. Accumulated across twelve months of feature releases, they are the difference between a polished product and an unpolished one. For how UX audit work connects to ongoing design quality, the UX audit services guide covers how structured audits identify and prioritize accumulated quality gaps.

How Does the Embedded Model Change This Process?

In the embedded model, the five phases described above are not sequential sprints that end before the next begins. They are continuous parallel tracks. The designer is in your team for discovery, architecture, design, implementation, and QA simultaneously, advancing each track as the product develops rather than completing one before starting the next.

This means design decisions are made in real time when engineering encounters constraints. It means architecture is revisited when new product requirements reveal gaps in the original structure. It means design QA happens continuously as features are built, not as a single gate at the end of a project engagement. The result is a shipped product that consistently matches its designs because the designer was present for every decision that could have caused a gap.

Foundey works exclusively in the embedded model. For how the embedded model applies to different product stages and team configurations, the embedded design team guide covers the evaluation framework. For a view of how the process works across real SaaS product engagements, visit the case studies page. For a free review of your product's current design and where the process gaps are creating quality issues, book a free UX audit. To discuss how the embedded model could work for your product, book a free call.

Frequently Asked Questions

What is the typical process for a UX design agency engagement?

Five phases: discovery and research, strategy and information architecture, design and iteration, handoff and implementation support, and design QA and launch review. The quality of the first phase (discovery) determines the accuracy of every subsequent design decision.

What happens during the discovery phase?

Kickoff session to understand business context, user interviews with five to eight real users, product analytics review, competitive analysis, and synthesis into prioritized design implications. Produces a research report, user journey map, and design problem priority list.

How long does each phase take?

Discovery: one to two weeks. Strategy: one to two weeks. Design: two to six weeks depending on scope. Handoff and implementation: concurrent with engineering, two to eight weeks. Design QA: one to two weeks per major release. MVP full cycle: four to eight weeks. Full product with design system: six to twelve weeks.

What should I as a founder do during a UX agency engagement?

During discovery: provide access to users, analytics, and product knowledge. During design: give specific, actionable feedback at each review milestone. During implementation: keep the designer involved when engineering questions arise. The engagement quality correlates directly with how available and specific the founder is at each stage.

What is the difference between a wireframe, a prototype, and a final design?

Wireframe: structural blueprint without visual styling. Answers "is this the right structure?" Prototype: interactive simulation of the flow. Answers "does this flow work in use?" Final design: full visual system applied to approved structure, covering all states. Answers "does this look and behave correctly for production?"

How does a UX agency handle developer handoff?

Complete handoff: annotated Figma files with spacing specs using design tokens, documented interaction behavior with timing values, responsive breakpoint specs, accessibility annotations, component library mapped to the codebase, and design QA after engineering builds. A shared Figma link without annotations is not a complete handoff.

What is design QA and why does it matter?

A structured review of the live build against approved designs after engineering implements the feature. Identifies discrepancies in spacing, interactive states, missing edge cases, and implementation gaps before users encounter them. Products that skip design QA consistently accumulate visual inconsistencies with every release.

What happens if the initial design direction does not work?

A good agency goes back to the research to identify which assumption was incorrect, re-frames the design problem, and iterates with the new insight. This is normal in design. Ask every agency you evaluate how they handle this scenario. An agency without a clear answer has not thought through what happens when design gets difficult.

How is the embedded UX design process different?

The five phases run continuously in parallel alongside engineering rather than sequentially. The designer is in Slack and standups, making real-time decisions as engineering encounters constraints. There is no handoff moment because the designer is never absent from the implementation process. This eliminates the timing gap that causes most discrepancies between designed and shipped products.

What should I prepare before starting with a UX design agency?

Access to product analytics, a list of user types, existing user feedback or support tickets, the specific flows to prioritize, and a measurable definition of a successful engagement. The clearer the starting context, the faster the discovery phase, and the sooner high-quality design work begins.