Pricing is only linked in the footer
“Not under Product, not under Solutions… Do I have to book a demo just to see a price?”
Proposed fix: Add “Pricing” to the top menu, between Product and Resources.
How it works
Watch a few people use the site, find the few problems that hurt most, fix them with the smallest change, and test again. AI agents that act as your users run that loop for you in a real browser or phone: websites and web apps on desktop and mobile, mobile apps (Android and iPhone) on a phone. Each step below comes with an example.
Before doing anything, each user looks at the page for a few seconds and answers: what is this, who is it for, and where would I click first? If the answers are wrong, the page is not saying what you think it says.
Example
Each user gets a realistic goal, like “find the price for two nights” or “change my delivery address”. Before every click they write what they expect to happen. When reality differs from the expectation, that gap is the finding.
Example
Guest planning a weekend away · mobile Task: Find the price for two nights
We rank everything we saw by how many sessions it hit and how badly. The report lists every problem, with the 3 worst at the top: that is what a team can actually fix before the next round.
Example
“Not under Product, not under Solutions… Do I have to book a demo just to see a price?”
Proposed fix: Add “Pricing” to the top menu, between Product and Resources.
For each problem we propose the least change that removes it: a label, a moved button, a visible price. Redesigns can wait. The fix comes as a prompt for your coding agent: for the top problems on every paid plan, complete and with before/after mockups on the Full study, Pro and Agency.
Example
# Fix 1 of 3: add "Pricing" to the top menu
Evidence: 4 of 6 AI agent sessions gave up looking for a price.
## Change
- Add a "Pricing" link between Product and Resources.
## Check
- Visible at 390px and 1440px without opening a menu.
## Do not touch
Plan prices, checkout, analytics. After you ship, the same profiles repeat the same tasks. The history shows what got better, what did not, and anything the change broke.
Example
Sessions blocked on the task “find the price”
Session recordings
The videos are not an extra: they are the evidence behind every finding. You see what the agent saw, step by step, next to what it was thinking at that moment.
Moments marked in this session
A video of the real browser or phone for every session, with the cursor or taps, plus a screenshot of each step.
Next to the video you see what the agent expected, what it tried and what it said at that moment.
In the report, a finding links to 0:42 in session 3, and to the same stumble in sessions 5 and 9.
Don’t take our word, or the agent’s: before you spend time on a fix, open the video and check.
Before anything runs, we design user profiles from your business: what you sell, who comes to your site and what they are trying to get done. Each one has a role, a goal, a stage (discovering, comparing, deciding), the needs and objections it arrives with, and a short note on why it plausibly visits your site and what is invented.
Your site, what you sell and who buys it. A B2B tool, a local shop and a members’ club get very different people.
Each profile comes to do something different, so together they cover the tasks that matter: compare, buy, get support, cancel, enter data.
Traits like reduced vision or imprecise taps are added only when they match your real audience.
The procurement manager comparing plans, the member trying to cancel, the clerk registering a product: each profile arrives with a role, a goal and a device.
Goal Check delivery costs before adding to the basket
“I’ll only add it if I can see what delivery costs first.”
Goal Track last week’s order
Logs in with a test account
“I’m already signed in. Where are my orders?”
Goal Compare plans and find the contract terms
“Is the annual price per seat or per company?”
Goal Check the API docs and rate limits before recommending it
“Rate limits… not on pricing, not in the docs index.”
Goal Cancel her membership
Logs in with a test account
“There’s an upgrade button on every page. How do I cancel?”
Goal Find out what members get and what it costs
“The grey text under each benefit is too faint for me.”
Goal Register a new product with its batch number
Logs in with a test account
“The code is already in the header. Why type it again?”
Goal Work out what this is from a link someone shared
“Is this a shop or an agency? Nothing here tells me.”
B2B SaaS
Online store
Membership site
Back office
Arrives from a search result or a shared link knowing nothing about you. Tells you whether your first screen explains what you do.
Use test accounts you create for us to try member areas, orders or settings. The model never sees the password, only that the login worked.
Physical and ability traits are not what a user profile is about. We add them only when they match your real audience: many sites don’t have older customers, so we don’t force them. When we do add one, we apply it to what the agent sees and does, not just to how it is described.
| Modifier | How we simulate it | What it tends to reveal |
|---|---|---|
| Reduced visionUsed when your audience includes older people or long reading sessions. | Screenshots are blurred and their contrast is lowered before the agent sees them. | Pale grey text, small icons, low-contrast buttons, text over images. |
| Imprecise tapsUsed when many visits are on a phone, on the move. | Tap and click coordinates get a random offset of a few pixels. | Tiny targets, links packed together, close buttons in corners. |
| In a hurryUsed when people arrive with a quick, concrete question. | Fewer steps and less time. The agent skims and gives up after a few wrong turns. | Buried calls to action, long pages before the point, slow feedback. |
| Low digital skillUsed when your customers rarely use the web. | The agent avoids jargon, hesitates at unlabelled icons and does not assume hidden menus exist. | Hamburger-only navigation, icon-only buttons, technical wording. |
Devices are chosen the same way: desktop, tablet or mobile, depending on where your customers actually are.
Every report ends with a short script to confirm the top findings with three to five real people. That is where testing with AI agents hands over to research with humans.
Public tests are read-only by default: users navigate and read, and on third-party sites they never submit forms. With your permission, on your own site, they can sign up and confirm emails with UX Surgery test inboxes. They never send messages or place orders.
ExampleLog: “Reached ‘Place order’. Stopping: this would create an order.”
Testing a web app behind a login needs proof that you control the domain, and test accounts you create for us. Mobile apps (Android and iPhone) run only from the build you upload.
ExampleDNS record: TXT uxsurgery-verify=7f3c… (illustrative value)
Agents stop before any payment step. They never enter or submit card details.
ExampleLog: “Card number field reached. Stopping before payment.”
Recordings and reports are stored in the EU, in Madrid, and deleted after 90 days.
ExampleStudy run on 3 May → deleted on 1 August.
Paste your URL. In a few minutes you get the 3 worst problems and one session video.