How to Become a Successful Non-tech Founder in 8 Steps

I got a lot of love for my article 9 things I learnt from the most successful non-tech founders and I realized that there aren't many resources for non-tech founders. This blog is in continuation of the same topic.

Looking at the profiles of the founders of the major players in the public markets such as Microsoft, IBM, Google, Apple and Amazon can discourage any non-technical founder.

Did you know Jeff Bezos had two Bachelor of Science degrees in electrical engineering and computer science? Or that Bill Gates had written his first computer program by the age of 13? Or that Google founders had acquired their P.Hd from Stanford University? The list goes on…

They were technical and built first versions of the product themselves.

However, despite their technical prowess, the most important thing was  that all of them believed in what they were doing. They were obsessed with the problem and wanted to solve it from their heart.

And that’s the entire point!

If you believe the problem has to be solved, then there’s no force in the world that can stop you from doing it.

But, you have one simple problem: You're non-technical. Ouch!

You’re a chef, firefighter, student, designer, teacher, or professor of economics? Doesn’t matter. You don’t understand tech at all? Doesn’t matter. You can still lead that technology change.


One line answer — By proving your obsession by building a product.

I can give you examples — Sean Rad (Founder of Tinder, now top grossing app on iOS store), Brian Chesky (Founder of AirBnB), Michael Dell (Founder of Dell) built some of the highest-valued tech companies even with non-tech backgrounds.

Their stories along with multiple others establish that non-tech founders can succeed.

Photo Credits: iPrice

First, let me tell you a truth no one's told you before

At Indiez, we have spoken to over 600+ non-tech founders who shared their product ideas and apprehensions with us. We realized there was a pattern.

There are two kinds of startups — ‘tech’ startups and ‘web-based’ startups. Startups like Google and Facebook that have complicated algorithms at their core are ‘tech’ startups, while a lot of other startups like Alibaba are simply ‘web-based’. They recognized that the web could bring together and match buyers and sellers on an entirely new scale, and at a very low cost.

And they built it!

Conclusion — You may have tech oriented solution to every problem but it’s not only technology that solves the problem.

That’s how Jay-Z built Tidal. He had a problem to solve and a network he could leverage. He used technology to solve that problem and built an app.

So if he can do it, so can YOU!

Now that we have this bit sorted, let’s move on.

Here is a step-to-step guide to help you with your first product.

1. Find a problem worth solving

The trickiest part is to find a problem worth solving and then coming up with the right way to do it.

“The very best startup ideas tend to have three things in common: they’re something the founders themselves wantthat they can build and that few others realize are worth doing.” — Paul graham

Find something that’s missing in your own life, and supply that need — no matter how specific to you it seems. Steve Wozniak built himself a computer; who knew so many other people would want one?

Quick tip — Don’t think of a billion dollar idea right now!

Read this awesome 7 min read to to save $100,000 on your app idea by testing it well first.

2. Double down on your skills

As a non-technical founder, your greatest trait is your ability to generate creative ideas. Having a contagious passionability to hustle, and dedication to the vision come way before any hard skill.

Brian Chesky, founder of AirBnB, said, “As CEO I’m the captain of the ship, I have two jobs: The first job is, I have to worry about anything that can sink the ship. Beyond that, I have to focus on two to three areas that I’m deeply passionate about.”

The three areas he picked were product, brand, and culture.

You need to believe that you can keep your ship sailing with the skills you have and those you can acquire. That belief will determine everything.

There are a lot of skills that are crucial for a founder, other than tech.

Pick your strengths and play with them while you learn other things by reading actively and networking with smart people.

Read this guide to develop the right mindset as a non-tech founder.

3. Start sketching your idea

You need an excellent way to communicate your idea to potential users, co-founders, developers and even investors. The best way is to start sketching, even if it’s on paper!

The following tools will be handy —

Get inspired — Use SketchAppResourcesUI Patterns, or ProductHunt to look for inspiration of great products, or even use some open-source freebies of app interfaces (Freebiesbug) and tweak them a bit.

Design — Use SketchBalsamiq, and AdobeXD to design an interface of your app.

Website — Use Unbounce or Instapage (my favorite).

Simple form building — WufooTypeform

Zapier will help you to connect all your tools to put your MVP together.

If a prototype looks good from the front end, you’ll have an easier time persuading talent to help you work on the back end.

Ryan Hoover built an MVP of Product Hunt in 20 minutes sitting at Philz Coffee in San Francisco using Linky dink, a simple link-sharing tool where group contributors receive daily updates with links submitted by other group members.

It’s really that simple!

Read this for more tools to help non-technical founders prototype.

4. Startup=Business

Find influencers in your industry whose experience and insights you can learn from. Cold email them and follow up till they agree to give you feedback.

Share your idea in the form of an MVP with them and ask for their input — How you can make money? How will you get users?

Ask them to point out product pitfalls that they notice.

Quick Tip — Spending time with experienced people can help you save thousands of dollars by avoiding obvious mistakes.

For example, we at Indiez were approached by someone who wanted to build an app that would have easily costed him $100,000. But after understanding his requirements, we suggested him a simple solution — build a chat bot instead.

He went on to acquire his first 1000 paid users without spending anything on expensive ads. From negotiating with a top rated agency at $100,000 to shipping the right product in $10,000, the learnings were life changing for him!

Flutebot built by Indiez

6. Define what you want to build

Understanding and documenting project requirements is a time-consuming process. A PRD is a document to define the purpose, describe features, set completion criterion and sketch deadline.

My personal favorite is PRD of Product Hunt. It’s extremely well documented and you can use the template to write yours.

Quick Tip — Skip the technical details. They can be figured out later.

5. You know what to build. Now let’s build

You could find a tech co-founderhire a freelance developer or use a development shop, or work with new-age models (like Indiez) that provide consulting along with product development.

You should use the PRD you created above to get a quote.

Quick tip 1 — Stay wary of anyone to eager to work with you, without even hearing the requirements in detail. If someone can give you an exact price tag or timeline after a five-minute phone call or a single email, they’re setting you up to fail.

Quick tip 2–75% projects fail due to project fatigue. Ensure that the project is divided into small timely deliverables.

6. Be on top of things

Do not sit back and wait for the development process to finish.

Ask your development partner to show you functional software. Download and demo your product every two weeks — minimum — and ideally, every week.

There are technologies that enable you to see the changes being made by the developer remotely in real-time. Get a version of it on your phone and play with the features as the app is being built. Don’t wait until the beta release is ready.

If the firm doesn’t allow you to do that, it’s not the best idea to work with them.

Correct if a feature has been implemented incorrectly and continue to take feedback from users and suggest any modifications if needed.

Quick Tip — Catching an error just one week, versus 3–4 weeks into the build, will save money, time and a lot of re-work. Take charge and always be one step ahead!

7. Start getting users

Start building an audience for your product by writing actively about it on Medium and other social media channels. Talk about your vision, share your learnings, and build some excitement around the product.

Engage with people who might be interested in testing the product for you and giving genuine feedback.

A simple way to do it is to set up a landing page (use tools like Instapage) with a simple deliverable (like an ebook or an exclusive pass) when they sign up for beta-testing.

Run a Facebook ad to a relevant audience to start generating a small list of beta users. Consider signing up for beta-list, Ship by Product Hunt and other pre-launch websites.

You can also read this awesome article on howto save $100,000 on your app idea through marketing hacks.

8. Time to ship

Now your product is ready and it’s time to test it vigorously. Hire freelance testers from Fiverr if you want to involve more people in the testing process.

After basic testing, do the beta launch. Actively engage with users to take feedback on the product. Understand what is working and what isn’t.

Use the build-measure-learn loop to reach the product-market fit. Once you establish that, double down and start pitching to potential team members as well as investors.

Now go out there. Take that plunge, take that leap of faith.

If you want a problem to be solved, there’s no reason you won't find a solution.

Your passion and belief to build your idea are central to everything that you are doing. Learn from the data and move on.

Let’s build awesome. 🙌

Let's talk about how Indiez can help you take control of your tech!
Contact Us