01
Internal implementation
Your team executes recommendations. I remain available for clarification and review checkpoints.
Primary service
Find what's holding your product back
When adoption, conversion or retention are off and the team disagrees why — a structured investigation finds where people struggle and what to prioritize.
What this is
A structured look at your product through the lens of real usage — where people stop, get confused, or work around the software. The output is a prioritized fix list tied to business metrics, not a generic review.
When founders call
- People sign up but never come back
- Support volume grows faster than the user base
- New features ship but dashboards stay flat
- Onboarding completion rates keep falling
- The team debates instead of learning from users
Typical situations
- People sign up but never come back
- Growth has stalled despite marketing spend
- New features ship but usage stays flat
- Support answers the same questions daily
- Customers abandon onboarding halfway
- You know something is wrong but not where
- Trial users do not become paying customers
- Retention falls and nobody agrees why
Good timing
- Before a major redesign or rebuild
- When you are about to hire more engineers but metrics have not moved
- Before fundraising or board reviews where product questions will come
- When expanding from one customer segment to another
Probably not the right fit if
- You already know exactly what to build and only need execution
- The issue is purely infrastructure with no user-facing ambiguity
- You need a full-time product executive, not a diagnostic phase
What you receive
Deliverables are tailored to context. A typical audit may include:
- Executive summary for leadership
- UX analysis with friction mapping
- Product analysis and flow evaluation
- Prioritized recommendations
- Business impact assessment
- Technical review where relevant
- Quick wins and long-term roadmap
- Opportunity and risk assessment
- Video walkthrough or workshop
- Presentation to stakeholders
What happens after the audit
An audit is a decision point — not the end of the engagement. Teams implement in different ways. I adapt to yours.
02
Implementation-ready documentation
I produce UX specifications, technical specifications, user stories and acceptance criteria your team can build from.
03
Collaboration with your designers
I work alongside your design team — critique, patterns, system alignment and delivery support.
04
Collaboration with your developers
I support engineering with specs, architecture notes and implementation review — without replacing your team.
05
Engineering planning participation
I join planning sessions to reduce delivery risk and ensure product intent survives technical trade-offs.
06
Hands-on implementation
When appropriate, I implement UX improvements or product interfaces myself — with development partners where the engagement requires it.
How recommendations are delivered
I adapt to your existing technology stack, team structure and delivery process. The objective is to reduce implementation risk — not to replace internal teams.
- Stakeholder presentation
- UX specification
- Technical specification
- Implementation roadmap
- User stories and acceptance criteria
- Architecture recommendations
- Workflow documentation
Related content
Book a Product Audit
Discuss your product context and whether an audit is the right starting point.