What does a consulting engagement cost?
Every engagement is quoted as a fixed scope after a free 30-minute call, so there's no hourly meter and no change orders. Cost tracks how many flows are in scope, how much evidence already exists, and whether you need the plan or the plan plus implementation support. An audit is the smallest way in, and the number is agreed before any work starts.
How long until we have something we can act on?
An audit produces a prioritized fix list in one to two weeks. A strategy engagement runs four to six weeks, but you don't wait until the end — findings are shared at weekly checkpoints, so the team can start on the clear cases while the rest is still being worked.
Do you design the fixes as well as identify them?
I'll design the flows and key screens where the recommendation needs to be made concrete, and I'll review your team's work as they implement. What I don't do is take over production design delivery for a whole product — if that's what you need, I'll tell you on the call and point you toward people who do it well.
What access do you need from us?
A working account in a realistic environment, whatever analytics and support themes you already have, any past research, and 30 minutes each with a few people across product, design, engineering, and support. That's usually enough. NDAs and vendor security reviews are routine.
We have no user research at all. Is an audit still useful?
Yes — an expert review finds the problems that are already known to break tasks, without spending participant budget to confirm them. It's also the cheapest way to find out which questions genuinely need research, so the study you run afterward is narrower and costs less.
Will you work directly with our engineers?
Yes, and the work is better for it. Effort estimates come from your engineers rather than from me, dependencies get named early, and recommendations are written in terms of what your stack can actually do this quarter.
Does the audit cover accessibility?
Accessibility barriers are flagged wherever they surface in the flows under review, and a barrier that blocks a task is rated critical rather than cosmetic. That's not the same as a full WCAG conformance audit with a formal report — if you need that for a procurement or legal requirement, I'll say so and help you scope it.
Can you help us make the case internally?
That's often the real job. Recommendations are framed against numbers you already track — completion rates, support volume, drop-off, churn — and the readout is built for the room that has to approve the work, not just for the design team.
