HADDONSoftware Solutions
Start a project hello@haddon.software

Calgary, Alberta — working with clients across Canada

Improve

Find out what is quietly costing you.

An audit is the cheapest way to find out whether you have a small problem or a large one. We review what you have, test it with real users, and give you a prioritised list — often the fix is three screens rather than a rebuild.

Why it matters

The short version.

An audit answers a question that is otherwise expensive to answer: is this a small problem or a large one? Teams routinely get this wrong in both directions — rebuilding something that needed three fixes, or patching something that needed rethinking. Both mistakes cost far more than finding out first.

The value is largely in the prioritisation. A list of forty problems is not useful; a list of forty problems ordered by impact against effort, with the top five marked as the ones actually costing you users, is a plan. Most products have a small number of issues doing most of the damage.

We also find it useful precisely because we are not attached to the decisions. Everybody internally knows why a thing is the way it is, and that knowledge makes the problem invisible. An outsider with a structured method and access to real users sees it in an afternoon.

A list of forty problems is not useful. Forty problems in priority order is a plan.

Is this you?

You probably need this if…

  • Conversion or completion rates are worse than they should be
  • You suspect something is wrong but cannot name it
  • Someone is proposing an expensive rebuild and you want a second opinion
  • You inherited a product and need to know what you are holding

What's involved

The actual work.

No two engagements are identical, but this is the shape of it.

01

Heuristic review

A structured pass against established usability principles, so the findings are not just one person's taste.

02

Usability testing

Real users attempting real tasks while we watch where they stall.

03

Accessibility check

Contrast, keyboard navigation, screen reader behaviour and target sizes against WCAG 2.1 AA.

04

Performance and flow review

Load behaviour and drop-off points, because slow is a usability problem.

What goes wrong

Mistakes worth
avoiding.

Named plainly, because most of them are easier to avoid than to undo.

  • Confusing an audit with an opinion

    A structured review against established principles and real user sessions is evidence. One experienced person's taste is not, however good the taste.

  • Fixing what is easiest first

    The satisfying small fixes often are not the ones losing you money. Impact-against-effort ordering exists to resist that pull.

  • Auditing without watching anyone

    Heuristic review alone finds the theoretical problems. Watching five real people finds the ones actually happening.

How it runs

Start to finish.

Each phase ends in something you can open, click or read.

  1. 01

    Walkthrough

    You show us the product and tell us what it is meant to do.

  2. 02

    Review and test

    Structured analysis plus live sessions with users.

  3. 03

    Prioritise

    Findings ranked by impact against effort, not by how much they annoy us.

  4. 04

    Readout

    A working session, plus the written report and recordings.

Deliverables

What you walk
away with.

Yours to keep, whatever happens next.

  • A prioritised list of issues, worst first

  • Recordings of users hitting the problems

  • An accessibility findings summary

  • A clear recommendation: fix, redesign, or leave alone

Questions

Worth asking.

Anything else — email hello@haddon.software and a human replies the same business day.

About two weeks from kickoff to readout, depending on how much product there is and how quickly we can get in front of users.

No, and there is no obligation. The report is written so any competent team can act on it. We would rather it get fixed than sit with us.

That is a genuinely useful result and it happens. You get to stop worrying and spend the rebuild budget elsewhere. We will say so plainly rather than inflate small findings.

Yes, and a comparative audit is often more actionable — it shows where you are genuinely behind rather than where you are merely imperfect. We use publicly available products and normal user accounts only.

Analytics tells you where people drop off. An audit tells you why. They are complementary — we read your analytics first precisely so the sessions can be aimed at the places that are already known to be bleeding.

Want to talk it through?

The first call is free, runs about thirty minutes, and you'll get a straight answer about whether we're the right fit — including when we're not.