
HireRoad, an HR software company, completed a legacy product rewrite in 15 weeks by reorganizing its engineering team to work "AI-native"—using AI tooling as the primary tool and humans to orchestrate and communicate—rather than simply adding AI access to existing workflows.
This approach achieved multiples of productivity gain instead of the 30% increases typical when AI is merely layered onto unchanged organizations, and suggests that winning with AI requires fundamental business reorganization, not just technology adoption.
What happened
HireRoad, an HR software company, scrapped its 18-month legacy product rewrite plan and instead reorganized its engineering team to work AI-native—using AI tooling first, with humans coordinating. The rebuild completed in 15 weeks instead of the planned 18 months, with the first 34 customers already migrated and live on the new platform, and the company used a smaller team than originally planned.
Why it matters
The shift from merely giving engineers AI tool access (which yielded 10–30% productivity gains) to fundamentally changing how work gets done can deliver multiples rather than percentages. This represents a business reorganization, not just a technology layer—comparable to how factories redesigned their layouts around electric motors decades ago rather than simply replacing steam engines with them.
What to watch
HireRoad expects to complete full customer migration and legacy decommissioning by the end of calendar year 2026. The company is now rolling out AI-native practices across other product lines, and the freed engineering capacity is being deployed to new initiatives.
Bob Morse, managing partner of Strattam Capital, opens with a case study of HireRoad, an HR software company owned by his investment firm. In December, when Jeff Fernandez joined as CEO, HireRoad faced a common problem in buy-and-build SaaS: accumulated aging code bases from acquisitions. The company had planned an 18-month clean-sheet rewrite of one of its oldest products, budgeted for a 30% surge in engineering headcount.
Instead, in February, Fernandez and the new CTO proposed a radical alternative: redesign the engineering organization and individual job roles around the power of off-the-shelf AI tooling. Rather than working the same way with AI bolted on, they would reimagine what people do all day. The result was completion in 15 weeks instead of 18 months—actually one week ahead of even the accelerated schedule. As of the article's writing, 34 customers had migrated to the new platform and were live with positive feedback. Full migration and legacy decommissioning is on track to complete by the end of calendar year 2026. Remarkably, the team accomplished this with fewer people than originally planned, freeing the intended 30% headcount increase for other HireRoad product initiatives.
Morse reflects on Strattam's broader experience providing AI tools like Copilot and Claude Code to engineering teams across its software portfolio. These efforts yielded consistent but plateau-like gains: 10% productivity improvement, then 20%, then stabilizing around 30%. The breakthrough came when leadership realized that providing tool access alone—what Morse calls "AI-sprinkled" organizations—was fundamentally different from "AI-native" work. He defines AI-native as daily practices that put AI tooling first and humans in roles of orchestration, coordination, and communication, not merely doing the same things faster but instead doing different things with more delegation and quicker learning loops.
Morse situates this insight within business strategy theory, citing Robert Burgelman's framework of induced (evolutionary) versus autonomous (revolutionary) strategies. Induced strategies advance the company's existing trajectory; autonomous strategies arise outside the business plan and require organizational revolution. The analogy of electricity in manufacturing is key: simply replacing a single steam engine with a single electric motor delivered minimal gains, but redesigning factories with distributed small motors throughout yielded explosive productivity increases—though this took decades. Burgelman's research on Intel, described in Grove's book "Only The Paranoid Survive," provides the motivational touchstone: when Intel faced a brutal price war in memory chips while its microprocessor business grew quietly, Grove and Moore famously asked themselves, "If we were fired and a new CEO hired, what would they do?" The answer was obvious—exit memory, go all-in on microprocessors—and they chose to execute that revolution themselves rather than wait for outside intervention.
HireRoad's concrete organizational changes included: new technology leadership training on a revised hour-by-hour work schedule optimized for AI tooling; sales working directly with engineers to put rapid prototypes into customer hands for faster feedback; customer support designing a high-confidence transition plan; and a bug-handling loop where the system logs issues, AI writes code fixes, and a human-in-the-loop approves before publication. The result was a smaller, more senior team with capacity freed for expansion into other initiatives.
Morse concludes by positioning AI-native organization as the third major management innovation of his private equity career, after 1980s cost-reduction and 2010s SaaS conversion. With roughly 10,000 privately held software companies in the U.S., he argues that leaders know—explicitly or by instinct—that repeating the same organizational approach in the age of AI is a losing strategy. Competitors moving at 3× speed will gradually starve rivals that don't change. He challenges readers to run the Grove thought experiment: if fired today, what would a new CEO do to win with your company in the age of AI? He suspects the answer is not "sprinkle more LLM access" but fundamental redesign of teams and daily work.
The article frames HireRoad's success as an example of a broader shift from incremental AI productivity gains to transformative organizational change. The author, a private equity investor, draws on business strategy frameworks—specifically Robert Burgelman's distinction between induced (evolutionary) and autonomous (revolutionary) strategies—to argue that the move from 30% gains to 3× productivity requires fundamental business reorganization, not merely technology adoption.
The parallel to electrical power's impact on manufacturing is instructive: factories achieved significant productivity gains only after being physically redesigned to distribute small motors throughout rather than replacing a single steam engine with a single electric motor. Similarly, AI-native organizations redesign how work gets done daily, not just which tools employees use. The author identifies this as the third major management innovation in private equity, following 1980s cost-structure removal and 2010s SaaS conversion.
The obstacle to such revolutionary change is institutional inertia. The article invokes Intel's famous strategic pivot—Grove and Moore's decision to exit memory chips and focus on microprocessors—as an example of how revolutionary moves require explicit CEO and board endorsement. The author suggests that software company leaders across the industry now face a similar choice: maintain existing organizational structures and gradually lose competitive ground, or undertake the uncomfortable organizational redesign required to realize AI's potential.
AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.
Free · takes 30 seconds · unsubscribe anytime
Ask AI anything about this article. Q&As are published on this page for other readers too.
Researchers at A Security disclosed vulnerabilities in Zoom's screen-sharing annotation protocol on Tuesday th…

Spotify will label artist profiles as "AI Persona" if they do not represent a real person, starting mid-Septem…

A portable, open-source tool called Se-harness (seh) generates unified instruction files (AGENTS.md) that work…

Snowflake held the inaugural CTO Circle event during Snowflake Summit 2026 in San Francisco, bringing together…

Snowflake held the inaugural CTO Circle event during Snowflake Summit 2026 in San Francisco, bringing together…

GitHub released the Copilot SDK for Java (version 1.0.7-preview.1), a client library that lets Java developers…

The AI news that matters, in one minute each morning.
Sign up free