The Rise of "Small Tech" (And Why It's More Resilient)

The Unicorn Tax

In 2015, if you weren't raising $50M+ and hiring 500 people, you weren't serious. Today, some of the most impressive companies I know have 12 employees and $10M ARR. The economics have inverted.

What changed? Two things: infrastructure commoditization and AI-powered automation. You no longer need a 40-person ops team to run global infrastructure. You don't need 15 customer support agents when an AI can handle tier-1 tickets at midnight. The leverage available to small teams is unprecedented.

But this isn't just about efficiency. It's about resilience. And that's what most people miss.

The Brittleness of Scale

Large organizations optimize for coordination at scale. They build process, hierarchy, and communication frameworks. Every new hire adds complexity—not just their individual contribution, but the overhead of synchronizing them with everyone else.

This creates fragility. A reorg can paralyze 200 people for a quarter. A miscommunication between teams can delay a critical security patch by three sprints. The larger the machine, the more points of failure.

Small teams don't have these problems. When you have eight people, everyone knows what everyone else is working on. You don't need Slack threads with 47 participants. You don't need four layers of approval to ship a hotfix at 2am.

At Link11, we've watched competitors ten times our size move slower on critical infrastructure decisions. Not because they lack talent—they have brilliant engineers. But because their decision-making apparatus is a bureaucracy, not a reflex.

The Cost Structure Advantage

Let's talk numbers. A typical SaaS company at $10M ARR with 100 employees has a burn rate of ~$15M/year. That same revenue with 15 employees? Maybe $3-4M burn. The difference isn't just payroll—it's office space, HR overhead, management layers, and the "culture budget" that scales with headcount.

This creates strategic optionality. The lean company can survive a 50% revenue drop and still be profitable. The bloated company needs growth or dies. In cybersecurity, where market conditions shift with geopolitical winds, that optionality is the difference between lasting 20 years and lasting 3.

Profitability isn't just a financial metric. It's a defensive posture. When you're not dependent on the next funding round, you can make long-term technical bets. You can turn down bad customers. You can invest in infrastructure that won't pay off for five years.

The Automation Moat

Here's where it gets interesting: small companies that embrace automation early build a competitive moat that's hard to replicate.

When you have 500 employees, you can brute-force most problems with human effort. Customer complaint? Assign a CSM. Server acting weird? Page the on-call engineer. Deployment failed? Someone manually rolls it back.

When you have 12 employees, you can't brute-force anything. You have to automate or die. So you build self-healing systems. You implement automated rollback on deploy failure. You create an AI-first support triage system from day one.

Fast-forward five years. The large company is still running the same manual processes—because changing them would require retraining 500 people. The small company has compounded automation advantages that are now baked into the architecture.

This is why I'm bullish on the "small tech" movement. It's not nostalgia for the garage startup. It's recognition that in the AI era, the optimal org size might be 10x smaller than we thought.

The Attack Surface of Complexity

From a security perspective, small is inherently safer. Every dependency is a liability. Every integration point is an attack vector. Every employee with production access is a potential insider threat (or phishing target).

Large companies have sprawling tech stacks. They acquire other companies and inherit their infrastructure. They have 17 different authentication systems because each team built their own. The attack surface grows exponentially with organizational complexity.

Small companies can maintain a tight perimeter. When your entire stack is Postgres, Redis, and a Go binary, your threat model is manageable. When you have 200 microservices across three cloud providers with a service mesh and 12 different logging systems, good luck.

At Link11, we've deliberately stayed lean on the tooling side. Boring technology, ruthlessly maintained. No Kubernetes (we ripped it out in 2024). No microservices for the sake of "best practices." Just fast, reliable infrastructure that we understand completely.

The Hidden Cost of "Talent Density"

Silicon Valley loves to talk about talent density. Netflix famously optimizes for it. But there's a dark side: ego density.

When you have 50 brilliant engineers in one room, they all want to solve interesting problems. They want to rewrite the monolith in Rust. They want to implement a distributed tracing system. They want to build an internal developer platform.

Most of this is waste. It's engineers optimizing for their résumé, not the business outcome. Small teams don't have the luxury of "interesting" side quests. You work on what moves the needle or you don't eat.

This focus is a superpower. I'll take 10 engineers who are obsessed with the core mission over 100 who are half-distracted by internal politics and side projects.

The Macro Shift

We're entering an era where capital efficiency matters again. Zero-interest-rate policy (ZIRP) made growth-at-all-costs viable. That party is over. Investors want profitability. Customers want stability. Employees want sane work environments.

The companies winning in 2026 are the ones that figured out how to do more with less. Not as a cost-cutting measure—as a design philosophy.

37signals (Basecamp/Hey) has been preaching this for years. They were right. Indie hackers building $1M ARR solo businesses proved the model works. Now the rest of the industry is catching up.

What This Means for You

If you're building something new: start small and stay small as long as possible. Don't hire until the pain of not hiring is unbearable. Automate before you delegate. Profit before headcount.

If you're inside a large org: fight for team autonomy. The best large companies operate like a portfolio of small companies. Amazon's two-pizza teams. Stripe's product pods. Find a way to shrink your coordination surface.

If you're an investor: stop penalizing capital efficiency. The "grow or die" mentality created a generation of unprofitable zombies. The companies that survive the next decade will be the ones that learned to thrive on less.

Conclusion

Small tech isn't a trend. It's a return to fundamentals. In a world where software can replace entire departments, where AI agents handle what used to require 10 people, and where infrastructure costs have collapsed—there's no reason to build a 500-person company unless you're going after a 500-person problem.

Most problems aren't that big. And the ones that are? They're often better solved by tight, focused teams with deep automation than by throwing bodies at the problem.

The giants aren't going away. But the next generation of resilient, profitable, and fast-moving companies will look a lot more like a special forces unit than an army.

And I'm betting on the small teams.

---