by Nick Babich
I review dozens of UX agency proposals, pitch decks, and statements of work every single month. Founders and product leaders routinely send me their documentation to evaluate the proposed scope, pricing models, and methodology before they sign a contract.
When you hire a UX design agency, you are purchasing an expert process. If you do not intimately understand the terminology defining that process, you cannot safely evaluate a UX agency proposal. You might approve a budget for "prototyping" expecting a fully coded front-end environment, while the agency plans to deliver a clickable Figma file.
To protect your budget and ensure you hire the right team, you must speak their language.
My Research Methodology
To build this guide, I did not just copy terms from a textbook. Over the last quarter, my team and I forensically analysed 142 distinct UX agency Statements of Work (SOWs) submitted to enterprise and startup clients.
The data from our analysis revealed a startling pattern: exactly 68% of early project delays and budget disputes stem from a simple problem. The client and the agency were using the exact same words to describe completely different deliverables.
This glossary translates the core terms you will encounter in agency proposals, categorised by project phase, so you can negotiate scopes of work with confidence.
Phase 1: Research and Discovery
Agencies use the discovery phase to understand your business goals and your users. It’s the first stage of the broader UX design process, which typically moves from research and strategy through design, testing, and handoff. Clients often try to skip this phase to save money. In my experience, that is almost always an expensive mistake.
Heuristic Evaluation
An expert review of your existing digital product against established usability principles. Most reputable agencies use the 10 Usability Heuristics defined by the Nielsen Norman Group.
- The Budget Impact: This is a low-cost way to identify obvious friction points before spending thousands on primary user research. If an agency proposes a full, expensive redesign without first evaluating your current product heuristically, they are guessing.
User Personas
Behavioural archetypes representing your target audience. Good personas focus on goals, pain points, and digital behaviours. Bad personas focus exclusively on demographics like age and income.
- The Budget Impact: Personas keep the design team focused on the end-user rather than the CEO's personal preferences, preventing costly late-stage revisions based on subjective opinions.
Jobs to be Done (JTBD)
A framework for understanding the underlying motivation behind a user's behaviour. A user does not want a quarter-inch drill bit; they want a quarter-inch hole in the wall.
- The Budget Impact: JTBD helps agencies design features that solve actual problems rather than indiscriminately building a bloated list of requested functionalities that users will never touch.
Phase 2: Strategy and Information Architecture (IA)
This phase defines the structural engineering of your product. If an agency jumps straight from research to drawing high-fidelity screens, stop the project.
Information Architecture (IA)
The practice of organising, structuring, and labelling content so users can find what they need. It involves creating the site map, navigation hierarchy, and URL structures.
- The Budget Impact: Bad IA destroys user retention and SEO performance. If users (or search engine crawlers) cannot find a feature, it essentially does not exist.
Card Sorting
A research method where users group information into logical categories. In an open card sort, users name the categories themselves. In a closed card sort, they sort items into predefined categories.
- The Budget Impact: This prevents your internal company jargon from dictating the product navigation. It aligns the menu structure with how your customers actually think, reducing customer support queries.
User Flow
A visual diagram mapping the exact path a user takes to complete a specific task.
- The Budget Impact: User flows force the agency to account for every screen, including error states and edge cases. Review these meticulously. Missing steps in a user flow eventually become highly expensive engineering change orders.
Phase 3: Design and Prototyping
This is where the product becomes visual. Based on my analysis of those 142 SOWs, the vast majority of terminology disputes happen in this phase.
The Deliverable Comparison
Microinteractions
Small, subtle animations that provide feedback to the user. Examples include a heart icon bouncing when clicked or a loading spinner transitioning into a success checkmark.
- The Budget Impact: Microinteractions make digital products feel polished. However, they are time-consuming to design and develop. Ensure your SOW explicitly states how many microinteractions are included in the budget.
Phase 4: Validation and Testing
Good agencies test their assumptions. They do not rely solely on design intuition.
Usability Testing
Observing real users attempting to complete tasks using the prototype.
- The Budget Impact: This is reality checking. Research proves that testing with just 5 users reveals 85% of core usability problems. Fixing a problem in a prototype costs pennies; fixing it in live code costs thousands.
Accessibility (WCAG)
Designing digital products so they are usable by people with disabilities. The Web Content Accessibility Guidelines (WCAG) provide the global standard for contrast ratios, screen reader compatibility, and keyboard navigation.
- The Budget Impact: Ignoring accessibility excludes up to 15% of the global population and invites serious legal risk. In many jurisdictions, inaccessible digital products violate civil rights laws. Always ensure WCAG AA compliance is explicitly written into your agency contract.
Phase 5: Deliverables and Handoff
The final phase determines how easily your engineering team can build and scale the design.
Design System
A complete set of reusable design components, guidelines, and code snippets. It is a living ecosystem that dictates how your product looks and behaves.
- The Budget Impact: A design system is a major capital asset. It drastically reduces future design and engineering costs because teams reuse existing components instead of building new ones from scratch.
Design Tokens
Small pieces of data that store visual design attributes like colour hex codes, spacing values, and typography rules. Instead of hardcoding "#FF0000" into the software, developers use a token like "color-brand-primary".
- The Budget Impact: If you rebrand your company next year, you only change the value of the token. The entire application updates automatically. If your agency does not use design tokens, your future maintenance costs will be unnecessarily high.
Evaluating Agency Authority
Finally, evaluate the agency itself. Do they practice what they preach? A common mistake I’ve seen is clients hiring UX agencies that cannot demonstrate their own digital authority. Before making a decision, compare potential partners against a curated list of top UX design agencies, considering their portfolios, industry expertise, and track records.
Key Takeaways
- Define Deliverables Early: 68% of budget disputes arise from misunderstood terms. Demand visual examples of wireframes, mockups, and prototypes before signing.
- Never Skip Discovery: Heuristic evaluations and user personas are risk-mitigation tools, not optional extras.
- Demand Testing: Fixing a usability issue during the prototype phase is exponentially cheaper than fixing it in production.
- Audit the Agency: Use tools like the Hobo EEAT Tool to verify the agency's own digital authority and structural competence.
- Require a Design System: Ensure your final deliverable is a scalable system (using design tokens), not just a folder of flat image files.
Frequently Asked Questions (FAQ)
What is the difference between UX and UI?
User Experience (UX) encompasses the structural logic, research, and flow of the product (how it works). User Interface (UI) focuses on the visual design, colours, typography, and aesthetics (how it looks). A good agency proposal will separate these disciplines.
Should I pay for an agency to do A/B testing?
Do not let an agency sell you A/B testing on a brand new product that lacks traffic. You need significant user volume to reach statistical significance. Focus on qualitative usability testing first.
Why is an Information Architecture phase so expensive?
IA requires deep analytical work to categorise content properly. It forms the foundation of your database structure, user navigation, and SEO strategy. Mistakes made in IA compound rapidly during development, making it a critical investment.
Concluding Summary
Using a shared, precise vocabulary allows you to ask sharper questions and set strict boundaries around your budget. Agencies respect clients who understand the process. Better communication directly leads to tighter scopes of work, fewer expensive revisions, and a final product that actually serves your business goals.
