I applied to 127 jobs. Got 3 callbacks. So I built an AI that does it better.
Last year I was job hunting. Applied to 127 positions manually. Tailored resumes, wrote cover letters, filled out the same forms over and over. Got 3 callbacks. Three.
Then I found out my resume was scoring 34% on ATS systems. Nobody told me — the system was filtering me out before a human ever saw my resume.
So I spent a year building the tool I wish existed.
AI Applyd runs a 6-step pipeline while you sleep: finds jobs across LinkedIn, Indeed, and Glassdoor, scores your resume against ATS, tailors it per role, writes cover letters, and submits up to 170 applications a week on the top plan.
Two modes: Copilot (review each application before it goes out) or YOLO (full automation — wake up to applied jobs).
Built the entire thing solo. TanStack Start + Hono on Cloudflare Workers. Bootstrapped. No investors. Just frustration turned into code.
Free to start, no credit card. Pro was $12/month when I posted this. It is $19.49/week or $38.99/month now.
Would love feedback from fellow indie hackers — especially on pricing and the auto-apply angle. Is "YOLO mode" too aggressive, or exactly what job seekers want?
this hits hard, especially the ATS part — most people don’t even realise they’re getting filtered before a human sees their resume
the copilot vs YOLO mode is actually a smart approach, gives control + automation both
since you're already getting traction and thinking about pricing, you could also try putting this into a competition
good way to validate positioning + get more visibility
also, prize pool just opened at $0, so your odds are the best right now
the invisible-filter part is what got me too. i spent months assuming humans were reading and passing on me, when most of the time no human ever saw it. copilot vs full-auto exists because trust is personal, some people want to watch the first ten go out, some never want to think about it again. thanks for reading.
Getting filtered out before a human sees anything is the real problem, so fixing that alone is valuable.
YOLO mode will appeal to people who just want volume without the grind, but it comes down to how accurate the tailoring is. If it’s off, people won’t trust it.
I’m seeing a similar shift with AI Home Health Software integrating AI into documentation and billing. It’s great when it removes repetitive work and catches things, but small mistakes create bigger problems fast. Same here, accuracy is what decides whether this becomes something people rely on or just try once.
accuracy is the whole ballgame, agreed. the failure i actually watch for isn't a bad application, it's a confident bad one, where the tool tailors something wrong and reports it as done. volume without accuracy just automates the rejection faster. that's the reason i'd rather show someone exactly what got sent than hand them a reassuring number.
This is exactly why generic job applications are broken.
You didn’t fail — the system did.
Building your own AI to bypass it is actually the logical move.
appreciate that, though i'd only half-take the 'you didn't fail' part. the system is genuinely broken, but i also fired off a lot of lazy applications early and blamed the funnel for all of it. building the tool forced me to separate which rejections were the system and which were just me not trying. both were true, and that was the uncomfortable part.
The gap wasn't the number of applications it was the 34% ATS score you didn't know about. Most job seekers optimize for volume because they can't see the filter that's silently rejecting them. You built the visibility first, then the volume. That's the right order.
that ordering was almost an accident, honestly. i built the score first because i wanted to know why i kept getting rejected, and only later realized the volume was worthless without it. seeing the filter is the part nobody sells, because it's less exciting than 'apply to 500 jobs while you sleep.' thanks, that framing is cleaner than mine.
Yes! Exactly.
This hits hard. That “127 applications → 3 callbacks” experience is way more common than people admit.
What I like most is you didn’t just complain about ATS — you actually built something that solves it end-to-end. The 6-step pipeline + sleep automation is a strong angle.
On “YOLO mode” — I think people want it, but also fear it. Maybe the sweet spot is control + transparency (like showing exactly what’s being sent).
$12/month feels very reasonable for the value, especially if it actually improves response rates.
Curious to see how users behave long-term — do they trust full automation or stick with copilot?
Really solid build 👏
late correction on the one number you quoted back to me. the $12/month was real when i wrote this post, but it is not the price any more. it is $19.49/week or $38.99/month now, and the top tier is $33.99/week. i have edited the post rather than leave your comment anchored to a number that stopped being true. the free tier still exists and still excludes auto-apply, so the honest version is: free to try the scoring, paid to have it actually apply.
early answer: almost everyone says they want full automation, then reaches for copilot the first time it touches something that matters, like a cover letter or a salary field. trust isn't a setting, it gets earned per action. the people who go full-auto are usually the ones who watched it handle the boring 80 percent first. 'control plus transparency' is exactly it, showing what's actually being sent is what converts a skeptic. thanks for the thoughtful read.
This comment was deleted a month ago
the churn point is the real one, and you're right that the use case is spiky rather than steady. someone lands a job and the reason to pay evaporates overnight. i've gone back and forth on sprint pricing for exactly that reason. the wrinkle is that a search rarely ends cleanly, people land, then get laid off, then start again, so the 'sprint' is really a recurring event with long quiet gaps between. i don't have this solved and i won't pretend the pricing is finished. the honest version is: price it to the search, not the calendar.