Loading...
Answers
MenuCan you be the founder of a saas startup if you're not a tech person?
Since 100% of the business relies on having the product and I don't have the skills to create the product, should I drop the idea or find a tech cofounder?
Because then I'm 100% reliant on the tech cofounder to build it and how do I know the person doesn't just build it and market it themselves?
Answers
Great question.
You should definitely not drop the idea if you think that it is worth pursuing. Just like you need the tech-founder, he needs a business founder with a dream, and the passion to make it succeed.
I suggest that following:
1. Do market validation/ POC to see if the idea has potential (get a general idea of how here: https://clarity.fm/questions/6423/how-do-you-do-market-research).
2. If it shoes potential, start looking for a tech-co-founder. There are numerous ways (try these):
www.meetup.com
www.founderdating.com
www.cofounderslab.com
http://www.founders-nation.com
www.founder2be.com
Linkedin...
3. Do a trial period + sign a founder's agreement.
Happy to help you with any of the above once/if you need.
Good luck!
I've successfully helped over 350 entrepreneurs, startups and businesses, and I would be happy to help you. After scheduling a call, please send me some background information so that I can prepare in advance - thus giving you maximum value for your money. Take a look at the great reviews I’ve received: https://clarity.fm/assafben-david
You ca do this for certain and agree with the other answer that you do not have to have the skills to create the product. If you are going to bring on a co-founder for the tech side, legal agreements can be to ensure both of you are protected.
You can also think about outsourcing the technical work to one of many companies who can architect and build out your product, meaning that you maintain ownership.
There is surely more than one way to approach, but do not give up on your concept due to a lack of technical skills.
Happy to discuss more if I can be of help to you.
Carlos
I can say as an experienced angel investor, the proven magical founder formula for a tech startup always consists of at least two people like Steve Jobs & Steve Wozniak and Bill Gates & Paul Allen. One of them is a business strategist with a massive transformative purpose to change the world. On the other side; the other one is a tech guru, who can convert the idea to a tangible solution.
This thing is also one of the key points all of the investors would like to see in a tech startup with the potential to grow exponentially.
And, you will need some other skills soon to grow your business exponentially.
I heard many variations of this question during the initial phases of building startups from new entrepreneurs.
Think of it this way. If you want to be a racecar driver, do you really need to be a mechanic? It helps if you know how to maintain the car and tune it. Most of the great racecar drivers are not known for their auto mechanic skills. However, the racecar driver cannot be successful without his car being in the top-notch condition. In most cases, they find somebody else who can maintain the car for them.
In my experience, the best founders are the ones close to the customer. If you are in sales or customer management, it would be very useful. You can always find people to help you build the tech platform if you know what the customer wants and how to get it to them. A technical co-founder or an agency can build the platform for you.
I'm a former early-stage SaaS co-founder and growth-stage SaaS CTO.
Many tech startups - including the ones I've been personally involved in - are co-founded by one person who focuses on business and operations and another who focuses on tech.
You should definitely focus first on gaining validation. Early validation doesn't usually require technology. For example, it is easy to conduct surveys and interviews, it is easy to deploy ads and landing pages, etc. Once you have some meaningful validation, you should ask *yourself* some key questions:
- Why are you and your team uniquely suited to grow this business?
- Why now?
- Why isn’t anyone else already doing it or why do you have the upper hand on them?
If you can answer those questions - fairly and confidently - then you have every right to consider yourself an important half of a co-founding equation. You will - of course - at this point need to bring in someone more technical. You will be reliant on them for the tech, but they will be reliant on you for everything else - business acumen, inside knowledge, connections, the things only you can bring to the table. A good technical co-founder will understand that an idea is just a seed, but it takes the right business partner to make it come to life.
Check out this recent blog post I wrote on the role of an early-stage CTO, how to find one and compensate one, etc:
https://www.linkedin.com/pulse/startups-burning-questions-ctos-answered-anthony-putignano/
If you have any further questions, let me know!
This is a complex question.
Likely best to talk with several smart people about whether or not your idea lends itself to your situation.
With the limited context you provided + no guess about your personality style, no way to guess.
Yes, yes, yes -- a million times yes!
Throw the idea that you "don't have the skills to create the product" out of the window. These days, you don't have to know how to code to build software.
There are a whole slew of "No-Code" and "Low-Code" tools available to help you build your tech startup -- and a whole community of solo founders to ask questions of. Check out these two resources:
I'm a software engineer and have been building startups for 15+ years. I'm making the transition into No Code for two reasons: first, to build faster and launch my own products with less work; and second, so that I do a better job helping non-technical founders launch their startups on thier own.
The ecosystem isn't 100% there yet, but it will be in the next few years. Depending on which tool you use, you may run into feature limitations and/or find vendor lock-in when you reach a certain scale.
But that still meshes with the ethos of a Lean Startup MVP: you're eventually going to throw it all away anyway and start over from scratch. And when you do, you'll have customers, you'll have money, and you'll be in a better place to hire developers without worrying about them stealing your idea.
Let me know if I can do anything to help. You got this!
I have helped many non-technical founders getting their ideas started and running successfully. it is the most important question when they start. I usually recommend two choices in this case.
1. Find a Co-founder
2. Recruit somebody who can do it
Following are the Pros and Cons:
SaaS is an extremely slow burn but can also have amazing growth potential depending on the space. You need to find technical talent that doesn't mind grinding for 6-24 months without turning much of a profit.
Even if you are well funded, unless you have prior success in SaaS, you will most likely burn up your runway finding product-market fit. This why I personally suggest against hiring technical talent until the business has achieved certain milestones.
You really need a technical cofounder that share the vision for the service, that understand the insane amount of work involved, and can build your MVP.
My last startup failed because of this very thing. Except that I was the tech person and he was the salesperson. He just did not understand the tech so he could sell it well. He was a highly successful salesperson but he just did not get the tech--so the company failed. I know many here are super positive about these issues and indeed a properly setup instrument can protect you from a usurping co-founder but if you do not understand the tech well things can go wrong. I suggest you get a tech adviser like myself to check what the person is doing (of course also get a co-founder agreement) and if all is going well. Set benchmarks that the tech person must meet in an agreement to keep him or her on their toes, Keep control but you can only keep control if you understand what the tech does and how it will help the world.
Related Questions
-
What is the average pre-money valuation of a enterprise/SaaS stat-up that is pre-revenue?
There is no valuation until you sell something. An idea or a company is only worth what its sales are. Once you have your initials sales, sales strategy and forecasting length (ie 9 months from first customer lead to close) then you have a formula for valuation. Valuation for start-ups is generally 3.5 x last years sales model should be the growth factor. When you are looking for investors, you will want to have atleast 9-18 months of SALES, not just pipeline and they will be looking at 5x revenue for a 3-5 year payback.TP
-
Freemium v.s. free trial for a marketplace?
It depends on a number of factors but I'd boil it down to two key things to start: 1) What is your real cost to provide a free plan or trial? 2) Who exactly is your customer and what are they used to paying and who and how do they pay today? When you say "online workforce marketplace" it sounds as though you're placing virtual workers. If that's the case, or if you're paying for the supply side of the marketplace, the question is how much can you subsidize demand? Depending on where you're at in the process, I'd also question how much you can learn about the viability of your marketplace by offering a free version, assuming again, that free is actually a real cost to you. I was part of a SaaS project that started charging people for early access based mostly on just a good landing page (we clearly stated they were pre-paying) and were amazed at the response. I've also run a SaaS product that offered free trials and realized that the support costs and hand-holding and selling required to convert from free trial to paid wasn't worth it, this despite the product's significant average ARR. You might be better off providing a "more information" sign-up form (to capture more leads) and let them ask for a free trial while only showing your paid options. I've been amazed at the lead capture potential from a simple "have questions? Click here and we'll contact you" This is all the generalized advice I can offer based on the limited information I have, but happy to dive-in further if you'd like on a call.TW
-
How should we plan a well-executed SaaS product launch to an existing customer base?
I'm a product developer, startup veteran, and advisor to SaaS companies. Hopefully you've been already developing this new product with input from your existing customers, letting them beta test it and give feedback. (If not, my advice is to STOP immediately and get enough pilot customers involved to be sure that you're delivering something really valuable to them, that works the way they expect it to work, is easy to understand and get started with, etc.. The last thing you want is to do a big splashy launch of a product that is D.O.A. because you built what you assumed the customers wanted instead of they actually demonstrated that they wanted.) OK, so let's assume that you've got customers in the loop. Interview the heck out of them. Really understand how they use the product, why they use the product, what makes it valuable to them, what they can do with it that they couldn't do before, etc. If the product's not done enough for them to be best testing it yet and getting results, at least get some insights into how they see themselves getting results from it. How does it/will it change their lives? As you do this, be on the lookout for things that really resonate. Emotional language, for example. "It's such a relief that I don't have to worry about sending invoices manually anymore." (or whatever pain it is that your software solves) Also look for (and try to elicit) specific result statements: "This new software saves me [or is going to save me] 15 hours a week. Now I can spend that time where I really want to, with my kids ( ... my cat ... my golf buddies ... )" You're doing this for three reasons: 1) This stuff makes for phenomenal testimonials; 2) it helps you come up with great ideas for pre-launch content; and 3) it generates *PURE SOLD GOLD* you'll use in writing the copy for your launch offer. OK, launch mechanics. There are people who teach huge long expensive courses on this stuff. I'll give you the Cliff's notes. While I haven't personally run a major product launch, I have been trained in the strategy and am very familiar with it. - Plan your launch period in advance. You might want to do a pre-launch sequence that lasts 1, 2, even 3 months depending on the magnitude of your product and how much effort you're willing to put into creating content for the launch. - Create some teaser content of interest to your customers who might want to buy this product. Offer to teach them something, or offer to give them a sneak-peak behind-the-scenes of your new product. - Send an enticing offer for this content out to your list. Get people who are interested in this content to sign up for it. This creates your launch email list. - Send your launch list weekly updates: development milestones, sneak-peak screenshots, videos, educational material, interviews with/testimonials from beta users, and so on. - You're not trying to sell here yet (not hard sell at least). Drop some hints that there is going to be a special offer when the product launches, just for special loyal customers like them. - Create at least three videos on topics that are really, really interesting to your prospective customers... not necessarily about your new product itself, but teach them about what they can achieve with it, or what others have achieved with it already. As you publish these videos, send the link out to your launch list. - Also send out an offer to see these videos to your main list, to entice more people to sign up for your launch list. - As you get closer to launch time, keep sending frequent updates to the pre-launch list, and send another email out to your main list to let them know that the product is launching soon, and that if they're interested in the special one-time-only launch pricing, they need to sign up for the "early bird list" (your launch list). - Send out a 24-hour notice that the launch is going to happen soon, and the launch pricing will only be available for a limited time (potentially, to a limited number of customers ... to increase scarcity and urgency). - I recommend that even if you plan to open the product up to all your customers that at launch time you limit it to a smaller number. This makes the inevitable post-launch gremlins less painful to deal with because you have fewer customers, and it motivates people to buy because they fear that they'll lose the opportunity to do so. You can open the product up to more people later... the delay will result in pent-up demand and easier sales. - Start the launch. Tell your early-bird launch list a few hours early, then tell your main list. Direct them to a web page with a video and long-form sales copy of your launch offer. - Send out 2-day, 1-day, 12-hour, etc. notices that the launch is ending soon and reminding people what they're missing out on if they don't act now. If you're offering a limited number of spots, tell people what percentage has already sold out. Remind people that if they're "on the fence" about this, that this is the time to make a decision. - Send out an email letting people know that the launch is over and thanking them for their support and their vote of confidence. Tell the people who didn't buy (or didn't get in) that you'll let them know that the product will be opening up for new registrations some time in the future. (You may get people sending you emails begging to be let in at this point, if your product is desirable and your marketing was executed well.) And, of course, you don't just have to promote your launch content to your existing customer list ... you can post it to social media (and encourage your customers to do so) to attract brand new customers into your world. If you'd like to go into more detail about launch planning for your specific product and market, I'd be happy to jump on a call and talk about ways to make this work for you.BB
-
How can I manage my developers' performance if I don't understand IT?
Whenever you assign them a task, break down the task into small chunks. Make the chunks as small as you can (within reason, and to the extent that your knowledge allows), and tell your devs that if any chunks seem large, that they should further break those chunks down into bite size pieces. For instance, for the overall task of making a new webpage, _you_ might break it down as follows: 1) Set up a database 2) Make a form that takes user email, name, and phone number and adds them to database 3) Have our site send an email to everyone above the age of 50 each week When your devs take a look at it, _they_ might further break down the third step into: A) Set up an email service B) Connect it to the client database C) Figure out how to query the database for certain users D) Have it send emails to users over 50 You can keep using Asana, or you could use something like Trello which might make more sense for a small company, and might be easier to understand and track by yourself. In Trello you'd set up 4 columns titled, "To Do", "Doing", "Ready for Review", "Approved" (or combine the last two into "Done") You might want to tell them to only have tasks in the "Doing" column if they/re actually sitting at their desk working on it. For instance: not to leave a task in "Doing" overnight after work. That way you can actually see what they're working on and how long it takes, but that might be overly micro-manager-y At the end of each day / week when you review the tasks completed, look for ones that took a longer time than average (since, on average, all the tasks should be broken down into sub-tasks of approximately the same difficulty). Ask them about those tasks and why they took longer to do. It may be because they neglected to further break it down into chunks as you had asked (in which case you ask them to do that next time), or it may be that some unexpected snag came up, or it may be a hard task that can't be further broken down. In any case, listen to their explanation and you should be able to tell if it sounds reasonable, and if it sounds fishy, google the problem they say they encountered. You'll be able to get a better feel of their work ethic and honesty by how they answer the question, without worrying as much about what their actual words are. Make sure that when you ask for more details about why a task took longer, you don't do it in a probing way. Make sure they understand that you're doing it for your own learning and to help predict and properly plan future timelines.LV
-
Does anyone know of a good SaaS financial projection template for excel/apple numbers?
Here is a link to a basic model - http://monetizepros.com/tools/template-library/subscription-revenue-model-spreadsheet/ Depending on the purpose of the model you could get much much more elaborate or simpler. This base model will help you to understand size of the prize. But if you want to develop an end to end profitability model (Revenue, Gross Margin, Selling & General Administrative Costs, Taxes) I would suggest working with financial analyst. You biggest drivers (inputs) on a SaaS model will be CAC (Customer Acquisition Cost, Average Selling Price / Monthly Plan Cost, Customer Churn(How many people cancel their plans month to month), & Cost to serve If you can nail down them with solid backup data on your assumption that will make thing a lot simpler. Let me know if you need any help. I spent 7 years at a Fortune 100 company as a Sr. Financial Analyst.BD
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.