On this page
A founder team can spend eight weeks shipping an MVP and still miss its first customer deadline because nobody agreed who owned sales, product decisions, or follow-through. Co-founder performance expectations turn a vague partnership into a working operating agreement before missed commitments become personal disputes.
Define co-founder performance expectations as operating commitments
Co-founder performance is not a quarterly scorecard copied from a large company. In an early-stage startup, it is the agreed standard for the work each founder must complete, the decisions each person can make, and the evidence used to judge progress. If your agreement says one founder “handles growth” and another “handles technology,” you have titles, not expectations.
Start with the company’s next 90-day objective. It may be securing ten customer interviews, shipping a paid pilot, reducing product failures, or preparing a fundable data room. Then write each founder’s contribution in terms of outputs and deadlines. “Own customer discovery” is weak. “Run 25 interviews with the defined buyer segment, document patterns, and recommend the first paid use case by 30 June” is usable.
- Outcome: What business result is this founder accountable for?
- Output: What work product proves progress: a prototype, pipeline, signed pilot, hiring plan, or financial model?
- Deadline: When will the team review it?
- Decision right: What can this founder decide alone, and what needs joint approval?
- Support needed: What input, budget, or access must the other founder provide?
This matters especially in India, where many founding teams begin as friends, classmates, or former colleagues. Familiarity can delay hard conversations. Write the agreement while trust is high and before cash, equity, or investor pressure makes every discussion heavier.
Split roles by decisions, not job titles
“CEO” and “CTO” do not settle ownership. A CEO may own fundraising but need the CTO’s input on delivery timelines. A product-focused founder may decide the roadmap but need commercial input before building a feature for one prospect. The goal is not to eliminate collaboration. The goal is to prevent decisions from waiting for unanimous approval.
Map your recurring decisions before you map your ambitions. Include customer commitments, pricing, hiring, product scope, vendor spend, fundraising, and founder hiring. For each one, name a directly responsible founder, a consultation requirement, and the point at which the issue moves to both founders.
| Decision area | Single owner | Joint approval trigger |
|---|---|---|
| Customer discovery and sales pipeline | Commercial founder | Pricing change or non-standard customer commitment |
| Product roadmap and release scope | Product or technical founder | Change that affects the agreed launch date or budget |
| Hiring contractors or employees | Relevant functional owner | Any long-term cost commitment |
| Fundraising process | CEO or nominated founder | Term sheet, valuation, dilution, or investor rights |
Document this in the founder operating agreement, not only in a chat thread. Decision rights are a practical extension of your company-building process. Our three-phase process treats team clarity as work that must happen alongside market and product work, not after it.
Use a weekly, evidence-based review
Performance expectations fail when the only review happens after a missed milestone. By then, founders usually argue about effort, intent, and memory. Use a fixed weekly meeting that examines evidence: what was committed, what was delivered, what changed, and what must happen next.
Keep the meeting short enough to repeat every week. Each founder should arrive with an update against their agreed outputs, including customer notes, product progress, hiring status, cash position, or investor activity. “I was busy” is context, not a performance update. The useful question is: what moved, what did not move, and why?
Weekly founder review: Begin with the prior week’s commitments. Mark each as done, delayed, blocked, or no longer relevant. For every delayed item, record the cause, the revised owner, and the new deadline. End by writing no more than three priority commitments for each founder.
Separate a performance gap from a company-level problem. If the team cannot secure interviews because the target segment is wrong, that is a validation issue. If interviews are available but the assigned founder repeatedly does not conduct them, that is an ownership issue. Treating both as the same problem produces poor fixes.
If your team needs an outside structure to turn these conversations into a build plan, Build with us. We work alongside founders across validation, product, fundraising, and go-to-market, with operators embedded in the work.
Measure behaviours that protect execution
Early-stage performance cannot rest only on revenue or fundraising. Those outcomes often depend on timing, customer cycles, and market conditions. Founders should still be accountable for the behaviours that create those outcomes: preparation, response speed, decision quality, customer contact, and honest reporting.
Choose a small set of behavioural standards that fit your stage. A technical founder may need to flag delivery risk before a customer promise is made. A commercial founder may need to log every material customer conversation and bring product feedback into the roadmap discussion. A CEO may need to maintain a current runway view and raise difficult financing issues early.
- Reliability: Does the founder meet commitments or flag risk before the deadline?
- Transparency: Does the founder surface bad news, weak data, and missed assumptions quickly?
- Customer contact: Does the relevant founder keep direct contact with users instead of relying on internal opinions?
- Decision discipline: Does the founder make calls within their role and involve others when the agreement requires it?
- Respect for runway: Does the founder treat time, cash, and hiring capacity as limited resources?
Avoid scoring personality. “More committed,” “more strategic,” or “better leadership energy” gives no one a usable correction. Describe the observable behaviour instead: meetings were missed, pipeline notes were absent, or a product dependency was raised after the deadline. Precision lowers the chance that feedback turns into accusation.
Address mismatches before they become equity conflicts
A missed commitment is not automatic proof that a founder is failing. One miss may come from a bad estimate, a family emergency, a customer delay, or a changing market. A pattern is different. When the same work repeatedly slips, the other founder absorbs the cost through extra hours, lower quality, or delayed fundraising.
Address the issue in three steps. First, state the gap using agreed facts: the deliverable, deadline, result, and effect on the company. Second, ask whether the cause is capability, capacity, motivation, or role design. Third, set a short correction period with a clear output and review date.
Do not renegotiate equity during a heated weekly review. Record the performance issue, agree on the correction plan, and return to equity or role changes only after you have evidence of a persistent mismatch. If the company documents vesting and departure terms from the start, difficult conversations have a clearer path.
Founders often delay this because they fear damaging the relationship. Delay usually does more damage. The founder who feels overburdened starts keeping an internal ledger. The founder receiving no direct feedback assumes the arrangement is acceptable. A direct conversation, held early and tied to written expectations, gives both people a fair chance to fix the work.
When the role itself is wrong, change it. A founder who is strong in product may not be the right owner for enterprise sales. Reassigning responsibility is better than protecting a title while the company loses time.
Make the agreement survive the next stage
Your first founder agreement should fit the company you have now, then change as the company changes. The expectations for two founders validating an idea are different from those for a team with customers, employees, and investors. Review the document at major operating moments: after validation, before a fundraise, after the first senior hire, or when one founder’s role changes materially.
Keep one shared document that records role ownership, current 90-day priorities, decision rights, weekly review notes, and unresolved issues. Your legal founder agreement and cap table should sit beside this operating document, but they serve different purposes. Legal documents define rights. Operating documents define how you work together on Monday morning.
| Stage | What performance should focus on |
|---|---|
| Idea and validation | Customer interviews, problem definition, testable assumptions, founder availability |
| Product development | Scope control, release quality, user feedback, delivery reliability |
| Early go-to-market | Pipeline discipline, customer retention signals, pricing learning, cash control |
| Fundraising and scale | Reporting quality, hiring decisions, investor communication, leadership capacity |
We see the founder relationship as part of the company’s execution system. Nebula is a venture builder in Tamil Nadu, building for India, and our venture building work takes ownership alongside founders from prototype to scale-up. See how we work across the engagement models, then decide where your team needs operating support.
Write the expectations before the next missed deadline forces the conversation. If you want embedded operators to help turn founder roles, milestones, and execution into a working plan, Build with us.
Enjoyed this? Get the next one in your inbox.
Fundraising guides and validation frameworks, every two weeks. No spam.
Frequently asked questions
How often should co-founders review performance expectations?
Review commitments weekly and revisit the full role and decision-rights agreement at major stage changes, such as after validation, before fundraising, or after key hires.
Should co-founder performance expectations affect equity?
Equity should not be renegotiated during a heated performance discussion. Use written vesting and departure terms from the start, document the issue, set a correction period, and make role or equity decisions using evidence.
What should a co-founder performance review include?
Review prior commitments, delivered outputs, delays, blockers, decision needs, and each founder’s next three priority commitments.
Ready to build your startup?
We work with a small number of founders each year — mentorship, fundraising support, and a co-founder network included.
Start a conversation
Talk to the founder directly. We reply within two working days.
Applying to Nebula 1.0? Apply here →