Building compliance infrastructure for international users is harder than expected

18 months into building our platform and the biggest surprise has been how completely US-centric most of the compliance and business formation infrastructure out there actually is. Everything assumes your user has a social security number. Everything assumes they have a US address. Everything assumes they already exist in the US financial system in some way.

Our user base is heavily international. Founders in southeast Asia, latin America, Africa, Europe, all of them trying to access US financial rails to run their businesses. The gap between what they need and what existing tools support is enormous. We have patched it with manual processes and support tickets for too long. At what point does it make more sense to find a backend partner that has actually solved the non-US compliance problem rather than continuing to build workarounds ourselves?

reddit.com
u/FrameOver9095 — 13 days ago

AI handles our support tickets fine, but CSM action items fall through every time

For CS Ops/CSMs, how are you tracking account needs that don't fit neatly into support?

Things like onboarding milestones, custom report requests, or internal handoffs. They aren't bugs or IT tickets, but still require owners and clear follow-through. If they only live in CSM notes or Slack messages, they get missed.

How do you manage this? Looking for low-friction workflows that won't add admin bloat.

reddit.com
u/FrameOver9095 — 19 days ago

Trying to manage request intake without turning every request into a project

A lot of work here starts as a small internal request, the usual stuff like can you update this process, ops please help with this vendor issue blah blah. Some of it becomes real project work, but a lot of it is just service-type work that needs an owner, a due date, maybe an approval, and a clean handoff.

The problem is that once everything lands in the PM tool, it starts looking like a project even when it really is not. Then the board gets noisy and actual project work gets harder to see.

So, how are you separating true projects from small operational requests and recurring internal service work? You keep them in the same system with different workflows or completely separate the intake process

reddit.com
u/FrameOver9095 — 21 days ago

How are you automating service request intake without making people fill out giant forms?

So I’m looking at ways to clean up internal service requests across IT, HR, finance, and ops.

Right now it’s the intake thats messing everything up the most. People send requests through Slack, email etc or in some cases directly to whoever they know. Then someone has to manually figure out who owns it, the info it is missing and whether it needs an approval.

For anyone who has automated this successfully, did you start with one shared intake form, or separate forms per team? And how much routing logic did you build up front?

Trying to keep this as practical as I can.

reddit.com
u/FrameOver9095 — 1 month ago
▲ 4 r/SaaS

SaaS founders underestimate how much chargeback management actually costs in time

Its not just the lost revenue or the damage to your stripe metrics,.,I actually logged my hours for one month handling this for our app.

Responding to disputes., gathering usage logs as evidence, following up with processors, and updating internal records. It came out to 11 hours of manual work for just 14 chargebacks.

At any reasonable founder or developer hourly rate, that time cost far more than the actual disputed revenue. The financial loss is visible right on your billing dashboard. The time cost is completely invisible, and most bootstrapped founders never calculate it until they’re burning out handling it manually every single week.

reddit.com
u/FrameOver9095 — 1 month ago

Service request management software for clients is perfect but our internal requests are a mess

We manage ticketing for 30+ clients. Their systems are pristine. Auto routing, SLA alerts, escalations, the works. Our own internal IT requests is however a complete disaster. Someone needs software access and it's a chain of Slack DMs and emails. Took an incredibly long time last week to get a new tech provisioned because the request bounced between four people and nobody knew who was supposed to do what. We literally sell this service to other companies and can't figure it out for ourselves.

reddit.com
u/FrameOver9095 — 2 months ago

So every morning I open the helpdesk queue and there's like 50 tickets just sitting there all marked the same priority. I have to go through each one and figure out if it's a password thing, hardware thing, network thing, whatever. Then manually assign it to the right team. This morning took me an hour and a half because people write the vaguest descriptions. "Computer not working" okay cool which computer and what's not working??? I keep asking if we can get something that does this automatically based on keywords or categories or literally anything. Boss says it's on the roadmap. Roadmap for what year though??

reddit.com
u/FrameOver9095 — 2 months ago