Across the first ten hires at twenty top B2B startups, more than 40 percent had a designer in one of the first three seats, either hired directly or as a co-founder. Almost none had hired a salesperson that early, according to Lenny's Newsletter's analysis of early hiring patterns at leading B2B companies. That single data point contradicts the assumption most founders carry into their first non-engineering hire: that it has to be someone who sells.
What "get users" actually means
Paul Graham's rule for the earliest stage is narrower than founders tend to remember it. He wrote that at the start, founders should only hire people who are either going to write code or go out and get users, paid in equity rather than salary. The rule does not say hire a salesperson. It says get users, and a lot of early, user-facing work looks nothing like a quota-carrying sales role. It looks like a designer shipping the interface people actually touch, or a generalist closing the loop between what users ask for and what gets built next.
The founder has to prove the sale first
SaaStr founder Jason Lemkin puts a number on the delay. He has said it is the job of the founder to sign up the first 10 to 20 customers before the company brings on a dedicated sales hire. That is not a payroll argument. A founder who has not closed 10 to 20 deals personally has no process to hand off: no objection list, no pricing data, nothing for a new hire to execute against.
The companies most often cited as sales-hiring case studies confirm the sequence. Figma brought on Kyle Parrish as its first-ever sales hire only after the company reached $2 million in ARR, and Parrish went on to build the sales organization that carried Figma to roughly $950 million in ARR by the time it filed to go public, according to First Round Review. The same account traces Dropbox's first enterprise rep, Sam Taylor, who later ran sales at Quip and Loom, and notes Stripe's early sales hires included Eric Lasker. In each case, the hire arrived to scale a motion the founders had already proven, not to invent one.
A different kind of first hire: the domain check
Not every early non-engineering hire is about revenue or design. Vanta's early hires included a compliance subject-matter expert, and the founders were direct about why:
"We could build, but we wanted the check on are we building the right thing, given our background wasn't in the space. The worst case would have been promising to get a company secure and compliant and then failing to do so." (Lenny's Newsletter)
That is a third category on its own. Not a builder, not a seller, but a check against a gap in the founders' own knowledge, in a market where being wrong is not a design flaw but a liability.
The question that actually decides it
All four data points answer the same question three different ways: what can the founders not do themselves, right now, that will break the company if left undone? For most technical founders, that gap sits in the product surface, which is why designers show up in the first three hires far more often than reps. For founders selling into a market they already understand, the gap does not open until the founder has personally closed a couple dozen deals, per Lemkin's benchmark, at which point the first sales hire's job is to scale a motion, not discover one, as the Figma and Dropbox histories show. For founders building in a regulated or unfamiliar domain, the gap is neither. It is the risk of confidently building the wrong thing, which is what Vanta hired against.
This week, name the one function where you personally have the least credibility to make the call: the interface, the pitch, or the domain rules. Hire only that seat first, and weight the offer toward equity over salary until the role has proven itself, in keeping with Graham's original instinct for early hires.