Discuss your website

Make it easier for customers to take the next step.

We help founder-led B2B SaaS teams spot what could be getting in the way of demo requests. Our UX audit reviews the path through your website and gives your team clear priorities, practical changes, and a way to check whether they help.

Discuss your website See the sample audit

Dublin-based · Remote-first · Ireland, UK and Europe

Illustration of a website UX audit with numbered callouts and a prioritised findings panel.
Illustrative audit preview

Who this is for

Built for B2B SaaS teams of roughly 5 to 50 people, where the founder or marketing team looks after the website and there is no dedicated UX specialist.

You are a good fit if

  • Your website gets visitors, but fewer request a demo or get in touch than you expect.
  • You want to know which website changes deserve your team's time next.
  • You have someone who can make the recommended changes.
  • You want an expert review before committing budget to a redesign.

You will need a different scope if

  • You need us to redesign or build the site, or carry out research with users.
  • You want to improve what happens inside your product, such as onboarding or trial activation. We can discuss these separately.

What you get

A clear view of the obstacles

We follow one key path, usually from landing page to demo request, on desktop and mobile. The review covers up to five agreed pages, plus the form errors and confirmation messages we agree to include.

Findings you can act on

See each issue in an annotated screenshot, understand why it may matter, and get a specific recommendation. We rate its severity, our confidence, and the likely effort to fix it, with a way to check the result.

Three priorities to start with

A PDF report brings the findings together, with a short summary and three immediate priorities. A walkthrough call of up to one hour helps your team understand the recommendations and plan the next steps.

You will know what we found on the page and what still needs testing with users or data. We focus on issues that matter to your agreed goal, with no guaranteed increase in demo requests or minimum finding count. AI tools support our internal workflow; we write and review every finding you receive.

See what a recommendation looks like

Illustrative example. These findings are written for “Northwind Analytics”, a fictional company, to show the format and depth of a real audit. They are not from a client engagement.

Finding 1 of 3 · Demo request form

The demo form asks for eight fields before explaining what happens next.

  • Severity: High
  • Confidence: High
  • Effort: Low
1 2 3
Annotated wireframe of the demo request page.
  1. Required phone number field.
  2. No copy setting expectations for the demo.
  3. Generic “Submit” button label.
Where
/request-demo, desktop and mobile.
What we observed
The form has eight required fields including company size, phone number, and “current tooling”. No text on the page says what a demo involves, how long it takes, or when someone will be in touch.
Evidence
Screenshot markers 1 (required phone field), 2 (no expectation-setting copy), 3 (submit button labelled “Submit”).
Why it may matter
Visitors may hesitate to share a phone number or spend time on a long form before they know what the demo involves. That could mean fewer completed requests. This is a hypothesis to investigate with form completion data or user research.
Recommendation
Agree with sales which details are essential at this stage. Test a shorter form with name, work email, and one optional message field, collecting other details later where possible. Explain what the demo covers, how long it takes, and who runs it. Label the button “Request a demo”.
How to verify
Compare the proportion of people who start and complete the form before and after the change, allowing enough time to gather useful data. Check lead quality with sales and account for changes in traffic sources.

Finding 2 of 3 · Pricing page, mobile

The demo button is easy to miss on mobile.

  • Severity: Medium
  • Confidence: Medium
  • Effort: Medium
1 2 3
Annotated wireframe of the pricing page at a 390 pixel wide viewport.
  1. Comparison table requires horizontal scrolling.
  2. Call to action sits below the table, far down the page.
  3. Column headers are lost once the table scrolls.
Where
/pricing, mobile.
What we observed
On a 390 pixel wide viewport the primary call to action appears only after a five-column plan comparison table that requires horizontal scrolling. The table has no sticky header, so column labels are lost after the first row.
Evidence
Markers 1 (table scrolls sideways), 2 (demo button below the table), 3 (column labels scroll out of view).
Why it may matter
Visitors comparing plans may miss the option to book a demo or lose track of which features belong to which plan. The layout issues are visible in the review; whether they reduce demo requests needs testing.
Recommendation
On narrow viewports, present plans as stacked cards with a “Book a demo” button on each. Keep the full table for desktop. Add a persistent call to action in the pricing page header.
How to verify
Compare the proportion of pricing-page visitors who reach the demo form before and after the change. Review mobile and desktop separately, and check completed requests too.

Finding 3 of 3 · Form success state

The confirmation message leaves visitors unsure what happens next.

  • Severity: Low
  • Confidence: High
  • Effort: Low
1 2
Annotated wireframe of the post-submission page.
  1. The entire success message: “Thanks!”
  2. Empty area where next steps could sit.
Where
/request-demo after submit, all devices.
What we observed
After submission the page shows “Thanks!” and nothing else. No confirmation of what was submitted, no expected response time, no way to add information or correct a mistake.
Evidence
Marker 1 (success message), 2 (empty page area where next steps could sit).
Why it may matter
Visitors may wonder whether their request arrived or when to expect a reply. This could lead to duplicate requests or follow-up emails. It is a lower priority than an obstacle to submitting the form, but still part of the first impression your sales team makes.
Recommendation
State the response time, name the person or team who will reply, and offer one useful next action, such as a link to a short product overview.
How to verify
Monitor duplicate submissions and “did you get my request?” emails over the following month.

Your audit includes the issues we consider important to your agreed goal, ordered by priority so your team knows where to start.

Scope, price and timing

Journey
One path through your website, covering up to five agreed pages plus agreed form errors and confirmation messages.
Devices
Desktop and mobile.
Deliverables
A PDF report with a short summary, three immediate priorities, and findings supported by annotated screenshots and recommended changes.
Walkthrough
One review call, up to one hour.
Timing
Delivered within five business days of receiving the brief and any access we need.
Not included
Redesigns, development, user testing, and analytics implementation. We can scope these separately.

How it works

  1. Agree the focus

    In a 20-minute call and a short form, tell us what visitors should do and where you think they get stuck. We agree which pages to review.

  2. We review your site

    We follow the agreed path on desktop and mobile, document the obstacles, and assess how each could affect the action you want visitors to take.

  3. Get your priorities

    Within five business days of receiving your brief and any access we need, you receive the report with clear priorities and recommended changes.

  4. Plan the next steps

    On a call of up to one hour, we talk through the recommendations, answer your team's questions, and agree how to check whether the changes help.

Who we are

Claudio Visentin

Game designer and feature owner

Claudio's experience includes owning live features on Seafight at Bigpoint, using analytics and player feedback to decide what to change and check the results. He brings that approach to your audit: understand where people get stuck, prioritise the changes, and define how to measure whether they help.

Claudio on LinkedIn

Chris Fagan

UX designer

Chris brings UX research and design experience across enterprise software, fintech and healthcare, including roles at Johnson Controls and Citco. His background helps him assess how clearly your website explains the offer and guides visitors to the next step. He holds master's degrees in Interaction Design and Digital Healthcare Innovation.

Chris on LinkedIn

Based in Dublin. We work remotely with clients in Ireland, the UK, and across Europe.

Discuss your website

Share your website and what you would like visitors to do more often. We will reply within two business days to discuss whether the audit fits and what to do next. No obligation or automated follow-ups.

The site you want reviewed. No need to type “https://”.

A sentence or two is enough. For example: “People visit our pricing page, but few request a demo.”

We use what you send here to reply to your enquiry. Nothing else.