Earlier quoted context omitted.
I think the right step would be to somehow communicate to the vendor that this feature is needed (eliminating the PM backlog BS) and their coding Agents should pick it and build it. The real moat they have is SaaS vendors have everyone believe that trivial feature requests take time to implement.
That introduces a level of indirection between "what I want" and what gets built. A workflow like the OP just has less friction. SaaS platforms would want to provide more stable accessible APIs if it becomes a popular model, because users would find it more usable .
Forcing an inversion of control on the SaaS stack
11–20 of 50 posts
Re: Forcing an inversion of control on the SaaS stack
#12Enterprise userscripts? Very neat, though I wonder if typical enterprise security policies would allow for this.
Re: Forcing an inversion of control on the SaaS stack
#13Re: Forcing an inversion of control on the SaaS stack
#14Although I absolutely understand the frustration expressed by the author, I find the notion that SaaS companies are somehow 'evil' because they optimize for the 80/20 rule a bit arrogant. Anyone working in SaaS - or really in any business- understands that you need to prioritize. In the end, your obligation as a company, regardless of your product, is to generate profits. And that's absolutely OK.
> In the end, your obligation as a company, regardless of your product, is to generate profits. No denying that. SaaS started with a user problem at the center of it and as they scaled, forgot about an individual user. This only presents the user frustration and a possible solution to it.
If you're building for individual users you're not going to succeed. We all prioritize for broad success from the beginning.
I'm very into the idea of inversion of control and giving users this flexibility but I agree with GP that the SaaS company critique is misplaced. I hope you find enough success with 100X that you end up coming to the same conclusion.
I'll also add that one of your video examples is essentially a Twitter spam generator; is that the kind of feature you think SaaS companies should be prioritizing?
Re: Forcing an inversion of control on the SaaS stack
#15I hope there's some forced migration of the SaaS business model towards primarily being "just an API" for whatever magic sauce it is they have. Too much of SaaS moats are just locking the backend behind an undocumented API. Users should be able to have full control over their experience interacting with third parties if they want it. This isn't unique to post-LLM stacks like this, but it seems like this shifts the ba…
I think the right step would be to somehow communicate to the vendor that this feature is needed (eliminating the PM backlog BS) and their coding Agents should pick it and build it. The real moat they have is SaaS vendors have everyone believe that trivial feature requests take time to implement.
So true. People are going to be sooo mad when they find out we all have these Build Features For Free buttons and just don't press them.
Re: Forcing an inversion of control on the SaaS stack
#16Re: Forcing an inversion of control on the SaaS stack
#17Earlier quoted context omitted.
> In the end, your obligation as a company, regardless of your product, is to generate profits. No denying that. SaaS started with a user problem at the center of it and as they scaled, forgot about an individual user. This only presents the user frustration and a possible solution to it.
> as they scaled, forgot about an individual user If you're building for individual users you're not going to succeed. We all prioritize for broad success from the beginning. I'm very into the idea of inversion of control and giving users this flexibility but I agree with GP that the SaaS company critique is misplaced. I hope you find enough success with 100X that you end up coming to the same conclusion. I'll also a…
Re: Forcing an inversion of control on the SaaS stack
#18You don't want to ship every feature every user wants, for various reasons that I assume are obvious. Instead make it extensible.