Anthropic’s take: Why not chasing Big Tech might be the smarter move

This article summarizes an episode of Lenny’s Podcast’s video series featuring Amol Avasare, head of growth at Anthropic

Photo credit: Shutterstock

Competing against established technology companies requires precise strategic focus. Amol Avasare, head of growth at Anthropic, argues that starting with limited funding forced his team to rethink how they build software.

He warns that trying to match the financial power of richer competitors often causes startups to fail.

To survive this disadvantage, Avasare believes that applying strict limits creates better digital tools. By focusing only on programs that help their developers work faster, the company builds an internal engine that speeds up its overall research.

Dealing with a late start

Entering a market dominated by companies with large budgets puts a startup at a disadvantage. To fix this, the company used its lack of resources to remove distractions and focus its early efforts.

Avasare notes, “When you have a bunch of constraints applied to you, it can bring a lot of freedom because it just frees up all this excess choice.”

He believes that having fewer options makes the next steps clear, allowing the company to avoid copying every feature offered by larger rivals.

Building a system that improves itself
To maximize this focused approach work, the team needed to master one specific skill. Dividing engineers across multiple projects prevents a company from achieving excellence in a single area.

The company avoided this outcome by directing all early efforts toward automated coding tools.

Avasare shares, “If you have the best models, that’s going to accelerate your researchers, and that’s going to accelerate the research loop.”

This internal focus means the software to directly help the team build better versions of the software, creating a self-sustaining cycle of progress.

Managing faster developers

Providing engineers with automated assistants creates delays for product managers and designers. Traditional team structures struggle to maintain pace with developers who write code at double their previous speeds.

To stop work from piling up, the company changed its operational rules. Avasare details, “If a project is two weeks of engineering time or less, then the engineer is on the hook to effectively be the PM for that.”

Automating the growth process