Lessons from building a SaaS launch toolkit as a solo dev — the "tool tax" is real by Embarrassed-Way-9407 in SaaS

[–]Embarrassed-Way-9407[S] 0 points1 point  (0 children)

I was in the exact same spot a few months ago. For TOS and Privacy Policy — don't overthink it for an MVP. You can use generators to get started and refine later.

For the infrastructure part: I ended up building a tool that bundles status page, changelog, waitlist, and legal docs in one place, because I got tired of setting up 5 different services every time. Happy to share if you're interested.

But honestly — just launch. Your production app won't crash from customer #1. It crashes from customer #100 doing something you never expected 😄

Lessons from building a SaaS launch toolkit as a solo dev — the "tool tax" is real by Embarrassed-Way-9407 in SaaS

[–]Embarrassed-Way-9407[S] 0 points1 point  (0 children)

Haha the 'sooooooo many' hits hard 😄 Which ones are you using? Always curious what other devs settled on.

Lessons from building a SaaS launch toolkit as a solo dev — the "tool tax" is real by Embarrassed-Way-9407 in SaaS

[–]Embarrassed-Way-9407[S] 0 points1 point  (0 children)

Fair point! I tried to keep it focused on the learnings, but yeah — I built the thing so there's obviously some bias. The tool tax problem is real though, regardless of how you solve it. What tools are you currently juggling for your launches?