Labyrinth
The enterprise giant with complex suites and long-term contracts.
The Pattern
What the Labyrinth pattern is
Licenses for a suite of enterprise software, usually on multi-year contracts, bring in a Labyrinth's revenue, along with the services it takes to set that software up and connect it. A customer typically comes in for one specific need, and five years later it's running half its operations on the suite. Every custom integration and procurement contract along the way adds another turn to the maze, so the way out gets longer and a rebuild gets more expensive. By the time anyone seriously considers leaving, getting out has become a multi-year project nobody wants to own.
Think: Oracle, SAP, IBM Global Services, Accenture enterprise consulting, Salesforce enterprise tier, Workday, ServiceNow, government contractors.
The Engine
How it makes money
Account depth holds a Labyrinth together: how far each enterprise account goes across several product lines and layers of integration. Many products end up tied to one customer through integrations and custom configurations, plus the political relationships inside the account, so replacing them becomes a multi-year, multi-million-dollar project. Put simply, the keystone is the complexity itself and the customer's inability to untangle it. If customers stop buying multiple products (the multi-product attach), you're left with the churn risk of a single-product vendor.
A Labyrinth sells a complex suite of enterprise software on long-term contracts, with the products deeply integrated. It wins by selling once into a Global 2000 account (one of the world's largest companies), then expanding across that customer's stack. Any one product could be replaced, but five or seven of them integrated across thousands of users is effectively irreplaceable. Each major customer then becomes years of recurring revenue that expands in a predictable way.
The Discipline
Operating principle
Enterprise contracts make customers stick and let the business scale, but the bureaucracy slows everything down, inside the company and with customers.
Land and expand (win one product, then sell the rest of the suite into the same account) is the business model here, which means discipline on strategic accounts matters more than logo count (the number of customers) at this scale.
Healthy
In the healthy version you land with one product or use case and keep expanding across the customer's stack, until removing you would take a board-level decision the customer is unlikely ever to make.
Unhealthy
The trouble is that the same complexity slows the company's own work to a crawl, so Labyrinths struggle to ship new things customers actually love.
New products more often arrive through M&A (mergers and acquisitions) than through internal development, so getting good at acquisitions is a skill a Labyrinth has to master.
What Works & What Breaks
Healthy vs. breaking
What healthy looks like
What breaks it
The Profile
Profile
Best Fit Founder
We'd look for an enterprise veteran who's patient and politically savvy, has an appetite for M&A and can live with political complexity. They should be unsentimental about cutting products from the portfolio, too.
Go-To-Market
Sales go into named enterprise accounts over long cycles, with help from partner channels (Accenture, Deloitte, Cognizant, Capgemini). The selling has to be multi-threaded, reaching the C-suite, IT, procurement and end users at the same time, because single-threaded selling (relying on one contact) fails.
Ideal Focus
Locking large organizations into multi-year contracts comes first, and then the job is selling more of the suite into each one. The numbers that matter are net revenue retention, multi-product attach rate (the % of customers using 3+ products), how deep you've gotten into strategic accounts and how broad the integrations are. Logo count is actively a vanity metric at this scale, because landing 10 small logos that won't expand is worse than landing 2 large ones that will. The best Labyrinths stand out for discipline in how each account is run.
Revenue Pattern
Contracts are large. New deals close in lumps, and Q4 close rates can run 2-3x the average quarter, but the renewal base underneath is smooth and gives you cash-flow visibility for years.
Unhealthy Signs
Risk, Speed & Burnout
Sales Cycle
A new logo takes 6-18 months, because it has to get through discovery, technical evaluation, security review and procurement. An upsell inside an existing account takes 3-9 months. After that, implementation can take another 6-24 months before the revenue is fully recognized.
Hiring Sequence (first 5 after founder)
- Enterprise Account Executive, who hunts named accounts
- Solutions Engineer / Sales Engineer, who owns technical credibility in deals
- Customer Success Manager, who owns retention and expansion at the strategic-account level
- Implementation / Professional Services Lead, who turns contracts into live revenue
- Partner Channel Manager, who manages SI relationships (Accenture, Deloitte, etc.)
The back office runs on Salesforce or SAP for CRM (customer relationship management), with configure-price-quote tools for building complex quotes and contract lifecycle management. Then there are complex billing systems, customer success platforms (Gainsight), partner portals and integration middleware.
The work moves in long arcs, with high-stakes meetings and a lot of time spent building consensus and handling politics inside the company. People burn out here from political fatigue more than from overwork.
Leading KPIs
- ACV (average contract value) - rising ACV signals a successful move upmarket and pricing power, and falling ACV signals discount creep or drift downmarket.
- Sales cycle length - cycles getting longer is an early sign buyers feel less urgency, often 1-2 quarters before close rates drop.
- Win rate - it tracks your competitive position deal by deal, and falling win rates show new competitive threats before they reach revenue.
- Renewal % - gross logo retention shows whether you're true infrastructure or just convenient tooling, and below 95% in enterprise is a warning sign.
- Expansion revenue % / Net Revenue Retention (NRR) - this is the engine of growth at scale, and 120%+ NRR means you don't need new logos to grow meaningfully.
- Multi-product attach rate (% of customers using 3+ products) - the truest measure of how deep the moat is. Customers with 3+ products almost never churn, and customers with 1 frequently do.
- Gross margin - it shows the cost of services-heavy delivery, and a declining gross margin means services revenue is hiding product weakness.
- Labor utilization % - services and customer success take a lot of labor, and utilization below 70% means you're carrying excess capacity.
- Client concentration % (top 20-50 accounts) - concentration runs high in this model, so tracking it is non-negotiable for board reporting and risk management.
- Services revenue as % of total (target <25%) - lower is healthier, because a rising services share means the product is too complex to deploy without consultants, which undermines software-grade economics.
Feature Focus
The multi-step buyer journey makes segmentation pay off.
Operations and the customer path get too complex.
CFO Watchpoints
What to watch
Defense
Defensibility
It's often high, because the top 50 customers can be 40%+ of revenue. Losing a single one of those accounts is big enough to make the news.
The market is an oligopoly, with a handful of mega-vendors (Oracle, SAP, Salesforce, Microsoft, IBM, ServiceNow, Workday) competing for the same Global 2000 accounts. Disruption tends to come from below, when mid-market specialists grow up the stack and win the first workloads at lower prices.
The moat stacks seven things together: switching costs, integration depth, procurement inertia, entrenched products, relationships, standing with industry analysts and the partner/SI ecosystem. Add 5-7 year contracts and the political capital the Labyrinth has inside the customer, and the cost and risk of removing it almost always outweigh the upside for that customer.
Switching cost is extreme. Replacing a Labyrinth means rewriting the integrations, retraining thousands of users, migrating data with zero tolerance for loss and renegotiating dozens of contracts. It's often a 3-5 year project that costs tens of millions.
Financial Impact
The money
Impact
ACVs are huge and contracts run for years, but revenue is lumpy and the business is bureaucratic, with high overhead. At the top end you get software economics that earn premium multiples thanks to high NRR and deep moats, but that's offset by the capital M&A uses up and by services-heavy delivery.
Target P&L Allocation
| Category | Target |
|---|---|
| Client Acquisition / Ad Spend | 20% |
| Total Labor | 30% |
| Fixed Overheads & G&A | 25% |
| Legal & Professional | 5% |
| Operating Income (EBITDA) | 15-20% |
Huge ACVs, long receivables; manage cash timing and overhead drag
Source: Compass archetype one-pager, target allocation as a percent of revenue
Project managers and implementation engineers get a base salary plus milestone bonuses, tied to finishing deployments, hitting go-live dates and the triggers for recognizing revenue. Customer success managers are typically paid on net revenue retention rather than gross retention.
Enterprise AEs (account executives) are on a 50/50 base/commission split. Accelerators (higher commission rates past quota) are built for long cycles and pay disproportionately for multi-year, multi-product deals, typically ramping hard from 100% of quota up to 200%+.
Since these are B2B (business-to-business) contracts, chargebacks are low, but credit memos and concession reserves are real and typically run 1-3% of revenue. Bad debt is rare, but it can be catastrophic when it happens.
Labyrinths carry a positive and significant working capital need. Net-60/net-90 enterprise terms leave large balances in AR (accounts receivable, meaning money customers owe you). Services work-in-progress adds to that, so AR needs careful management.
Revenue Quality Score
8 / 10. Labyrinth revenue is exceptionally durable and sticky. It's lumpy when new deals close, though, and exposed to swings in the renewal cycle, and sometimes services drag pulls it down.
Trajectory
Where this goes
Total Global 2000 and public-sector spend in your categories is as big as a Labyrinth can get. After every viable account has as many products as it will take, growth has to come from M&A and renewal pricing, and both have diminishing returns. You've hit the ceiling when M&A goodwill grows faster than revenue.
There's very little room to change the core, but M&A gives you plenty of options. You can buy your way into adjacent categories, though you can't pivot away from the suite model.
The endgame is almost always as a public company, like IBM, Oracle and Salesforce, or as the target of a mega-deal. Private exits are rare, because the businesses are so big.
Common Founder Failure Modes