I built an auto-apply tool, then found out a lot of "applications" never actually submit
quick build-in-public update, solo founder, no team.
backstory: i built a thing that auto-applies to jobs. felt great. then i started checking the receipts and noticed something uncomfortable. a chunk of "applied" jobs had no confirmation on the other end. the form filled, the button got clicked, nothing landed. the tool reported success. the job never got it.
filling boxes is easy. actually landing in the employer's system is the hard 10%. so i rebuilt the whole thing around one question: did this submission actually go through. now every auto-apply runs a verification pass and only calls it done when it can confirm (a confirmation page, a confirmation email, or the application showing in the candidate portal, two of three or it flags it). if it can't confirm, it says so instead of lying to you.
what i learned: the trust gap in this category is enormous because the audience has been burned by tools that count a filled form as a win. verification is the product, the apply is just the verb.
if you've used any auto-apply tool and felt unsure whether it really submitted, that feeling is the exact thing i'm building against. did you ever confirm one of those actually went through? how?
it's free to start if you want to poke at it: https://aiapplyd.com/?ref=indiehackers
Verification is the product is a reframe that probably applies to most automation tools in categories where the action happens on someone else's system. If you can't confirm the outcome independently, you're just automating the hope that it worked.
Discovering this by watching silent failures accumulate rather than a single loud one is both the worst and most honest way to find it. The applications looked like they went through, which is exactly what makes this kind of bug invisible until someone specifically goes looking for it.
"Verification is the product, the apply is just the verb" is the whole positioning, and it generalizes: every automation category quietly counts the easy metric (form filled) instead of the true outcome (application landed). Your real competitor isn't other auto-apply tools, it's the distrust they created, so I'd make the confirmation the billable unit and the public proof at once: only charge for confirmed submissions and show the receipts. In a category full of tools that lie, being the one that says "this didn't go through" out loud is the moat, not a limitation.
Verification is the whole point here. A lot of workflow tools quietly define success too early, so the user gets the feeling of automation without the result they thought they were buying. I ran into the same thing with DictaFlow: speech to text is easy to demo, but if the text doesn't land cleanly in the actual field where you're working, the product failed even if the transcript was perfect. "Verification is the product" is a much stronger frame than "auto-apply faster."
The gap between 'form filled' and 'actually submitted' is the exact same pattern we see in business automation. Most tools report success on action completion, not outcome confirmation. That distinction separates tools that give you peace of mind from tools that give you a false sense of activity. Did you find the two-of-three verification threshold through testing, or was there a specific failure that revealed that balance?
This is a subtle but important shift. Most tools in this space optimize for “task completion,” but the real user expectation is outcome completion. If “submitted” doesn’t reliably mean “received,” then everything built on top of that assumption breaks. Verification as the core feature is actually a much stronger positioning than automation.