Part IThe Story
Everyone Below the Accent
The trouble started with an accent mark. On a Friday afternoon in mid-2019, Rippling sent a routine payroll run to its bank. One customer's name, French in origin, carried an accent aigu, the small slanted stroke over the e in café and cliché. The software that translated Rippling's records into the bank's format had never been taught that character. When it reached that name, it did not flag the record and skip it. It stopped processing payments entirely.
"Everyone who was above the name with that character on the list got paid," Matt MacInnis, then Rippling's chief operating officer, recalled in an interview in late 2023. "Everyone below didn't."
The support queue filled first: fifty inquiries from people who had not been paid, and the number kept climbing. The code fix was simple. Most of the affected companies agreed to wait until Monday. A few did not, and one of them was a trucking company. When MacInnis told its CEO that his employees would be paid after the weekend, the line went silent. Then the man said, "This is a big deal." Some of his workers had already missed one or two mortgage payments. A third would cost them their houses.
On a Friday, the only dependable way to get money to those people was Western Union. So Parker Conrad, MacInnis, and a few others withdrew as much cash as they could from their own bank accounts and went to a Western Union kiosk inside a CVS drugstore in San Francisco. There, a company that sold automated payroll software paid a trucking company's employees by hand, with its executives' personal money. Rippling had about 150 employees. The trucking company is still a customer.
Rippling now has a written set of principles for its leaders. Most of it looks like any other company's: leaders "go and see" problems in person, and they set "maximally ambitious goals." One line stands out. Rippling leaders go to Western Union.
That line matters more because of who wrote it. Three years before the CVS trip, Conrad had become Silicon Valley's best-known cautionary tale. He was the founder of the fastest-growing software company of its moment, and he had been removed over compliance failures in a business, health insurance and payroll, where those failures mean real people go without coverage or pay. Before that, he had spent seven years at a startup that was always, in his words, "a month or two away from missing payroll." Few people in technology had spent more time worrying about the date a paycheck clears. Few had been punished more publicly for how they ran a back office. By the time he stood at the kiosk, he had spent most of his adult life on the specific problem of making sure people get paid.
Rippling would later be valued at $16.8 billion, would pass roughly a billion dollars in annual revenue, and would make its founder a billionaire. It would also give him a way to argue back. The rest of this profile keeps returning to that Friday, because Conrad's career is largely a series of attempts to control what happens to the names below the accent mark.
By the Numbers
The Second Attempt
$16.8BRippling valuation after its $450M Series G, May 2025
$4.5BPeak Zenefits valuation, 2015, before it was halved
12 hrsTime to secure a $500M term sheet as Silicon Valley Bank failed
~$1BRippling annual revenue, mid-2026
7 yrsTime spent at Wikinvest/SigFig, pivoting roughly every six months
6 wksGap between resigning from Zenefits and starting Rippling
~22%Conrad's estimated stake in Rippling, 2022
Seventy Hours a Week at Something Else
His background is easy to state, and it explains less than it seems to. Parker Rouse Conrad was raised on Manhattan's Upper East Side. His father, Winthrop B. Conrad Jr., became a senior partner at Davis Polk & Wardwell, a white-shoe law firm. His mother, Ellen Rouse Conrad, founded an environmental nonprofit called the Bedford 2020 Coalition. Each morning he crossed the park to the Collegiate School on the Upper West Side, one of the oldest and most selective boys' schools in the country. Nothing in that upbringing pointed toward an underdog.
Two facts from his high school years point in opposite directions. His grades, he has said more than once, were mediocre. He also spent close to two years in a neuroscience lab studying the neurobiology of sea snails, and the project placed third nationally in the Westinghouse Science Talent Search, which came with a $20,000 prize. On March 9, 1998, The New York Times ran a story under the headline "3 New Yorkers Make Top 10 in Science Competition," and he was one of the three. Even as a teenager, he worked this way. He did little in the things he was required to do and a great deal in the one thing he had chosen.
The award helped get him into Harvard, where he started in the fall of 1998. He did not throw himself into chemistry. He threw himself into The Harvard Crimson.
"I was spending all my time at the Crimson, like 70 hours a week," he told Business Insider in 2015, "and I didn't go to class for like a year." He became managing editor, one of the paper's top jobs, and at about the same time he failed out of the college. "I had to leave Harvard, really halfway through my tenure as the Crimson managing editor. It was this incredibly humiliating and shocking experience."
He spent the year away working at the Arkansas Democrat-Gazette, a long way from Davis Polk. Then he went back to Cambridge and finished, graduating in 2003 with an A.B. in chemistry.
This period matters because it shows a pattern that holds for the next two decades. Conrad gives total attention to whatever has captured him and pays the cost somewhere else. At the Crimson, the cost was his transcript. At Zenefits, it would be compliance. At Rippling, it is what people who have worked with him describe as an exhausting closeness to the details, which he has turned into a management philosophy and which the industry later called "founder mode."
The newspaper years show up in his business life in another way. Conrad trained as a newsman, and he would later lose the most important public fight of his career to someone who, by his own description, writes far better than he does. A former managing editor of the Crimson found himself unable to get his own version into print. He would eventually stop trying to win the argument in prose and try to win it with a company. That comes later.
A Better Denture
By the mid-2000s, his life looked settled. He was a product manager at Amgen, the biotech company, in Southern California. He lived two blocks from the beach in Santa Monica with his girlfriend, Alexandra MacRae, whom he had first met at summer camp in middle school and then found again in college. He commuted along the Pacific Coast Highway and was getting what he called "lots of atta-boys" at work. "I felt like I was a big star in the company," he said later. "I was very, very junior, but felt like I was moving up and getting lots of attention."
Somewhere in those years, shortly after college, he was diagnosed with testicular cancer at 24. He was treated and declared clear. He rarely spends much time on it in interviews, but the experience gave him a patient's view of the American health insurance system, and that later became one of the inputs for Zenefits.
What finally pushed him out of Amgen was arithmetic. "At the company I was working at," he told Garry Tan years later, "you had all these different levels that you needed to move up in your career, and you had to spend two years here and two years there. At a certain point, I realized that, if you added up all the time it would take to get anywhere in your career, I was like, I'm gonna be dead before I accomplish anything." Coming from someone who had recently been treated for cancer, the line carries more weight than a joke about corporate ladders.
Around then, his freshman-year roommate called. Mike Sha had day-traded with Conrad out of their dorm room and wanted to start a company. In Conrad's telling, they then did "the absolute worst thing that you can do to start a startup": they decided to start a company first and went looking for an idea afterward. They chose a wiki for stock research. Conrad quit Amgen, left Los Angeles, and moved north. Wikinvest launched in San Francisco in 2007.
At first they had no salaries and no apartment. Sha's grandparents owned an empty unit at Rossmoor, a retirement community in Walnut Creek, so the two founders lived there rent-free. The community did not allow residents under 65. "We were sneaking in and out each time," Conrad said. "We lived there for about six months. It was by far the worst six months of my life. There was a store outside of Rossmoor that was literally called 'A Better Denture' right outside the gate." His summary: "It's a funny story now — but I sort of felt then like my life fell off a cliff."
The six months turned into seven years. Wikinvest pivoted roughly every six months while it searched for something people wanted. In 2009, in the middle of the financial crisis, Conrad pitched about seventy-five investors; in another telling he puts the figure at seventy. Almost all of them said no. They eventually raised a $2.5 million seed round at a $7.5 million valuation, on the strength of a pitch deck and no working product, and stretched the money as far as it would go. Garry Tan, later president of Y Combinator, remembers almost renting space from them in their South of Market basement office, "this tiny little hole in the corner of the basement," in a building that has since become a restaurant.
"We were constantly a month or two away from missing payroll," Conrad said.
Two details from this period recur later. The first is that he came away deeply cynical about venture capital. He watched investors chase a new theme every six months (social, local, mobile, and so on) while real software took years to build. The second is smaller. One of the jobs that fell to him was administrative, and he hated it. "I am an unusually resentful of the sort of busy work, administrative work," he said on a 2020 podcast. "It's why I was so resentful of having to fax in insurance applications at my first company."
By 2012, Wikinvest had become SigFig, and the two founders had fallen out. Fortune later put it plainly: Conrad "was pushed out of his previous startup, SigFig, by his own co-founder." SigFig survived and now sells back-office financial software to banks. Conrad was 32, out of a company he had co-founded, holding about $20,000 in savings and a strong grudge against fax machines.
The Sucking Sound
What came next happened quickly. Conrad taught himself Python. He recruited Laks Srini, an engineer from SigFig, as his co-founder. He applied to Y Combinator with a video that ran two minutes and thirty-seven seconds, which later circulated as a model application. He has given two reasons for joining YC. One was the small check, which he hoped would keep him away from the investors who had burned him. The other, which he calls the real one, was "the intensity of the program and the how much it sets the company up for success by just getting you in this groove of like really delivering and executing and a lot of urgency in the business."
Paul Graham pushed them to ship, and they launched in three weeks, ahead of competitors. Conrad describes the market response as a kind of suction: the product was pulled out of them faster than they could build it. Zenefits launched in September 2012 and was incorporated in January 2013. The Affordable Care Act was arriving, small businesses were trying to understand it, and Conrad's own time as a patient had shown him how little anyone understood about coverage.
The business model was clever and, as it turned out, fragile. Zenefits gave small businesses its HR software for free: onboarding, payroll connections, benefits administration, the paperwork Conrad had resented at Wikinvest. It made money when those companies bought health insurance through the platform, collecting the broker's commission that would otherwise go to a local agent. The software was free because the company was an insurance brokerage. That meant this young San Francisco startup was operating in one of the most heavily regulated industries in the country, licensed state by state and overseen by fifty insurance commissioners.
The growth was extraordinary. By Conrad's account, Zenefits went from zero to $1 million in annual recurring revenue in its first year, to $20 million in its second, and to $65 million in its third. Forbes called it the hottest startup of 2014 and ranked it ahead of Uber and Airbnb. Andreessen Horowitz put more money into Zenefits than into any other company in its portfolio. Within two years the company had 1,600 employees and 10,000 customers. In the spring of 2015 it raised $500 million at a $4.5 billion valuation, bringing total funding to about $583.6 million. Fortune put Conrad at No. 20 on its 40 Under 40 list, and Forbes listed him among America's richest entrepreneurs under 40. Early on, as the headcount climbed, Conrad was still personally running to the Apple Store and ordering laptops from Amazon to hand to new hires.
Unlike most founders on those lists, he was not celebrating. In September 2014, Farhad Manjoo of The New York Times profiled him under a headline that asked why someone who was "rattling an industry" was so anxious. Conrad's answer later became an epigraph:
— Parker Conrad, to The New York Times, September 2014Even when we think things are going well, it always feels like the wheels are ready to come off the cart.
When Kickstarter co-founder Yancey Strickler wrote a book about rethinking corporate purpose years later, he quoted that line, noting how sharply it clashed with the admiring tone of the story around it. The founder appeared to be the only person in the piece who expected something to break.
Conrad did not see himself as a winner. "It feels like we're threatened on every side," he told Fortune in 2015. Entrenched brokers had complained to regulators in several states. Utah briefly barred Zenefits under a law against insurance rebates until the company fought it in court. ADP, the payroll giant, was in a legal dispute with the company. "It's so clear to me that we're right," Conrad said.
During this stretch, Zenefits brought in David Sacks as chief operating officer. Sacks was also an investor. He had been PayPal's COO before its sale to eBay, had founded Yammer, and had sold it to Microsoft for $1.2 billion in 2012. He was wealthy and well connected through the so-called PayPal Mafia, and he was known for writing sharply. He did not need the job. He took it anyway.
Three Lines of Code
The trouble at Zenefits started where the trouble at Rippling would start, with a small mechanical detail.
In the fall of 2015, BuzzFeed News reporter William Alden published a series of stories. The first, on November 25, reported that Zenefits had let unlicensed employees sell health insurance in several states. A follow-up the next February reported that 83 percent of the company's insurance deals in Washington state through August 2015 had been handled by employees without the required state license. Washington's insurance commissioner opened an examination. Around the same time, the Wall Street Journal reported that Zenefits had missed revenue targets. Fidelity, an investor, marked down its stake.
Then came the detail that made the story memorable. California requires prospective insurance brokers to complete a long online pre-licensing course, and the course checks that the student is still present by requiring a click every few minutes over dozens of hours. BuzzFeed reported that Conrad had written a script that made it appear brokers had completed the training when they had not. The California Department of Insurance said it was investigating whether brokers had used software to skip the mandatory course. The press called it "the macro."
Conrad's account came years later, on Jessica Livingston's podcast The Social Radars. He says he wrote the script for himself while taking the course for his own license, and that he knew the material and passed the exam with a 94. "I wrote a three-line script that kept you logged in," he said, "and it didn't take the test for you, it didn't give you any answers, it didn't advance you through the course content — it just maintained the session." He has said he believed the forced clicking was a bug in a badly designed course, not its purpose. Livingston, who co-founded Y Combinator, offered her own view: "Any reasonable human being is not going to want to spend 20 hours hitting the refresh button every five minutes."
Both readings can be true at once, and they say different things about the same person. The script was the reflex of someone who resents administrative busywork and automates it the moment he can. It was also the reflex of someone who did not consider that the busywork might be the requirement itself, and that the regulator's whole method of verifying a broker's presence was to make it tedious. An instinct that would later be worth billions also helped cost him his company.
On licensing, Conrad gives a more detailed defense. In his account, most Zenefits employees were licensed in their home states, the company held its own licenses, and its lawyers had told them individual out-of-state licenses were not needed. Once regulators objected, Zenefits began licensing everyone everywhere, and he says compliance was above 95 percent in his final year. He also argues there was no financial reason to skip the licenses, since getting one usually meant paying a fee without additional training. "There is a moral character to making a mistake like this versus going out and saying we're going to undermine the licensing regime," he said. "We just didn't think they had to be licensed because that's what our lawyers told us was required." He says that in December 2015 he hired PwC to audit the insurance business, intending to report the findings to regulators, pay the fines, and move on, and that he kept the board informed until the day he left.
That day was February 8, 2016.
The announcement included a statement attributed to Conrad, and it was gracious: "I am immensely proud of the organization we have built and the industrywide impact we've had but recognize that our company's management infrastructure and policies haven't kept pace with our meteoric growth. Elevating a strong management hand with successful experience and impeccable credentials is without a doubt in the best interests of the company at this time."
The email Sacks sent to employees that day read very differently.
— David Sacks, email to Zenefits employees, February 8, 2016We sell insurance in a highly regulated industry. In order to do that, we must be properly licensed. For us, compliance is like oxygen. Without it, we die. The fact is that many of our internal processes, controls, and actions around compliance have been inadequate, and some decisions have just been plain wrong. As a result, Parker has resigned.
The construction "as a result" did the damage. Sacks continued: "We must admit that the problem goes much deeper than just process. Our culture and tone have been inappropriate for a highly regulated company." He promoted Josh Stein, a former federal prosecutor who had been the company's vice president of legal, to chief compliance officer. Conrad left the board as well. Three new directors joined that day: Antonio Gracias of Valor Equity Partners, Bill McGlashan of TPG Growth, and Peter Thiel of Founders Fund. Founders Fund would later invest in Rippling too.
What followed is well known. In June 2016, Zenefits cut its valuation in half, to about $2 billion, and "trued up" investors' positions to head off lawsuits. Roughly 10 percent of employees took a two-month severance offer. Soon after, the company's director of workplace services sent an email that leaked and became the defining image of the company's culture: "Cigarettes, plastic cups filled with beer, and several used condoms were found in the stairwell. Yes, you read that right. Do not use the stairwells to smoke, drink, eat, or have sex." Conrad later called the coverage that followed, with its stories of orgies, a fabrication built on a single discovery. It did not matter. Vanity Fair's headline for the next round of layoffs began "Zenefits, of Sex-in-Stairwells Fame." The layoffs kept coming: 250 people, then 106, then about 430 in February 2017 under Jay Fulcher, who had replaced Sacks. That left roughly 500 employees, down from about 1,600 at the peak.
In October 2017, the Securities and Exchange Commission settled with Zenefits and Conrad for a combined amount of nearly $1 million over "materially false and misleading statements and omissions" to investors about regulatory compliance. As is standard, neither admitted nor denied wrongdoing. In 2018, Conrad signed an order and stipulation with the California Department of Insurance.
The man who had said the wheels always felt ready to come off had been right about that. He had been wrong about which wheel.
Whoever Writes the Memo
Accounts of the Zenefits collapse disagree about many things, but one is the core of the dispute: whether Conrad was removed because of what he did or because of how the story was told.
The official record is clear. The SEC sanctioned him personally. The company used unlicensed brokers, he wrote the macro, and he was CEO, so the regulatory failures happened on his watch. Sacks has stuck to that version for ten years.
Conrad's version is about authorship. He says that at TechCrunch Disrupt, Sacks presented the compliance failures as a problem in the sales organization, which reported to Conrad, when in fact about 70 percent of the violations came from account management, which reported to Sacks. He says he could not respond publicly because the company invoked attorney-client privilege over the findings. He says the departure release he had negotiated was replaced with one that blamed him. And he says he was subjected to a sustained campaign in the press. "I wasn't allowed to sort of talk about the things that I'm talking about with you guys right here," he told Livingston in 2023, seven years later.
His most revealing comment from that interview is an admission about his opponent's skill: "David is an incredible writer and really good at sort of framing these kind of attack narratives." The former Crimson managing editor was conceding he had been outwritten. "I've never been like really good at that," he added.
He has described one intervention from outside. In his telling, as the attacks continued, he complained to Sam Altman, then president of Y Combinator. "Then overnight it stopped," Conrad said. "Sam had spoken with Mark Andreessen and told him he was risking his relationship with Y Combinator if these attacks continued." There is no public record of that conversation beyond Conrad's account. He has also said that Zenefits under its new management was being "driven right into the ground."
For years the dispute stayed quiet. Then on July 24, 2024, Sacks, by then a prominent Trump supporter and podcaster, posted on X that President Biden had been "actually deposed" when Democrats moved behind Kamala Harris, and he called it a coup. Conrad replied with one line: "Let me tell you, coups are this man's speciality." Sacks posted a screenshot of the reply with his own response: "You were sanctioned by the SEC. Nobody else, only you. But you've spent the last decade trying to shift the blame onto others for your own poor ethics." He added a clown emoji.
Then Paul Graham, who had pushed Zenefits to launch in three weeks twelve years earlier, joined the thread: "Do you really want the full story of what you did to Parker to be told publicly?"
Neither Conrad nor Sacks has ever told the full story in public. Rippling declined to comment when Fortune asked. But the exchange showed two things. The wound was still open eight years later. And the founder of YC, whose judgment carries great weight in Silicon Valley, had chosen a side.
Conrad's main response to the narrative, though, was never going to be posts or podcasts. He had concluded long before that he could not win that kind of fight.
The Inductive Step
He waited six weeks.
In April 2016, Conrad began a new company with Prasanna Sankar, who had been Zenefits' director of engineering. They worked out of Conrad's house in San Francisco. In July, Vanity Fair, relying on a Fortune report, noted with some puzzlement that the ousted CEO was building a company that would compete with the one that had just removed him. One source called the project "embryonic." It involved getting new employees set up with laptops and software on their first day, which looked like one feature of the old company rebuilt as a smaller business.
He named it Rippling. Conrad has never publicly said where the name came from, so this next point is a coincidence, but it fits. In automated theorem proving, "rippling" refers to a set of heuristics developed at the University of Edinburgh beginning in the 1970s, when Raymond Aubin noticed a recurring pattern in inductive proofs and called it "rippling out." In an inductive step, you have a hypothesis that is already known to be true and a target conclusion that differs from it only slightly. The method marks the shared structure, called the skeleton, and marks the differences, called wave-fronts. It then applies rules that move the differences out of the way until the hypothesis can be used to complete the proof.
Read with that in mind, Rippling's founding resembles an inductive step. The skeleton was the same as at Zenefits: employees, payroll, benefits, and the administrative work around them. The differences were the parts that had gone wrong: the brokerage revenue model, the heavy reliance on manual operations, and the gap between how fast the company grew and what its systems could support. Conrad's job was to move those differences out of the way until the original idea could be proven correct.
He admits that proof was not his only goal. In 2025, he told Brian Halligan on Sequoia's Long Strange Trip podcast where the company came from:
— Parker Conrad, on Sequoia's Long Strange Trip podcastRippling was born out of kind of this, like, revenge fantasy. That's what kind of got the company going, and it's certainly what kept me going for the first couple years.
He was more specific with Livingston. "The only way for me to sort of talk about this, to speak in some way to like my former colleagues, friends and family, to the tech community, to the media about these issues is to build this specific company and build it into an enormous hundred-billion-dollar outcome." He did not pretend this was healthy. "It wasn't that I wasn't depressed about all of this. That was the thing that got me going." And: "There was a long period of time where that was the first thing on my mind every day when I woke up in the morning and the last thing every night when I went to bed."
The macro had kept a login session alive through dozens of hours of forced clicking. Rippling's early years kept a grievance alive in the same way, every morning and every night.
The grievance did not make him careless about product. For the first year and a half to two years, Rippling hired only engineers and product people, with no sales or operations staff. By the fall of 2017 it had fourteen employees, and by 2018 it had sixty. When Rippling launched publicly in a limited form on March 14, 2017, with $7 million in funding and a place in Y Combinator's Winter 2017 batch under group partner Garry Tan (the same man who had once nearly rented a corner of the Wikinvest basement), Conrad explained the main lesson he took from Zenefits, which was about manual work:
"It's really if you scale things up manually, one of the things, the mistakes we made or I made, is, if you scale things up manually you can come back and automate them later," he told TechCrunch. "The difficulty of automating a manual process, I'm convinced it grows not just with the employees doing that manual process but as the square of that difficulty. It's very hard to write down the spec to automate it completely. You have to start automating things when it's done at a small scale or you're screwed."
The point, as he puts it, is that a manual process done by hand for long enough becomes undocumented company practice, and automating it later means reconstructing knowledge nobody wrote down. Zenefits had grown on people doing things by hand, including licensing, enrollments, and the Apple Store runs. Rippling would be built on the opposite principle.
In October 2018, Rippling released its full product, and Conrad wrote the launch post himself. He did not call it an HR system. He called it an "Employee Management System," a layer "a level deeper in the stack" that would connect HR and IT around a single record for each employee. "It may seem unusual to combine HR and IT into one system," he wrote. "But we think this is the future for these software categories because both the HR and IT departments are fundamentally concerned with who your employees are and what their roles are in your company." The post explained the idea with examples: a new support rep added to support@company.com automatically; Excel installed for "everyone in Finance"; a Salesforce account created when a sales rep starts. When anything about an employee changes, every downstream system updates.
He had been describing this idea since the first week. "If you are the system a company uses for onboarding new employees and setting them up in different systems," he said in 2017, "it makes you into the system of record for employee data by definition." The laptop provisioning that Vanity Fair took for a feature was the way into the employee record.
A Bizarro-World Salesforce
Conrad's favorite comparison has a deliberately odd name. "People misunderstand, in my view, what Salesforce is because they think it's a CRM system," he told TechCrunch in November 2021, the week Rippling announced a Sequoia-led $250 million round at a $6.5 billion valuation. "I think Salesforce is really a system for managing business process and workflow across your company that happens to be built on this underlying foundation of customer data." Rippling, he argued, was the same kind of system turned inward: "this sort of bizarro world version of Salesforce where everything is re-centered around employee data."
This is the heart of his strategy, and it is a strategy built on doing the opposite of the standard advice. Silicon Valley's most repeated rule is to focus: pick one narrow problem, solve it extremely well, and expand only after you have earned the right. Conrad cites Bill Gurley and David Sacks as leading proponents of that rule, a citation that seems unlikely to be neutral. He calls the rule "wrong, or at least extremely limiting." His alternative is what he calls the compound startup: building many related products in parallel on one shared foundation of data, permissions, workflows, and analytics, so that each product makes the others more valuable.
"It's something that I believe that almost no one else agrees with," he said in 2021. He makes the argument historically. "If you look at companies like SAP, Oracle, and Microsoft, they actually look like compound software businesses," he told Tan. The narrow-SaaS period, in his telling, was a temporary situation created by the move from on-premise software to the cloud, when "there was so much greenfield territory" that almost any narrow tool could become a business worth a few billion dollars. "Ten years ago, the big question that everyone had is 'How many of these SaaS products can actually become billion-dollar companies?' And the answer, it turned out, was every single one of them." That land has now been taken. "Because the conventional wisdom is so strong in the idea that you shouldn't do this, there are these undiscovered islands of product market fit that are just beyond the horizon line."
He pairs the strategic argument with an economic one. Over the last five years, he says, public software companies have been "spending 50% more on sales and marketing, but they're adding 10% less in new ARR with that increase in spend. Fundamentally, the business model for a lot of software is just broken. There's too many businesses." A compound company sells one product and then sells the next ones to the same customer more cheaply. By 2023, he said, Rippling's cross-selling alone added more than $5 million in new annual recurring revenue every month, before counting any new customers.
He also uses his own company as evidence. Conrad says he personally runs Rippling's payroll, which at one point covered about 2,000 people in a dozen countries, and describes it as a "part-time job." He has also said that he handled all of Rippling's internal administration himself using the product. When Cursor co-founder Michael Truell visited Rippling's offices for an on-stage conversation, Truell mentioned that Rippling may have been the first software Cursor bought and that he had run payroll for a long time. Conrad said he was still a payroll admin at Rippling. A 2020 podcast listed his title as "customer support." "I'm the primary user of our product," he said. This is the Wikinvest founder who resented faxing insurance forms, now running a company built to eliminate that work and doing the work himself to check that it has been eliminated.
The compound model affects how Rippling is staffed. About half its employees are engineers. Conrad has said Rippling spends far more on R&D relative to revenue than typical SaaS companies, and he credits that for the product's quality. To build many products at once, he hires founders: first more than fifty, later more than a hundred, many of them from failed or acquired startups, put in charge of individual product lines as general managers. "I like working with people who have a chip on their shoulder," he said in 2021, and the reason is not hard to guess.
Since 2019, Rippling has raised money with written memos rather than pitch decks. Conrad rewrites the memo for each round, and in March 2024 he published a lightly redacted version of the one behind the Series F, a $200 million round with a tender offer at a valuation above $13 billion. The memo is also sent to job candidates before their first interview, so recruits read the same argument investors read. Having lost one fight over a written narrative, he made sure he wrote the narrative this time.
The product list kept growing. A Paycheck Protection Program loan tool shipped in April 2020. Global payroll arrived in 2022, along with a Finance Cloud that added spend management, corporate cards, and bill pay. Then came recruiting, performance management, learning, scheduling, a PEO, and a workflow studio. By the time Kleiner Perkins wrote about the company, Rippling offered two dozen cloud products. Its about page states the mission more plainly than most: "We free smart people to work on hard problems." On Livingston's podcast, Conrad cited third-party audits showing that a company of 1,000 employees using Rippling needed about 28 people in HR and finance, compared with about 46 at companies using other systems.
He once said there was "a hundred billion dollar just like sitting right there on the floor and nobody can see it except for us." That is the same hundred-billion-dollar figure he named as the scale needed to answer for Zenefits. The business plan and the grievance had the same target.
Twelve Hours in March
On Friday, March 10, 2023, Silicon Valley Bank failed, and Rippling's money was there.
That was the problem in its simplest form. Rippling processed customers' payroll through SVB, so when regulators froze the bank, the funds for paychecks owed to thousands of workers at hundreds of companies were stuck. The Washington Post later put the amount Rippling needed to cover at $545 million. It was the Western Union Friday again, except the gap was no longer a few trucking employees' paychecks. It was more than half a billion dollars.
Conrad's approach was much the same as in 2019, scaled up. He raised money fast. Working with Greenoaks Capital, Rippling had a $500 million term sheet within about twelve hours. It covered the remaining gap partly by liquidating money market funds held with JPMorgan. Paychecks went out. Afterward, Rippling moved its banking to JPMorgan.
There is an obvious irony in how this happened. Conrad had spent years criticizing investors as trend-chasers with short attention spans. In 2020 he had said his fundraising "trick" was to "just find a way to be the Twitter guys," meaning to build something investors could not afford to ignore. "Most of the 'tactics' around fundraising don't really matter," he said. "They're such a rounding error." The SVB weekend tested that view, and it held up. Rippling could raise $500 million in a day because investors already believed in it. Its credibility had been built through years of memos.
"The best revenge is massive success," a No Priors host said to him later. Conrad's answer was less tidy. He said that what made the hard periods at Rippling bearable was comparison. "No matter how bad things got I sort of always had this thing where I'm like, oh, man, this like just pales in comparison to how bad things were, you know, right at the end and just after I left at Zenefits when things got like really very dark." Zenefits had become his reference point for what bad really meant. A bank failure with half a billion dollars in payroll on the line was still not as bad.
All the Way to the Ground
In the summer of 2024, Paul Graham published an essay arguing that founders should be more hands-on than the professional-management model suggests. The industry started calling this "founder mode." Conrad had been working this way for years. "Going all the way to the ground floor particularly when something's broken is like that's the way to go," he told Tan. "Like you got to just really get your hands dirty, get in the weeds." He added a caution most people quoting him leave out: founder mode is for things that are broken, not a routine excuse to go around your executives. Halligan, the HubSpot co-founder who now coaches CEOs for Sequoia, has noted one of Conrad's habits: in some interviews, he gives a senior candidate an NDA and the board deck and watches what they do with it.
By the mid-2020s, Rippling was no longer an underdog in any sense. It was valued at $13.5 billion in 2024 after a Coatue-led round. In May 2025 it raised $450 million in a Series G at $16.8 billion, bringing total funding to $1.85 billion, with new investors including Sands Capital, GIC, Goldman Sachs Growth, and Baillie Gifford. Forbes estimated Conrad's net worth at about $2 billion. Rippling had about 2,800 employees in 2024 and about 5,000 in 2025, with offices in San Francisco, New York, Dublin, London, Bengaluru, Sydney, and Singapore. In June 2026 it launched Rippling Data Cloud, a business intelligence product that connects a company's employee records with outside business data. By the next month, annual revenue was around $1 billion. When Halligan, who once thought Conrad would never get off the mat, introduced him on air, he said: "Almost everyone, including myself, never thought he would get this company off the ground."
The fighting did not stop. In March 2025, Rippling sued Deel, its biggest competitor in global payroll, in Ireland, alleging corporate espionage. The suit said a Rippling employee had been passing internal information to Deel. Deel countersued in Delaware. In April 2025, the alleged spy admitted to it, in what Fortune called "a major scandal rocking the HR world." Conrad called the suit a public stand to defend the technology industry. In 2026, a judge denied Deel's motion to dismiss Rippling's racketeering case, and the case moved forward. That same summer, Rippling fought a smaller trade-secret dispute with a startup called Runlayer, which both sides eventually dropped. Conrad's view on conflict was formed in the Zenefits fight, and he has not mellowed. He goes all the way down to the ground in court as well.
What he tells other people is bleak. "People come to me all the time and they're like, 'Oh, I'm thinking about doing — you know, starting a company. What do you think?'" he told Halligan. "And my advice is always like, 'Don't do it. It's a terrible idea.'" People laugh, he says, but he means it. "It's not just that it's hard to be successful, it's that it's sort of really kind of soul destroying, like, even when you're successful." He also rejects one of Silicon Valley's favorite beliefs, that failure is the best teacher. "Zenefits failed for like dumb reasons," he said. "Companies fail for like many dumb reasons. And like it's really hard to sort of take a lot of lessons away from that. And actually, you probably learn a lot more by being at a company that's working and seeing, like, how it works."
That position fits his history. A man fired twice, once by his college roommate and once by the board of a $4.5 billion company, says the failures taught him relatively little. He gives two concrete lessons from Zenefits: be extremely careful about regulatory compliance, and avoid building on manual operations, an aversion he admits may sometimes go too far. Rippling now has a chief compliance officer, Bridget Abraham, listed on its leadership page alongside the general counsel and CFO. The rest, he says, came from watching the thing work: the growth that pulled Zenefits forward, the experience of finally building something people wanted, and the 2019 Friday when one accented letter stopped a payroll run and the CEO went to a drugstore with his own cash.
He still runs the company's payroll himself. Each pay cycle, an alphabetized list of thousands of employees in a dozen or more countries goes through the system, and the names with accents in them go through like all the others. Somewhere among Rippling's customers is a trucking company whose employees, one Friday in 2019, got their pay from a Western Union kiosk at a CVS in San Francisco. It is still a customer.
Part IIThe Playbook
What follows are the operating principles that come out of Conrad's three companies: the seven years at Wikinvest, the rapid rise and fall at Zenefits, and the deliberately different second attempt at Rippling. Some he has stated outright, often as a direct challenge to standard startup advice. Others show up only in how he behaves, such as the payroll he still runs and the memo he rewrites for every round. The common thread is a belief that the routine parts of running a company, including administration, records, compliance, and paychecks, are where companies are actually built or broken, and that founders who ignore those parts end up paying for it later.
The principles
- 1.Automate while it's small, or never.
- 2.Build the compound from day one.
- 3.Find the record underneath the categories.
- 4.Be your own most resentful customer.
- 5.Go to Western Union.
- 6.Stay in stealth until the product can carry the story.
- 7.Write the narrative before someone else does.
- 8.Be the Twitter guys.
- 9.Hire founders with something to prove.
- 10.Treat the regulator as part of the product.
- 11.Burn the grievance as fuel; don't mistake it for a strategy.
- 12.Study what works, not what failed.
R
From Snails to Systems of Record
The key dates in a career shaped by paychecks, licenses, and second attempts.
1998
Places third nationally in the Westinghouse Science Talent Search for sea-snail neurobiology research; enters Harvard that fall.
2003
Graduates from Harvard with an A.B. in chemistry after failing out and spending a year at the Arkansas Democrat-Gazette.
2007
Leaves Amgen and launches Wikinvest (later SigFig) in San Francisco with his college roommate, Mike Sha.
2012
Leaves SigFig after a falling-out; joins Y Combinator with Laks Srini; Zenefits launches in September.
2015
Zenefits raises $500M at a $4.5B valuation; BuzzFeed reports on unlicensed brokers in November.
2016
Resigns as CEO on February 8; begins Rippling with Prasanna Sankar in April.
2017
Rippling launches with $7M in March; SEC settlement with Zenefits and Conrad totals nearly $1M in October.
2018
Rippling launches its full "Employee Management System" combining HR and IT.
2019
Payroll failure and the Western Union trip; Rippling begins raising every round with written memos instead of decks.
2023
Raises a $500M term sheet in about 12 hours during the Silicon Valley Bank collapse.
2025
Sues Deel over corporate espionage; Series G values Rippling at $16.8B.
2026
Launches Rippling Data Cloud; annual revenue reaches roughly $1B.
Principle 1
Automate while it's small, or never
Conrad's most useful lesson from Zenefits is an engineering claim, not a moral one. "The difficulty of automating a manual process," he said in 2017, "grows not just with the employees doing that manual process but as the square of that difficulty." The reasoning holds up. A manual process done by a few people is still fairly well defined: you can watch it, write it down, and turn it into a spec. Once dozens or hundreds of people have done it by hand for years, it picks up exceptions, workarounds, local habits, and knowledge that exists only in people's heads. Automating it then means reconstructing all of that.
Zenefits grew on manual work, including Apple Store runs, account managers doing enrollments by hand, and licensing handled one case at a time. Conrad says the company "leaned way too much on ops," and that the habit was one of the "dumb reasons" it failed. At Rippling he went the other way. For its first eighteen months to two years, the company hired only engineers and product people, so there was simply no operations team to fall back on. Conrad has admitted the aversion may sometimes go too far. He has said Rippling might benefit from doing more things that don't scale. He thinks the cost of that mistake is smaller than the cost of the one he made before.
The usual startup advice, "do things that don't scale," is right about the early stage of finding customers. Conrad's point is that it is dangerous once a company starts scaling for real. Doing a few things by hand to learn is fine. Building the company around manual work is a debt that keeps growing.
Tactic: List every recurring manual process in your company that takes more than one person, and automate the most frequent one while it is still small enough to specify completely.
Principle 2
Build the compound from day one
Conrad's compound-startup thesis is often summarized as "go broad instead of narrow." The more important claim is about timing. "Companies that focus early on tend to continue to focus," he says. A company built around one product organizes everything around that product: its data model, its sales process, its hiring, its board's expectations. Adding a second product later, he told SaaStr's audience, means "you kind of have to almost refound the company."
So he built many products at once from the start and accepted the cost: slower early traction, much higher R&D spending, and the risk that the company is "only as strong as your weakest link." The benefit is that integration becomes the product. "If the integration doesn't matter," he has warned, "then there's no product value to you or your clients for doing these things together. All you have is the difficulty and challenge of doing multiple things in parallel well." The compound model works only when the connections between products are worth more than the products themselves. Integration that is merely possible is not enough.
This is not a recommendation for everyone. Conrad's own summary of the approach concedes that it requires a lot of capital and R&D, which may limit it to a small number of companies. It is an argument that the narrow approach has been overused, and that the most valuable problems sit across categories where narrow companies can't reach them.
C
Focus vs. Compound
How Conrad's model departs from the default SaaS playbook.
| Conventional wisdom | Conrad's position |
|---|---|
| Pick one narrow problem and solve it extremely well. | The narrow problems are "picked over"; the biggest problems span many systems. |
| Earn the right to expand from product to platform. | Companies that start focused stay focused; expanding later means "refounding." |
| Integrate with partners through APIs. | Native integration on a shared data model is "so much more powerful." |
| Buy growth with sales and marketing. | S&M efficiency is "broken"; cross-sell to existing customers instead. |
| Keep R&D lean until you find fit. | Spend unusually heavily on R&D; about half of Rippling's staff are engineers. |
Tactic: Before narrowing your scope, map the customer's whole problem across every system it touches, and ask whether solving the connections between those systems is a bigger opportunity than solving any one of them.
Principle 3
Find the record underneath the categories
Rippling's key insight was not about payroll, benefits, or device management. It was about the data underneath all three. "Both the HR and IT departments are fundamentally concerned with who your employees are and what their roles are in your company," Conrad wrote in 2018. Salesforce, in his reading, is a workflow system built on customer data. Rippling would be the same kind of system built on employee data, the "bizarro world" counterpart.
That reframing changed the competition. Onboarding tools were a commodity, but owning the employee record was not. "If you are the system a company uses for onboarding new employees and setting them up in different systems," he said in 2017, "it makes you into the system of record for employee data by definition." Laptop provisioning was the entry point that captured the record, and once Rippling had the record, every other product could rely on it for permissions, approvals, reporting, and policies.
The broader lesson for founders is to look past the categories customers use, such as HR software or IT software, to the shared data those categories all depend on. Whoever owns that shared data controls what gets built on top of it.
Tactic: Identify the data object your product touches that other systems also depend on, and design your product to become its authoritative source rather than one more copy of it.
Principle 4
Be your own most resentful customer
"I am an unusually resentful of the sort of busy work, administrative work," Conrad said. Most founders who use their own product (often called "dogfooding") do it out of duty. Conrad does it out of irritation. He faxed insurance forms at Wikinvest and hated it. At Rippling, he runs payroll, at one point for about 2,000 people across a dozen countries, and calls it a part-time job. He has said he handled all of Rippling's internal administration through the product, and he told Cursor's founder he is still a payroll admin.
This works because it puts the CEO where problems actually show up. A CEO who runs payroll notices the extra click, the confusing screen, and the edge case the product team dismissed. A CEO who once listed his title as "customer support" reads the complaints himself. Conrad's version of founder mode, going "all the way to the ground floor," comes from this habit.
He adds one limit that is easy to miss: founder mode is for things that are broken. A CEO who digs into everything stops managing and becomes a bottleneck. The aim is to know the product well enough to recognize when something is wrong, not to do everyone's job.
Tactic: Take on one recurring operational task your product is supposed to handle, do it yourself every cycle, and keep a running list of every moment it irritates you.
Principle 5
Go to Western Union
The 2019 accent-mark failure is now one of Rippling's leadership principles, and it represents a specific idea: when software fails and real people are hurt by it, the fix has to be personal and immediate, even if it does not scale. Conrad and MacInnis did not file a ticket or promise to do better. They withdrew their own money and went to a CVS.
This can look like it contradicts Principle 1, but it doesn't. Automation is for the system. When the system fails, the person affected (a trucker one missed payment away from losing his house) needs something done that day. The phrase "go to Western Union" turns that into a rule: rank the harm by how bad it is for the person on the other end, not by how inconvenient it is for the company.
It also served a strategic purpose. Rippling's competitors could always point to Zenefits. A story about the CEO wiring paychecks with his own money answers the question of whether Conrad can be trusted with payroll better than any marketing could. The trucking company is still a customer.
Tactic: Write down, in advance, what your leaders are authorized to do personally and immediately when a failure causes real harm to a customer's people, and make sure the answer includes spending their own time and, if necessary, their own money.
Principle 6
Stay in stealth until the product can carry the story
After Zenefits, Conrad had every reason to want public vindication. He waited anyway. Rippling worked out of his house for its first two years, hired only engineers, and gave the press little: an "embryonic" project in Vanity Fair, a limited launch in 2017, and the full product only in October 2018. By then, as one observer put it, it was "already miles ahead."
There were two benefits. The first was technical: building the shared data model, compliance infrastructure, and payroll engine in all fifty states is slow foundational work that public attention would only have disrupted. The second was about reputation. A disgraced founder who announces a big plan invites mockery. A disgraced founder who shows up with a working product that does something no competitor does forces people to look at the product.
Waiting is harder when you have something to prove, and Conrad has admitted that proving something was his main motivation. He still held off until the product could speak for him.
Tactic: Set a concrete product milestone, rather than a date, that must be met before any public announcement, and hold to it even when you are under pressure to be seen.
Principle 7
Write the narrative before someone else does
Conrad lost the Zenefits fight largely in writing. "David is an incredible writer and really good at sort of framing these kind of attack narratives," he said, and "I've never been like really good at that." The press release was replaced, privilege kept him from responding, and the "as a result" framing stuck.
At Rippling, he has controlled the written record. Since 2019, every funding round has been raised with a memo instead of a deck. He rewrites it each time and published a redacted version in 2024. Job candidates get the same memo before their first meeting. Conrad wrote the 2018 launch post himself and coined the terms that define the company: "compound startup," "employee management system," "bizarro-world Salesforce," "irreducible crap work." Other founders now repeat those terms.
The broader lesson is that a company's story gets written by someone whether or not the founder does it. A founder who doesn't write it down leaves it to others, and a carefully written memo shapes how investors, recruits, and the company itself understand what it is doing.
Tactic: Replace your pitch deck with a written memo, give it to investors and candidates alike, and rewrite it from scratch at each financing round so it reflects what you actually believe now.
Principle 8
Be the Twitter guys
Conrad pitched seventy-five investors in 2009 and came away contemptuous of most fundraising advice. "Most of the 'tactics' around fundraising don't really matter," he said. "They're such a rounding error. The important thing is to build a business that's so compelling that they can't afford to ignore you. And then all the other rules go out the window." His shorthand for this was "be the Twitter guys," a reference to the company investors were chasing at the time.
The SVB collapse proved the point. A company that needed $545 million over a weekend got a $500 million term sheet in about twelve hours. That speed came from years of investors already believing in Rippling, not from deal skill that night. The memo, the metrics, and the growth had done the work beforehand.
His own career is also a warning. At Zenefits, a "nosebleed valuation" based on aggressive projections created expectations that, when growth slowed, made investors anxious enough to turn on him. Being the company investors chase cuts both ways. Conrad's response at Rippling was to build the business first and let the valuation follow, rather than raise on projections and then try to meet them.
Tactic: Stop optimizing your pitch and spend that effort on the single metric that would make investors call you first, then raise only when that metric speaks for itself.
Principle 9
Hire founders with something to prove
"I like working with people who have a chip on their shoulder," Conrad said in 2021, and the reason is obvious. Rippling has hired first more than fifty, then more than a hundred former founders, and put many of them in charge of individual product lines as general managers. The compound model needs this. A company building two dozen products at once needs two dozen people who can run each one like a startup, and former founders already know how.
Conrad has said, on Sequoia's podcast, that he values "cultivating a founder mindset on the team" and that a chip on the shoulder can be a "superpower." Former founders, especially those whose companies failed, often have both skill and something to prove. They have fought for every customer before. Rippling gives them shared infrastructure, distribution, and the employee data model, and asks them to win again.
The risk is a company full of people who want to be in charge. The compound model reduces that risk by giving each founder clear ownership of a product line, so each has a real domain and real accountability.
Tactic: When hiring leaders for new product lines, recruit people who have founded companies, especially ones that didn't work, and give each of them a domain they can own end to end.
Principle 10
Treat the regulator as part of the product
Zenefits lost because it treated regulation as an outside obstacle that could be worked around: with lawyers' interpretations, with a three-line script, with the assumption that a company license covered individual brokers. Whatever the fair division of blame, the result was severe. An 83 percent unlicensed rate in Washington, an SEC settlement, a halved valuation, and a founder removed.
At Rippling, Conrad says the company tries to be "really extremely, extremely careful about compliance," regulatory compliance in particular. That matters more than it might seem, because Rippling has grown into some of the most regulated areas in business software: payroll taxes in every state, global payroll, a PEO, corporate cards, and banking. Its leadership page lists a chief compliance officer. Each new product means new regulators, and the compound model only works if the company can take on regulated areas without exposing itself in each one.
The script shows how easily this goes wrong. To Conrad, the forced clicking looked like a bug, and his instinct was to automate it. To the regulator, the tedium was the point. Founders who build automation will repeatedly see regulatory friction as inefficiency. Sometimes they're right. When they're wrong, the consequences can end a company.
Z
Same Skeleton, Different Wave-Fronts
What changed between the first attempt and the second.
| Dimension | Zenefits | Rippling |
|---|---|---|
| Revenue model | Risk Free software, paid by insurance broker commissions | Scale Monthly software fees across many products |
| Operations | Risk Heavy reliance on manual ops | Scale Engineers-only early team; deep aversion to manual ops |
| Compliance | Risk Licensing gaps; SEC settlement | Try "Extremely, extremely careful"; dedicated compliance chief |
| Public posture | Try Hypergrowth headlines, $4.5B valuation in two years | Scan Two years in stealth; memos instead of decks |
| Product scope | Try Benefits-led HR suite | Scale Compound HR, IT, finance, and data platform |
Tactic: For every regulated activity your product touches, name an owner whose job is to read the requirement as the regulator intends it, not as your lawyers say you can minimally satisfy it.
Principle 11
Burn the grievance as fuel; don't mistake it for a strategy
Conrad has been unusually open about his motivation. Rippling "was born out of kind of this, like, revenge fantasy." It was "the first thing on my mind every day when I woke up in the morning and the last thing every night." He was depressed, and that depression "was the thing that got me going." Few founders admit something like this, and it explains a lot: he returned six weeks after the ouster, he worked with unusual intensity, and the fights with Sacks and Deel have never really stopped.
The less obvious part is that the grievance supplied energy but not direction. The plan (compound architecture, the employee record, automation from the start) came from a product idea he would have pursued anyway. "I wanted this product to exist" is the first reason he gives on Livingston's podcast, before the revenge. Over time, he says, he came to love the people and the problems themselves. The grievance got him through the first two years, and the product idea carried the company after that.
Conrad also says this approach has costs. His standard advice to aspiring founders ("Don't do it. It's a terrible idea") comes from his view that company-building is "soul destroying, even when you're successful." A grievance can keep you going through that. It can also leave you in fights long after there is any point to them.
Tactic: If anger is driving you, write down separately the product thesis you would pursue without it, and check every major decision against that thesis rather than against the grievance.
Principle 12
Study what works, not what failed
Silicon Valley treats failure as the best education. Conrad, fired from two companies, disagrees. "Companies fail for like many dumb reasons," he said. "It's really hard to sort of take a lot of lessons away from that. And actually, you probably learn a lot more by being at a company that's working and seeing, like, how it works."
Coming from him, this is significant. He limits what he took from Zenefits to two concrete lessons: compliance and manual operations. Everything else, he argues, is mostly noise, because a failed company fails for many tangled reasons and the post-mortems tend to be rationalizations. What taught him more was seeing what worked at Zenefits: the market pulling the product forward, the three-week launch, how fast a team can move when demand is real. He kept those and dropped the rest.
That is why Conrad spent so little time on reflection after Zenefits. He didn't take a sabbatical or start angel investing. He started again on the same core problem with the known flaws removed, and reused the parts that had worked.
Tactic: After a failure, write down no more than two specific lessons, then spend the rest of your effort studying a company that is working right now.
Free playbook
Get The Business Model Playbook
58 business models, one visual page each: how the money flows, the metrics that matter, and who runs it. Free when you join the Faster Than Normal email.
Free. No spam. Unsubscribe anytime.
Part IIIQuotes and Maxims
In their words
— Parker Conrad, to TechCrunch, March 2017The difficulty of automating a manual process, I'm convinced it grows not just with the employees doing that manual process but as the square of that difficulty. It's very hard to write down the spec to automate it completely. You have to start automating things when it's done at a small scale or you're screwed.
— Parker Conrad, on the Something Ventured podcast, 2020The important thing is to build a business that's so compelling that they can't afford to ignore you. And then all the other rules go out the window. And then it's like very easy to raise. And if you can't build something that is that compelling, then God help you.
— Parker Conrad, on the compound startupBecause the conventional wisdom is so strong in the idea that you shouldn't do this, there are these undiscovered islands of product market fit that are just beyond the horizon line. If you can sail out and make it there, everything else about your company will work.
— Parker Conrad, to Fortune, 2015It's so clear to me that we're right.
— Parker Conrad, on Sequoia's Long Strange Trip podcastIt's not just that it's hard to be successful, it's that it's sort of really kind of soul destroying, like, even when you're successful.
Maxims
- Automate early or pay later. The cost of automating a manual process grows much faster than the process itself, so automate while it is small.
- Compound from the start. A company that begins focused stays focused, and broadening later means almost refounding it.
- Own the shared record. Whoever controls the data other systems depend on controls what gets built on top of it.
- Use the product yourself, especially the tedious parts. The CEO who runs payroll finds the problems no report will surface.
- Go to Western Union. When software failures hurt real people, fix it personally and immediately, even if that means your own money.
- Let the product make the case. Stay quiet until the product can speak for itself.
- Write your own narrative. A memo shapes how investors, recruits, and the company see the business; if you don't write one, someone else will tell the story.
- Fundraising tactics are a rounding error. Build something investors can't ignore, and the deal mechanics stop mattering.
- Read regulations the way regulators intend them. Friction that looks like inefficiency may be the requirement itself.
- Keep failure's lessons short. Take one or two specific lessons from what broke, and learn the rest from companies that work.
