I'm currently building Here Is My CV, a Canva-like resume builder that helps people create resumes and online CVs.
Like many indie builders, I spend a lot of time deciding what to build next.
Should I add more templates?
More AI features?
More customization?
Recently, I realized I was making assumptions.
So I asked a simple question:
What frustrates you most about existing resume builders?
The options were:
- ATS compatibility
- Too many templates
- Customization issues
- Annoying paywalls
The results surprised me.
ATS Compatibility Won
I expected customization or pricing to come out on top.
Instead, ATS compatibility received the most votes.
At first, I thought people were asking for ATS optimization tools.
But after reading comments and talking to job seekers, I realized something else was happening.
Most people don't actually know whether their resume is ATS-friendly.
They don't know:
- Which templates are safe to use
- Whether formatting breaks during uploads
- If ATS scanners can properly parse their content
- Why some applications never receive responses
The issue wasn't ATS itself.
It was trust.
The Builder Mistake
As developers, we often think more features create more value.
Users don't always agree.
Many resume builders compete by adding:
- More templates
- More design options
- More customization controls
But the feedback I received suggested people wanted something simpler.
They wanted confidence.
A clean template they could trust.
What I Shipped
Based on that feedback, I introduced a new template called ATS Classic.
Instead of focusing on visual complexity, the goal was:
- Clean structure
- Readable hierarchy
- ATS-friendly formatting
- Simple customization
Nothing revolutionary.
Just a template designed around the most common concern users shared.
Make your own ATS-friendly CV at https://hereismycv.com
My Biggest Takeaway
The most valuable product insights often come from asking simple questions.
I could have spent weeks debating feature priorities.
Instead, a small poll revealed a problem I had underestimated.
As builders, we often focus on what we think users want.
Sometimes it's worth pausing and asking them directly.
The answer might completely change what you build next.
What user feedback has completely changed the direction of a product you're building?
Top comments (0)