Case study · Custom AI Systems
A product audit that surfaced six hidden issues
SucceedEx used their own product every day. A first-time user hits things the team has long since stopped seeing.
6issues surfaced
- Client
- SucceedEx
- Problem
- A team too close to its own product to see what a first-time user hits.
- Approach
- Use SucceedEx's product like a new customer for a day, then rank what surfaces.
- Verified result
- 6 issues surfaced
The problem
SucceedEx knew their product worked. They used it every day, which is exactly why some of its rough edges had gone invisible: the team had built those paths and learned to walk them without noticing.
The gap is not effort, it is proximity. A first-time user meets the product with none of that context, and hits friction the team has stopped registering.
What was assumed
The product is fine, we use it every day.
What Stallwart asked
What does a first-time user hit that the team has stopped seeing?
What Stallwart built
Stallwart spent a day using SucceedEx's product the way a first-time customer would, with none of the team's built-in knowledge. What surfaced became a ranked, specific report: six usability issues, each one actionable rather than a vague note that something could be better.
- 01
Use it like a first-time customer
Approach the product with no inherited context, following the paths a new user would, so the friction a new user meets shows up instead of being walked past.
- 02
Record what the team has stopped seeing
Note each point of friction as it happens, the ones built past and no longer registered, before familiarity explains them away.
- 03
Rank it and make it actionable
Turn the findings into a ranked, specific list. Each item names what to fix, not that something could be better, so the team can act in order.
The findings
Six issues the team had stopped seeing.
6issues surfaced
A day spent using SucceedEx's product like a first-time customer surfaced six usability issues the team had built past and stopped noticing. The report was ranked and specific, and every item was actionable.
Engineering decisions
Audit from the outside, not the team's seat
The team cannot un-see what it built. A first-time pass is the only way to meet the product as a user does.
The trade-off
An outside pass misses internal context, which is the point: that context is what hid the issues.
Rank the findings, do not just list them
An unranked list leaves the team guessing what matters. Order tells them where to start.
The trade-off
Ranking is a judgment call, so it is argued, not just asserted.
Be specific, never 'this could be better'
A vague note is not actionable. Naming the exact issue is what lets the team fix it.
The trade-off
Specific findings take longer to write than general impressions, and are worth more.
In practice
Kaviarasu
Founder, SucceedEx
SucceedEx's founder described Stallwart spending a day using the product like a first-time customer and surfacing six issues the team had stopped seeing because they had built them. The report was ranked and specific, with every item actionable rather than a vague note that something could be better.
This work connects to
- Custom AI Systems
- Product and UX audit
- Production AI systems
Frequently asked
What is an AI product audit?
It is a structured review of a product carried out as a first-time user would experience it, surfacing usability issues the team has stopped seeing. The output is a ranked, specific, actionable list rather than general impressions.
Why can't the team find these issues themselves?
Because they built the product and use it daily. That proximity is what hides the issues: the team learned the rough paths and stopped registering them. A first-time pass meets the product without that context.
What does the report actually contain?
A ranked list of specific usability issues, each one actionable. For SucceedEx that was six issues, ordered by what to address first, with each item naming the problem rather than noting that something could be better.
How long does an audit like this take?
The SucceedEx audit was a day spent using the product like a new customer, followed by ranking and writing up what surfaced. The value is in the fresh perspective, not the hours.
What does a first-time user hit that your team has stopped seeing?
We use your product like a new customer and hand you a ranked, specific, actionable report.
Last updated: October 7, 2026