<story><title>Hidden work when launching a SaaS</title><url>https://workshop.kwoosh.com/post/the-hidden-work-when-launching-a-saas.html</url></story><parent_chain></parent_chain><comment><author>mrkurt</author><text>This is hidden work for running a function SaaS, not launching one.&lt;p&gt;The trick to launching a SaaS is picking the right things to _not do_. Some of the fun of a SaaS is iterating on everything from product features to pricing to support tooling. It&amp;#x27;s very difficult to get pricing, trial periods, and billing model right on the first try. So usually you&amp;#x27;re better off doing less of that, and figuring it out later.&lt;p&gt;And you really don&amp;#x27;t need a crazy sophisticated drip email setup. Doing email marketing for existing users and new signups right is something that will get you incremental gains. If you convert 5% better when you have 1000 signups per month, you&amp;#x27;ll be happy. If you convert 5% better when you have 10 signups per month you&amp;#x27;ll never even know.&lt;p&gt;Silly as it sounds, if you spend more than an hour or two thinking about sales tax before launch, you&amp;#x27;re wasting time. Screwing up sales tax at launch will not kill you. _Skipping sales tax entirely_ at launch will not kill you. In fact, very little that can go wrong will kill you. You&amp;#x27;re probably going to die because you didn&amp;#x27;t make enough go right.</text></comment>
<story><title>Hidden work when launching a SaaS</title><url>https://workshop.kwoosh.com/post/the-hidden-work-when-launching-a-saas.html</url></story><parent_chain></parent_chain><comment><author>dalfonso</author><text>Yes, these are the &amp;quot;features&amp;quot; that really bog down the excitement when trying to launch -- user invites, user profiles, billing, transactional emails, password reset, file upload, PDF conversion, free trial capability, coupon code capability, shared accounts, PERMISSIONS, etc.  Then you get to the next level -- search, caching, deploying.&lt;p&gt;Not exactly in the same vein as the others, but I&amp;#x27;ve never seen soft-deletes done really well either i.e. the user can &amp;quot;delete&amp;quot; something but it still lives in the database.  It&amp;#x27;s one of those features that sounds good but when it comes time to implement, it ends up being more trouble than it&amp;#x27;s worth.</text></comment>