My co-founder recently decided to shut the company down, focusing on what he/she does best rather than being reliant on tech/design loops by making our amazing designer create a Shopify site that he/she can manage him/herself.
Without going into details, it is fair but we will need to have serious talk once everything has settled so I can move forward.
Anyhow, as my payment for these past years, I get to sell whatever we have created, code wise, and get the dough for it.
The problem is that I have no clue how to properly handle a sell like this.
There is a bunch of new startups that has recently popped up, doing what we initially did with a caveat; they lack an app for it, currently hustling to make things work. So there might be a pretty good possibility for us to sell it.
To give you an idea what we are doing; an React Native app that sell and connect a very specific type of workshops with costumers over custom WebRTC Video chat(fork of React Native-based Jitsi Meet). What I can tell, I haven't seen another custom Jitsi-Meet integration yet that gives the ability customize the UI that we have.
We use Firebase as our backend and Stripe as our payment integration. Data entry / workshop scheduling is managed using a custom built CMS. We have custom emails + in-app notifications work through Firebase Cloud Functions.
Should I contact these startups? Anything I should do first, legally wise?
I'm clueless.
Software without a market and customers already using it is basically worthless. If you were in a hot market and had clients a competitive startup might offer some decent money but it’d be mostly for the customer list.
One time that software can hold value is when you have a unique patent or have invented something that is truly new and revolutionary. Think scientific software algorithms or long standing problems where your code can be integrated quickly and solve a problem that isn’t something people can easily replicate with just some time.
For the most part the sounds of your code is that other people could replicate it fairly readily with just some time. I am not criticizing anything, just saying it doesn’t sound like you invented anything truly new. More like you guys put things together in a way to solve a problem which likely had value to people but not enough for the software to hold substantial value without a market and user base.
You can of course try and maybe you’ll get lucky. But I’d likely say you’d have better luck carving out a library or a complete product and open source it. Then sell consulting services around it and maybe host it etc.
The costs are sunk, your best bet is trying to use the software as leverage, not trying to sell it outright. At least that’s been my experience when I had companies fail before we had real traction. I did have one offer for like $5k on software we spent ~600k developing. I held the code and integrated parts into other projects that went on to make me money.
Good luck, and maybe you can prove my experience isn’t true today.
It sounds like your co-founder is trying to fire you and leave you with the code, which is not needed because it can be done with Shopify now.
> Should I contact these startups? Anything I should do first, legally wise?
Don't sign anything regarding the breakup of your company. Consider your founding documents very carefully. What do you own according to these documents?
The breakup of a company is a negotiation. Maybe not a very pleasant one, but potentially every bit as important as the founding negotiation.
You will probably want to run your question by a lawyer.
As far as your options, I agree with everyone here who says you likely won't have much luck selling the code. People rarely buy code; they buy customers or revenue. It doesn't seem like you have either, and I don't have much to add there.
BUT! You do actually have something you can sell... your experience. Your last two years weren't a waste. We've hired founders at my company before, and they're great... they have an amazing mindset, are great at making things happen, and tend to be ambitious. These two years of experience are going to make you very valuable to someone. Like you said, there's a bunch of companies out there doing something similar. They don't need your code, but they'd love your experience. You've spent years understanding the space, thinking about the market, and getting a first-hand technical understanding.
I'd think of it that way... this is an amazing resume for you. You'll be able to turn this into money, just not the way you're currently thinking!
Good luck :)
Speaking as someone who not only invests in websites but authored some early studies on the fair value of micro-sites (back in 2012) that deal is utterly bogus.
The value of the business is in the traffic and audience, not the code. To be honest, getting rid of the legacy code and moving the site onto my standard platform is a major goal of the early integration process. I do not pay for code (sorry).
What you have been handed is the back-end of a potential product, the market value of which is unproven (since you haven't been given the customers). While I'm sure the technical quality of the work is excellent, there are multiple strikes against it from a business valuation perspective. Fight for your share of the store profits.
* The company will be completely shut down, no more b-corp.
* I own < 50% of the company
* My co-founder will continue based on our last pivot minus my technical knowledge.
* I would love to be able to chill on this for a while, but my co-founder want to move forward and close our old business down by the end of this year so that he/she can close all tax/business stuff.
* My co-founder invested money to pay our designer / product owner, I invested my time.
* We had no real customer traction due to our (now in retrospect, bad) decision to pivot away from the app we worked hard to release, not maintaining it and work on v2 of it instead. It sucks because through my co-founder, we had serious reach through social platforms such as Instagram, but we also knew the initial business model couldn't scale so we had to pivot.
* Deep inside I knew our code would be a hard sell and I see the bigger picture now. Thank you all for zapping me out of it. I do think that cross-platform WebRTC integration has some value, but as some of you point out, my knowledge is probably more valuable than the code it self. I will reach out to all of you who have pinged me. I might be up to join as a contractor for some time, to help out with knowledge transfer / maintain the code.
* Since my co-founder will still work within the same market, I can't open-source the code without causing friction I'd say. So might not do that.
* I consider my co-founder a really close friend so it is of high importance for me to keep our friendship intact. For us to be able to do that, I need to figure out what is fair so all of your comments really helps!
I'll keep on answering questions as they come. Again, thank you all for your answers.
In Ancient Days, Ampex was the king of video tape recording and magnetic storage. They created a system for recording documents onto video tape, and then later a system for recording documents into mass storage. The software engineers on this project created a database system to manage the storage. When the project was inevitably cancelled, they allowed the software engineer to keep the code from project Oracle.
Of course the value depends on the what the code accomplishes, and what new ideas you can leverage it into.
[1] https://www.cia.gov/library/readingroom/docs/CIA-RDP80-01794...
My company has one chief competitor.
If that competitor went out of business and offered me their source code, I'm unlikely to pay for it. Code tends to be highly coupled to the specific assumptions, structures, workflows, architecture, and environment it was designed for, unless the team has gone out of their way to make it reusable. Most often, it would be easier to rebuild the same functionality from scratch than integrate someone else's code into your product.
What is valuable are the more generalizable and often intangible assets my competitor has accrued:
1. Its relationships with potential clients. 2. The lessons they've learned in building the business so we might avoid them. 3. Their employees.
Do you have any of the above to offer to companies tackling similar problems?
That said, isolated parts of a codebase can be useful, if it's easy to reuse and solves an extremely challenging problem and has required a large amount of investment to develop and mature. If such a part of your codebase exists, you could try finding a buyer for that.
Code is inflexible. Code has bugs and vulnerabilities and patent infringements and licensing issues. Code needs lots of maintenance.
The value is in the people who know the code. That's you. If you sell the code, you have to go along with it.
This statement sounds like your co-founder is just getting rid of you because he realised a designer can do better than you and won't need shares of the company. You validated the market for him and he doesn't need you. This is the reason I always tell idea guys to pay me or go and learn programming themselves and implement their ideas.
Is the stripe integration in react-native? If so, I think it would be great to open source it and publish to npm. There really isn't a good react native stripe library out there, the only one I have dealt with is tipsi-stripe[1] which is poorly documented, poorly maintained and inflexible.
If you really don't want to open source it, I'd love to chat about buying it off you.
Take a loss on this startup and move forward to something new.
But where people here are correct is that in most cases, source code by itself will fetch a lower price than the customer contacts, email marketing lists, pre-qualified leads, ad designs, etc.
That said, we did sell source code at a good price a few times, but that only worked because:
1. The company buying it had overpromised to their customers and were contractually bound to deliver, so purchasing my whacky half-finished source code was cheaper for them than paying the penalty for not delivering on time. As part of the deal, we were also hired for a month to integrate their CI into the app and ship it. After they dodged legal responsibility this way, I believe they never used the source code again, but instead hired a team to rewrite everything from scratch. So they paid us purely for the time savings.
2. The software being sold had been featured on national TV together with a major Hollywood movie studio praising it. This started out as helping people for free and then we built without any feedback what we thought the market needed. But it was a ridiculously unbelievable stroke of lucky events that led to us sending a feature-limited version to studios and them using it and promoting it among themselves.
3. The source code being sold was rumored to contain an algorithm doing content-based image retrieval (think Google Images search) more efficiently than the largest publicly available search engines.
4. The source code was sold at a big loss. It would have cost 5x the price to hire a team to build it again.
It doesn't sound like you're famous yet or like you invented the next big algorithm, and you probably don't want to get paid scraps either, so your best bet if you insist on monetizing the source code would be to find the one medium to large company that urgently needs this video chat to work or else they face horrible consequences. Only then will you get a good price.
If there's no interest though, then any upfront work you do now will be wasted effort.
Depending on what your co-founder is walking away with, you may want to negotiate a better exit. If there is nothing else, then more than the code work on selling yourself to an interested company.
Code is cheap. Your legacy from this startup will be experience, not code. Move on and start fresh.
Dump it and start something new.
It's a sunk cost.
I've got vast amounts of code from previous projects. All worthless.
A bunch of Reddit employees broke off years ago and started a company called Imzy, the CEO decided to shut it down and took ownership of the source code, which he then sold to someone (I want to say techcrunch) for precisely 1 million dollars.
I guess it is harder to make a platform and just sell it exclusively to a client than making a platform and offering it as a product for many other developers. In this case though, he might just be able to sell a few hundred copies of his code for like $100, which is not a lot of money, asuming the platform is fully functional.
1. I used it as a very expensive resume. Costs me a few hundred dollars in running costs on AWS but pays back regularly by helping me win new consulting clients.
2. Mine was a travel startup so had few reusable modules e.g. booking engines for various GDSs (Sabre, Travelport and even Expedia's API). I manage to sell these with little modifications to a few companies that were building things from scratch. After initial sale and a minimal support period, further support was charged at consulting rates.
3. Initially I thought that I would be able to sell the whole development stack specially the user management, email verification, security, PCI compliance payment solution stack etc. But never found any takers for that part of the code. Don't really know why.
4. I initially folded my startup because of lack of experience in sales and marketing. But I am plugging those holes in my competence and I might resurrect this startup in a couple of years from now. I am glad that I never gave up my rights to any part of the code or technology.
Not sure if any of above is relevant to your particular case except #1 which could be useful if you decide to do consulting/freelancing in future.
Edit: formatting / typo
I'd definitely suggest that you chat with a lawyer first so you can be sure that you're protecting yourself properly, both from your old co-founder, and from any people you might show the code to.
Are you required to sell the code as a part of your separation from the company? If not, you might consider starting your own company around it, if you still believe in the product.
Ultimately, I don't think you're getting a great deal here. If you don't have a prior agreement that gives you anything more liquid, you might be out of luck (since your co-founder is winding down the company, you soon won't even have an entity to file a complaint against), but "code in lieu of cash" isn't a great payout.
That said, maybe worth contacting these other startups. I double they'd pay for the existing source code to just launch. But, it might make you a good hire you for them.
If you sell your code, the most it would probably fetch is somewhere in the low three digits, and it would probably be snapped up by someone who doesn’t care about the business they just want to have a beefy open source project as part of their resume or portfolio (which is basically the smart way to get open source credibility without toiling for years to no end, think about it, 300 bucks buys two years of open source experience).
If I were you, I’d beat them to the punch and open source your project and move on with your life, let others maintain it and maybe make it into something great.
Pull the code apart and find the interesting ways you've built it, then create training videos on how you did it and sell it as a course.
What value does your software provide over Shopify? Whatever the answer is, thats is how much your software is worth. Your partner has decided that the value add of the software isn't enough to justify the cost of you, sorry.
It sounds like it's a simple CRUD app that can be mostly replaced by shoppify focus on what sets it apart, who would want that feature and what value they would assign to that feature.
You could try whitelabeling the product and sell it as a platform and try to compete directly with shoppify, but it seems like the business people just don't see the value in your software.
Having said that, I don't think this would be easy feat though, especially considering you've spent 2 years building it, the price might not be something affordable for early-stage startups.
I'm sorry I cannot give you advice for your future endeavors, but if your code ends up shelved, please consider sharing your Jitsi Meet customizations with us (I'm one of the Jitsi core devs) so we can improve the SDK.
Best of luck!
> There is a bunch of new startups that has recently popped up, doing what we initially did with a caveat.
this is also a huge red flag, if there are many companies already investing in doing the same, why would they take your codebase? best case scenario would be to get a job on the same space now that you have: experience.
Many, if not all of whom you pitch your product for and are interested to buy it would ask you to work for them. Even if that doesn't happen, get prepared to handle lot of support calls; so factor that into the price.
>Anything I should do first, legally wise?
Invoice from your company that they are selling to you, for some token amount. Perhaps a legal binding agreement should help as well. Get advice from a proper legal counsel.
Startups with the resources to purchase likely have the resources to build themselves. And the inclination.
Your best bet is to prospect for companies who might consider the IP for a secondary product that compliments their core offering. They'd likely want code + customization + a maintenance period. It could be worth it.
Send me a note if you'd like to discuss further.
What's your co-founder walking away with? If they're walking away with cash and your walking away with (non patented) IP then you got the short end of the stick.
As others mentioned, be sure you have clear and unhindered rights to the code and IP.
Otherwise, take your knowledge and skills and do consulting work (maybe for one of those competitors). Even if you walk away with no remuneration, you have great hands-on experience in a production environment.
If you open source it today, and give it away completely for free, you will be lucky if one person forks or stars the repo, then never looks at it again.
You’re probably too “in it” right now to make good decisions.
Set up a good demo of what your code does, then approach new companies and offer to provide it to them either for a fee for service (best) or by joining them. Good luck.
2. Open source it and add a donate link.
Also make sure you have paperwork in place that gives you right of IP. Given that the past IP was owned by your company, this is not merely a handshake and email.
A lot of readers are probably keen on owning a business and your reality check can maybe turn into good advice for others.
Not trying to be snarky, but I genuinely prefer "they" and "themself" for talking about a generic other person like this. Also less keystrokes.
It would be a pity if that code goes lost
I am not sure of the details, but if you can make a Shopify plugin which others can use you could make some money out of it.
I might have a potential usecase for your code. Please contact me using the email in my bio.
Thanks.
- Decide who gets the data: users, you, someone.
- Sanitize servers and services by trying to overwrite data with junk values before canceling.
- Cancel monthly services and free services.
- If it was good, don't let the team relationship go to waste. Talk with whoever's left / worked-with previously about doing something else.
---- Then and only then ----
- Do "consultingish" work or solve a problem you have to find a problem worth solving.
- Sell something good people want before you invest too much time/money/mental health building something too much.
- Keep it real: building "your amazing idea" without a feedback loop gathering critical data from paying/potential customers is #fail.
- Someone though will have to step-up to be the sales/buzz builder or one will need to be found (hopefully, someone you've known for some time or a friend-of-a-friend). No useless "idea guys" allowed.
- Sales/buzz person or someone will need to be the captain of the ship ultimately in-charge of everything.
- Iterate fast, executing based on feedback and sales numbers. Prefer the best one you can get into if you can. (YC, hihi.;)
- Everyone at the beginning gets equal equity vested over 3-5 years. First employees should get ~1% equity, more if it's an employee-owned co-op.
- Don't pray for funding, sales/profit cures all.
- Raise funding only if you could definitely grow faster with more money.
- Skip accelerators unless you need a network and/or are relatively inexperienced.
- When you get big enough, incorporate (California or Delaware C-corp). If it's s consultancy, LLP or LLC. https://clerky.com
Yikes, it sounds like you are walking away here with virtually nothing.
If I were you, I would fight for ownership in whatever is next for your cofounder. If that means it is a Shopify store, that is fine, but you should get X% of revenue, profit sharing, something out of this.
The code you have now is ultimately worthless and is not a good 'payment' for the time and energy you invested into this company.
I do not think the current arrangement you have outlined is in any way fair.
I keed, I keeeed.
Unless this IP or "Code" was written by someone else let it die on the vine with the rest of the company, write new code for your own project, use your experience to make improvements to the new code and start fresh, it sounds like you were using pieces of gpl code anyways.
Why would you bother taking the risk of creating a unicorn only to have your pokects picked by your "cofounder" that quit, then sues once it becomes profitable?
No matter what agreement you made, even if you get it notarized, your risking much more than if you just knuckle down and do the work again yourself.
Besides it's always easier and faster to do it a second time.