I spent 14 years as a real estate appraiser before I built any software. The work was never the hard part. The hard part was the email I'd put off sending for two weeks: "Hi, just following up on the invoice from last month."
I assumed that was a me problem. Turns out it's close to universal, and I only realized how universal when I went looking for the actual language people use.
I read through a stack of Reddit threads on how people describe late and unpaid clients, and the pattern was almost comically consistent. People weren't writing about the money. They were writing about the asking. A few that stuck with me:
- "I'd rather do 10 hours of extra work than send that 'just following up on payment' email."
- A nanny, after three weeks of a family forgetting to pay: "asking for payment is so awkward."
- A tutor, two years in: "this is genuinely one of the parts I still haven't figured out."
- A photographer: "I feel if I were to ask for payment, things would get awkward."
Thread after thread, the emotional center was the same. Not "I'm worried I won't get paid." It was "I can't make myself be the person who asks." One person called it freezing. Another said the silence after sending an invoice was the part they struggled with most.
That's a different problem than the one most invoicing tools solve. The tools assume the bottleneck is creating the invoice. For a lot of solo operators, the invoice goes out fine. The bottleneck is the follow-up, the second and third ask, the one that feels like nagging someone you have an ongoing relationship with.
I noticed something else: the pain scales with how personal the client relationship is. Tradespeople in those threads mostly shrugged, invoicing a stranger for a roof is transactional, nobody feels weird about it. But nannies, tutors, photographers, home organizers, anyone whose client is half-friend, described real dread. When the relationship matters, asking for money feels like risking the relationship.
So I built a small tool around exactly that: Payable.at. You send one payment request, and it handles the reminders for you on a schedule until the client pays, then stops. The point isn't efficiency. The point is that you're never the one sending the awkward second message. The tool is. It works with the payment methods people already use (Venmo, Zelle, PayPal, Stripe), so there's nothing new for the client to learn.
I won't pretend it's for everyone. If you invoice strangers for one-off jobs and don't feel weird chasing them, you don't need it. But if you've ever left money on the table because sending the reminder felt worse than eating the loss, that's the exact person I built it for. It's free to start.
The bigger lesson, for anyone who builds things: I almost positioned this around "get paid faster" and "cash flow," the rational, financial framing. The language people actually use told me the real driver is social discomfort, not money anxiety. I'd have built the right tool with the wrong message. The words your users reach for unprompted are usually more honest than the words you'd write for them.
Solo founder, still-practicing real estate appraiser. Payable.at is the thing I wish I'd had for the last decade of chasing invoices.
Top comments (0)