A cofounder weekly check-in is a protected, recurring meeting where you and your cofounder align on the numbers, surface tension, make decisions, and check each other's capacity. Run it the same time every week. Cover four things in order: metrics, tensions, decisions and commitments, capacity. Keep it to sixty to ninety minutes. Document what you agree.
Why a weekly cadence beats talking all day
You already talk to your cofounder constantly. Slack, hallway, late-night calls. That is operational chatter. It is not alignment.
The two are different. Chatter moves tasks. A check-in moves the relationship. It is the one slot where you step back from the work and look at whether you are still building the same company, still trust each other, still carrying a fair share.
Skip it and relationship debt compounds quietly. Small resentments, unspoken disagreements, decisions nobody actually made. By the time it surfaces, it is a rupture instead of a note. A structured founder sync exists to resolve that debt before it grows (Scale Yourself).
The mechanics are flexible. The existence of the meeting is not. Day, length, venue, and format are all open season. The one thing that should never move is the protected time in your calendar (Scale Yourself). Consistency is the whole point of a cadence (Atlassian).
How long and how often
Weekly is the default. Sixty to ninety minutes. Pick a slot that is out of the operational rush, Friday afternoon or a quiet morning, so you can actually think.
Adjust for the season. During fundraising, when the company is moving fast and you are apart more, cut to twenty minutes a few times a week instead of one long block (Scale Yourself). More touchpoints, shorter each. The cadence flexes; it does not disappear.
This is one of the highest-leverage meetings you run. Treat it that way. No phones, no half-attention, no letting it slide when the week gets busy. The busy weeks are exactly when you need it.
The check-in agenda
Run the same four sections every week. Order matters. Put the hard conversations early, before energy drains and the clock runs out. Keep a shared agenda open all week so either of you can drop items in as they come up, so nothing gets lost (Michael Wolfe, Point Nine).
| # | Section | What you cover | Time |
|---|---|---|---|
| 1 | Metrics | The two or three numbers that define this week. What moved, what stalled, what it means. | 15 min |
| 2 | Tensions | Anything off between you. Feedback in both directions. Name the hard thing directly. | 20 min |
| 3 | Decisions & commitments | Open calls that need a final say. Who owns each. Then document the agreements. | 20 min |
| 4 | Capacity | Honest read on energy and load. Where each of you is stretched. What to hand off. | 15 min |
A few notes on each.
Metrics
Start with the scoreboard. Not a status dump of every task, the handful of numbers that tell you whether the company is working. Keep it tight. This section grounds everything after it in reality.
Tensions
This is the section most teams skip, which is why most teams need it most. Feedback, positive and negative, should flow in every direction, and difficult topics get surfaced here on purpose (Scale Yourself). If nothing is ever raised, that is not harmony. That is avoidance.
Name the specific thing. "You committed to the investor deck and it slipped twice" beats "I feel like you're not pulling weight." Concrete, not characterological. If a tension is bigger than the meeting, do not force-resolve it here. Flag it and work through it properly with a real conflict resolution approach.
Decisions and commitments
Every week produces calls that got made in passing or not at all. This is where you make them cleanly. For each open decision, agree who has the final say. Ambiguity about decision-making authority is one of the most reliable sources of founder conflict.
Then write it down. Document the agreements so a decision is a shared fact, not two different memories. Keeping your commitments current is what turns a good conversation into an operating system instead of a nice chat. This is where a running record of commitments earns its keep.
Capacity
End with the human read. Not tasks, load. How stretched is each of you. What is quietly slipping because someone is underwater. Founder burnout rarely announces itself; it shows up as missed check-ins and short tempers. Ask directly, answer honestly.
Keep it current
The check-in works because it repeats. One good meeting changes nothing. Fifty in a row change how you operate together.
Tie it back to the structure you have already built. Your roles and responsibilities tell you who owns what, so metrics and commitments have clear owners. Your founder operating agreement sets the ground rules the check-in enforces week to week. The meeting is where those documents stay alive instead of gathering dust after month one.
Assign owners and due dates to every action item, and track them into the next week (Michael Wolfe, Point Nine). Open the next check-in by reviewing last week's commitments. Did they happen? If not, why? That single habit closes the loop between talking and doing.
A partnership does not drift apart in one bad week. It drifts in a hundred skipped conversations. The weekly check-in is how you catch the drift while it is still small, name it, and correct course together. Protect the slot. Run the agenda. Keep it current.
Frequently asked questions
- How long should a cofounder weekly check-in be?
- Sixty to ninety minutes once a week is the common range. During fundraising, some teams cut to twenty minutes a few times a week instead. The duration is flexible. The protected slot in the calendar is not.
- What should a cofounder check-in cover?
- Four things: the metrics that matter this week, any tension between you, the decisions and commitments you are making, and each person's capacity. Cover them in that order so the hard conversations do not get squeezed out at the end.
- How often should cofounders meet formally?
- Weekly is the default cadence. The exact day and length can move. What should never move is the existence of a regular, consistent, protected time to align and surface what is off.
- What is the difference between a check-in and a normal standup?
- A standup covers tasks and status. A check-in covers the relationship: strategy alignment, feedback in both directions, and the trust between founders. It is where you name the hard thing before it becomes relationship debt.
- Do we need a check-in if we talk all day already?
- Yes. Talking all day is operational chatter. A check-in is protected time to surface tensions and document the agreements you keep skipping past. Constant contact is not the same as alignment.
