How to Write a UX Audit Proposal Clients Understand

What is a UX Audit Proposal?

A client tells you their website isn't converting as well as expected. They've spoken to a few agencies, reviewed some redesign proposals, and received wildly different recommendations. One agency wants to rebuild the homepage. Another suggests changing the navigation. Someone else says the entire experience needs rethinking. Nobody has clearly explained what's wrong with the existing website. This is where a UX audit proposal can make a difference. Instead of immediately recommending a redesign, you offer to investigate the website's usability problems, explain their potential impact, and identify what should be improved first. But selling an audit requires more than promising a detailed report. Your proposal needs to explain what the client will learn, what work you'll perform, what they'll receive, and what happens afterward. A strong proposal answers five questions: 1. What problem are we trying to understand? 2. Which pages and user journeys will be evaluated? 3. How will the evaluation be conducted? 4. What will the client receive? 5. What decisions will the findings help inform? The proposal shouldn't promise that every business problem will be solved through UX improvements. Its purpose is to establish a sensible evaluation process.

Start with the Client's Problem, Not Your Services

Many proposals begin with a long introduction about the agency. They explain the team's experience, design philosophy, tools, and methodology before discussing what the client actually needs. That makes the document feel more like a sales brochure than a useful project proposal. Start with the problem instead. For example: "Your website attracts visitors, but the current enquiry journey may contain usability issues that make it difficult for potential customers to take the next step. This audit will examine the key pages and interactions involved in that journey, identify observable friction points, and recommend improvements for your team to evaluate." Notice what this does: it acknowledges the client's concern without claiming to know the cause before conducting the audit, while establishing a meaningful outcome: a clearer understanding of the experience and a prioritized list of possible improvements.

• Who is the website designed for and what are visitors supposed to accomplish?
• Which pages or conversion journeys matter most to business revenue?
• What friction points has the client or their support team already noticed?
• What analytics, funnel data, or user recordings are available to review?
• Are there technical, budgetary, or scheduling constraints to account for?

Define the UX Audit Scope and Explicit Exclusions

Without a defined scope, a client may expect a complete evaluation of every page, feature, device, and user journey. An agency may have intended to review only the homepage and primary conversion flow. That difference can create friction before the project is finished. Here is a practical scope breakdown for a B2B SaaS website:

• Exclusions to state explicitly: User interviews, formal accessibility (WCAG) certification, technical code refactoring, analytics instrumentation, and full Figma redesign mockups.
• Why exclusions matter: Stating what is out of scope is not a weakness—it gives the client complete confidence in what they are purchasing.

Explain Your Methodology in Plain English

Clients don't necessarily need a long explanation of every UX framework, but they do need to understand how your findings will be produced and validated:

• 1. Review the selected experience: Examine agreed pages, navigation paths, forms, and relevant interactions.
• 2. Evaluate usability patterns: Assess consistency, clarity, feedback, error prevention, and cognitive load using frameworks like the Nielsen Norman Group 10 usability heuristics.
• 3. Document observable issues: Record findings with screenshots, visual hotspot coordinates, explanations, and supporting context.
• 4. Prioritize recommendations: Balance severity, the importance of the affected journey, confidence in evidence, and engineering effort.
• 5. Present the findings: Host a walkthrough to explain critical friction points and help stakeholders plan immediate fixes vs. roadmap initiatives.
• Transparent tool disclosure: If using automated heuristic tools or AI scanners, explain that automated checks support initial inspection, while experienced designers validate findings and tailor recommendations to the client's goals.

Show the Client What Deliverables They Will Receive

A client shouldn't have to imagine what a UX audit report looks like. Detailing the exact deliverables gives stakeholders peace of mind:

Include a Real Report Example in Your Proposal

Showing a sample report makes your proposal substantially easier for clients to evaluate. It demonstrates the clarity of your findings, shows how issues are prioritized, and confirms the deliverable will be useful for their internal developers and designers. For agencies using My Design Audit, you can link directly to a white-label demonstration report: Explore the Outseta White-Label Demonstration Report This sample report illustrates how website UX findings, visual hotspots, and prioritized recommendations can be presented under an agency's branding without manual formatting overhead.

• Explore the Outseta White-Label Demo Report
• Read our Guide to White-Label UX Audit Reports
• Browse All Interactive Sample Reports

How to Structure Pricing and Estimate Effort

Pricing should reflect project scope and required hours. A focused review of marketing pages requires far less effort than a multi-tier SaaS onboarding flow. Estimate effort across core activities before quoting a fixed project fee:

• Fixed project fees work best when scope is tightly bounded, with separate hourly terms for follow-on implementation.
• For detailed industry benchmarks on agency vs. freelance pricing tiers ($1,000 to $15,000+), read our complete guide on UX audit costs.

Setting a Realistic Project Timeline

Clients appreciate knowing delivery dates upfront, but offering a fixed turnaround without scoping creates pressure. Break the schedule into transparent milestones:

An 8-Part UX Audit Proposal Template You Can Adapt

Use this structured outline as a starting point for client proposals:

• 1. Project Background: Summarize client goals, current conversion challenges, and reasons for the audit.
• 2. Project Objective: Define the purpose: uncover usability obstacles, evaluate friction, and recommend prioritized fixes.
• 3. Scope of Work: Detail evaluated URLs, user journeys, responsive viewports, and explicit exclusions.
• 4. Methodology: Explain heuristic review, visual hotspot evidence collection, and validation procedures.
• 5. Deliverables: Outline executive summary, visual issue cards, severity scores, and implementation roadmap.
• 6. Timeline & Milestones: Present phased schedule and client dependencies (e.g. staging access or analytics data).
• 7. Project Fee & Terms: Fixed engagement price, payment terms (e.g. 50% upfront, 50% upon delivery), and out-of-scope rates.
• 8. Acceptance & Next Steps: Clear call-to-action explaining how to approve the proposal and schedule the kickoff.

3 Proposal Mistakes That Cost Agencies Credibility

Avoid these common proposal traps to win more client trust and project approvals:

• 1. Promising conversion improvements before the audit: A UX audit identifies usability friction, but cannot guarantee conversion rates because market positioning, pricing, and traffic quality also dictate outcomes.
• 2. Making the scope sound bigger than it is: Overpromising a "complete product audit" when you only review 3 pages destroys trust. Be explicit about page counts and exclusions.
• 3. Selling the document instead of its usefulness: Clients don't pay for page counts; they pay for clarity and actionable engineering guidance.

Where White-Label Reporting Fits into Agency Delivery

For agencies delivering UX audits regularly, report preparation can become repetitive. Teams spend considerable hours organizing screenshots, formatting findings, and preparing branded slide decks. A structured reporting system like My Design Audit helps automate the heavy lifting—providing heuristic usability assessments, visual hotspots, prioritized recommendations, and improvement roadmaps under your own brand identity. The reporting tool supports your delivery workflow without replacing expert judgment. You remain responsible for validating findings, refining recommendations, and tailoring insights to the client's commercial priorities. Explore an interactive demonstration: View the My Design Audit white-label demo report My Design Audit offers a 14-day trial with a payment card required. Review subscription terms before starting.

• Explore the Outseta White-Label Demonstration Report
• Read our Guide to White-Label UX Audit Reports
• Explore Agency Pricing & 14-Day Trial Details

Frequently Asked Questions About UX Audit Proposals

Quick answers to common questions about preparing and pitching UX audit proposals:

• What should a UX audit proposal include? Client problem statement, objectives, scope, methodology, deliverables, timeline, pricing, exclusions, and approval steps.
• Is a UX audit proposal the same as a UX audit report? No. The proposal scopes the engagement before work begins; the report presents the findings and fixes after evaluation.
• Can an audit be sold separately from a redesign? Yes. Audits make excellent standalone discovery engagements ($1,500–$5,000) that frequently lead to larger redesign retainers.
• Should proposals include a sample report? Yes. Providing a sanitized or white-label sample report helps clients visualize the deliverable quality.
• How detailed should a UX audit proposal be? Detailed enough to establish clear expectations without overwhelming the client. A focused engagement needs 3–5 pages, while enterprise audits require formal master services agreements.
• Can agencies use AI tools to prepare UX audit reports? Yes, provided findings are human-validated and adapted to the client's specific business goals.