Non-technical solo founder building a SAAS
I am a solo founder, with product marketing/business background and I have been learning to code so I can build a SAAS tool. I have built prototypes experimenting with Twilio APIs, some basic Python, Google sheets, Google apps script, etc. But I am still an amateur. This is something folks often don't recommend (for a solo non-technical founder of a SAAS tool)
However, I don't want to bring a tech co-founder until I have validated my product. Plus my rationale is that if I learn to code and I have contractors to help me, then I will be able to understand potential issues as they come up. Is this a valid thought process? Or am I thinking about this the wrong way?
Trending on Indie Hackers
Can you make a MVP that is the simplest and show it to the customer? If yes, that's good enough. Your thinking is correct, as a tech guy I don't believe a "business" without solid proof. If you think that an idea works, show me the number whether it's an order or whatever.
I am not a good developer either. My background is product marketing and project management transiting to a web developer. Even I have a cs degree and code for several years. I occasionally found myself stuck in a problem for a long time. However, I am still able to solve the problem and move forward to finish the MVP. Nowadays, I find programming is much easier than 10 years ago. So don't be too worried unless you're building another google / tesla.
Just google more accurately, make a work log / detailed doc and you can be a good-enough programmer to build something working.
Don't over-engineering stuffs. Drop docker if it's annoying, use shitty jquery if finding React hard to go with. Leave server alone with heroku, firebase or tools. Drop everything unnecessary.
A project usually consists of frontend, backend, devOps, design, marketing. Find ways to drop areas you're not good at and you can move forward.
Thanks @bennychan!!
That is very helpful. Honestly, I am spending more time learning to code rather than on my company, which I am perfectly happy with for the time being. What I struggle with is understanding the best stack to use and making sure I am learning the appropriate language/framework
It's sort of like representing yourself in court. Not recommended in general (and lawyers will give thousands of valid reasons), but given the right circumstances, it could work out pretty well.
As long as you're confident you can code it yourself...It's fine.