How I audit websites
This audit is not a templated teardown or a ...
a critique of your headlines
a rewrite of your hero section for ‘clarity’
advice on how to ‘simplify’ your copy
suggestions to be more ‘persuasive’
tips to reduce “cognitive load” with less text
A/B test ideas for pricing or product pages
This website audit is ...
An intel product that looks into why people and {soon} LLMs & AI agents ...
— misread your product value
— can’t tell what problems it solves
— can’t fit it into real-life workflows
— get stuck on the wrong details
— click around but can’t explain it back
— form the wrong idea or expectations
This audit reveals where people’s understanding breaks, why it happens & how to fix it.
It also gives you the clarity to realign your website committee & act with precision.
let’s talk {book 30-min call}assets I look at
— your website {of course}
— your software {UI + structure + micro-copy}
— demos & product tours
— knowledge base + user docs
— ICP definitions
— positioning docs
things I don‘t need to know
I don’t analyze internal decisions. I look at the consequences ... what your message does once it’s live, not what it was meant to do.
my methodology
I. Software taxonomy
How you structure, nest & name your capabilities can block website clarity & logic.
Questions I ask:
— Is taxonomy misrepresenting your product?
— Does structure flatten your core value?
— Is your internal logic misleading people?
— Does feature grouping disrupt understanding?
let’s talk {book 30-min call}II. Information architecture
This isn’t about menus or site nav. It’s about how you order, layer, and reveal product info.
Questions I ask:
— Are you showing too much info, too soon?
— Are you guiding understanding or stacking info?
— Where does logic fail in a non-linear journey?
— Is complexity built up before the basics land?
let’s talk {book 30-min call}III. Product narrative
If your product explanations fail, people get confused or interpret things their own way.
Questions I ask:
— Do you mix abstract claims & tech details?
— Where do you over-explain or under-define?
— Where does syntax feel right but mislead?
— Where does language fail to meet reality?
let’s talk {book 30-min call}how long my audit takes
This is a 4-week sprint that begins once 100% payment is made.
let’s talk {book 30-min call}what you get
a quick-read doc for decision-makers
— built for internal convos & alignment
— key structural issues at a glance
— what’s the cost of not fixing the issues
— biggest growth opportunities
an in-depth, easy-to-skim annex
— your taxonomy misfires, clearly explained
— a scan of IA issues {not UX, but info logic}
— narrative mismatches creating confusion
— each gap traced to root causes
— risks & consequences mapped to each issue
— explanation & additional notes
— software taxonomy restructuring
— info logic & flow optimization
— narrative samples to guide future writing
— team-ready fixes, ranked by impact & effort
let’s talk {book 30-min call}I work with Product Marketers ...
My audit makes you the one who brings clarity. So your ‘website committee’ can see what you’ve sensed all along ...
And gives you the clarity, rigor, and language to align the room and fix your website.
let’s talk {book 30-min call}One-time payment.
Single-product B2B SaaS audit is €4,180
The price goes up for multi-product B2B SaaS.
Payment upfront, work starts immediately after.
Everything stays confidential.
