Team, Co-founders & Legal

How do we divide roles and decision-making so we don't step on each other?

A starting point

Split the company into clear domains and give each person a final say in theirs. One founder owns product and engineering, the other owns growth, sales, and money, or however your strengths cut. Overlap is where fights start. Agree that inside your domain your decision is final unless the other formally objects, and pick one person as CEO who breaks ties on company-wide calls. Two people trying to co-decide everything is slower and angrier than one clear owner per area.

Go deeper

Hand-picked from around the web, each with a note on why it earns your time.

3 resources 3 link-checked

Read

✍️ Essay
✓ Link checked Free Intermediate

Why we picked it This is the cleanest map of the three ways co-founders actually decide things: consensus, functional expertise (your domain, your call), and CEO tie-break. Batista's sharp point is that early co-founders sit at near-zero hierarchical distance, so nobody wants to pull rank, and that awkwardness is exactly why fights fester. It gives you the language to agree up front which mode applies where, so overlap stops being a turf war.

On Co-Founder Decision-Making

From edbatista.com by Ed Batista 12 min read

  • Name the three decision modes explicitly (consensus, domain expertise, CEO authority) and agree which one governs which call before you need it
  • Consensus is the trap: leaning on it for everything produces circular arguments and paralysis, not harmony
  • The CEO must learn to influence rather than command, and the other founder must genuinely disagree and commit, not silently resent
Open edbatista.com →
📄 Article
✓ Link checked Free Intermediate

Why we picked it GitLab runs a fully remote company on exactly the rule your answer prescribes: every area has one named owner who holds the final say, and everyone else can weigh in but does not co-decide. It is the most operational, copy-able playbook for one clear owner per domain, written by a company that lives or dies by it. Steal the mechanic wholesale: assign the domain, name the person, and let disagreement escalate cleanly instead of stalling.

Directly Responsible Individuals (DRI)

From GitLab Handbook by GitLab 15 min read

  • A DRI is one named person with final say in their area, which kills the 'who decides?' ambiguity that slows two founders down
  • Input is welcome and disagreement is encouraged, but the DRI makes the call and the team commits
  • Split ownership so decisions never have two owners: overlap, not disagreement, is what actually causes the deadlock
Open handbook.gitlab.com →
📄 Article
✓ Link checked India Free Beginner

Why we picked it The single clearest explanation of the two documents Indian founders confuse: the founders' agreement (equity, vesting, roles, IP, departure, signed at or before incorporation) versus the shareholders' agreement (investor voting rights, drag/tag, reserved matters, signed at your raise). It nails the timing rule that trips people up: sign before shares are issued, because you cannot bolt vesting onto already-issued shares without every founder consenting. It is blunt that IP a founder built before incorporation belongs to that founder personally until a formal IP Assignment moves it to the company, which is exactly what breaks a diligence during your first term sheet.

Founders' Agreement: Definition, Key Clauses, and Template for Indian Startups

From EquityList by EquityList 15 min read

  • Founders' agreement governs the co-founder relationship; the shareholders' agreement layers in investor protections later, they are not the same document
  • Sign at or before incorporation and always before shares are issued, or vesting cannot be applied retroactively
  • Pre-incorporation IP stays with the individual founder until a formal IP Assignment Agreement transfers it to the company
Open equitylist.co →

People also ask

Do I actually need a co-founder, or can I go solo? You don't strictly need one, but the data says teams outlast solos: complementary skills, shared load, and someone to argue you out of bad calls al... Beginner 3 resources → Where do I actually find a co-founder if I don't already know one? Start with people you've already worked with, ex-colleagues and classmates beat strangers because you've seen them under pressure. If your network ... Beginner 2 resources → What should I look for in a co-founder, and what are red flags? Look for complementary skills, shared values on money and ambition, resilience under stress, and someone you can fight with and still respect. Red ... Beginner 3 resources → Should I co-found with a friend or family member? It's the most common path and one of the riskiest, familiarity is not the same as compatibility as business partners, and a bad split can cost you ... Intermediate 2 resources → How do I 'date' a potential co-founder before committing? Run a real trial: work on a scoped project together for a few weeks, ideally under a deadline, and pay attention to how they handle disagreement, d... Intermediate 3 resources → As a non-technical founder, how do I find a technical co-founder? Earn it: show up with customer proof, a clear plan, and ideally a scrappy no-code prototype so you're offering a partnership, not just an idea. Goo... Intermediate 3 resources →