SaaS asymptotes are brutal, brutal things, and they sneak up on first-time SaaS owners all the time. You feel like you're doing everything right, the product is getting better, you haven't stopped working... but growth hits a wall.
This happens with mathematical regularity.
"That's a metaphor, right?"
No, I mean there is literally a formula. Tell me your acquisition numbers last month and your churn rate; I'll tell you your revenue when you hit the wall.
This is a great business waiting to be built. The state of the art for it, at places which charge $$$$ for tax preparation, is "Get out your calendar, tell us what days you were in X (perhaps by filling in Excel), and a ludicrously underutilized person will total by hand."
A number of people got in touch with me in the 2013ish era as a businessman with legitimate banking on both sides of the Pacific to help them move money out of Mt. Gox.
Which, as you might expected, I noped right out of.
Proposed transaction would sound like "I'll pay you $120k in JPY, coming from Mt. Gox. You pay me $100k in the US. It's a win win; I avoid Mt. Gox's banking delays and you make money."
I suspect a great deal of peoples' annoyance with KYC isn't anything which is actually *required*, but is hitting poor *implementations* of it, sometimes with no clear path forward, which prevent them from doing the thing they actually want to or have to do.
This is often times because post-opening KYC is generally coming from exception handling in the financial system, and because (for the types of transactions likely to cause that in the lives of "typical people commenting about KYC") it is an edge case and not very designed for.
You often see (or worse, don't see) cracks in the abstractions, too, where you are dealing with someone passing a message from someone passing a message from someone passing a message from the underlying call site which generated the exception.
I've been a small business owner and can talk at length about SMB banking, and will later, but let's put on the software developer hat right now.
Lots of software talks about money, keeps records about money, does calculations about money, but can't *touch* money.
This is extremely frustrating when you're building SaaS apps for businesses, because you have total control over your UX right until your app needs to touch money... at which point all data about it lives in a silo you can't access.
Back when I was a Stripe user, my #1 ask for 3 years running was Capital. (Loans based on anticipated future revenue, which my SaaS company had in abundance while my bank account was feeling rather lonely.)
We have now made that capability available for our customers' customers.
Historically, banks were the primary point of interaction with the financial system for small businesses, and that interaction was largely mediated by humans.
Increasingly, the interaction is via an online platform, which provides a lot of the front and back office of the SMB.
If, for example, you run a platform which helps connect contractors and home owners, you likely have better data on their businesses' pipelines, revenue history, customer satisfaction, etc than any bank could hope to have.
There's an interesting microeconomics / finance / incentives angle here, where if this is your anticipation, you might decide to book the travel now and expect that providers will be lenient with cancellation/refunds if conditions worsen markedly over the next 6+ months.
Note that purchasing that option value is very much not a zero risk trade. For one reason, unlike financial options traded through a clearinghouse, you may be directly exposed to credit risk of the counterparty, which may not survive all possible futures.
Bonus lesson from credit card processing: the chargeback mechanism writes an option for the purchaser. The cost of it is bundled into the economics of credit cards, which are complex and involve multiple parties.
That option may have been mispriced in 2020 vis travel plans.