Business co-founders in tech startups are less valuable than they think
162 comments
·April 27, 2025dgs_sgd
verelo
I’m running a business that’s currently doing around 32k a month at ~85% margin after 2 years in operations, no funds raised to far. I have a friend who is an MBA and only held corporate roles up until now. I’ve been running companies my entire life, and had one exit that was 42.5M US.
We discussed partnering up, and when i mentioned a buy in or 10% equity split (with no buy in) or some combo of the two, he backed off pretty quick.
Turns out he expected something around 40%-50% with no buy in. To me this is just unintelligent? Especially from an MBA.
TuringNYC
From what i'm reading, you seem like you need employees or outsourcing, not partners. Why would you even bother with this person, their incentives seem all misaligned.
Not sure if they approached you, or vice versa -- but people often approach with deals like this because they are trying to find suckers who they can dupe. And sadly, they find them.
HWR_14
He discussed partnering up on your current business or were you talking about a new and different startup? I think you mean the first one, but that seems shocking to me.
ZeroTalent
MBA doesn't mean that much by itself.
jongjong
I would say that MBA means nothing by itself. It's 100% about their social network. MBAs were a great way to network as a lot of elite kids got MBAs. An MBA is just a proxy for something else which isn't necessarily there...
s1artibartfast
>To me this is just unintelligent?
You would know better than us, but I dont think of 10% as a partnership. Maybe they just thought they were going to get a killer deal.
anitil
10% sounds like an employee with a decent lottery ticket to me. Maybe that's unfair.
_bin_
Very typical. I've run into cases where an "idea guy" basically says "you do all the product and tech half, I'll do marketing and strategy." Which is dumb, because sometimes I'm legitimately better at the strategy half too. Generally these people want ridiculous equity splits of that nature.
It's worth anyone technical's time to build skills in strategy, marketing, finance, etc. The technical co-founder always gets screwed and suffers from a general lack of respect. In my opinion, it's usually unwise to take positions where you're strictly the technical co-founder, or where you're marketed as the same.
parpfish
> Which is dumb, because sometimes I'm legitimately better at the strategy half too
A semi-related thought I've had recently:
I've run into a number of non-technical product people that say that they're primary skill is that they have a great "product sensibility" that engineers lack so they need to step in and provide guidance. It's true that many engineer-designed products are terrible, but I'd argue that most engineers have pretty good product sense.
The problem is that engineers have a conflict of interest that leads to them making sub-optimal product decisions. A non-technical product person gets the "luxury" of only thinking "what is the best product for the user?", so they end up with a good design. But an engineer can't help but also factor in "i'm the one that has to build this, so how much extra work am i giving myself?" so they're design will be a compromise of what's good for the user and what can be built easily.
this can have big consequences for how an org should divide work. If somebody has a broad set of responsibilities, they can't help but make tradeoffs (that they might not even be cognizant of) because they're weighing multiple objective functions.
So, when it comes time for figuring out who should be in charge of strategy, it might not just be an issue of "who's better" but more an issue of "who has the least conflict of interest"
zdragnar
I don't think this is a conflict of interest.
Every feature, design decision, and iota of technical debt are money and time. Either that's raised and spent up front, eating at equity, or it is deferred until a point where revenue pays for it, it is redundant due to a pivot, or becomes so essential that new funding is raised (possibly from a pool that doesn't dilute so much value).
Presenting an accurate and fair cost / benefit analysis of these tradeoffs (at least on the technical side) is the main purpose of a technical lead. Non-technical business people can't get that information on their own. They should have a say in the decision if it materially affects the product's launch, but that's the normal give and take.
fuzzfactor
>"who has the least conflict of interest"
What about "what role needs to be done the most at the time?"
>sometimes I'm legitimately better at the strategy half too
Technical people should be eager for more business responsibilities than ever before starting a business.
If it's an "engineering company" ideally you would have two founders each having outstanding technical abilities, and far exceeding anything a non-technical alternative could bring to the table from a business or sales aspect. To begin with if you want to start a business, you need to be the kind of engineer that wants to build sales in some way or another. On the front lines and/or in the background.
And to be real one of you is going to have to go full-time into sales & marketing to pursue some type of cash flow until things get rolling in some way. At least.
Then you can more sensibly consider having the non-tech MBA type come in under the top engineer who has been successfully selling already. And that's the beginning of a chain-of-command where an "engineer" is never hired or fired by anything other than an "engineer". And there's always an engineer (sharp in business, not lacking anything needed) at the top of any non-tech hierarchy by design.
Non-engineering companies where the non-tech-types dominate the hierarchy, can still have decent opportunities for the engineers they hire to work on projects under them. But there may not be as much room for upward movement or appreciation for outstanding skill up and down the line. Might also be more often found involved with financial irregularity, or more commonly non-fair dealing even with some of their own people sometimes.
TuringNYC
>> But an engineer can't help but also factor in "i'm the one that has to build this, so how much extra work am i giving myself?" so they're design will be a compromise of what's good for the user and what can be built easily.
The PM/Strat component is like a fifth or tenth of the tech work, typically. Every product design decision often has a magnitude more of associated implementation work. The only way i'd go with this setup is if the PM/Strat person if one of these things:
- PM/Strat person already has customers lined up
- PM/Strat person has paying partners lined up
- PM/Strat person has had exits with associated aura
- PM/Strat person puts in upfront $ to compensate the tech person
- PM/Strat person takes a way lower equity
throwawaymaths
> But an engineer can't help but also factor in "i'm the one that has to build this, so how much extra work am i giving myself?
I wonder how many startups have failed because the tech has been too much of a pain in the ass to maintain and the technical staff burns out and leaves, with more and more expensive developers postponing leaving till as late as possible and doing as little as possible
cruffle_duffle
Conflict of interest is exactly how I term it as well. Tech people with good product sense have to work very hard to override their engineering instincts or they’ll handicap the product.
I’m guilty of it all the time. What helps is remembering that absolutely nobody gives a shit about the code or the architecture. Nobody. It really doesn’t matter. They just want an awesome product.
(Which isn’t to say none of that matters, because it does. We are engineers and know the consequences of shitty technical decisions… it’s just that you have to pull yourself out of that mode when thinking of what needs to be built)
mountainriver
It’s funny how many people think their ideas are truly brilliant and warrant a massive amount of respect.
Anyone who’s worked as an engineer for awhile knows that ideas are a dime a dozen, they are rarely unique, and are about a millionth of what needs to be done to succeed
randysalami
What is needed in your opinion?
EDIT: I say this as an engineer who is putting his notice in tomorrow to found a startup
EDIT EDIT: Thanks guy, this is along the lines I'm thinking. I'll be competing with companies like Asana, Monday.com, and ClickUp. I worked in a consulting environment for two years and these tools could never be adopted despite the org size growing to 1000+ people in my larger team. It was a big pain point and I think I've built a solution that will help big time.
JumpCrisscross
> worth anyone technical's time to build skills in strategy, marketing, finance, etc.
This leads to jack-of-all-trades types. Good non-technical folk exist. They’re just not easy to find for obvious reasons (same as good technical founders who can see the forest for the trees).
A good technical founder dilutes their comparative advantage e.g. negotiating with suppliers and prioritising payments ahead of a close.
_bin_
It can, to be sure, and it's not ideal. But the perception that technical co-founders typically get gypped hard is very warranted. This is a thing where you can often still get a reasonably good result with a technical co-founder, not as good as were he solely focused on product/tech stuff, but enough that his individual outcome may be higher than letting the biz guys run it.
Obviously good biz guys somewhat mitigate this but finding those is easier said than done.
liquidpele
“Jack of all trades, master of none, is usually better than master of one”
TuringNYC
>> I recently walked away from a potential startup because my non-technical partner (MBA ideas guy) wanted an 80/20 equity split in his favor. I was the first to broach the discussion and proposed 50/50.
I'm constantly approached by "business guy" with deals like this. Here is the truth -- even 50/50 isnt enough because technically, the tech-co-founder is often doing all the upfront work and taking all the upfront risk. The business-co-founder gets a free option to do work (or not) afterwards. All upside and little downside.
IMHO good business co-founders are worth gold and make their worth obvious. They already have POs lined up, they have partnership agreements already in the works, they have VCs willing to invest based on past performance. Perhaps they already tried the business with some overseas teams doing POCs. Perhaps the business co-founder already has exits or a successful business and is willing to pay the tech-co-founder some nominal amount to show skin in the game. Those are all good signs.
If those arent the case, and the "business-co-founder" is sitting back while the other is hard at work coding a prototype -- you dont need a co-founder. Just be the CTO+CEO and hire the "business" work yourself!
In the absolute worst case, i've seen a "business-co-founder" continue to push the definition of MVP more and more and the "tech-co-founder" seeing the sunk-cost of the work they have put in, continues to ever-expand the MVP. Meanwhile the "business-co-founder" gets months or a year of free labour with a free option to participate -- or not.
osrec
Good you walked away. In my experience, the heavy lifting in a tech start up is, by definition, the tech. The "idea guys" rarely understand that it's the execution that makes an idea valuable.
Sales are important, but are a bit of a crapshoot. You can't consistently sell trash, no matter how good a salesperson you are. The guy was happy to roll the dice, while using your mental energy. Great deal for him, but not so good for you. You risk the burnout, stress and pressure, while he feeds you requirements and deadlines, and essentially becomes your manager.
In my younger days I got a lot of similar proposals, but thankfully could see right through them from day one. Bootstrapping as a solo founder was the harder, but ultimately more rewarding route for me.
notfromhere
The business side needs to have subject matter expertise in the market, running an org, fundraising, marketing, etc. 'ideas guys' are pretty worthless without that.
80/20 is an insane proposal; 50/50 feels reasonable, but I 100% agree with you that the technical side is way more crucial than the business side, since under $10m in ARR your biggest issue will be making the tech work well enough to attract customers.
pier25
> wanted an 80/20 equity split in his favor.
If they're so confident in their value they should just find some money and pay for the development of the product to a freelancer or employee.
bn-l
They may be a little surprised how much that costs. And then the running of it and the bug fixing and the feature expansion. It may be a little… “surprising”. My advice is to get idea guy to price it out haha.
slt2021
they are so confident they are offering to pay with 20% of equity (basically vapor), instead of hard cash.
imagine the chutzpah
yibg
Fairness of the equity split aside, it also indicates he doesn’t see you as an equal partner. Rather you are seen more as an employee that is going to be working essentially for free. So he probably also won’t value your input and contributions in the venture either.
LouisSayers
> wanted an 80/20 equity split in his favor
I would have been tempted to take the idea, partner with someone else and run hard with it in spite.
I can't stand people with this mindset, and it's fair game if that's the cards they want to play.
Ancalagon
I had this exact scenario happen on the ycombinator cofounder matching of all places. Except the other cofounder (non-technical) wanted it 95/5.
Yeah, I stopped all contact that same day. That project never got launched.
TuringNYC
>> I had this exact scenario happen on the ycombinator cofounder matching of all places. Except the other cofounder (non-technical) wanted it 95/5.
I've gone to some of these just out of curiosity and it seems like people on the hunt for suckers. Having been thru this myself and seen the drama play out with friends from back in the dot-com days to now --
CO-FOUNDING IS LIKE MARRIAGE You cannot just match to someone. There has to be a low-stakes dating period, an engagement period, and then "marriage". You have to be able to walk away early on w/o extensive entanglement. The best co-founder is someone you've known for a long time in various semi-tense scenarios, where you can evaluate their ethics under pressure. This ideally means having worked together or done many projects together.
notfromhere
You should have countered with 95/5 in reverse, because if you can't code, nothing is getting done anyways.
crazygringo
I don't agree at all. Not even with the premise that "there are significantly more business guys looking for tech guys than the reverse".
There are a lot of business and tech guys and most of all of them are pretty clueless when you randomly meet them in "gatherings".
But a valuable business co-founder brings extensive domain expertise, a network of people, sales skills, management skills, and fund-raising talent.
There's little point in arguing who is "more" valuable -- the business side or the tech side. They're both critical to have.
For some reason, this post equates the "business side" to the person with the "idea". But that's a strawman. Having an idea doesn't make you a "business" co-founder. Being a business cofounder means having a experience and talent on the business side of things. And a good business co-founder generally doesn't have a lot of trouble finding good tech people, because that's one of those business skills that they're good at...
John23832
> But a valuable business co-founder brings extensive domain expertise, a network of people, sales skills, management skills, and fund-raising talent.
A valuable technical cofounder brings the skills to literally create what you're trying to sell. Otherwise, have fun selling dust. Or networking to sell nothing.
The "0 to 1" here isn't "no management to management" it's "not having a product built to having a product built".
frenchmajesty
Hey, OP here. I view it like this: if you were to take all technical people on the market for launching a startup and plot them on a distribution to find the "valuable in early stage" subset, you would find that 35% are good enough to get a startup off the ground. They don't need to be extraordinary programmers, just good enough but with a lot of drive.*
However, for non-technical folks that are on the market, the distribution is worse. Only the top 10% ~ 15% actually have sufficient abilities to pull it off. The remaining fall into the archetype I wrote about here.
The caliber for what's in the market is skewed thus the technical person has to be a whole lot more picky than the other way around to avoid ending up with a dead weight.
[*]: This excludes specialized skills like Deep Learning or chemical bio-engineering, etc...
conductr
If you're taking a fail fast type approach, the business guys fail faster when they can't get a tech co-founder to rally around their ideas. If you can't do that, you probably can't sell the MVP either. On flipside, the tech guys will spend month and even years polishing their 'product' without ever actually launching it with actual attempts to sale it. So they fail slowly after sinking tons of time. They'll talk about it as a side-project to minimize the appearance of failure but if they put all that work in they really do want it to succeed. They just get to the point where code is good enough and can't force themselves to transition to marketing/sales/etc.
bix6
Solo founders do worse and teams with a technical founder do better particularly in enterprise. So it seems your best chance is one of each.
ashalhashim
The ideal business co-founder has to be strong in distribution AND eliciting product feedback. This is why the “MBA types” and ex-McKinsey consultants fare so poorly - they’re used to companies spending loads of money to hear what they think. As an early-stage startup founder, nobody gives a shit about your product and no one wants to hear what you think. Your job is to identify where demand is highest in the market and then turn that demand into dollars. They also need to be excellent communicators who understand or at least appreciate how much goes into building products.
For those reasons, the best business cofounders in my experience, are former salespeople (for b2b startups), demand generation marketers (for b2c), and product managers.
n_ary
The article reads… interesting. A business depends on its demand, competition, scale, operation costs and numerous other factors. If the product is a tech, a technical founder can have immense impact on future success but marketing, customer acquisition, sales, networking, fund raising and other huge headaches are often burdens carried by non-technical counter part.
Of course, the person building something from a vague idea to life wields magical power, but the other aspects of business are more so important.
As an engineer myself, I can see 500 ways I can improve things at my employer’s business, but while I have a technical vision, the non-technical founders of the business has broader picture and what I may wish to spend time optimizing might just be a pocket change issue not worth solving.
We technical folks undermine the mountain of difficulties of marketing and sales as well as interacting with people to convince them to part with their money. Of course, I have seen a fair share of over confident wanna-be founder who would just be next trillionaire if someone would build the 10000th Airbnb clone but for pets so they could sell it and give 5% equity to the builder because their idea was the main thing, but in broad sense of things, tech is just a means to an end for a successful business and simply building is not the 100% of execution step.
saucymew
Great points. Good founders are on both sides of selling and building. If you don't believe in sellers, you've never worked with good ones.
bjornsing
I’m not sure it’s fair to say Zuckerberg’s only advantage over the Winklevoss brothers was his engineering skills. I think he quickly understood the whole dynamics of that potential business and had a more clear vision. Being able to digest a lot of seemingly disparate information (e.g. how college students responded to the “hot or not” prank) and create a compelling vision along with a path to get there, that’s both very hard and very valuable.
But I do agree with the overall sentiment that these ex-McKinsey “business co-founders” often lack the most valuable skills. I’d even go as far as saying they are generally quite bad “idea guys”, in the sense that they are more Winklevoss than Zuckerberg.
I even have a sneaking suspicion that Europe is so far behind the US in the startup game partly because the “ex-McKinsey guy on top” anti-pattern is the social norm here.
neilv
One thing I've wondered about for awhile: How do you find a business co-founder you can trust?
For one example, the article says that some of the best value that a business co-founder can contribute is disproportionately building the relationships. But those relationships can be more connected to the business cofounder themself, than to the company.
It's a bit different for the technical co-founder, since your perceptible contribution is usually IP expressed in in artifacts like code that is owned by the company, and can't legally be taken with you.
There's also the perception of the value of that IP: much like a novice programmer might think that most of the value is in their own software/knowhow/grind/brilliance, the novice business person might think most of the value is in their own ideas/leadership/network/hustle/brilliance.
The business person might also perceive the technical contribution as being commodity skills, and ones that can increasingly be done by "AI" robo-plagiarism for $20.
So, if the business person is, say, having second thoughts about the 50/50 split, they can make a backroom deal with investors to cut out the technical cofounder, or bring their new relationships with investors and/or customers with them to a different (or 'different') startup.
Obviously, one defense is for the technical co-founder to somehow be a superhumanly valuable non-commodity, and to make sure that the business co-founder understands that.
But, realistically, doesn't the technical co-founder probably need a lot of trust in their character and commitment of the business co-founder? Maybe even more than vice versa?
JumpCrisscross
Anyone can do a back room deal to screw their partners. Mark Zuckerberg was a technical founder, for example.
neilv
Maybe, although students in the dotcom boom was a different situation than now.
(Source: Was one. Many people were trying to fund you, sometimes without you even asking. And you couldn't go to a student party without some Sloan or HBS student zeroing in on you, and wanting to talk with you.)
fellowniusmonk
If you are the technical co-founder who is writing code you should ensure you have legal protections before anyone else has access to what you have written.
This can be a legal agreement or built in protections via copyright law.
Same as any author who produces work that others can profit off of in perpetuity, don't sign your built in protections away.
neilv
In the example I'm giving, code IP isn't very relevant to a business cofounder screwing, because the (real or perceived) value of the code IP is less than the relationships that may be tied to the business cofounder.
All the code IP protections mean, in this regard, is that the technical cofounder has less value comparably tied to them personally.
827a
> some of the best value that a business co-founder can contribute is disproportionately building the relationships.
The other subtle thing I take issue with on this is: What relationships, exactly? Most of the time I've seen this surface as a few early customers you might not have otherwise gotten, which is great and necessary, but IME that well runs dry pretty quick, and those customers oftentimes don't stick as well as ones that were found on merit. A better relationship with vendors? Again, weird, merit should trump that personal relationship.
If you're building a business that relies on a small number of very high value contracts, I think I could see a world where having a foot in the door on those high value customers is worthy of elevating the body that foot is attached to toward Founder. That isn't, generally, how most software companies sell software though.
frenchmajesty
The point I maybe did not stress enough on is the relationship aspect is two folds:
- Have ability to gain hard-to-obtain relationships in the beginning
- Have ability to grow the pace at which you gain those over time
It the beginning it will give you the money to play the game long enough (ie: customers and angel investors). In the short term it help tremendously in deal-making, fundraising, enterprise sales, hiring superstar employee. In the long term, you can broker insane deals like OpenAI convincing Microsoft to invest $10B and bet their AI future on you or get acquired.
PS: Microsoft is now backtracking out of that situation, but Altman convincing them to get in bed in the first place is very impressive.
tptacek
In reality, it should flipped! The technical person is the one who breathes life into an idea and should get the lion’s share
Then you want an employer/employee relationship, not a cofounder relationship. I would run, not walk, from a company with a founder arrangement where some subset got "the lion's share" for reasons like this.
6stringmerc
As a business guy, getting “it should be flipped” wrong and going to print / ready for audience viewing only emphasizes the importance of being able to meet certain expectations such as basic communication when wanting to be taken seriously. This is not a unique instance I have observed. It is not directed specifically at this writer, it is using this writer as an example of hypocrisy in self-serving pleadings.
If you’re going to de-value the role of somebody who can do what you can’t, be prepared to get called out on it or brushed aside without explanation because you blew it. Harsh but true. I know this because I worked sales support with technical people and not technical people in high stakes business relationships.
This is why startups don’t hire people like me because they don’t value what I do and frankly I’m okay with this mutually dismissive relationship. This forum is a frequent reminder of why so many startups are unsuccessful.
tptacek
I'm actually not making a case for business cofounders being undervalued. Maybe they are maybe they aren't. But if you think they're overvalued, put up or shut up: hire them instead of partnering with them. That doesn't happen because strong business cofounders won't accept those terms, which to me is a pretty clear indication that "it should be flipped" is false.
goatherders
This post is hilarious and details exactly why so many startups die in infancy. Yes yes, engineers are brilliant and without them nothing ever gets built.
And even still, sometimes things get built and never turn into a real business precisely because of this hubris. And 99.9% of the time, the ones that DO grow over time would have grown much much faster if "the business guy" had been there all along.
frenchmajesty
This is true! I argue here that the right business co-founder who drives long term financial success to the company is super rare and super valuable. The problem is the average one you'll run into at a networking event cannot deliver on that.
They are much more "I give the ideas and I want to keep 90% equity and you shut up and listen to me because I'm the CEO" guys.
goatherders
Absolutely. Idea guys are the worst.
And a good business person is worth their fair share of equity in a SU environment
totalhack
Well, pretty much everyone is less valuable than they think!
I've bootstrapped and sold two startups, first time with 5 (!) equal cofounders and second time with 3. I've learned a lot along the way, obviously some of that through mistakes of my own. Have my cofounders been perfect? Heck no -- one lacks the same level of drive, the other is less trustworthy (always multiple irons in the fire kinda guy). But we all have strengths, are all generally better off together, and have the combined skill set to run super lean. Even if you think you can do some things better alone, you can never do it all, and that grind will take quite a toll.
Related: over the years the topic of going into business with some of my best friends has come up, and I always say I would never do that. Running a fast-moving, high stakes business with multiple founders involves a lot of tough conversations and occasional relationship strain. My business partners are business partners first, friends second, and I think that's important to consider if you really value a friendship.
dingdingdang
Having started businesses with the explicit lack of biz-co-founders I beck to differ. That is of course unless your da Vinci-like super modal capabilities allows you to feel unlimited joy when doing business plans, taxes & marketing alongside your (hopefully) core competency of product development.
CharlieDigital
I also agree based on several failed startups I've been a part of and a few successful startups.
The business side is the difference between side project and successful venture.
_bin_
I do actually know a few people who are like me and really enjoy both doing the biz plan/strategy half, and the marketing work, and product/tech. It's not as common but I enjoy working with them a whole lot more. We almost always create better results when the tech people are also biz people who understand how what we build needs to fit into the market. It's also super helpful to have some personnel fungibility when you have a small team where you're shelling out 5-20% equity for new members.
In my ideal world basically everyone is like this and the walls between "idea guy" and "tech guy" are knocked down. I've heard a lot of folks get cynical about sharp technical types who get hired by big 3 mgmt consultancies, but ime they're often great places to find those who are both technically sharp and can make a killer deck.
rchowe
I discovered I liked business planning, strategy, and marketing pretty early in my technical career.
I also discovered that one of the thing business people bring to a company are connections, especially if they have already worked in a vertical, and few people want to talk to a bright kid about their problems.
dust42
Having seen plenty of businesses throughout my life, both successful ones and less successful ones I'd say the most important traits are:
- the ability to execute
- having drive, focus and flexibility to adapt
- being able to manage a team and keep it focused, motivated and on track
this is valid for both the technical founder and the business founder alike.In a perfect team the business founder has a very good understanding of the tech side and the technical founder a good understanding of the business and marketing side. Product is nothing without sales and sales nothing without product. Despite this being obvious I have seen several companies fail on this.
Last not least it depends on the product. The more complex the tech is the higher the share of the technical partner should be and vice versa the more specialist business domain knowledge is needed, the higher the business partner's shares are.
FlyingSnake
> ability to execute
How do we define what execution looks like?
As a general rule we must be wary of “business cofounders” who sell pontification as execution.
neom
I was one of the "business guys" at DigitalOcean from very tiny to big. Execution looked like: 20% of the time in meetings discussing what the next period of time without seeing each other was going to look like and 80% of the time on flights and in hotels. My mantra was always "be directionally correct, go to market as hard as I can every single day, and fully trust the engineers building the products around me".
mlinhares
If your "business cofounders" aren't closing deals and landing sales they're useless. So if you're going to join a "non-technical founder" they must both have the contacts or a in in the industry you'll be trying to join and must be a great salesman.
If they don't have that, walk away, this person has no value.
TuringNYC
>How do we define what execution looks like?
- Previous exits
- Previous successful business
- Bringing 1-3 potential buyers to the table who can define what is needed and what they would pay, ideally clear "if X then i pay Y"
dust42
The ability to execute means to deliver timely and on budget.
I have seen people who would not be able to set up and manage a hot dog stand and yet they were trying to run a business with 50 employees. The only result was burning money like there was no tomorrow.
w10-1
The value of a business co-founder lies in their ability to build business relationships and extract value from them.
The value of one founder to another lies in complementary skills and perspectives engaging start-up issues in a productive way, which usually means deep levels of mutual understanding and trust -- which can be antithetical to business relationships and personal comfort. So: hard.
The CEO/COO split reflects the difficulty of scaling this.
Is the solution to talk early? Maybe, or maybe that interferes with trust-building. The key thing I believe (here and elsewhere) is to avoid projecting what you want or fear into what you have. If it's important to success, validate it. For that, it helps to have people willing and able to be honest and truthful, particularly about unknown unknowns -- even if it is otherwise their mandate and mission to project confidence and gain trust.
I recently walked away from a potential startup because my non-technical partner (MBA ideas guy) wanted an 80/20 equity split in his favor. I was the first to broach the discussion and proposed 50/50. It was a severe misalignment in expectations, and this was after 3 months of meeting regularly to refine the idea and build out prototypes (read: I was building the prototypes).
My advice is to have this conversation with a potential business co-founder as early as possible to avoid wasted time. I could have saved myself months.
Look out for business guys who severely discount your value as a technical founder. Not saying they're all like this, but a really skewed equity split is typically a red flag.