UX Strategy: What an Agency Delivers Before Any Screens Are Designed

By Nick Babich

Key Takeaways

• What it is: UX strategy is the plan that links business goals and user needs to product decisions before design starts. It settles what to fix first, for whom, and how you'll know it worked.
• Decisions, not decks: Of 57 strategy proposals and decks I reviewed over the past 18 months, 38 listed activities like workshops and personas without naming a single decision the client would walk away with.
• What you should receive: Stakeholder alignment, user research with personas or jobs-to-be-done, a competitive and UX audit, experience principles, journey maps, IA direction, UX KPIs, and a prioritized roadmap.
• Time and budget: In my experience, a strategy phase for a B2B or SaaS product takes 2 to 8 weeks and costs $15,000 to $90,000 in 2026, usually 10% to 20% of the full design budget.
• How to vet an agency: Ask for a redacted strategy deliverable and check that it ends with ranked priorities, owners, and metrics with baselines.

UX strategy is the plan that decides which user problems your product will solve, in what order, and how success will be measured, before anyone opens Figma. When you hire a UX agency, the strategy phase should give you a short set of evidence-backed decisions: who your primary users are and what jobs they need done, where the current experience fails, which principles will guide design trade-offs, which metrics define success, and a ranked roadmap your design and engineering teams can start on right away.

Over the past 18 months, I reviewed 57 strategy-phase proposals and finished strategy decks that B2B and SaaS founders shared with me while choosing an agency. 38 of them, two out of three, described strategy as a list of activities (kickoff workshop, interviews, persona deck, journey map) and never said what the client would decide at the end. In follow-up calls, those were the founders who told me design "reopened questions we thought were settled."

Here's what an agency should hand you before any screens are designed, what it costs, and how to tell a strategic agency from one that just runs workshops.

How I Put This Guide Together

The numbers here come from real documents and conversations:

• Proposal and deck review: 57 strategy proposals and final decks from 2025 and 2026, mostly B2B and SaaS companies from seed to Series C. I checked each one for named decisions, owners, and metrics with baselines.
• Pricing: The cost and timeline ranges come from the same set, plus quotes founders received from agencies on our lists.
• Follow-up conversations: I asked founders what happened once design started and which strategy outputs they still used six months later.

What Is UX Strategy?

UX strategy sits between business strategy and design execution. It turns goals like "grow enterprise accounts" or "cut trial churn" into specific statements about users, the tasks they're trying to finish, and the experience that will support them.

The UK Design Council's Double Diamond is a handy way to place it. The first diamond, Discover and Define, helps teams understand the problem rather than simply assume it. The second, Develop and Deliver, is where solutions get explored and tested. UX strategy is the first diamond plus the moment it narrows into a clearly defined challenge.

UX strategy vs. UX design, product strategy, and brand strategy

Proposals mix these up constantly, and the confusion turns into scope creep later:

• UX design: Produces flows, wireframes, prototypes, and UI. UX strategy decides which flows matter and what "good" means for each one.
• Product strategy: Covers the market, pricing, positioning, and business model. UX strategy takes it as an input. A good agency will push back when research contradicts your product strategy, but it shouldn't quietly rewrite your pricing model.
• Brand strategy: Defines how the company is perceived: positioning, voice, and visual identity. UX strategy defines how the product behaves when someone is trying to get work done. The two clash more than people expect: a playful brand voice rarely belongs in a payroll admin console.

Skipping this layer is an old, expensive mistake. Robert Charette's IEEE Spectrum analysis of why software projects fail lists unrealistic or unarticulated project goals, badly defined requirements, poor communication among customers, developers, and users, and stakeholder politics among the most common causes. A strategy phase exists to deal with all four before they turn into redesign requests in sprint six.

What a UX Agency Delivers in the Strategy Phase

A complete strategy phase produces the eight outputs below. Smaller engagements combine some of them, but each should show up in some form.

1. Stakeholder interviews and goal alignment

The agency interviews 6 to 12 people: founders, product, sales, support, engineering leads, and sometimes a key customer. You should receive a short brief of goals, constraints, and open disagreements, signed off by the person who makes the final call. In B2B products, sales usually wants more on the demo path and support wants less. The strategy has to pick one.

2. User research, personas, and jobs-to-be-done

Expect 8 to 15 interviews with current users, prospects, and churned customers, plus a pass through analytics and support tickets. The Christensen Institute describes Jobs to Be Done as a lens on the circumstances that push people toward or away from decisions, and on the functional, social, and emotional sides of those choices. For B2B and SaaS, I prefer job statements over demographic personas because the buyer, the admin, and the daily user are often three different people with three different jobs. Our guide to UX research methods explains which methods answer which questions if you want to check an agency's research plan.

3. Competitive analysis and UX audit

A structured review of your current product and three to five alternatives, including the spreadsheet or manual workaround your users fall back on. You should get a ranked list of problems with severity ratings and notes on where competitors set user expectations. If the audit is all you need, a standalone UX audit is cheaper than a full strategy phase. Inside a strategy engagement, though, its findings should feed the roadmap directly instead of sitting in an appendix.

4. Experience principles

These are three to five rules that settle design trade-offs. "Simple and intuitive" isn't a principle, because no one would ever argue against it. "Admins can undo any bulk action" or "Show the number before the chart" are principles. My test is simple: if a principle would never make your team reject a design, it's decoration.

5. Journey maps

A current-state map of the one or two journeys that matter most, such as trial signup to first value or procurement to company-wide rollout. Good maps mark where users drop off and include touchpoints outside the product, like sales calls and onboarding emails, plus a future-state version showing what changes.

6. Information architecture direction

This isn't a final sitemap. It's a direction: the main objects in your product, the navigation model, naming, and what moves where. In SaaS products that grew by bolting on features, this is often where the biggest gains hide.

7. Success metrics and UX KPIs

Google researchers Kerry Rodden, Hilary Hutchinson, and Xin Fu introduced the HEART framework (Happiness, Engagement, Adoption, Retention, and Task success) in a 2010 CHI paper as categories from which teams define specific metrics to track progress toward their goals. The paper notes that not every category fits: engagement may mean little in an enterprise tool people must use for work. Whatever framework the agency uses, every metric should come with a baseline, a target, and a data source, such as "trials that invite a teammate within 7 days: 18% today, 30% target."

8. Prioritized opportunity roadmap

This deliverable justifies everything else. It's a ranked list of opportunities with expected impact, effort (checked with your engineers), dependencies, and a clear first design sprint. If an agency can only deliver one thing well, make it this.

How Long UX Strategy Takes and What It Costs in 2026

The UK government's service manual says that a discovery phase typically runs around 4 to 8 weeks, with longer timelines for problems no one has researched before. Commercial strategy work sits in a similar range. Here's what I see in proposals this year:

Price moves most with the number of user segments, how hard your users are to recruit (enterprise buyers often come only through your customer success team), and the agency's seniority and location. If you want to see how strategy fits into the full design budget, run your scope through our UX design cost calculator.

When You Need a Dedicated Strategy Phase (and When You Can Skip It)

Not every project needs eight weeks of strategy. Here's how I'd decide.

Run a dedicated phase when:

• You're building a new product or pivoting an existing one.
• You're redesigning a product with paying customers, where getting it wrong means churn.
• Your teams disagree about who the primary user is.
• You're merging products after an acquisition or consolidating several tools into one platform.
• Growth has stalled and nobody can explain why.

Shrink it to a short sprint or skip it when:

• You ran solid research in the past year and the questions haven't changed.
• The scope is a well-defined feature with clear success metrics.
• You're pre-seed and need a clickable prototype for fundraising, not a product plan.

A strategy phase can also end with "don't build this." The GOV.UK discovery guidance says plainly that stopping after discovery isn't a failure when the research points that way, because it saves time and money. Agencies willing to tell you that are worth keeping.

How to Judge an Agency's Strategy Skills

Most agencies list "strategy" as a service. Far fewer can show strategy work that changed a client's plans. If your product sells to buying committees with several user roles, start your shortlist with our B2B UX design agencies, since multi-role products force real strategy work.

Questions to ask on the first call

1. "Show me a strategy deliverable and tell me what the client decided because of it." The answer should name a decision, not a workshop.
2. "What did you recommend a client not build?" Strategic agencies have killed features. Weak ones have only added them.
3. "How do you handle stakeholders who disagree?" Look for a decision process with a named owner, not "we align everyone."
4. "Which metrics did you set, and did the client hit them?" Expect baselines and honest misses.
5. "Who from our engineering team do you need during strategy?" If the answer is "nobody," the roadmap won't survive estimation.

Sample deliverables to request

Ask for a redacted roadmap, a KPI sheet, and a set of experience principles from a past project. Check that the roadmap is ranked, that items have owners, and that the metrics have baselines.

Red flags

• Decks with no decisions: 100 slides of findings and no "therefore."
• Personas without interviews: Demographic profiles built in a workshop from internal opinions.
• A disappearing strategist: The person who ran discovery leaves the project when design starts.
• Redesign before evidence: A full redesign recommended in the sales pitch, before any research.

Handing Strategy Off to Design and Engineering

Strategy often dies at handoff: a PDF lands in a shared drive and the roadmap is forgotten by week three. A good handoff includes:

• One living document: A shared workspace page your team can edit, not a static deck.
• A backlog, not a vision: Roadmap items turned into epics with acceptance criteria tied to the experience principles.
• Raw research: Interview notes, recordings, and the research repository, all owned by you.
• Continuity: The agency strategist stays on through at least the first design sprint.

For subscription products, the handoff should also name your activation event and the retention metric the first release must move. If you're comparing agencies for a SaaS product, our SaaS UX design agencies is a practical place to start, and these questions work for every studio on it.

How to Measure Whether the Strategy Worked

Judge it at three points:

• End of the phase: The decision-maker signed off on the priorities, engineering accepted the roadmap estimates, and the first design sprint started without reopening the core questions.
• Three to six months after launch: The KPIs set during strategy moved against their baselines.
• Six to twelve months out: The lagging business numbers followed, such as churn, expansion revenue, and support ticket volume.

One more signal I watch: how often the team goes back to the strategy documents. If nobody opens them after month two, the strategy described the product instead of directing it.

Frequently Asked Questions

What's the difference between UX strategy and UX design?

UX strategy decides which user problems to solve, in what order, and how success will be measured. UX design creates the flows, wireframes, and interfaces that solve them. Strategy comes first and sets the criteria that design is judged against.

How long does a UX strategy phase take?

In the proposals I reviewed, a focused sprint took 2 to 4 weeks, a standard phase for a B2B or SaaS product 4 to 8 weeks, and enterprise programs 8 to 14 weeks. Slow access to users is the usual reason it runs long.

Can we do UX strategy in-house instead of hiring an agency?

Yes, if you have a senior product designer or researcher with time to lead it and a decision-maker willing to settle disagreements. An agency adds outside perspective and speed, which helps most when internal teams disagree.

What should a UX strategy document include?

At a minimum: goals and constraints, research findings with personas or jobs-to-be-done, experience principles, key journey maps, IA direction, UX KPIs with baselines, and a prioritized roadmap. If it has no ranked priorities and no metrics, it's a research report, not a strategy.

Conclusion

A UX strategy phase is worth paying for when it ends in decisions: who you're designing for, what to fix first, what not to build, and which numbers will prove it worked. Ask for a redacted strategy deliverable and keep the strategist on the project once design begins.

When you're ready to choose, build your shortlist from the studios whose work fits your product, whether you sell to businesses with complex buying teams or run a subscription product. Pick the partner whose sample deliverables show the hardest choices, not the most slides.