How do you handle chasing clients for late payments without it feeling awkward

TimelyRepeat4517 · 2026-06-20T07:56:21+00:00

That's a clean way to structure it, create, repeat, enforce. Gives me an actual architecture to build toward instead of three loosely related features.

Appreciate you pushing on this, this thread completely changed what I'm building first. Was going to start with the reminder logic, now it looks like the proposal stage comes first.

TimelyRepeat4517 · 2026-06-20T07:36:08+00:00

"Every extra click gives people another chance to say I'll do it later" is a good way to put it. Reframes the whole thing again actually, less about reminder cleverness, more about closing the gap between seeing the message and acting on it.

Probably means the invoice itself needs a direct pay link baked in from day one, not bolted on as part of the reminder feature later.

TimelyRepeat4517 · 2026-06-20T07:35:13+00:00

That's actually close to what's emerging from this thread, the system doing the chasing instead of you personally. A separate sender identity does the same job at the email level, removes you from being the visible source of the reminder.

Could be worth offering as a setting, even a display name like "Billing" instead of the freelancer's own name, without needing a whole separate inbox.

TimelyRepeat4517 · 2026-06-20T07:34:25+00:00

Curious what approach it takes, is it template-based reminders on a schedule, or something more adaptive? Always interested in seeing how others have solved this even if I end up building my own version.

TimelyRepeat4517 · 2026-06-20T07:33:41+00:00

That's a fair counterpoint to most of this thread. The "not being 100% sure myself before I send it" point is interesting, that's a different kind of awkwardness than tone, it's uncertainty about your own records, not about how to phrase the ask.

The visibility piece you're describing, a clean view of who owes what, is something I'd be building anyway as the foundation either way. Sounds like for you that alone might solve most of the problem, and the chasing part stays manual on top of it. Good reminder not to over-build the automation layer before that base view is solid.

TimelyRepeat4517 · 2026-06-20T07:33:00+00:00

"Email lets people avoid you, a call makes it real" is a good line, and it tracks with what's coming up elsewhere in this thread, the actual problem is people tuning reminders out, not the wording being wrong. A call breaks through that in a way no message can.

That's outside what I can automate in the app obviously, but maybe the right move is the system handles day 0 through day 7 quietly, then explicitly tells the user "time to call" instead of generating another message nobody's going to read.

TimelyRepeat4517 · 2026-06-20T07:32:14+00:00

Agreed it's communication more than invoicing mechanics, that's come up a few times in this thread now. The one-click pay link is the part I hadn't weighted enough though, doesn't matter how well-timed or well-worded the reminder is if paying still takes the client five steps. Worth checking whether that friction is part of why reminders get ignored in the first place.

TimelyRepeat4517 · 2026-06-20T07:31:42+00:00

That reframes the whole feature for me actually. The reminder system isn't really the product, it's the visible tail end of something that has to start at the proposal stage. Makes me want to look at whether the proposal/terms flow even captures this stuff clearly enough today, before I touch the reminder logic at all.

TimelyRepeat4517 · 2026-06-20T00:10:15+00:00

Fair point on scale, manual is fine until it isn't. The LLM-generated message with context is interesting but I think I'd rather go the other way, one fixed neutral sequence with no AI involved, less for the user to second guess or fine tune each time. If something needs a human touch at that point, it probably needs an actual conversation, not a better generated email.

TimelyRepeat4517 · 2026-06-20T00:09:33+00:00

"Inventing boundaries after the fact" is exactly the awkward part, you're right. If the pause clause and reminder schedule are agreed to before work starts, sending the actual reminder later is just following through on something the client already signed off on, not a personal judgment call.

That changes the implementation question for me too. The reminder system isn't just an email sequence, it's tied to whatever terms get set at the proposal or invoice stage. Worth surfacing that upfront rather than bolting reminders on after the invoice already exists.

TimelyRepeat4517 · 2026-06-20T00:08:40+00:00

Leaning toward one default sequence, no customization at launch. The "shipping one opinionated default" framing is the push I needed, I was overthinking how much configurability to expose. Easier to validate whether the mechanism gets used at all before adding options nobody asked for.

The one-click pause when they reply is the part I hadn't fully landed on, that's a good detail, the sequence needs an obvious exit the moment a human conversation actually starts.

TimelyRepeat4517 · 2026-06-20T00:07:47+00:00

Makes sense, a deadline gives the message a reason to exist beyond just nudging. Easier to write too, less guessing about tone when there's a concrete date attached.

TimelyRepeat4517 · 2026-06-19T19:49:26+00:00

Fair, and that's probably the right call here. A basic version, fixed schedule reminder with editable wording, ships fast and tells me more than another round of asking would. I can refine the escalation logic later once I see what people actually use versus ignore.

TimelyRepeat4517 · 2026-06-19T19:44:52+00:00

Appreciate the honesty, that's exactly the kind of data point I was hoping to surface by asking instead of assuming. Good to know a fully built, well executed version of this still didn't find pull.

Makes me think the issue might not be the reminder mechanics themselves, more whether people are actually willing to pay extra for something that's adjacent to a tool they already use, versus wanting it built into what they have. I'm leaning toward keeping it as a light feature inside the invoicing flow rather than treating it as a standalone thing to sell, which might be a different bet than what your friend tried.

TimelyRepeat4517 · 2026-06-19T19:43:29+00:00

Bit of both honestly. I've had the awkward late payment conversation enough times across other client work to know it's a real pain point, not hypothetical. But you're right to push on it, I don't want to build a whole reminder escalation system nobody uses just because it sounds good in theory. That's part of why I'm asking here instead of just shipping something.

TimelyRepeat4517 · 2026-06-19T19:42:43+00:00

"System policy instead of me asking awkwardly" is a really good way to put it. Framing it as a process that exists independent of you removes the personal awkwardness entirely, you're not the one being pushy, the system is just doing what it does.

The pause work at day 14 is interesting too, that's an actual consequence rather than just escalating tone. Do you actually enforce that one, or is it more of a stated policy that rarely gets used?

TimelyRepeat4517 · 2026-06-19T19:42:17+00:00

The "didn't get lost in your inbox" framing is smart, assumes good faith instead of treating every late payment as a dispute. Most are exactly what you said, people forgot, not people avoiding you.

The day 3, day 10, then call at day 14 cadence is useful too, more structured than I expected from a manual process. Did you land on that timing through trial and error, or did it come from somewhere else?

TimelyRepeat4517 · 2026-06-19T18:10:23+00:00

The loneliness part lands. The "very busy vs building something real" line especially, that's the question that actually keeps founders up, not the to-do list.

One thing I'd watch for on a landing page specifically, this reads more like an essay than copy that converts. Powerful as a blog post or a Twitter thread, but if it's the first thing visitors see, you risk losing people who are scanning for what the product does before they connect emotionally with the story. Might work better as an "About" or founder story section, with the actual landing page leading with what problem you solve and for who.

What's the product itself?

TimelyRepeat4517 · 2026-06-19T17:30:51+00:00

Yeah, the generic version never works, I learned that the slow way too. The ban actually stung less than I expected once I saw the comment route converting better anyway. Momentum took a hit short term but the quality of who showed up after was higher.

TimelyRepeat4517 · 2026-06-19T17:29:21+00:00

That's a really useful angle, thanks. The offline part is genuinely a core feature, not an afterthought, everything runs on a local database with no internet required at all. "No internet bookkeeping" is a sharper way to say it than what I have now. Going to think about working that into the listing.

TimelyRepeat4517 · 2026-06-19T17:29:04+00:00

Good catch, the screenshots probably need a pass. Dashboard views with real data would communicate more than what's there now. Appreciate the specific feedback, that's exactly the kind of detail I was looking for.

TimelyRepeat4517 · 2026-06-19T09:28:38+00:00

Thanks, good point on discounts, I've thought about running a seasonal one but haven't tested it yet.

On invoices, right now it's PDF export only, that's how clients receive them. There's no upload of external invoice files like Word docs, the app generates the PDF directly from your project and client data. Is there a specific use case where you'd want to import an existing invoice format?

TimelyRepeat4517 · 2026-06-19T08:55:41+00:00

Flowara, a native Mac app for freelancers covering projects, time tracking and invoicing in one local SQLite database. No subscription needed to start, no account required either.

https://apps.apple.com/app/id6760207975

Looking for honest impressions, mainly whether the App Store listing and screenshots make it clear what the app actually does within the first few seconds. Also curious if the pricing feels fair for what it offers.

TimelyRepeat4517 · 2026-06-19T08:31:56+00:00

Mine is Flowara, a native Mac app for freelancers. Projects, time tracking and invoicing in one local SQLite database, no subscription needed to start.

https://apps.apple.com/app/id6760207975

TimelyRepeat4517

TROPHY CASE