A founder I know spent two years building payroll software for small restaurants. Boring, right? Except payroll software meant she had direct deposit relationships with every hourly worker at her clients. By year three, she launched a wage-advance product for those workers and the payroll tool became the entry point to a consumer fintech business her investors had wanted all along. The payroll product was never the destination. It was the door.
This is the Trojan horse strategy, and once you see it, you can’t unsee it. The best early-stage startups consistently enter markets through a product that incumbents don’t find threatening, use it to build the data, relationships, or infrastructure they actually need, and then pivot up. Here’s how the pattern plays out.
1. Pick the Unsexy Workflow Nobody Wants to Fight Over
Big companies protect their big revenue lines. They do not protect their annoying operational plumbing. This is the gap early-stage startups exploit first.
Stripe is the canonical example. Credit card processing in 2010 was a market dominated by First Data and legacy bank processors. Nobody sane was going to beat them head-on. But developer tooling to implement payments? That was beneath the incumbents’ notice. Stripe won developers with seven lines of code, not by competing on interchange fees. Once they owned the developer relationship, expanding into fraud tools, business banking, and revenue recognition became straightforward. The API was the Trojan horse. The financial infrastructure was the target.
The lesson: find the workflow your target market’s incumbent treats as overhead. Build the best possible version of that unsexy thing. Incumbents will ignore you until it’s too late.
2. Use Data Access as the Real Product
Many Trojan horse plays are fundamentally about getting to data the market doesn’t yet realize is valuable.
When Veeva Systems started selling cloud software specifically to life sciences sales reps, the obvious product was CRM. But the real asset Veeva was accumulating was structured data about how pharmaceutical companies track, compensate, and deploy their field teams. That data became the foundation for a compliance and commercial data business that now generates revenue well beyond what a vertical CRM would ever justify. They entered through a workflow need and exited owning the data layer.
This matters for how you think about your early product’s value. If your entry product gives you access to data that incumbents either don’t collect or don’t share, you may be sitting on something more valuable than the product itself. The question to ask: what does your product see that nobody else can?
3. Build the Audience Before You Build the Product You Actually Want to Sell
Some of the sharpest Trojan horse plays don’t start with software at all. They start with a community or an audience that happens to need a product.
HubSpot’s early bet on inbound marketing content was functionally a media play. They published relentlessly about marketing, built a massive audience of marketers looking to get better at their jobs, and then sold those exact people the software to execute what the blog was teaching. The content wasn’t a marketing channel. It was the trust-building mechanism that made selling into a crowded CRM and marketing automation market possible. By the time they went upmarket, they had a captive audience that already believed in the methodology.
The cleaner version of this is building a free tool that your target buyer uses daily. Clearbit (now part of HubSpot) gave away an email lookup tool for years. That tool sat in the daily workflow of salespeople and growth marketers everywhere. When they launched their data enrichment API, those same users were already trained to think of Clearbit as essential infrastructure.
4. Commoditize Your Complement to Lock In the Market You Want
This one is slightly more aggressive and requires you to understand your target market’s economics well enough to know what they consider discretionary.
Amazon Web Services is the most extreme example. AWS made computing infrastructure cheap enough that almost any startup could afford to build. This looks altruistic. It isn’t. Cheap infrastructure meant more startups, more startups meant more software businesses, and more software businesses meant more eventual AWS customers. Amazon commoditized the complement to their own product and then reaped the compounding benefit. They entered the market as a cost-reducer and became the dominant infrastructure provider.
Early-stage startups can run a version of this by offering genuine value at or below cost in an adjacent space, capturing distribution, and then charging for the product that actually matters. This is why successful platforms sometimes launch with artificial usage limits: they’re managing the pace of a deliberate commoditization play, not just gatekeeping access.
5. Enter Through the Person Who Can’t Say No to Free
Enterprise sales is slow. Procurement is slower. But individual contributors will adopt a free tool in an afternoon if it makes their job 20 percent easier, and individual contributors eventually become champions.
Slack didn’t sell to CIOs. It got adopted by engineering teams and design teams who were tired of email, and then IT had to deal with it after the fact. Figma got into design workflows because individual designers started using it for free, then design teams standardized on it, and eventually enterprises had no choice but to pay. Both companies entered through the individual contributor, built undeniable utility, and let adoption pressure force the enterprise conversation.
The strategic insight here is about who has permission to say yes without a procurement cycle. That person is almost always an individual contributor who cares about their own productivity more than they care about vendor consolidation. Build for them first. Enterprise deals follow.
6. Let Your Trojan Horse Create Switching Costs You Didn’t Advertise
The most durable Trojan horse plays create lock-in that customers only fully notice after they’re already locked in.
QuickBooks built its moat not through accounting features but through the accountant relationship. When a small business owner’s accountant said they worked in QuickBooks, the conversation was over. Intuit didn’t need to win on product merits because the accountant ecosystem made switching painful in ways that had nothing to do with the software itself. The Trojan horse was cheap small-business accounting software. The actual product was a network of professional relationships that would defend the category for decades.
Think about what your entry product will make sticky over time, not just what it does on day one. The switching cost doesn’t have to be technical. It can be relational, habitual, or embedded in a workflow so deeply that replacing it requires changing how an entire team works. If your Trojan horse creates those conditions while it’s inside the walls, you won’t need to fight for the market. It’ll already be yours.
