The Weekly Co-Founder Sync: Agenda, Questions, and What It Means When It Stops Happening

This article is part of our guide to co-founder conflict.

Every piece of advice about founding partnerships eventually arrives at the same recommendation: talk to each other regularly about the partnership itself, not just the company. Investors say it, coaches say it, founders who have been through a breakup say it with some feeling. Almost nobody says what the conversation should contain, which is why most founding teams try it twice, run out of things to say by the third week, and quietly let it lapse.

This is the missing part: what to put in the hour, what to ask, and what the meeting is telling you when it starts to disappear from the calendar.

Short answer: what is a weekly co-founder sync?

A weekly co-founder sync is a standing hour, separate from every operating meeting, in which the founders talk about the partnership rather than the business: which decisions got made and which got reopened, what each person is carrying, what is not being said, and what needs to change between the two of you before next week. It is not a status meeting, a planning session or a one-on-one in the management sense. It has its own agenda, its own rules, and one deliverable: a single agreement about how the two of you work together, written down and checked the following week.

Start it before you need it. A sync installed while the partnership is calm is a maintenance habit. One installed after a bad quarter is a negotiation, and both founders know it.

Why the operating cadence does not cover it

Founding teams usually believe they talk constantly, and they do. The product review, the pipeline call, the hiring debrief, the investor update, the late message about tomorrow's demo. None of those conversations has room for the question of whether the two of you are still deciding things well, because each has an agenda that rewards whoever has the most to report and penalises anyone who raises something that is not on it.

The partnership also has no owner. The company has a CEO; revenue has someone whose job it is; the relationship between the founders is everyone's responsibility and therefore nobody's. Problems with an owner get a meeting. Problems without one get explained away until they are large enough to force one, by which point the conversation has to cover a year of material in an hour and goes badly.

The sync gives the partnership an owner, a slot and a method. That is the whole mechanism. It works for the same reason a monthly close works: the discipline is in the recurrence, not in any single instance.

The rules

Six rules, all of them about protecting the hour from the company.

1. Same slot every week. Not "sometime Thursday". A fixed time that both calendars treat as immovable. Moving it is allowed; skipping it twice in a row is not, for reasons covered below.
2. Both founders, nobody else. No chief of staff, no advisor, no note-taker. The presence of a third person changes what gets said.
3. Out of the operating space. A walk, a different room, a call from home. Holding it at the desk where the company happens makes it a company meeting.
4. No laptops, one shared document. Phones face down. The only screen is the log where the week's agreement gets written.
5. Operating items get parked, not discussed. They go on a list with an owner and a meeting. If a business decision cannot wait an hour, it was never going to wait for the sync anyway.
6. It ends with one agreement. Not three. One thing that changes between the two of you, specific enough to check.

Forty-five minutes to an hour. Shorter and the fourth part of the agenda gets skipped; longer and it becomes an offsite.

The agenda: six parts in one hour

This is the structure the whole article rests on. Timings are a guide, not a stopwatch.

1. Park the operating items (5 minutes)

Both of you say what is on your mind about the business. Each item gets a line on the parking list, an owner and a meeting where it belongs. Then the list goes away. The point of doing this first is that neither founder can concentrate on the partnership while holding an unmentioned product problem.

2. Review the week's decisions (10 minutes)

Walk through every decision of any size made since the last sync. For each one: whose call was it, was it actually closed, and has either of you reopened it privately since? The private reopening is the one to catch. A decision that is formally made and informally contested is a deadlock in its early form, and the fix is cheap at this stage: name whose domain it was, or agree that it has no owner yet and give it one.

3. Check the load (10 minutes)

Each founder describes what they are carrying this week, inside the company and outside it, and estimates how much of it the other can see. Hours, travel, a hiring round, a sick parent, a partner who has had enough. The aim is accuracy rather than sympathy. The contribution ledger that poisons so many partnerships is built from weeks in which one founder's load was invisible to the other, and this part of the agenda is the cheapest way to keep both ledgers public.

4. Say the unsaid (15 minutes)

The same question, asked of each founder in turn: is there anything you have been not saying to me? The listener does not interrupt, correct or fix. They can ask one clarifying question. That is all.

This is the part most founding teams skip, and the part the sync exists for. The avoided subject in a founding partnership is nearly always something small enough to raise in week one and large enough to end the partnership by month six. Asking the question every week lowers the cost of the answer, because the answer stops being an event.

If the honest answer is "nothing" for three weeks in a row while the room feels tense, the question is being answered politely rather than truthfully, and that is worth saying out loud too.

5. Repair and appreciate (5 minutes)

Each founder names one thing the other did that week that helped, and one moment that needs repairing: a sharp message, a decision taken without the courtesy of a heads-up, a joke that landed badly. The repair happens in the room. Couples research is clear that stable pairs are not the ones who avoid friction but the ones who repair it quickly, and nothing in that finding depends on the pair being married.

6. Leave with one agreement (5 minutes)

What changes between the two of you before the next sync? It should be concrete enough to verify: "You get the deck before the board call, not during it." "I stop answering for you in the product review." "We decide the hire together by Friday." It goes in the log. The next sync opens by checking whether it happened.

The questions: weekly, monthly, quarterly

The six parts above are the skeleton. These are the questions that fill it, grouped by how often they earn their place.

Every week

• Which decision this week did you disagree with and not say so?
• What did I do this week that made your job harder?
• Where did you cover for me, and did I notice?
• What are you dreading next week?
• What would you want me to know that you have not told me?

Once a month, replacing part four for that week:

• Are our roles still what we agreed, or have they drifted? Where?
• Is there a person on the team one of us is managing around the other?
• What have you told an investor, advisor or your partner about us that you have not told me?
• If you could change one thing about how we decide, what would it be?

Once a quarter, in a longer session:

• Are we still building the same company, on the same timeline, for the same reason?
• Does the equity split still describe the contribution? If not, this is the conversation, and the sync is where it gets scheduled rather than where it gets held.
• What would make either of us want to leave in the next year?
• Read the written agreement together. What in it is no longer true?

Once a year: the question First Round Review's essay on co-founder relationships recommends revisiting annually, which is whether the two of you still share a vision for what this is and where it goes. If that question has not been asked since the pitch deck, the answer has probably changed for at least one of you.

What to do with the answers

Keep a log. One line per sync: the date, the agreement, and whether last week's agreement held. Nothing more elaborate, because an elaborate log stops being kept.

After four weeks, read it back. Patterns show up in the log that are invisible week to week: the same founder always carrying more, the same decision reopened three times under different names, an agreement that keeps being made and never kept. A subject that appears in part four for three consecutive weeks is no longer a sync item. It is a project, and it needs its own time, possibly its own third person in the room.

The log is also the honest record when memory diverges, which it will. Two founders remembering the same quarter differently is normal. Two founders with no record of it is how arguments acquire a history going back years.

When the sync stops happening

The sync is almost always the first meeting a founding team cancels, because it is the only one without an external consequence for skipping it. How it gets cancelled is itself information, and it is worth reading carefully.

Both of you cancel it because things are fine. Usually harmless, provided it comes back within a fortnight. A sync abandoned during a good quarter is simply not there when the quarter turns, and it is far harder to reinstate under pressure than to keep running when there is little to say.

One of you cancels it, repeatedly, with good reasons. Each reason is real. The pattern is avoidance. Something is in part four that the canceller does not want to be asked about, and the sync has become the one hour in the week in which the question cannot be dodged. Do not raise the cancellations as an accusation. Raise them as a pattern: "We have moved this four times in six weeks, and I think there is a reason."

It happens, but it has turned into a status meeting. The operating items stopped getting parked, part four gets a shrug, the hour fills with pipeline. The partnership is being managed around inside the meeting built to maintain it. This is the quietest version and the most common; the fix is to run the agenda strictly for a month and see what surfaces.

It happens, and it is tense every single week. Good news, in a sense. You have found the subject. The sync has done its job by making the thing visible, and the two of you are now having the same difficult conversation weekly without resolving it. That is the moment to bring in someone whose only interest is the working relationship, because a conversation that has been attempted ten times by the same two people rarely improves on the eleventh.

It has never been held at all, despite both of you agreeing it was a good idea. That is warning sign number four, and it belongs on your list rather than on your calendar's conscience.

Variations: remote, three founders, married co-founders, pre-launch

Remote and across time zones. The sync works on a call, with two adjustments: cameras on, and the shared log open on both screens so the agreement is written in front of both of you. Rotate who takes the awkward hour if the time zones are far apart; a sync that is always 7am for the same founder becomes that founder's chore.

Three founders. Run the full hour with all three, and add a rotating pair conversation each week so that every pair gets time without the third. A founding trio without pair time develops a standing two-against-one, and the one is not always the same person.

Married co-founders. Hold the sync at the office, not at home, and keep it strictly about the working partnership. Couples who run a company together need two different conversations, and the sync should be the business one. The other one is covered here.

Pre-launch. Start now, while there is nothing to decide. The first few syncs will feel thin. Use them to work through the questions that founding teams usually skip, and to find out whether the two of you can hold a weekly hour before there is a payroll depending on it.

Five ways founding teams ruin it

1. Running it as a performance review. Part three is about load, not output. The moment one founder starts grading the other's week, the other stops reporting honestly.
2. Using it to relitigate. Part two reviews whether decisions closed, not whether they were right. A decision that was wrong and closed is a lesson. A decision reopened every week is a deadlock.
3. Skipping the repair. Part five feels optional and is not. Friction that goes unrepaired for a week compounds; friction repaired in the room is simply gone.
4. Scheduling it where it will die. Friday at five, Monday at eight, the slot after the board meeting. Pick an hour neither of you resents.
5. Doing it in writing. A weekly written update to each other is useful and is a different thing. Tone, pauses and what gets said after "nothing, really" do not survive Slack.

FAQ: the weekly co-founder sync

How often should co-founders meet one-on-one?

Weekly, for the partnership conversation specifically. Daily contact about the business is not a substitute, because it never has room for the questions in part four. Fortnightly is the minimum that still catches problems while they are small; monthly turns every sync into a catch-up on a month of unsaid things.

How long should a co-founder sync be?

Forty-five to sixty minutes. The six-part agenda needs the full hour when there is something to say and finishes early when there is not, and finishing early is fine. Routinely running over an hour means operating items are not being parked.

What should co-founders talk about in a weekly check-in?

Decisions, load, the unsaid, repair, and one agreement. Not the product, the pipeline or the hire; those have their own meetings. The test for any item is whether it is about the company or about the two of you running it.

Is a co-founder sync the same as a founder one-on-one or a leadership meeting?

No. A leadership meeting runs the company, and a management one-on-one runs a reporting line. The sync runs the partnership, which has no reporting line and no other meeting. Founding teams that already hold a founders-only operating meeting still need the sync, held separately, because the operating agenda crowds out everything else.

What if my co-founder will not do it?

Ask for four weeks, not forever, with the agenda shared in advance so it does not look like an ambush. If the answer is still no, the refusal is itself the subject: a founder who will not spend an hour a week on the partnership is telling you something about how they rate it, and that is worth raising directly rather than inferring.

What if the sync just turns into a fight every week?

Then it is working, and the two of you have outgrown it. The sync is a maintenance tool. A subject that produces the same fight weekly needs a different setting, with someone in the room who is not party to it. Keep the sync running for everything else and move that one subject out of it.

Do we still need it when everything is going well?

Especially then. Good quarters are when the sync is cheapest to hold and when the habit gets built. The quarter that goes badly is not the time to be learning how to talk to each other.

Should a third person facilitate it?

Not routinely. A facilitated sync is a coaching session, which is a different and more expensive tool for a different stage. Bring someone in when the sync has surfaced a subject the two of you cannot move alone, and keep the weekly hour as your own.

Next step

If the two of you have never held this hour, the first one is the hardest, and it is mostly hard because of what gets said in part four.

Aether Practice offers co-founder sessions for founding teams in San Francisco, New York City and Norway: the same conversation, with someone in the room whose only job is to make sure both of you say the true thing and the partnership survives hearing it. If you want to rehearse what you are going to say in part four before you say it, AET01 Conflict gives you a counterpart that will not simply agree.

Keep reading in this cluster: The complete guide to co-founder conflict · Twelve warning signs · The co-founder agreement questions · The 50/50 deadlock · Mediation, coaching or a lawyer

Research and further reading

• Lockett, R. Renew Your Co-Founder Vows, and Other Tactics for Strengthening the Most Important Relationship in Your Startup. First Round Review. Regular co-founder time, an annual vision conversation and quarterly goal reviews, from an executive coach who works with founding teams.
• Graham, P. (2006). The 18 Mistakes That Kill Startups. paulgraham.com. Y Combinator's early statement that fights between founders are common, and that the time to act on doubts about a partnership is before it is under load.
• Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383. Why a recurring, protected setting changes what people are willing to say.
• Jehn, K. A. (1995). A multimethod examination of the benefits and detriments of intragroup conflict. Administrative Science Quarterly, 40(2), 256–282. The distinction between disagreement about the work and conflict between the people, which part two of the agenda is designed to keep apart.
• Gottman, J. M. & Silver, N. (1999). The Seven Principles for Making Marriage Work. Crown. Repair attempts and turning toward, the research behind part five.
• Rosenberg, M. B. (2003). Nonviolent Communication: A Language of Life. PuddleDancer Press. A way of phrasing the unsaid as an observation and a need rather than a verdict.
• Shaikh, O., Chai, V., Gelfand, M., Yang, D. & Bernstein, M. S. (2024). Rehearsal: Simulating conflict to teach conflict resolution. Proceedings of the CHI Conference on Human Factors in Computing Systems. Evidence that practising a difficult conversation beforehand changes how it goes.
• Also read: Co-founder coaching in San Francisco and New York · When one co-founder stops pulling their weight · Co-founder coaching

Last updated: October 2026.