Defining SaaS Audit Boundaries

1. The Art of Drawing Lines: In-Scope vs. Out-of-Scope

An audit is a diagnostic tool, not a redesign project. Failing to make this distinction clear in writing is the most common mistake freelancers make, leading to endless revisions and unpaid work. Your scope document is where you draw these lines with surgical precision.

The VWO guide on UX Audits provides an excellent, industry-standard separation of duties.

Let's summarize the core distinction:

• IN SCOPE (The Diagnosis): This is what the client is paying you for. It involves reviewing, evaluating, and analyzing the existing product to identify problems and recommend solutions. Your output is information and a plan.
• OUT OF SCOPE (The Execution): This is the work that comes after the audit and should be scoped as a separate, subsequent project. It involves creating, designing, developing, and implementing. Your output here would be assets and code.

This separation is non-negotiable. It positions the audit as Phase 1 and the redesign as a potential, more lucrative Phase 2.

2. Defending Your Scope

Defining scope is one thing; enforcing it is another. Scope creep—when a client asks for "just one more thing"—erodes your profitability. Your scope document is your primary defense.

This video provides the tactical language and mindset needed to protect your boundaries.

The key takeaway is this protective clause: "Any items not detailed in this agreement are considered out of scope and may require a change order." Your scope template will serve as the detailed agreement for your audit. When a client asks for something not on the list (e.g., "Can you just mock up that new button for me?"), you now have the basis to respond with Janda's script: "Thanks for this request. Since it isn’t part of the original audit scope, we would be happy to provide you with a price and timeline to add it to the project."

3. Your Deliverable: The UX Audit Scope Template

It's time to build your reusable asset. You will create a one-page scope document in Figma that you can quickly customize for any client proposal. This is not just an exercise; this is a core business tool.

We will use a canvas structure as a guide, but tailor it specifically for a SaaS UX audit.

Building the Template in Figma

Follow these steps to create your professional scope document.

1. Setup:

   • Open Figma and create a new file named [Template] UX Audit Scope of Work.
   • Create a frame with a standard A4 or US Letter aspect ratio. Give it a title: UX Audit: Scope of Work.

2. Project Definition:

   • Create text blocks for the following items. Use placeholders that you can easily replace for each client.
     • Client: [Client Name]
     • Product: [SaaS Product Name]
     • Date: [Date]
     • Project Goal: [Example: To identify the top 3 friction points in the user onboarding flow that contribute to user drop-off, and provide actionable recommendations to increase the new user activation rate by 10% within 3 months.]

3. Core Audit Areas (In Scope):

   • Create a section titled Core Audit Activities.
   • This section details the work you will perform. Using the list from the VWO article (LINK), create a checklist:
     • Review of Key User Journeys: (e.g., Onboarding, Subscription Upgrade, Core Feature Usage).
     • Heuristic Evaluation against established usability principles.
     • Quantitative Data Analysis: Review of existing analytics (e.g., GA4, Clarity, Hotjar) to identify behavioral patterns and drop-off points.
     • Qualitative Review: Analysis of session recordings and heatmaps.
     • Evaluation of UI/Design Consistency and adherence to brand guidelines.
     • Accessibility Review (based on WCAG guidelines).

4. Final Deliverables:

   • Create a section titled Final Deliverable. This clarifies what the client will physically receive.
   • State clearly: "A single, comprehensive UX Audit Report presented in a Figma presentation, containing:"
     • Executive Summary: High-level overview of findings and business impact.
     • Methodology: A brief of the process used.
     • Prioritized Findings: A ranked list of all identified usability issues, with severity ratings (e.g., Critical, Major, Minor).
     • Annotated Screenshots: Visual evidence of each issue within the product's UI.
     • Actionable Recommendations: Clear, data-backed suggestions for improvement.

5. Excluded Activities (Out of Scope):

   • This is your most important defensive section. Create a section titled Specifically Excluded From Scope.
   • Use a prominent icon (like a red 'X') for emphasis.
   • List the items from the VWO article (LINK):
     • Complete UI/UX Redesign (e.g., creating new wireframes, mockups, or prototypes).
     • Development of new features or backend functionality.
     • Full-scale content creation or copywriting.
     • Implementation of any recommended changes (coding, bug fixing).
     • Configuration or installation of analytics tools.

6. Client Responsibilities & Timeline:

   • Add two final sections:
   • Client Responsibilities:
     • Provide full access to relevant analytics platforms (Google Analytics, Clarity, etc.).
     • Provide access to a test account or the live product.
     • Designate a single point of contact for questions.
   • Project Timeline:
     • 5 Business Days, commencing upon receipt of all required access from the client.

Spend about 25-30 minutes building this template. Use your UI design skills to make it clean, professional, and easy to read. This is a direct reflection of your own brand.

Conclusion

You have now built a critical business asset: a formal Scope of Work template. This document moves you from being a freelance designer to a professional consultant. It proactively addresses potential misunderstandings, protects your time and profitability, and sets the stage for a smooth, well-defined engagement.

Key Takeaways:

• A formal scope document is non-negotiable for protecting your business.
• Clearly define what is INCLUDED (diagnosis, analysis, reporting) and what is EXCLUDED (design, coding, implementation).
• The final deliverable of an audit is a report—a strategic plan—not a redesigned product.
• Defining client responsibilities upfront prevents delays and places accountability where it belongs.

Preview of the Next Lesson:

Your scope document now lists "Heuristic Evaluation" as a core activity. In our next lesson, we will focus on mastering that specific skill. You will learn to perform a heuristic evaluation on a target SaaS product using a specialized checklist. We will build the very checklist you will use to systematically identify usability flaws in a client's product.