Loading...
Answers
MenuI wrote some software. How do I valuate its worth and find a suitable company to acquire the product and continue supporting it?
- It's web-based, and architected as a SaaS solution
- There is huge market potential for the product
- I don't have the resources to sell or market it. We bootstrapped it and are short on cash atm.
- I think our business model is faulty and we need to find a suitable buyer to transform it into a profitable product/service.
Answers
If it's generating USD $10,000 or more in MRR, then you can try listing if on ExitRound but based on your description, I think a sale at this moment is unlikely. Acquisitions like the one you're dreaming are either motivated by the book of business or an engineering team. Code is thrown away and product discontinued. So the idea that a business is going to buy you to fix the problems of the product is unrealistic.
Happy to talk to you to help you determine if the business is potentially salvageable.
Have you considered seeking investment instead (or already tried)? If it isn't already a profitable business with good revenue, investment seems more likely than a reasonable acquisition. Angel investors are expecting to take risks and it sounds like your product is still in the risky stage.
The unfortunate misconception about SaaS apps is that the value is in the code. It rarely is.
With the arrival of cloud computing, and languages like Ruby on Rails (and even PHP these days) that can quickly build an app from re-usable 3rd party code, the app itself has almost no value unless you’ve found a way to achieve something technically that few others could.
A SaaS company’s value is therefore primarily in it’s
- Team – a good team of engineers can be acqui-hired while a good founding team will often be easy VC bait.
- Users – even if they’ve not yet been monetized.
- Cashflow – even if the company hasn’t yet reach profitability
The reality is, without at least one of these three things, you have nothing.
Buyers who would pay for your idea, could quite easily pay the same amount for the development of what you already have minus the flaws.
If you believe the product is solid, but you’re pre monetization with a good idea and bad business model, then my best advice would be to develop the business model first. Do a search for interviews by Jason Cohen and Eric Reis. They’re the best speaker I know on the topic of customer development and how to find what works.
Best of luck.
It may seem surprising at first that the valuation results are influenced by your need for business valuation. Business valuation is a process of measuring business worth. In addition to valuing the individual business assets and liabilities, the method can be helpful when allocating the business purchase price across the individual business assets, as part of the asset purchase agreement. Market based business valuation methods focus on estimating business value by examining the business sale transaction data available from the actual marketplace. Comparative transactions involving private companies that closely resemble the subject business. Selling price to business earnings such as net income, SDCF, EBITDA, or net cash flow. Each pricing multiple is a ratio of the likely business selling price divided by the respective economic performance value. So, for instance, the selling price to revenue multiple is calculated by dividing the business selling price by business revenue.
You can read more here: https://www.valuadder.com/valuationguide/business-valuation-five-steps.html
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
How do I value my startup for acquisition?
As you may know, we acquired Clarity recently and have done numerous acquisitions at Startups.co so we spend a lot of time thinking about this. I've also personally been acquired a few times so I've been on both sides. With that said I think the earlier comment about how much value you can bring to the acquirer is always a great place to start. For example, if your company had $100k in sales per year, no reasonable multiple of that is going to get you into a meaningful acquisition price. So scratch that. Instead - try to determine what kind of revenue the acquirer might generate in the first and second year post acquisition. That at least gives you a starting point. What you can't do is start thinking about what Instagram sold for. None of that type of silly math matters. Those are one of conditions where a company is in such hot demand is so singular in it's value (no one else was that big at that time in that particular segment) that they play by entirely different rules. What's nice about the 'what value can we bring' discussion is that it shows that you are thinking about what's in it for them, not just what's in it for you.WS
-
Which is the best hosted free bug tracking tool for a team size of up to 10 members?
Being a freelance developer for the last 10 years or so, I have seen and used almost every project management software you can think of, open-source and closed, and I have found that the "best bug tracking tool" completely depends on your process. I employ and direct teams in an Agile process that involves loose story-based requirements with point-based estimates, two-week cycles of iterative development, planning and retrospective sessions, and look-ahead and show-and-tell meetings with the stakeholders. It's important to me, then, that my tools have a method of capturing all those pieces with as much detail as I need but no more. On projects, I've successfully used Pivotal Tracker, Unfuddle, Redmine, Codebase HQ, Basecamp, Trello, and many others. I usually recommend people to Trello for light, agile management; it's essentially a digitized version of sticky notes and swim lanes. If your team actually needs a full-featured ticketing system, see Redmine (Rails), Trac (Python), or Mantis (PHP), depending on your language preference. Hosting a version of these yourself is fairly trivial, and numerous options exist for cheap or free hosted versions. For something in the middle, Github Issues is a good fit and the open-source clone GitLab.org replicates most of those features nicely. However, if you're looking for a hosted version, you're probably looking to offload that tricky "backup" thingy, and in that case, how important is your data? How proprietary? What's your business model? If you're working on an open-source project, Github will give your team a free account with private repos, issues, wikis, and the like. If you're okay with your project being "readable by all", public projects on Pivotal are still free. I'm mostly a consultant these days, leading small groups of junior or intermediate developers into a more productive, more mature, fully operational teams of senior software developers. One of the first things I teach folks is how to use a project management system... and why! It'll save your bacon if it's simple, effective, and reliable. With a few minutes of discussion about your project, I can probably help you select the right tool and service for your team. Let me know if I can help with that. Best of luck!DR
-
I have a great app idea, and I need help bringing it to life.
I'm not sure if this is how you imagine this world to work, but at least according to the order you wrote it "raising funds" was first. In reality it should actually be one of your final steps of the stage you are at right now. It may even come after a year or two! So you have this great app idea, and you're looking for a place to start... Don't! Don't start yet before you decide whether you have what it takes to get into a roller coaster that can ruin your life and make you miserable! Not trying to scare you but I think most people only hear about these great success stories. They have this dream of maybe, possibly, becoming the next big thing... Because they have the best idea for an app... You don't hear about the failures so often. And even if you do, you don't hear about what the founders of these failing startups had to go through. Truth is you are most likely gonna fail. And I'm saying that without even knowing what your idea is. There are so many barriers on your way that even a great product with a great team is likely to fail. Some people would say "I'm not afraid of failing", "It's good to fail cause you learn", "Failing will make me stronger for the next startup". That's somewhat true but it doesn't mean that failing is easy. As oppose to what people sometimes say - you do not want to fail! It's very painful!!! You have to understand what failing in a startup means. You can work your a$s for 2-3 years, have little to no salary, waste other people's money (most likely your friends and family first), lose friends, fight with your partners, your family, your spouse, devote 20 hours a day for your startup all this time, forget about the little and big things you used to enjoy in life, and only then, after debating 100 times whether you should quit or not, you finally decide that it's not gonna work and you've failed. Disappointing your family, your investors, yourself. Trust me it is painful. Are you sure you wanna do this to yourself? If yes, give me a call. I have the experience you need! From idea stage, to proof of concept, to running beta tests, getting millions of millions of users in ways you can't even imagine, creating features and experience that will make these millions of users completely addicted and viral, raise money in a smart way, hire the right people, find a great co-founder, succeed, fail, be persistent, and enjoy the ride! Good luck, RoyRM
-
How can I take an idea for a new app and turn it into a real product?
Here are some options: ___Free Options___ 1) Make apps without needing to spend a lot of time learning to code. Look into "MIT App Inventor" (http://appinventor.mit.edu/explore/). It's a very _easy_ way to make pretty complex apps using drag and drop coding. You can find youtube tutorials that will show you how to make your first app within 5 minutes. I've used MIT App Inventor to make prototype apps for many of my ideas, saving me tens of thousands of dollars if I paid a dev to do it instead. Learn to do "real" coding yourself. The main investment will be your time. There are plenty of free resources for learning coding on the web. I'd suggest learning "React Native", it's a relatively new way to code apps, which allows you to make one app that will run on both Android and iOS. 2) Find a software engineer cofounder. Go to Meetups, conferences, local hackerspaces / makerspaces. Hang out on relevant online forums (e.g. https://www.reddit.com/r/startups/ make sure to read their rules for posting before posting though). It won't be easy to find a tech cofounder, your idea will need to be amazing, and you yourself will need to be very passionate and capable in order to convince someone to partner up with you for sweat equity. ___Paid options___ 1) Use developers with less established reputations / portfolios (lower cost, higher risk) Be very wary of freelancers on sites like Upwork, Fiverr, etc. Here are some basic hiring rules: In your hiring script, make sure to ask for all applicants to give their account name for github/bitbucket and Trello. Don't hire agencies, only hire individuals. To get hired, ask them to do a simple task via Trello and submit the code via github/bitbucket. This task should only take them maybe 1 hour. Check the quality of what the applicants and if they deliver it in a timely manner. Keep the 1 or 2 people that do a good job. If you don't do this vetting these "low cost" developers may end up costing a lot in the longer run. 2) Use developers with more established reputations / portfolios (higher cost, lower risk) With this option your app will probably cost > $20k to develop, but it can be worth it if you have a single idea that you know you want to move forward with. I can introduce you to a very high quality developer in NY if you're at this stage. Let me know if you'd like any additional help more tailored to your specific app ideas, best, LeeLV
-
How do I run a successful closed beta for my web application that is almost done with development?
Create an ideal customer profile. Create some questions that will allow to you survey a potential tester to determine if they fit your profile. Design simple landing page with very clear value proposition that speaks to your ideal customer. Ask for a minimum of information up-front (email), but ask for more info after they commit by submitting the first piece of info. (KISSmetrics does a good job of this on their current website trial signup). Use the their answers to these profiling questions to put the applicants into buckets. Let in the most ideal bucket first, or split them into groups if they're big enough. Try and measure engagement the best you can. Measure qualitative and quantitative data. Schedule calls with your beta testers to find out more, especially with the ones who's user behavior seemed to indicate that they didn't get value from your product. Find out why. Make sure they are indeed your ideal customer. Pick up the phone and get to know your customers inside and out. Meet them in person if possible. Incorporate their feedback quickly and get more feedback. Rinse repeat.DH
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.