The Six-Dollar Secret: Why the Next Trillion-Dollar Company Will Look Nothing Like a Software Company
A deeper dive into Sequoia’s thesis and what it means for builders right now
There’s a ratio sitting at the center of everything happening in AI right now, and most people building software are either ignoring it or haven’t fully reckoned with its consequences.
For every dollar a company spends on software, six go to services.
That single ratio explains where the real AI opportunity lives and why the companies that figure it out early will redefine what it means to be a software business.
Julien Bek at Sequoia Capital just published a piece that crystallizes the logic better than anything I’ve read this year. His thesis: the next trillion-dollar company will be a software company masquerading as a services firm. Let me unpack why I think he’s right, what it means for how we build, and what we see at Customertimes every day that confirms it.
The Founder’s Dilemma
Every founder building an AI tool is haunted by the same question: what happens when the next model version makes my product a feature?
It’s a fair fear. If you sell the tool, you’re in a race against the model. GPT-5, Claude 4, Gemini Ultra, each release is a potential existential threat to your differentiation. But here’s the flip side that changes everything: if you sell the work instead of the tool, every improvement in the model makes your service faster, cheaper, and harder to compete with.
A company might spend $10,000 a year on QuickBooks and $120,000 on an accountant to close the books. The next great company won’t sell better accounting software. It will just close the books. The software stack becomes infrastructure. The value delivered is the outcome.
It’s the difference between being a vendor and being a business partner. It’s the difference between the tool budget and the work budget and the work budget is six times larger.
Intelligence vs. Judgement
To understand where AI is actually going, you need one conceptual framework: the distinction between intelligence and judgement.
Intelligence is rules-based work. Translating a spec into code. Testing. Debugging. Medical coding. Filling insurance forms. Screening resumes. Matching invoices. The rules can be breathtakingly complex but they are rules. Given enough data and compute, these tasks are fundamentally learnable.
Judgement is different in kind, not degree. It’s the decision about what to build next. Whether to take on tech debt. When to ship before it’s ready. Which strategic bet to make. Judgement requires experience, taste, and instinct accumulated over years. It’s what you’re actually paying for when you hire a great CFO or a senior partner at a consulting firm.
Here’s the critical insight: AI has already crossed the intelligence threshold in software engineering, and every other profession is next.
A year ago, most Cursor users treated AI as fancy autocomplete. Today, more tasks are being started by agents than by humans. Software engineering accounts for over half of all AI tool usage across professions. Every other category is still in single digits. The reason software got there first is structural, it’s primarily intelligence work. Code either compiles or it doesn’t. Tests pass or they fail. The feedback loops are tight and the outputs are verifiable.
Today’s judgement becomes tomorrow’s intelligence.
As AI systems accumulate proprietary data about what good decisions look like in a domain, the frontier shifts. What required a seasoned professional last year becomes automatable this year. The line doesn’t hold still.
Copilots and Autopilots: Two Very Different Bets
Bek draws a clean distinction that I think will define how we look back on this era.
A copilot sells the tool. Harvey sells to law firms. Rogo sells to investment banks. The professional is the customer, the AI makes them more productive, and the human stays responsible for the output. This is the right model when AI is still developing and you’re augmenting judgement, not replacing intelligence.
An autopilot sells the work. Crosby sells to the company that needs an NDA drafted. WithCoverage sells to the CFO who needs insurance, not to the broker. The customer is buying the outcome directly. No professional intermediary. The AI handles the full task.
The higher the intelligence ratio in a field, the sooner autopilots will win. And once an autopilot establishes itself in the intelligence-heavy outsourced work, it starts accumulating the data and the client trust, to push toward the judgement work over time. The copilot-to-autopilot transition is already happening. The starting position determines the trajectory.
Start Where Work Is Already Outsourced
This is the strategic insight that I think deserves the most attention from anyone building in this space right now.
If a task is already outsourced, three things are true simultaneously:
The company has already accepted that this work can be done externally
There’s an existing budget line that can be substituted cleanly
The buyer is already purchasing an outcome, they’re pre-trained to pay for results
Replacing an outsourcing contract with an AI-native services provider is a vendor swap. Replacing headcount is a reorg.
One of those is a procurement conversation. The other is an organizational transformation that requires board approval, union negotiation, and change management. Start with the vendor swap.
The Opportunity Map: Where the Money Is
Let me walk through the numbers that stuck with me from Bek’s piece, because the scale is genuinely staggering:
Accounting and Audit: $50-80B outsourced in the US The talent crisis here is acute and structural. Roughly 340,000 accountants have left the profession over five years while demand grew. 75% of CPAs are nearing retirement. The licensing pathway is long, and starting salaries lag tech and finance. Nobody is filling this gap except AI. Companies like Rillet are building the AI-native ERP that will close the books; Basis started as a copilot and is moving toward autopilot.
Supply Chain and Procurement: $200B+ Most enterprises only actively manage their top 20% of suppliers. The long tail, the other 80%, gets zero attention because it’s not economical to have humans do the work. Contract leakage runs 2–5% of total procurement spend. The autopilot doesn’t need to displace anyone here. It’s capturing work nobody was doing. That’s found money with no incumbent to fight.
Insurance Brokerage: $140-200B Standard commercial lines are highly standardized. The broker’s core value-add is shopping across carriers and filling forms, pure intelligence work. Distribution is fragmented across tens of thousands of small brokers running identical processes. No single incumbent controls the customer relationship. The conditions for disruption are perfect.
Recruiting and Staffing: $200B+ The largest services market on the list. The top of the hiring funnel, screening, matching, outreach, is pure intelligence. Closing a candidate and assessing culture fit is judgement. The wedge is the intelligence-heavy, high-volume work where matching is standardized. Juicebox, Mercor, and others are building across the spectrum.
Management Consulting: $300-400B This is the hardest nut to crack. Almost all judgement or so it appears. The interesting question is whether AI can disaggregate consulting into intelligence components (data gathering, benchmarking, research synthesis) and judgement components (strategic recommendations, stakeholder navigation). Automate the former, elevate the latter. The pioneers here are still TBD, but the prize is enormous.
IT Managed Services: $100B+ Every SMB outsources its IT. Patching, monitoring, user provisioning, alert triage: intelligence work running on repeat across thousands of identical environments. The existing software layer sells tools to the MSP. Nobody has yet sold “your IT just runs” directly to the SMB as a guaranteed outcome. That gap is the opportunity.
Services-Led Growth
At Customertimes, we live this thesis. Our products work because we don’t parachute in with a tool and hope for adoption. We sit with clients as integrators. We learn the process before we touch the technology.
That sequencing matters enormously. You can’t build a great autopilot for accounting from the outside. You need to understand the edge cases that break the rules. The handoffs that happen between teams. The exceptions that actually define what “closing the books” means in practice for this particular company.
Services-led growth isn’t a business model compromise. It’s a data acquisition strategy. Every engagement teaches you what good judgement looks like in that domain. That proprietary understanding is the moat that makes the eventual product defensible against the next model release.
The Window Is Open, But Not Forever
The copilot companies built in 2024 and 2025 are sitting on a paradox. They have the customer relationships and the domain knowledge. They also face the innovator’s dilemma moving to autopilot means cutting their own customers out of doing work those customers are currently paid to do.
That tension is real, and it’s slow. Which means the window for pure-play autopilots built from scratch is genuinely open right now.
If you’re building from scratch in any of these verticals, you don’t inherit the copilot’s constraint. You can sell the outcome from day one. You can structure your pricing around results, not seats. You can build your data moat around what good output looks like, not what a professional found helpful.
The ratio that started this piece - six dollars in services for every one dollar in software - is the size of the untouched market. Most of it hasn’t seen a serious AI autopilot yet.
The builders who understand that are going to build very large companies.
This post was informed by Julien Bek’s essay “Services: The New Software” published by Sequoia Capital on March 5, 2026. Highly recommended reading for anyone building in this space.