Original Summary

Instead of building for a month and then looking for users, I did it backwards. I asked one honest question in a payroll community (“how do you double-check payroll before you run it”) and just read. Around 14 people described their real process. Most of my assumptions were wrong. The pain isn’t catching errors. It’s comparing this run to the last one and flagging what shouldn’t have changed: a new name, someone terminated who’s still getting paid, a number that jumped too much. Duplicate IDs and blank cells? Table stakes, nobody cares. The comparison is the actual job, and I’d built it as a side feature. My competitor is Excel, not other software. Everyone serious had a spreadsheet they’d trusted for years, basically a family heirloom at this point. If you’re not clearly better than that, you don’t exist to them. The pain I solve is rare but expensive, not frequent. The #1 daily headache is chasing people for timesheets, which no tool fixes. What I help with (the terminated employee still getting paid) is rare but brutal when it slips. Someone mentioned a real case of a terminated person paid 600k. So I stopped selling “save time” and started selling “catch the one that costs six figures.” The thing that actually makes people click, though, is privacy. “Runs in your browser, nothing gets uploaded” is what got a tester to even open the link, because it’s salary data. Had it buried at the bottom. Moving it up. What I still haven’t figured out: whether anyone will pay. Pain is real, usage is starting, willingness to pay is still open. Built it as a solo dev, happy to share the link in the comments if anyone wants to look.   submitted by   /u/Suuehtam [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/10/16 06:53:31