WebYes · 2023 to present
Building a B2B SaaS from 0 to 1, reaching 5,000+ users by focusing on accessibility
WebYes is a web auditing and compliance platform that helps agencies and site owners find and fix accessibility, performance, SEO, quality and uptime issues from one dashboard. I joined as the company's first and only designer and designed it end to end, from an empty Figma file to a live product across a web dashboard, WordPress plugins and a Chrome extension.
Visit WebYes- My role
- Sole product designer
- Team
- 2 PMs · engineering lead · engineers
- Duration
- 2023 to present
- Status
- Live in production
- Published
- 2025 · 12 min read

The problem
Audit tools are good at finding issues and bad at getting them fixed. They hand you 200 errors with no order and no answer to the only question that matters: which of these is a legal risk, and what do I fix first?
Impact
- 5,000+
- Total signupsDashboard, plugins and extension, launch (2023) to Aug 2026
- 29%
- Signup to paidShare of all signups that upgrade to a paid plan
- 80%
- Checkout completionOf users who choose a plan and start checkout
- 70%+
- Paid users via accessibilityPaid conversions whose first scan was an accessibility scan
What I did
- 01
Owned every screen, end to end
Discovery, information architecture, interaction, visual design, the design system and developer handoff, as the company's first and only designer.
- 02
Prioritisation over completeness
Competitors dump a flat list of every issue. WebYes opens on the highest-impact, lowest-effort fixes, with the full list one click away. Users get a first action, not a backlog.
- 03
Legal jurisdiction as a filter, not a report
Pick ADA or EAA and every score, issue and quick win re-filters to what is legally mandatory there. Competitors sell this answer as a static PDF; it is built into the daily workflow.
- 04
One design language, three surfaces
The dashboard, the WordPress plugins and the Chrome extension are built from one token-based system, so the product's own UI ships WCAG-compliant by construction.
In the product


The full story
Behind the password: the research, the iterations that did not work, how the jurisdiction filter almost shipped as a PDF, and the evidence behind each decision.
