Then, when you go to make it official, you have much more power in the negotiation.
If it's working well, making the "shadow IT" SaaS tool an official purchase typically goes:
Team Lead: Everyone is using this tool, we're about to go above the free tier and need to purchase it.
IT/Finance: You should have gone through the process, you need to fill out these forms.
VP/CEO (to IT/Finance, seeing value of tool): Just get it done
Examples: YouTube, GitHub.
> Just get it done
Getting it done is a process heavy, minimum 4 month process because of purchasing rules. That's the problem I'm calling out.
No need for someone to do that. The process and distribution method kept you from that.
I may have been unclear. The "bottom up" approach is precisely designed to circumvent and solve the case where the user is not necessarily the buyer. It emerged to solve the "shrink-wrap software", or when you did not have an army of salespeople.
One way to look at it is "bringing SaaS to enterprise", which was typically the distribution model for consumer applications.
Plus delegating control of your payment relationship with your customers to a third party is more of a pain than a boon.
My engineers could spend money on new pieces of third-party infrastructure pretty easily via Heroku plug-ins. If the spend got big we figured out how to address it.
For this dynamic to work for you as SaaS developer, you need enough runway to wait for your users to adopt your tech and have some fraction organically grow big enough to be real money.
This rhymes with how Intuit won the accounting market. They initially got destroyed in reviews when compared to their more mature yet complicated competition, but everyone starting a business wanted cheap and simple. You just need to be willing to wait for enough of your early garage-based startup customers to become S&P 500 companies. While you're waiting, you're also evolving your product so that it better meets your growing customers' needs.