I Simplified My Job Tracker MVP After Brutal Feedback — And It’s Much Better Now
A few days ago I shared my simple Job Tracker MVP and got some brutally honest feedback.
Biggest things people pointed out:
• too much visual clutter
• dashboard sections competing for attention
• users only care about follow-ups and momentum
• spreadsheets are “good enough” unless the UX feels effortless
So I spent the last few days simplifying the experience.
Changes I made:
• faster “Quick Save” flow
• cleaner dashboard layout
• smarter follow-up prioritisation
• reduced visual noise
• reminder channels for Email / SMS / WhatsApp
• action-focused dashboard instead of “analytics everywhere”
• responsive UI improvements
One interesting UX challenge:
When there are only a few follow-ups, the dashboard looked visually unbalanced because one side became much taller than the other.
I ended up dynamically showing/hiding insight cards depending on follow-up activity to keep the layout balanced.
Still early.
Still rough around the edges.
But it already feels 10x better than the first version.
Would genuinely love feedback from people actively job searching:
• What’s still missing?
• What would make you actually switch from spreadsheets/Notion?
• What would make this feel “sticky” enough to keep using daily?
If anyone wants to try it and share honest feedback, here’s the current version:
https://job-tracker-web-931v.onrender.com/
Happy to keep the early version completely free while I improve it based on real user feedback.
The simplification is the right move.
For something like this, “more features” rarely beats “less friction.”
People do not switch from spreadsheets because they want analytics.
They switch when updating the tracker feels faster than avoiding it.
That is the real bar here.
The stickiest version of this is probably not “job tracking.”
It is “next action clarity.”
The product people come back to daily is not the one that stores applications.
It is the one that removes uncertainty.
What do I follow up on today?
Who is cold?
What is likely dead?
What needs one click right now?
That is the habit loop.
Also: Job Tracker is functional, but very disposable.
If this becomes more than a utility and starts acting like a decision layer, something like Xevoa.com would age better than a literal descriptor.
Thanks, this is really helpful feedback.
I completely agree with the “next action clarity” point. The more I simplify the product, the more obvious it becomes that the real value is not just storing applications, but helping job seekers know exactly what to do next.
I’m going to focus the dashboard more around:
• follow-ups due today
• cold applications
• likely dead opportunities
• quick one-click actions
• reducing uncertainty instead of adding more analytics
Also, your point about the name makes sense. “Job Tracker” is clear, but it does feel more like a utility than a long-term product brand. I’ll think more seriously about whether a brandable name like Xevoa would fit better if the product moves toward being a decision layer.
Really appreciate this — it gives me a much clearer direction.
One practical follow-up on the Job Tracker thread.
I remembered this one because the product had a very clear positioning fork: stay as a simple application tracker, or become more of a next-action clarity layer for job seekers.
That changes the naming problem a lot.
If the product is only storing applications, “Job Tracker” is fine. But if the real value is helping users decide what to follow up on today, what is cold, what is likely dead, and what needs action now, then the product starts feeling more like a career workflow/decision layer than a tracker.
I’m doing a few focused naming and positioning audits for early products at $99 while refining the format.
For this product, I’d review the current name risk, category framing, landing-page angle, domain perception, and whether a name like Xevoa actually fits the stronger direction or if the current utility name should stay for now.
Not a long consulting thing. Just a sharp written breakdown you can use before building more pages, users, and product memory around “Job Tracker.”
If useful, connect here and I can give you a clear outside read:
https://www.linkedin.com/in/aryan-y-0163b0278/
That’s exactly the right direction.
If the product becomes “next action clarity,” the name matters more because it stops being a tracker and starts becoming the thing users rely on to decide what to do next.
That’s where “Job Tracker” starts feeling too temporary.
Just to be transparent, I own Xevoa.com.
I mentioned it because it fits that decision-layer direction much better than a literal descriptor. Short, clean, more software-native, and broad enough if the product grows beyond job applications into career workflow.
If you ever seriously test that positioning, Xevoa would be worth considering before the product gets too locked into the utility frame.