← Back to list
Colossus (Invest Like the Best / Business Breakdowns)Podcast15 Nov 2022Source: joincolossus.comHost: Patrick O'Shaughnessy

Parker Conrad - Building a Compound Company - [Invest Like the Best, EP.303]

In plain words

This interview features Rippling CEO Parker Conrad on the 'compound company' idea—building multiple products (HR, IT, finance) together instead of focusing on one. He argues the old SaaS rule of 'focus on one product' is fading; deeply integrated suites will dominate again. His view: build around employee data, so each product shares infrastructure, beating point solutions on cost and quality. Key holdings: Rippling (24+ products, built by small teams in 12-18 months), Brex (partner for expense management, with revenue share), and Salesforce (as a parallel for customer-data-driven platforms).

AI SummaryAI-generated · may contain errors · verify against the original

Rippling co-founder and CEO Parker Conrad proposed the concept of a "compound company," which involves building a suite of interrelated products such as HR, finance, and IT simultaneously, rather than focusing on a single product. He argues that using employee data as foundational infrastructure ena

~10 min full read · 8 sections
Deep Analysis

At a Glance

Parker Conrad, co-founder and CEO of Rippling, proposed the concept of a "compound company" — building multiple interconnected product lines such as HR, finance, and IT simultaneously, rather than focusing on a single product. He argues that the past 20 years of SaaS market dogma of "focus on a single product" is becoming obsolete, and deeply integrated software suites will once again dominate the enterprise software market, because their dual product and business advantages far exceed point solutions.


Theme 1: Compound Companies — Breaking the "Focus" Dogma, Returning to Historical Patterns

Parker Conrad argues that the golden rule of the enterprise software industry — "focus on a single product first, then expand into a platform" — is now outdated, and the real opportunity lies in building multiple interconnected products simultaneously.

Argument:

  • Historical comparison: 20–30 years ago, enterprise software giants (SAP, Oracle, Microsoft) were all compound companies with extremely broad product lines. Over the past 20 years, the cloud migration forced them to be broken down into point solutions, but now that the "delivery vehicle" has stabilized, the compound model will make a comeback.
  • Market structure shift: "The vast majority of focused point SaaS opportunities have already been snapped up. In every niche you enter, you face five competitors. The true untapped opportunity is what others are unwilling to do — building multiple interconnected products at the same time to achieve seamless integration."
  • Customer data model: With employee data as the core infrastructure (similar to Salesforce using customer data as the core), all products are built around a unified data model, enabling native cross-product integration.

Deduction and Verification:

  • Verification signal: Whether Rippling can consistently gain share across multiple verticals (HR, IT, Finance, Device Management) while maintaining customer retention rates higher than those of single-product competitors.
  • Falsification condition: If any product line, when operated independently, is significantly less efficient than a focused competitor, it indicates that the compound model has failed in that domain.

Theme 2: Four Competitive Advantages – Where Rippling Wins

Parker Conrad reveals four core advantages of a unified platform over point solutions, and these four advantages repeat across every product line.

The Four Advantages:

Advantage Dimension Specific Content Comparison with Competitors
Deep Integration of Employee Data All products are built on a unified employee data graph, naturally understanding organizational relationships Point solutions must rely on integrations to piece things together
Middleware Capabilities Workflow automation, role-based permissions, approval routing, reporting and analytics—these underlying capabilities are built once and reused across all products Competitors "patch up" these capabilities after the fact, with quality that is an order of magnitude worse
Cross-Product User Experience Transfer Once a user learns Rippling's query language, reporting, and workflow configuration, the learning cost for new products is zero Third-party products require learning from scratch
Pricing and Contract Advantages Sales and marketing costs are amortized across multiple SKUs, allowing for lower overall pricing to customers Point SaaS companies must recover all costs from a single SKU

Mechanism Breakdown: This model is similar to how Microsoft used the Office suite to defeat single-point tools—but Rippling's depth of integration goes far beyond simple bundling.

Data Point: Rippling currently has "at least 24 SKUs," and each new product is built by a small team of 4–5 people in 12–18 months.


Theme 3: Middleware and the Employee Data Graph — The Moat of Infrastructure

Parker Conrad defines Rippling's core infrastructure as the "Employee Graph" and argues that it is a prerequisite for building a compound company.

Key mechanisms:

  • From employee directory to employee graph: A traditional employee directory only contains usernames, passwords, and groups. The employee graph, however, encompasses all data such as compensation, position, department hierarchy, team, work location, computer equipment, operating system, GitHub PRs, Jira tickets, Carta equity, etc.—all unified through the employee as a "common point of connection."
  • Middleware layering: Capabilities such as workflow automation, approval routing, role-based permissions, and reporting analytics are abstracted into a platform layer. Each new product directly calls these layers, eliminating the need to rebuild them from scratch.
  • Unexpected functionality: Because all products are integrated into the employee graph, cross-product capabilities emerge automatically. For example, automatically issuing a company credit card to employees who attend a company party and live more than 40 miles away—no integration is required between the expense management product and the survey product, as both are linked to the employee graph.

Analogy: Salesforce is a business process and data management platform for customers; Rippling is the same system for employees—the two are mirror images of each other.


Theme 4: Founder Recruits Founder — "Funding and Distribution as a Service"

Parker Conrad believes that Rippling's core selling point for attracting former founders is: "If you build it, customers will come" — the company provides capital and distribution capabilities, while the founder focuses on the product.

Mechanism:

  • Former founders join and are responsible for building a new product line from scratch. The early team does not rely on the company's hiring resources; they must recruit the first 3–4 engineers through their personal networks ("This is the real test — if you can't even do this, you can't lead this product line").
  • The company provides: funding (no need to worry about cash flow), infrastructure (org chart, middleware), and distribution channels (Rippling's customer base and sales team can directly market new products to existing customers).
  • "The hardest thing for a startup is 'If you build it, will anyone use it?' — we solve that problem. We can turn on the customer demand faucet for these products."

Supporting Viewpoint: This model essentially treats "funding" and "distribution" as infrastructure services for internal entrepreneurs, allowing them to focus solely on the product itself.


Topic 5: The Role of Investors — The Danger and True Value of the "Value Proposition"

Parker Conrad is highly skeptical of investors' "value proposition," arguing that investors' active advice often destroys value, but capital market judgment and recruitment assistance have real value.

Core Points:

  • "Investors spend 3–4 times a year, a few hours each time, thinking about your company, yet believe they should offer advice — this is very dangerous. They are smart but don't understand your business, and are often fighting the last war."
  • Personal experience: The advice Andreessen Horowitz gave during the Zenefits period (to accelerate growth more aggressively) was all wrong. If he had done the opposite at the time, the company might have been more successful.
  • The true value of investors:

1. Capital market judgment: Ask them "Is this investable for investors?" — they understand the capital market's investability better than founders.

2. Recruitment assistance: Some investors are deeply involved in executive recruitment, which is indeed useful.

Data point: During the Zenefits period, investors advised the target to increase from 10 million to 20 million, but Conrad's already high level of aggressiveness was further amplified, leading to overexpansion.


Targets Mentioned

Target Guest Attitude Key Data
Rippling Bullish (Proactive Build Model) 24+ SKU; 1,700+ employees; 12-15 countries; 4-5 person team per new product, 12-18 months to build
Brex Partner (Competitor + Cooperation) Rippling has its own expense management product, but also cooperates with Brex, with revenue sharing; the sales team is also evaluated on Brex sales
Tilt Partner (Attitude Not Stated) Maternity leave management vendor; cross-selling activities within Rippling
Salesforce Benchmark Analogy As a "customer-centric" compound enterprise software platform
Microsoft Benchmark Analogy Beat Slack with bundled pricing (Teams free), a successful case of a compound company
SAP/Oracle Historical Analogy Compound companies 20 years ago, all with broad product lines
Zenefits Past Experience (Negative) Investor advice led to overexpansion; former COO David Sachs used a PR attack strategy

Judgments Worth Remembering

1. “The doctrine of focus is becoming obsolete—compound companies will once again dominate enterprise software” (Parker Conrad)

Historical parallel: 20 years ago, SAP/Oracle/Microsoft were all compound companies; cloud migration broke them apart, but once distribution stabilizes, integration advantages will once again surpass focus advantages.

2. “The four advantages of compound companies—employee data, middleware, user experience migration, and pricing dilution—recur across every product line” (Parker Conrad)

Mechanism: These four advantages are not accidental but determined by the underlying architecture. Rippling enters any new domain by winning with these four cards.

3. “The ‘value proposition’ of investors is very dangerous—they spend a few hours a year thinking about your company yet believe they can offer advice” (Parker Conrad)

Falsification condition: If an investor's advice causes you to deviate from verified user needs, it is counterproductive. The only thing worth asking is “capital market acceptance.”

4. “Rippling's middleware capability is an order of magnitude stronger than any point SaaS competitor—because we built it natively, while they are patching after the fact” (Parker Conrad)

Data: Workflows, approval chains, reports, permissions—these capabilities are “forced garbage” in all point SaaS, but in Rippling they are the core platform.

5. “For former founders, Rippling offers ‘financing as a service’ and ‘distribution as a service’—eliminating the hardest startup problem of ‘if you build it, will they come’” (Parker Conrad)

Mechanism: Internal entrepreneurs don't need to worry about cash flow or customer acquisition; they only need to focus on the product, and the company will channel customer demand like a faucet.

6. “The employee data graph is a unified enterprise software metadata model—all systems are connected through the common link of the employee” (Parker Conrad)

Analogy: Salesforce connects all systems through customers; Rippling connects all systems through employees—the two are mirror images of each other.

7. “Non-scalable actions are more valuable than dashboards—getting down to the ground level reveals real problems” (Parker Conrad)

Mechanism: When a problem arises, first look at 20 support tickets, 20 Gong call recordings, and the codebase—not at reports. Data is only useful when you know what the problem is.

8. “The worst days at Rippling are far better than every day after Zenefits collapsed—because the second startup feels like going back to normal difficulty after playing on expert mode” (Parker Conrad)

Analogy: The first startup expanded rapidly but was panic-inducing; the second startup “has seen the movie before,” and the rhythm is completely different.