What it takes for a non techie to start and scale a tech SAAS startup?

It's all in the mind. I think it's important to give yourself some credit. If you've been driving for years, and have been working with computers for a long time, it's easy to think "why not?". So, ask yourself - "what do I know about software startups?".
I think most non-techies think it is a "hard sell" and "harder still to make money". However, it's not. And, they'll make money. It's not hard - it's just a lot of small steps.

Hello @Deep1010 ! 👋

Welcome, and congratulations for your startup kickstart! 🎉
I currently advise non-tech founders in the Edith & Nous project and here are some insights on how to be successful as a non-techie.

TL;DR:

• Validate your product needs before any development
• Work with a product-minded developer
• Each developer hour should be focused on product development, avoid tech for tech
• Avoid unnecessary distraction (meetings, calls, ...) so you can focus on your business
• Invest your time in growing your business (getting more customers, gathering feedback)

As I don't know what is your SaaS, I can only give general advice.
First of all, if you don't have a product yet, you should try as much as possible to validate your ideas with no-code tools or at very low cost.
One of the common mistake is to hire developers and work on a very complex product, which cost time and money and lead to failure. Narrow the scope of your product and make sure you reduce the amount of tech work to the minimum until you have market confirmation (people paying for your product). If you don't feel confident enough in no-code tools or low-development tasks, invest in your learning so you get at least a grasp of what it takes to build a SaaS from the engineering side.

Development should only come after you have confirmed there is actual need for your product, and this is generally at this point that you will need to have a developer working at least part time on this.

The critical point is to work with someone you trust and can deliver well in terms of product. It doesn't really matter which technology is used, but make sure this person has some experience in building products and is able to grasp what matters in your business area. Each hour passed writing code should deliver value for your customers and your developer should understand that.
Another common mistake is engineers willing to experiment or have fun with the code and losing sight of the product requirements. It often leads to overcomplicate products, or worse, useless feature. Techies should help you determine how best translate product requirements to code, not produce code for the sake of it.
Avoid developers agencies, it often cost a lot, and look for freelancers with product experience.

At some point, your developer should be able to produce and deliver without much help from you, which means you'll need to be able to explain properly what you need and let the production be done.
During the development time, your main goal is to promote and drive growth and you should not waste time on anything else. Avoid unnecessary meetings or calls and look for your customers.
Julian Shapiro wrote an amazing handbook related to this topic if you need some information.

If you follow those general rules, and assuming your product have a real need, you should be on the right track 😊

One thing that I'm trying to do is to listen as carefully as possible to BotMeNot beta users.

Most likely, you'll need to validate your SaaS first. Afterward, start building a community around it. Then, you should gather as much feedback as possible and see what's applicable/possible to implement and what isn't.