Which of us is CEO — and do we need a GTM co-founder?

You and your co-founder are both engineers, and neither of you has said out loud which one is chief executive. Settle that before you settle anything about hiring. The person holding that title owns who the buyer is, what the buyer pays, and what the product must touch to deploy, and all three get decided in the design, months before anyone could be hired to decide them.

Name the CEO first.

You leave the title open for good reasons. The work is shared, the friendship is older than the company, and naming one of you feels like ranking two people who are equal. So it floats. It floats through the first buyer meetings, the first hires, and the first pitch, and each of those rooms decides it for you, badly.

The test is plain. It is in the deck. It is on both of your profiles. And when a stranger asks which of you runs the company, neither of you looks at the other first. We have watched founding teams answer that question in unison and we have watched them answer it two beats apart, and the two beats told us more than the answer did. An all-engineer team is not a mark against you — we back technical founders who saw the problem first. A team that has not decided is a different thing, and every investor you meet will read it the same way: not two equals, but one unresolved argument.

The CEO job is the commercial job.

You are probably picturing the chief executive as the founder who absorbs the parts neither of you wants — the incorporation, the bank account, the investor updates, the recruiting. That is administration, and it is the smallest part of the job.

The chief executive is the company's commercial mind. Who is the buyer. What obligation does the product discharge. What do they pay, and on what metric. What must the product touch in order to deploy. Whether the story survives contact with someone who did not build it. If your team hands the title to whoever minds it least, you have handed those decisions to nobody, and nobody is who will have made them by the time you notice.

Commercial decisions are made in the design.

You make the decisions that determine whether the product can be sold while you are still choosing what to build. Commercial work sounds like selling, and before there is a product it is something else entirely.

It is deciding what the buyer pays and on what metric, because the metric is nearly impossible to change at renewal. It is deciding what the product must touch in order to deploy, because an installation the buyer will not approve is the objection that arrives last, after you have already won on the technology. Every one of those is a commercial decision, and every one gets made in the design. The sales leader you hire eighteen months from now cannot go back and choose again. They inherit your answers and are measured on them.

Pick the founder who is better in the room.

You choose on one axis, and it is not the one that feels fair. Not the founder with the idea. Not the one who is more senior, wrote more of the code, or brought the other one in. Pick the one who is better in a room with a buyer: who takes an objection without retreating into architecture, who can sit in a silence, who can ask for something and hear no without spending the next ten minutes proving the no was wrong.

That is a ranking between two people who are friends, which is exactly why teams avoid making it. The avoidance has a shape and everyone in the room can see it — the shared title, both names on every email, the pause before either of you answers. If neither of you is better in that room, you have learned something more useful than a title. One of you has to become that person starting this month, and the other one has to say out loud that they are not it.

Restraint is the hard part.

You can learn the sales seat, and founder-led selling carries a company further than the conventional advice suggests. What a technical founder brings that no hired seller can is credibility in the technical room and the ability to record a no without flinching, because you are not paid on the yes.

What you have to learn is smaller than it looks. Ask for something the buyer can refuse. Leave every conversation with a second name. Do not demo until they have named the obligation. The hard part is restraint. This market is small and talkative, and an overclaim from a founder travels the way a discount does.

A co-founder is not a first sales hire.

You will reach for a senior seller with a founder title, and those are not the same job. A co-founder owns the question of whether anyone wants the product. A sales hire converts demand that has already been proven. Bringing a go-to-market co-founder in late means a founder-sized grant for someone who did not choose the problem, and it works only if they would have chosen it.

The test is short. They arrive with the buyer's words, not with a network. They have sold to your buyer, not to security leaders in general. They can name the budget line. They accept founder vesting with a cliff. And they join before the first sales hire, never after the first failure.

A founder in the sales seat works.

You take the seat back, and that is not a failure state. When a first sales-leader hire fails, the offer that follows is a president or a chief operating officer to sit over the problem. In our portfolio a founder personally taking the sales seat is an interim answer that worked, and a title layered over the problem was not. If one failed hire returns you to founder-led selling, the honest reading is that the sale was not yet transferable to a stranger. Fix the motion yourself, and leave the seat when it repeats without you — not before.