
UX for AI-Era Small Business Products
Interface, content, and interaction design for small-business products in a world where agents are also users.
Foundations
Designing for the Person
The Execution Playbook
UX for small business is whether the task that earns money, such as booking a visit or requesting a quote, can be finished on a phone by a person and by an agent acting for that person. A named button and a labeled field serve a screen-reader user and a browser agent alike: WCAG 2.2 Name, Role, Value is a Level A success criterion for making controls understandable to assistive technology.
That shared foundation has plenty of room for repair. In February 2026, WebAIM's Million report found automatically detected WCAG 2 failures on 95.9% of one million home pages, an average of 56.1 detected errors per page; those automated results are not a full accessibility audit.
One task, four checkpoints, two readers
The model we use starts with one task that earns money and follows it through four checkpoints. A person on a phone walks the path by reading and tapping; an agent reads the names, roles, and labels exposed by the page. As web.dev's advice for agent-friendly sites puts it, agents do not look at your website on a monitor.
- FIND: Reach the right page and identify the link to the task.
- UNDERSTAND: See the offer, the price where available, and what happens next.
- ACT: Complete the form, use the button, or make the booking.
- CONFIRM: See what happened and what comes next.

Both readers follow the same task through four checkpoints. A failure at any checkpoint, often ACT, can stop the task before confirmation.
Our reading is that a cause blocking one reader usually blocks the other too. A clickable div with no accessible name, for example, can leave both a screen-reader user and an agent unable to identify the control. A native button with a clear name gives each reader a recognizable action.
The checkpoints also keep a redesign conversation grounded. If someone finds the service but cannot tell whether you serve their location, the trouble sits at UNDERSTAND; if they send a request and receive no indication that it arrived, CONFIRM needs work. Those are different problems, even when both appear in a report as a missing conversion.
If visitors arrive but don't book or request a quote
The trouble often sits at ACT, although an unclear offer at UNDERSTAND can stop a visitor before the form appears.
- Why Your Website Is Not Converting: 11 Path Failures helps you find the step losing people, with Baymard's checkout research showing an average US checkout with 23.48 form elements by default against an ideal flow as short as 12 to 14.
- Microcopy Examples: 9 Choices Compared settles what buttons, errors, and confirmations should say, including a hypothetical choice between “Submit” and “Send my quote request” that tells a visitor what the button will do.
- Core Web Vitals and Mobile Speed Reference Card gives you the thresholds and places to check field data; the Web Almanac 2025 found that 48% of mobile sites passed all three Core Web Vitals, compared with 56% on desktop.
If you don't know what users need
Start with the person's journey across all four checkpoints, then ask people to attempt the task before deciding what the site needs.
- What Is UX? A Small Business Journey Dissected follows a hypothetical plumbing booking on a phone, showing how finding the service, understanding the offer, and receiving confirmation shape the whole interaction.
- How to Do User Research Without a Research Team shows how to use recent-customer interviews and five task testers, drawing on Nielsen's recommendation to spend a 15-person testing budget on three iterative rounds of five.
- Website Information Architecture: A Clinic Teardown uses the fictional Northfield Physio to show how to organize menus around customer language and test whether people can find pages before launch.
If AI and agents are changing how people reach you
The agent is a second reader at every checkpoint, while people who reach your site may arrive with a more specific fact to check or action to take.
- Does UX Still Matter When AI Is the Interface? examines the change in search behavior: Pew's study of 900 US adults' March 2025 browsing found a traditional result was clicked on 8% of visits to pages with an AI summary versus 15% without.
- How to Make Your Website AI Agent Friendly explains how agents read pages, how to identify bots, and how to test a booking; it also distinguishes the WebMCP draft from a W3C Standard.
- Chatbot UX: 11 Failures and How to Confirm Them checks what can break when chat sits on the task path, including misleading answers of the kind for which Air Canada was held liable for negligent misrepresentation in 2024 BCCRT 149.
If your website needs rebuilding anyway, Iron Goo's Foundation engagement is an AI-ready site rebuild using a current stack, structured data in every page template, security hardening, and handover documentation. The rebuild is the moment to ship the named controls, labeled fields, and stable layouts both readers need.
If you want to measure and keep improving
Measurement follows the task across all four checkpoints, while accessibility and consistent controls help both readers complete it.
- How to Measure UX and Fix What Is Failing shows how to measure one task, fix one problem, and remeasure across complete weeks; Sauro's 78% average completion across 1,189 mostly lab tasks is context, not a target.
- Website Accessibility Checklist for Every Site turns WCAG 2.2 requirements into checks and a 30-minute test session; automated tools miss part of the work, and axe-core's 57% figure is Deque's own claim.
- Design System for Small Teams: What to Build helps you keep fixes consistent with a system your team can maintain, recognizing NN/g's guidance that a full design system needs a dedicated team.
Start with the task that earns money
Our first-action routine gives you an observable failure to work from. Use the same task for both passes so you can compare where each reader gets stuck.
- →Try the task on your phone
Pick a booking or quote request and complete it on your own phone over mobile data. Count every screen, tap, and field, and note the first place you would give up.
- →Repeat with a keyboard
Use Tab, Shift+Tab, and Enter to attempt the same task without a mouse. Check that every control is reachable and has a name that identifies its purpose.
- →Write down the first failure
Record the control, screen, or missing information that stopped you. Use that failure to choose the reading path that fits the problem.
Ready to move?
Tell us where your business is today. A written assessment lands in your inbox within two business days.
Talk to us