How to create a successful SaaS from scratch.

Steal the process I've used to build 5 $10k+ MRR SaaS's.

🧵 THREAD 🧵

#1 Find a problem

Problems are everywhere.

Everyone has one:

>> Agency Owners
>> Coaches
>> Freelancers

All you have to do is Investigate, ask Qs and deep dive into a niche.

Then find a painful problem that people wouldn't mind paying money to get rid of.
#2 Find an existing solution

This one is the easiest part of the process.

Here's what to do instead:

Go to Google and search for "[Problem] + software".

Compare the available solutions.

Pick the best one.
#3 Reverse engineer how it works

Break down the solution in it's core components.

Most SaaS are structured this way:

>> Database
>> Back-end
>> API
>> Front-end

This is easier if you already know programming.

But if you don't, you can pay someone to break it down for you.
#4 Make it better

Think of ways to make it better.

See what the current solution is lacking and fix it:

>> Is it too slow? Make it faster
>> Is it too ambiguous? Make it simpler
>> Does it lack features? Add them

The thing is to add VALUE to your solution.
#5 Build it

I've said this before and I'll say it again:

You DON'T have to code your SaaS yourself.

Instead, pay someone to build it for you:

>> Go to lemon(dot)io
>> Tell them about your project
>> Let them match you with a dev
>> Give project to dev
>> Wait until it's done
#6 Traffic

All that's left is driving traffic to your SaaS.

Start with free traffic:

>> Blogs
>> Social media
>> Podcasts
>> Newsletter
>> Your own course

Then use paid traffic:

>> Ads
>> SEO
>> Influencers

From $0 to $2.5k MRR -> free.

$2.5k and above MRR -> paid.
That's it!

I tweet about SaaS, marketing and online business.

Follow me for more actionable advice on those topics.

And if you’d like to get more in-depth SaaS advice subscribe to the Newsletter:

https://t.co/diC24UT2Qu

More from Startups

💪 And we're down to the last 48 hours until the biggest live-streamed startup event hosted by @thepatwalls & @shipstreams kicks off!

With this, let's get motivated with some curated readings & posts by fellow #24hrstartup participants & indie makers. Check them out below!

✍️ Andrew Parrish wrote - "Why I'm Participating in the 24 Hour Startup Challenge".

@makersup's takeaway - Makers love possibilities, the joy of building. Any aspiring maker should experience the end of lurking on forums & reading @wip's to-dos.

Read:

👩‍💻 @anthilemoon created a list of @women_make_ members participating in the #24hrstartup challenge. Do let her know if she missed anyone!

More at:
https://t.co/zYKVZEq8aq


😺 We can't forget one of the key platforms in shipping indie, can we, @ProductHunt?

Check out @ProductHunt's guide to launching at: https://t.co/VB6WgGx6sa.

In addition, it would be wise to prepare for the launch. Fine tune your assets and post at

🚢 Well, we definitely can't leave out the man behind all of this, @thepatwalls!

Launching isn't easy, but know what you'll be facing even before coding. Check out @thepatwalls' "words of shipping" at:

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.