Which one of the following do you do next?
- keep on pushing to deliver quality stuff for both
- quit the 9-5, hire yourself as freelancer to spend more time on your project
- quit the 9-5, use your own savings to survive and build an MVP as soon as possible
- quit the 9-5, get funding and fully commit to your startup
IMHO if you freelance you also spend a lot time working for somebody. Same as a 9-5 job.
What i would do:
I can definitely attest to this. Recently tried the whole "freelance part-time, startup on the side" thing.
It failed miserably.
Freelance work is objectively messier and more time consuming than a standard 9-5.
And if you're a developer, you can probably (maybe?) afford to hire a freelancer to help you move faster if your after-work time isn't sufficient to keep a good pace.
Personally, my goal would be to quit the 9-5 as soon as possible no matter what I'm working on! But I first did that when I started freelancing, and I'm currently doing that now :)
As most have said, option 1 is the best one, I'll add my own take :)
Building any product is risky, if you work at an established company a the risk of a new product is losing money, if you are building a startup the risk of your new product is no income.
If you can develop your product nights and weekends then do that, it means less going out but that's why we do it. All the while, test and iterate. Collect as much feedback as possible, talk to as many people as you can squeeze in and once you think you've had enough talk to more. There are 2 main stages to work through in going from idea to MVP to product.
Something as simple as a landing page with form and $50 of Google ads can help you validate your idea to see whether it's worth it. It's not too time consuming so this is a pretty easy first step.
A) Once you have an MVP, get those people (and more, run more ads, post here, on reddit etc) to test the product out and note their feedback. This is also doesn't have to be too time consuming, set up a system for reaching out and collecting feedback (maybe a google form or airtable form).
B) Try to connect with the people testing it on a call and record it if you can, this does get a bit time consuming but it's not too bad to juggle with a job.
It's important to not just ask for features to tack on so much as understand their goals, problems, and how your product solves for them in a way no other product does. No one wants features they want problems solved.
Rinse and repeat A and B as you iterate until you get to a point where people are regularly using your product, the kinks are worked out, and you have people paying/willing to pay. You'll get a gut feeling when managing the support volume/sales strategy/product development is just too much to do with 9-5 AND is worth quitting your job for.
But
I would re-evaluate my need (or rather, desire) to code an entire program and see if it's worth going down the no-code solution. This is what I've been doing this past month and honestly, it seems like a better approach for me.
Can you elaborate on what you mean by this? Or paste me a good link? I don't understand where the definition of "no code" begins and ends... Seems like most ideas or MVPs require something custom.
No worries! As a developer I wasn't really appealed by the whole no-code aspect of things until I realized that it actually can be pretty customized. But for example, you can make pretty customized landing pages for your app and "replace" some of that development with no-code, and still leave the rest of the development for your core product, if that makes sense. Not everything needs to be developed, at least for the MVP, because the most important thing is to ship it sooner than later.
Here's a pretty good resource I use for no-code build: https://www.makerpad.co/. This website was even built off of no-code, and it seems pretty customized.
Hope that helps!
Have you done any validation of the need your mvp is planning to solve? If you want to quit your job, do that first to make sure there are people who actually want the thing you're building. Otherwise I say keep grinding away at both.
Stay employed, build your project during your free time. See it grow until it can replace your employment income, then leave and focus on the project full-time.
I would opt for 1., with these immediate steps:
Then look into bootstrapper funding sources like Earnest Capital or indie.vc to make sure you stay your own boss.
This way you keep your job if your idea does not stick or you can prove your idea an generate enough revenue to quit your day job.