Do you have an amazing idea for a SaaS application? An idea that solves a real problem for your customers. An idea that has been validated properly and is ready to be carved into a kickass application. The next step is to build it.
Build it and they will come.
In the US, 23% of SaaS businesses are founded by non-technical executives and 20% of angel investors invest in non-technical entrepreneurs. (Source: TechCrunch)
Non-technical founders are in no way excluded from being able to create a SaaS product. There is no need for technical skills in order to launch an application and non-tech founders have the advantages of understanding their target audience, knowing what problem they want to solve, and how people actually use their products.
This article is for non-technical founders who want to build a SaaS product and are looking into the basics of what is needed. We will cover basic terminology, how to hire freelancers or work with agencies, and what to keep in mind when building a product.
This guide assumes that you already have an idea that you've validated with your target audience.
Before we get into the technical specifics, non-technical founders need to know what a SaaS product is and how it differs from other types of products.
Software as a service (or SaaS) is a way of delivering applications over the Internet—as a service. Instead of installing and maintaining software, users simply access it via the Internet. It is a software application that resides in the cloud.
There are different types of applications, but when founders like us think about building an app they're probably thinking about web apps. Web applications make up approximately 93% of all SaaS businesses (source: TechCrunch 2017).
Being a non-technical founder you will still need to know some basic terminology of web applications.
Branding - This is the brand identity of your app. This includes logo, color scheme, fonts, and so on.
UI/UX - User interface (or UI) refers to how a user interacts with an application. User experience (or UX) also relates to this as it encompasses everything from performance to design for non-technical founders.
Programming language - A programming language is a set of instructions for computers to follow. You can't do anything in the digital world without it! There are many different kinds, but HTML and JavaScript (jQuery) are two languages that non-technical founders will need to use when building web applications.
Server - A server is the computer system where your application will reside (e.g., web servers). Servers store data and provide it to users when they need it.
Database - A database is a place where all your data can be stored. Think of this as an excel sheet with a predefined structure.
Front-end - The visible part of a website that users interact with, like pages and buttons. The front end is what's seen by visitors to your site. Web developers create them using HTML, CSS, or JavaScript (more on this below).
Back-end - The non-visible part of a website that handles the business logic, databases, and storage. The back end is where developers create all the code to make your app work properly (e.g., writing purchases into a database or checking if an email address already exists in order to prevent duplicates).
Cloud - A synonym for the Internet. This refers to the storage, servers, and other services that allow us to create an application without having their own server or expensive data center.
Every web application works something like this,
The browser (front-end) sends a request to the server.
The Server (back-end) runs an application that provides the requested service like data storage, manipulation, etc.
After processing, the Server returns some kind of response back to the Browser. It may be an updated copy of the same page, an error page, a response page, or just another blank data-entry form.
There is so much more to know, but this should be enough to get started.
You need to create an MVP (Minimum Viable Product) before you can start marketing it because this is the only way that a founder will know if their idea has potential or not. Think of the MVP as the first version of your product stripped down to its core functionality.
A SaaS application just like most web applications needs a front-end, back-end, and database. If non-technical founders want to launch a web application, they're going to need some external help for everything from design and development to marketing and customer success.
You need a designer to make the front-end look good and consistent with your branding.
A front-end developer to create the web pages and make the front-end interactive and work with your business logic.
A back-end developer to write the back end of the application (which includes database, storage, server).
A project manager to manage the project timeline and close-out work.
(Optional) A founder will also need a copywriter for SEO content, customer success managers to answer questions from customers after you launch your product into beta or live.
You need to convert your idea into a set of features. Then convert these features into actionable steps, with whom, what, when, and how.
To build a product you will need to find the right people for each job, and then manage them. Freelancers can be a great way for non-technical founders to build their products. You need to know what skills you want your freelancer or agency to have, and then find out if they're available at the right price and location.
Another way to go about it is partnering up with an agency like us. An agency offers a better return on investment than hiring freelancers one by one. You have more time on your hand to manage core operations and generate traction while your agency builds the product for you.
At this point, you should have an idea of how you want to invest the capital and budget accordingly. Do you want to spend it all on a huge marketing campaign? Spend nothing on marketing and launch the product quietly with just your close friends as customers? Spend more money to get your product in front of a large audience of potential customers?
You can find freelancers on freelancing platforms like Upwork, Guru, and Freelancer. Use keywords to filter down the results so you can find someone with the skills that match your needs.
You want to find freelancers with the right skills for your project. To make sure you're hiring someone who can deliver, ask these questions:
What do they charge? Hourly or fixed price?
Which type of projects have they done in the past and what were their results?
What tools are required to complete this project?
What are their qualifications such as education, certifications, or experience in this field of work?
We strongly recommend fixed pricing over hourly. Hourly pricing can be confusing for founders, as it is difficult to estimate how long a project will take. Fixed pricing is clear for both parties upfront and there are no surprises at the end of the project.
Set up milestones in your contract with the freelancer and make sure they get paid upon hitting the milestones.
You may include a non-compete clause in the contract. For example, this might state that for six months after completion of work on your project, the freelancer cannot do any development projects for other people or start their own company and compete with yours.
Hiring freelancers is a great tool to have in your arsenal. But it may not be the best choice for every founder. Managing freelancers is at least a part-time job in and of itself, it can be even more difficult to manage freelancers that don't have the same cultural, geographical, or timezone as you do.
The following list includes specific examples of founders who should not hire freelancers.
Founders with a very limited amount of time.
Founders who don't want to be responsible for project management.
Founders that are aiming for a target market like healthcare or finance and need specialists in those fields.
Founders that have a strict deadline and can't afford to have delays.
Founders that don't have an idea of what kind of talent they need.
If you fall into any of these categories, you may want to look into hiring an agency to build your product instead of freelancers.
With agencies, you are hiring a team of professionals with expertise in the field you need. This will significantly decrease your chance for failure and increase the chances that the agency can deliver on time. And you have complete control over how much you want to be involved in the process.
Going with an agency to build your product can be a great way to get your product up and running quickly.
The first step is finding agencies that specialize in SaaS products. You will want to find someone who has experience working with MVPs. After finding the right agencies, you will need to do some research and find out how long it takes them on average to build an MVP or web application. This is important as this information helps with planning your budget for hiring help from an agency versus freelancers.
There are a few other things to keep in mind:
You need an agency that is experienced enough in designing SaaS products with non technical founders. You need to find the agency with the right size and resources for your project. A small to medium agency should be favored for developing an MVP. Do your own research: find out what agencies have the right experience for your product. Agencies charge different fees for different services - you need to find out what their fees are. Fixed pricing should be favored.
When you work with an agency, it's important to remember that they are there to serve as more than just a resource for building out your product; they should also provide support services like creating customer acquisition strategies and targeting specific verticals or audiences.
We build MVPs for clients all over the world. We love to work with first-time founders and with at least 3 years of experience in their industry. Reach out by booking a discovery call and let us help you launch an amazing product.
Once, you've found the freelancer or agency you want to hire. You need to communicate with your tech partners for next steps. You will need to work with them to create a project plan.
Keep the following things in mind:
Create a project brief - this should include the scope of work, timeline for completion and your budget expectations.
Remember to set clear goals - this will help avoid any misunderstandings down the road about what is expected of them in terms of time and deliverables.
It's important to have an open dialogue throughout the project. This should include regular check-ins to make sure that your goals are being met.
It is also a good idea to set up milestones or checkpoints in the development process - this will help avoid any surprises as it'll give you more insight into what stage they're at and what it looks like.
The agency or freelancer will need to be completely transparent in the process, which means he has to share all of their work with you and show how they're progressing on your project.
You should also do your best to be an excellent client and help your technical partners do their best work.
Communication - this is key. You need to be open and honest about your expectations, needs, goals and challenges.
Participation - be sure to participate in the process. This includes testing out your product before you launch it, and being active in conversations about what changes need to be made throughout the development cycle.
Humility - do not be afraid to ask for help. If you don't know how something works, it's okay to say so and reach out for advice.
Patience - remember that this process takes time.
Commitment - show up and work with your technical partner on a regular basis, even if it's just for an hour at a time.
Kindness - remember that the freelancer or agency you're working with are human beings, and treat them as such.
I hope this guide helps you launch an amazing product. You can always reach out to us by booking a discovery call to discuss your idea.
Here are a few more articles you might like.