So I'm making another thing.

This one is an 📕Online book +💻app.

It's a project that I've been building towards for a year+.

I've done a ton of interviews around problem validation.

Now, time to build.

My goal: Launch in < 60 days.😬

The problem I've identified (🧵):
How do you make and launch a side project without code? #NoCode

Making and launching is overwhelming, and can be exhausting especially as a side project.

I know it is hard, because I've launched several projects myself.

But when reviewing data...
from Side Project Stack, I discovered something that really surprised me.

I did not realize how many folks using http://SideProjectStack.com  had a desire to make and launch but had not yet launched one project yet.
69% of folks trying http://sideprojectstack.com/get-stackd-product-hunt-launch have never successfully built + launched!

This really surprised me.

It dawned on me that bc many people I interact with on Twitter are vocal, already have made and launched a side project.

I was blind to the silent majority.
So I began to investigate. I was really curious to find out why.

I began to talk with and interview more than 25+ of Makers/Soon to be Makers in addition to the 100+ Makers I've talked to about their no-code side project stacks over the past year.
And bc of Side Project Stack, I saw how Makers were successfully launching, again and again.

Combined talking with Makers who have not 🚢, core issues and trends began to emerge that are major roadblocks to Makers shipping.

I found It can be distilled into 3 main buckets.
1️⃣Time - Many folks I talk to don't have a playbook for launching a side project and are using strategies for launching a startup.

Making a side project is ≠ to a startup

Why do we use the exact same strategies and tactics as a startup?
We need less TechCrunch and more side project stories.

Not knowing what is the next best thing to do, means you can go the wrong direction fast and lose critical inertia and confidence.
Or worse yet, try to solve the problem before you validate the problem.

2️⃣Audience - Building an audience from scratch is hard. That's something I've built. And I still am working to build it. What's even tougher is building an audience while building a side project. Why?
Because its a side project, you are so short on time.

Every step you take must be a step in the right direction. Or you'll sink quick or worse yet, spend months of time and loads of money building something no one wants.

Compounded by the fact that now anyone can build with
nocode. It's a noisy world out there. You launch, get some publicity, then what?

If you don't build alongside making an audience you've lost a powerful lever for people to know your story, know you, invest their time in you and your product to get the initial inertia.
People want to help. Early adopters don't want a polished product, I think a lot of Makers don't realize that's ok.

3️⃣Product - How to make something without code? That's the initial thesis behind http://sideprojectstack.com . But I've observed often, Makers overbuilding with what
I call "expert level" stacks, and miss the opportunity to start small or using an easier stack to learn to validate.

Stop me if you have ever felt this way: You have a vision for something but you don't know where to start?

I've been there. And what happens is you try to build
the whole thing at once. Wasting time and effort. The problem is if you don't talk to your early adopters you'll never confidently have a good starting point. Get validation.

Everyone argues of what an MVP is. But no one thinks about who it should be built for, ur early adopters
What's more there is a group of people even before the early adopters. Did you know there is a segment of people called Innovators?

And as a Maker, you are primed to leverage these early users. But many miss the opportunity to.
But how do you build for them? They actually prefer and overlook a non-polished product. We mistakenly think our first version has to be the final version.

In the book and app I am going detail out an approach based on 100+ other Makers, so you can get going confidently.
So my goal will be to bridge the gap. I have a unique perspective that I believe I can leverage and help people make and launch.

My initial theory for the solution is an online book and app. Paired together in a unique way. Bc I want people using it to spend more time making.
I am a big proponent of learning while you do something.

It's what I did.

And with just enough navigational direction to start off with, I hope to help Makers make w/confidence that ur building it right to save time and aggravation.

Nothing beats that feeling.

What's next?
I'll be sharing everything I have learned from 100+ stacks as well as my own experience launching many projects.👍🏼

Hope that you'll join me.

Feel free to join the newsletter so you won't miss an update and I'll give you a heads up before its launched. https://bit.ly/39ieIdv 
You can follow @MichaelJNovotny.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:

By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.