Loading...
Answers
MenuShould we use another small startups API for a core piece of functionality or build a 'lite' version of our own?
About to start building a product and another small but successful startup offers an API that would give us a core piece of functionality we are looking for. They aren't really a direct competitor so partnering with them could lead to building some great relationships in our space. On the other hand it leaves us kind of vulnerable, knowing how fast a company like this can pivot and leave us on the dust. Any insight would be helpful!
Answers
So the question is what are your "Plan B" options. Let's assume for a sake of argument you've weighed the options (build your own, buy from an established competitor, partner with this startup) and you've decided that partnering is the best option. One way you could protect yourself in the event this company either shuts down or pivots and no longer supports what you need, you could negotiate to have the code put in an escrow account that has triggers to release the code to you. You of course will be restricted to the usage (e.g. you couldn't take it and compete). I've used escrow agreements in past deals and can discuss the details if your interested. Caveat, I'm not an attorney so can only provide business advice. Good Luck!
As someone who has both practiced lean startup methodologies, as well as someone who values their own time.
Go with the small startup's API until you have other resources other than yourself who can develop better than you can. It's just not worth getting tied up reinventing the wheel when it si your job to defer, outsource (elance, odesk, freelancer.com, guru.com, gun.io,) or lisence their code. Your responsibility is to move the company forward in big steps toward its core mission. Not tackling something because you think you could do it.
If you would like to discuss this further, give me a call. On the house.
When you wake up in the morning, say to yourself "Get to that MVP" 3x. Saying that would make the answer to this question a no brainer!
Good luck!
You don't even necessarily need the code should they pivot and do something else. You just need contracts in place for support. You need them to support you for a certain length of time and even have a stipulation that they support you for yet another length of time after they pivot or no longer have whatever version of the API it is.
That way, you'll have time to build your own. OR at that time you can negotiate buying it from them or upgrade to the latest version of their API.
No one is going to want to just give you the code should they pivot and make a new version. As a developer, I wouldn't. That's potentially trade secrets, etc. However, I would certainly sell it to you (maybe ensuring you don't resell it) should I move on and not want to support you with servers, etc.
But really, what's it take to keep a server around, with an older API version, for one paying customer? It's not as if they are losing on the deal (hopefully).
We're in the business of software here and the good thing is that there's absolutely no reason they would ever lose some version of an API. They could always go back in their revision control systems and resurrect it. So you aren't going to lose it. Not if you have an agreement. Though that agreement doesn't need to be harsh. It should be quite easy to negotiate.
I've been involved with the creation of several apps for startups that were based on third party APIs as a central piece of the software architecture. From my experience, there have been pros & cons to this approach, but I would generally recommend using the API if you can.
Things to watch out for:
Is the API a new API? If so, proceed with caution. We've worked with several third party APIs where we were the first or among the first developers to use the API. In each of these cases, there was a significant amount of back and forth with the API development team that extended the development time required to complete our app. This was sometimes due to API features that were in the documentation but not yet implemented. Other times, it was due to features that were available in the API, but not in the documentation. And yet other times, some of the documented features were present, but not functioning properly and we had to wait for bug fixes, clarification, etc. If the API is mature and is in use by a large number of users, most of these issues will be ironed out. I don't think you want to be the ones who end up doing the ironing though.
Do you have options to create an alternative source for the data? One app we worked on had maybe ten 3rd party APIs baked in. Over time, we replaced a number of these APIs with our own home grown solutions and some of them we swapped out for other 3rd party APIs that were cheaper, better, or faster. You may not need to have all of this completely figured out, but you should have a rough idea for plans B and C that you can pull trigger on should the need arise.
You’ve raised a very valid point! Using another startup’s API can be a smart move to save development time and resources, especially if they offer a well-tested and reliable solution. However, the risk of dependency on their service is something to consider seriously, particularly for a core functionality. It might be worth analyzing the stability of their business and service terms, as well as having a contingency plan in place.
If you're working in logistics or trucking, this resource could provide additional insights: https://www.cleveroad.com/blog/trucking-api/. It discusses API integration and its potential in building robust solutions. Best of luck with your product development!
Related Questions
-
How do you get a product prototype developed in China sitting in the US?
It varies and it's very very specific to what you want to develop. The concrete design of your circuit matters. Also prototype building costs are usually a factor 10-100 higher than series. If you already have your prototype then you can shop around various manufacturing companies. To do that, you need Gerber files (your PCB design) and a bill of materials. You also need to think about casing: designing it and creating the mold is expensive. If you don't have your prototype yet, I recommend having it engineered in eastern Europe. Custom engineering is cheap there and high quality. IP protection is a problem. One thing to do is to distribute the work to different manufacturers. For the design phase you are safer if you design your prototype in Europe or the US where international patent laws apply. I could give you more specific advise in a phone call, getting to know a bit better what you are trying to build.GF
-
What percentage of VC funded startups make it to 100m+ revenues in 5 years or less?
100M+ in revenues in 5 years or less does not happen very often. As an example of one sector, here is an interesting data visualization (circa 2008) of the 100 largest publically traded software companies at that time that shows their actual revenue ramp-ups from SEC filings (only 4 out of these 100 successful companies managed this feat, which themselves are an extremely small percentage of all of the VC-funded software companies): How Long Does it Take to Build a Technology Empire? http://ipo-dashboards.com/wordpress/2009/08/how-long-does-it-take-to-build-a-technology-empire/ Key findings excerpted from the link above: "Only 28% of the nation’s most successful public software empires were rocketships. I’ve defined a rocket ship as a company that reached $50 million in annual sales in 6 years or less (this is the type of growth that typically appears in VC-funded business plans). A hot shot reaches $50m in 7 to 12 years. A slow burner takes 13 years or more. Interestingly, 50% of these companies took 9 or more years to reach $50m in revenue."MB
-
What is a normal churn rate for b2b saas company with an average monthly revenue of $850 per customer? Is 10% of the total monthly sales high or low?
10% of the total monthly sales churning on an absolute basis is near fatal. That means that within 5 months, you have 50% absolute churn per year, which reveals fundamental flaws with the service itself. Anything above small single digit churn is telling you and your team that customers are not seeing enough value in your product. I'd start by doing as many exit interviews as you can with those that have churned out, including, offers to reengage at a lower price-point while you fix the issues that matter to them. Happy to talk through this in more detail in a call.TW
-
How much equity should I ask as a CMO in a startup?
Greater risk = greater equity. How likely is this to fail or just break even? If you aren't receiving salary yet are among 4-6 non-founders with equivalent sweat investment, all of whom are lower on the totem pole than the two founders, figure out: 1) Taking into account all likely outcomes, what is the most likely outcome in terms of exit? (ex: $10MM.) Keep in mind that 90%+ of all tech startups fail (Allmand Law study), and of those that succeed 88% of M&A deals are under $100MM. Startups that exit at $1B+ are so rare they are called "unicorns"... so don't count on that, no matter how exciting it feels right now. 2) Figure out what 1% equity would give you in terms of payout for the most likely exit. For example, a $10MM exit would give you $100k for every 1% you own. 3) Decide what the chance is that the startup will fail / go bankrupt / get stuck at a $1MM business with no exit in sight. (According to Allman Law's study, 10% stay in business - and far fewer than that actually exit). 4) Multiply the % chance of success by the likely outcome if successful. Now each 1% of equity is worth $10k. You could get lucky and have it be worth millions, or it could be worth nothing. (With the hypothetical numbers I'm giving here, including the odds, you are working for $10k per 1% equity received if the most likely exit is $10MM and the % chance of failure is 90%.) 5) Come up with a vesting path. Commit to one year, get X equity at the end. If you were salaried, the path would be more like 4 years, but since it's free you deserve instant equity as long as you follow through for a reasonable period of time. 6) Assuming you get agreement in writing from the founders, what amount of $ would you take in exchange for 12 months of free work? Now multiply that by 2 to factor in the fact that the payout would be far down the road, and that there is risk. 7) What percentage share of equity would you need in order to equal that payout on exit? 8) Multiply that number by 2-3x to account for likely dilution over time. 9) If the founders aren't willing to give you that much equity in writing, then it's time to move on! If they are, then decide whether you're willing to take the risk in exchange for potentially big rewards (and of course, potentially empty pockets). It's a fascinating topic with a lot of speculation involved, so if you want to discuss in depth, set up a call with me on Clarity. Hope that helps!RD
-
For every success story in Silicon Valley, how many are there that fail?
It all depends on what one decides to be a definition of a "success story." For some entrepreneurs, it might be getting acqui-hired, for some -- a $10M exit, for some -- a $200M exit, and for others -- an IPO. Based on the numbers I have anecdotally heard in conversations over the last decade or so, VCs fund about 1 in 350 ventures they see, and of all of these funded ventures, only about 1 in 10 become really successful (i.e. have a big exit or a successful IPO.) So you are looking at a 1 in 3500 chance of eventual venture success among all of the companies that try to get VC funding. (To put this number in perspective, US VCs invest in about 3000-3500 companies every year.) In addition, there might be a few others (say, maybe another 1-2 in every 10 companies that get VC investments) that get "decent" exits along the way, and hence could be categorized as somewhat successful depending on, again, how one chooses to define what qualifies as a "success story." Finally, there might also be companies that may never need or get around to seeking VC funding. One can, of course, find holes in the simplifying assumptions I have made here, but it doesn't really matter if that number instead is 1 in 1000 or 1 in 10000. The basic point being made here is just that the odds are heavily stacked against new ventures being successful. But that's also one of the distinguishing characteristics of entrepreneurs -- to go ahead and try to bring their idea to life despite the heavy odds. Sources of some of the numbers: http://www.nvca.org/ http://en.wikipedia.org/wiki/Ven... https://www.pwcmoneytree.com/MTP... http://paulgraham.com/future.html Here are others' calculations of the odds that lead to a similar conclusion: 1.Dear Entrepreneurs: Here's How Bad Your Odds Of Success Are http://www.businessinsider.com/startup-odds-of-success-2013-5 2.Why 99.997% Of Entrepreneurs May Want To Postpone Or Avoid VC -- Even If You Can Get It http://www.forbes.com/sites/dileeprao/2013/07/29/why-99-997-of-entrepreneurs-may-want-to-postpone-or-avoid-vc-even-if-you-can-get-it/MB
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.