Skip to main content
Foundra Launch

SearchSign in

Co-Founder Roles on Launch Day: Who Does What

Teamwork · 10 min read ·

Splitting launch-day jobs between co-founders: five roles, a simple schedule, how to hand over, how to disagree well and how to look after the partnership.

Illustration: Two hand-drawn coffee mugs, one with a terracotta label 'build', the other 'listen', with a shared timetable between them on cream paper

Launching with a co-founder is a gift. There are two brains, two sets of hands and someone to share the nerves with. It is also a source of avoidable friction. Two people who are each trying to do everything will duplicate work, drop tasks and, in the worst moments, argue in public about who should have replied to a comment.

The remedy is simple and surprisingly rare: decide who does what before the day begins. This guide sets out five roles, a simple schedule and some habits for keeping the partnership healthy under pressure.

Why roles matter

The division of labour, one of the oldest ideas in economics, is that people become more effective when they specialise in particular tasks rather than each doing everything. A launch day is a compressed version of the same lesson. With two people and dozens of tasks, specialisation reduces switching, speeds replies and gives each person a clear sense of what they are responsible for.

Roles also protect the relationship. Many co-founder arguments are not about substance; they are about who was supposed to do something. A clear allocation removes the question.

The five roles

Whether you are two people or five, these jobs need doing. One person can hold more than one role in a small team, but each needs an owner.

1. The voice

Writes and posts the announcements, replies to public comments and keeps the tone consistent. This is the public face of the day. The voice should be someone who writes clearly and stays calm under criticism.

2. The fixer

Watches errors, monitors speed and capacity and ships repairs. The fixer protects the product's behaviour and has authority to roll back a change. Ideally this is whoever knows the code best.

3. The listener

Collects feedback from every channel, groups it, spots patterns and passes the important items to the others. The listener keeps the list of what people said and, later, the list of what changed.

4. The planner

Keeps the schedule, sets reminders for the second announcement, tracks the numbers and notices what is slipping. The planner does not do every task; the planner makes sure none are forgotten.

5. The anchor

Looks after the humans: makes sure everyone eats, takes breaks and gets sleep, and calls a pause when someone is overwhelmed. In a team of two, you take turns.

Write each role on a card with the name of its owner. Put the cards where both of you can see them.

A simple schedule

Use a shared timetable for launch day with three columns: time, what is happening and who owns it. For example:

  • Early morning: the fixer checks the product and page; the voice prepares posts; the planner confirms the schedule.
  • Launch hour: the voice publishes and replies; the fixer watches errors; the listener starts the feedback list.
  • Mid-morning: the voice continues replies; the listener summarises the first themes.
  • Midday: everyone takes a real break, in shifts if need be.
  • Afternoon: the fixer ships a small fix if needed; the listener and planner decide what goes into tomorrow's update.
  • Evening: a short review together: what happened, what we learned, what is next. Then stop.

Adjust to your own rhythm, but keep the review and the break.

Decision rules

The hardest moments of launch day are decisions made fast. Agree the rules beforehand.

  • The role owner decides within their area. If the fixer says roll back, the fixer rolls back, and the others support.
  • Anything that changes a public claim needs both founders' agreement, even if that takes five minutes.
  • Money and legal matters are decided jointly, never in the heat of the moment.
  • If you cannot agree, take the more cautious option and revisit it after the day.
  • No public disagreement. If you disagree about a reply, argue in your private channel, then post one answer.

Having the rules in writing means you do not have to negotiate them while stressed.

Communicating between yourselves

Choose one private channel for internal messages and keep it clean. A few habits help.

  • Short, specific messages. "Sign-up error on Safari. I am on it." not "something seems off".
  • Acknowledge. A thumbs-up is enough to tell the other person you saw it.
  • Hand over explicitly. "I am going for lunch. You have replies until two." Handovers are where things get dropped.
  • Say when you are overwhelmed. The earlier you say it, the easier it is to help.
  • Keep it kind. Tired people are curt. Assume good intent.

Showing roles to users

Users appreciate knowing who they are talking to. On your page and in your replies, let people see each founder's name and area. "Priya looks after support; Dan looks after the code." It helps people ask the right person and shows that the team is organised. Make sure each person is happy with how they are described.

Google's guidance on helpful content asks for clarity about who is behind a page. Naming founders and their areas is an easy way to meet that standard.

Handling the strain

Launch day is intense, and strain can reveal old tensions or create new ones.

  • Expect a wobble. Around mid-afternoon, energy dips and tempers fray. Plan the break for then.
  • Separate the day from the relationship. A sharp word at four in the afternoon is not a verdict on the partnership. Say so, apologise and move on.
  • Debrief kindly. In the evening review, start with what went well. Then discuss what to change, focusing on the process, not on blame.
  • Take time apart afterwards. Both of you should rest before making big decisions.

If disagreements persist, talk about them calmly in a quiet moment. A trusted adviser or mentor can help you work through them. Many partnerships also benefit from a written agreement about roles, decision-making and what happens if things change; take advice from a qualified professional when you draw one up.

Delegation beyond the two of you

If friends or family offer to help, give them small, defined jobs and clear instructions. Delegation, the passing of responsibility for a task to another person, works when the task and the standard are clear. "Test the sign-up on your phone and tell me if anything looks wrong" is a good job. "Help with marketing" is not.

Thank everyone, and tell them what difference they made.

A worked example

Two co-founders launching a recipe-sharing app meet the evening before. They agree: Maya is the voice and the listener; Jon is the fixer and the planner; each takes the anchor role for the other. They write the roles on cards and stick them above their desks. They agree that Maya decides what to say publicly, Jon decides whether to roll back, and anything touching claims or money needs both.

On launch day Jon finds a slow page and fixes it within an hour. Maya replies to comments and notes that three people mention the same unclear button. At midday they take an hour apart. At three they have a sharp exchange about whether to add a feature that people ask for; they remember the rule, defer the decision and agree to talk in the evening. In the evening review they list what went well, what they learned and what to change. They decide to add the feature the following week, and they go to bed on time.

Nothing about the day was easy, but nothing was chaotic.

When roles are unequal or unclear

Sometimes one founder carries more of the work. Talk about it before launch rather than resenting it during. Ask each other: what am I best at, what do I dread, and where do I need help? Swap tasks where the answers allow. If one of you has more time, use it, but make sure credit and decisions stay balanced. Roles are about fit, not hierarchy.

If you are not sure who should lead a particular area, try the role for a week and review. A short experiment settles most disagreements better than a long discussion.

Questions co-founders ask

What if one of us is travelling on launch day? Plan around it. Time zones can be an advantage: someone awake in another part of the world can cover replies while the other sleeps. Agree handover times and keep the shared document up to date.

Should we both reply to comments? Better to let one person lead and the other support. Two voices in a thread can contradict each other. If you must both reply, agree on the key points first.

How do we share credit? Be generous in public and specific in private. Name each other's contributions in your posts and in thank-you notes.

What if we disagree about launching at all? Do not launch while divided. Talk through the specific fears, find what would settle each, and either fix those things or delay. A launch is much harder when one person is silently opposed.

How do we keep friendships alive? Remember why you started working together. Take one evening off together after the launch, with no talk of the product.

A short pre-launch conversation

Sit down for thirty minutes with these questions. What is each of us most worried about? What does each of us want from the day? What will each of us do if something goes badly wrong? What is our rule for stopping and resting? Write the answers on one sheet. It is surprising how often a few honest sentences prevent a day of tension.

Summary

Co-founders launch better when roles are clear: a voice, a fixer, a listener, a planner and an anchor. Write the roles down, share a schedule with owners and agree decision rules before the day. Communicate briefly and kindly, show roles to users, plan for the afternoon wobble and debrief with care. A clear division of labour does not diminish the partnership; it protects it.

Questions and answers

Should co-founders split roles on launch day?
Yes. Clear roles reduce duplicated work, dropped tasks and arguments in the middle of the day.
What if we both want to do the same thing?
Decide in advance who leads and who supports each task, and agree that the lead makes the call during the day.
How do we handle disagreements under pressure?
Agree a rule beforehand, such as the role owner decides, and revisit the decision after the day.
Do we need to tell users who is who?
It helps. Show each founder's name and role so users know whom to contact.

Sources

Help centre