find what's slowing your product down.

prioritized findings, each tagged with:

severity

what it costs the product

effort

rough implementation weight

fix

concrete next step

examples

useful references

the final artifact depends on what the audit uncovers: a written report, a semi-functional prototype in the browser, low- or high-fidelity design directions, annotated flows, technical notes, or some mix of those.

depending on the product, the audit can cover interaction states, motion, responsive behavior, component consistency, accessibility, hierarchy, forms, empty states, error states, marketing-to-product cohesion, code organization, component boundaries, data flow, and performance bottlenecks.

delivered with a 60-minute walkthrough so the priorities, tradeoffs, and next steps are clear.

day 1

30-minute kickoff. access, context, sharpest concerns.

days 2–5

product flows, design system, component architecture, codebase structure, marketing surface.

day 6

findings and recommended next steps delivered.

day 7

walkthrough call. q&a, priorities, next steps.

$3,500, paid up front. one round of clarifying questions included after delivery. implementation can be scoped separately; the audit stands alone.

two decades in the browser. work for modern treasury, axoni, vice media, condé nast, amazon. long practice at the line between interface, systems, and implementation.

• how is this different from a design review or a UX audit?+
• can it cover deeper frontend architecture?+
• we already have designers. why would we need this?+
• what if we just want you to fix the stuff yourself?+
• do you sign NDAs?+
• what tech stacks do you work with?+
• what if we're pre-launch?+