In late 2019, the remote WordPress VIP enterprise agency where I'd spent the last four years as an engineer and architect was hemorrhaging fifty thousand dollars a month. Three senior leaders had left in a restructuring the year before. The founder was floating the idea of folding us into a sister company. We had about twenty engineers and a runway that was getting shorter by the week.
Two and a half years later, we had over 130 engineers across 40 countries and were netting half a million dollars a month.
This is what that actually looked like. Not the conference talk version. Not the framework. The real thing.
The Crisis That Started Everything
I joined as a senior engineer in 2015. Solid client work: enterprise publishers, a major Google partnership, WordPress Core contributions. For three years the role was architect and engineer, focused on delivery, not strategy. Building things for the company, not building the company itself.
That changed in 2018. The CTO left for Google, the managing director moved on, the program director followed. A dozen or so people were laid off at the end of that year, and then a slow bleed through 2019 as the financial situation got worse. Someone had to step into the technology leadership role, and that ended up being me. CTO in responsibility if not yet in title. The chance to lead at this level had been a goal for years. The timing was terrible.
Over the next year, things got worse. The company was losing fifty thousand dollars a month, and the conversation about shutting things down was no longer hypothetical. By fall 2019, with the title finally official and the company on the edge of being absorbed into a sister organization, a pivotal deal changed the trajectory. Not because of the deal itself, but because it proved a strategy that had been taking shape for months. One that would eventually fund everything that came next.
The Tip of the Spear
Enterprise sales cycles are brutal. Six months to a year for a large contract. Multiple stakeholders, procurement reviews, legal back-and-forth. For a small agency competing against larger shops with dedicated sales teams, that cycle is a death sentence.
So we built a way around it.
We started offering thousand-dollar performance audits. The team had been working with Google on web performance before Core Web Vitals were even announced. We'd helped bring them into the WordPress space at their first WordCamp in 2018, and had been collaborating with their team even before that. We had deep, genuine expertise in an area that most agencies treated as an afterthought.
For a thousand dollars, we'd audit an enterprise publisher's site in a week and deliver a report showing exactly what was costing them traffic, revenue, and search ranking, along with what it would cost to fix. Actionable, specific, backed by data. The fix became the follow-on project, and most of the time that follow-on led to bigger engagements.
Here's why a thousand dollars is the important number: a purchase order that small gets through enterprise procurement with almost no friction. No lengthy RFP process. No committee approval. One person signs off.
But what a thousand-dollar audit actually buys you is a vendor relationship. An executed MSA and SOW. Once you're an approved vendor with an existing contract, future work (fifty thousand, a hundred thousand, half a million) is a procurement formality. You've eliminated the hardest part of enterprise sales by making the first purchase trivially easy.
We closed more contracts in the year after launching this strategy than in the previous three years combined. It became the engine that funded everything.
COVID Hit. We Were Ready.
When the pandemic shut down offices worldwide in early 2020, most companies scrambled to figure out remote work. We'd been remote-first since founding. The processes, the tooling, the async communication culture, the years of experience operating across dozens of countries and time zones were already in place.
At the same time, every large organization suddenly needed digital transformation, and they needed it yesterday. Website migrations, platform modernization, performance optimization at scale. The demand spike was extraordinary, and we were one of the few enterprise-grade agencies that could deliver without ever needing to be in the same room.
The agency had always been known for strong engineering, but after the 2018 leadership exodus and nearly a year of neglected relationships, we'd fallen from grace with WordPress VIP and the broader partner ecosystem. Rebuilding those relationships became a priority, then expanding the network to Pantheon, WP Engine, Liquid Web, and others. By the time COVID hit, we had referral pipelines from every major hosting platform feeding into the performance audit funnel. Remote-first wasn't just a perk anymore. It was a competitive weapon.
The combination of a proven sales strategy, a once-in-a-generation demand spike, and an operating model built for exactly this moment created a growth window that doesn't come around often. We ran at it.
None of this was one person. The people around me during this period were incredible. They made sure we kept delivering while the org was being pulled in ten directions at once. They picked up what leadership couldn't carry, supported each other through a pandemic, and trusted the process even when the pace was relentless. I would have moved mountains to make sure every one of them had a job, and many of them did the same for each other. The strategy was mine. The execution belonged to all of us.
Building the Machine
Growing from 20 to 130 engineers in two and a half years while staying profitable requires a specific kind of discipline. Here's what we learned about what actually matters.
Keep the overhead lean. We grew billable engineering staff aggressively and kept non-delivery leadership small. People services, a three-person sales team, and a single leader covering engineering, delivery, design, and product. We ran at 85-90% billable utilization in a given month while still carving out paid time for education, open-source contributions, and team events at conferences.
That balance matters. Lean doesn't mean extractive. Engineers had room to grow, contribute to the community, and stay connected to each other. But the operational overhead was tight. Every non-billable dollar had to justify itself.
Process is what lets you scale without losing quality. Every document and process in the organization got overhauled: onboarding, project delivery, client engagement, performance reviews, technical standards. All of it, rewritten and systematized. When you're adding people faster than any individual can personally mentor them, the process carries the knowledge. Without it, every new hire reinvents everything from scratch, and quality falls off a cliff.
Career ladders aren't optional. Around 60 engineers, we started losing people we couldn't afford to lose. Not to compensation, but to lack of progression. They couldn't see a future. I built formal career ladders showing every level from junior to staff, what was expected at each, and how to get there.
The effect was immediate. Retention improved within a quarter. Engineers who had been quietly interviewing stopped. People don't just want to be told they're valued. They want to see the path, in writing, with clear criteria. Build this before you think you need it, not after you start losing people.
Hire for signal, not credentials. We used paid engineering challenges as a filter. Every candidate got a real technical problem, and every candidate got paid for their time regardless of outcome. This filtered for people who could actually do the work rather than just talk about it, and it showed candidates we respected their time. In a competitive hiring market across 40 countries, that reputation compounds.
Remote requires deliberate investment in people. Remote work is liberating and isolating in equal measure. At scale, you can't assume people are fine just because they're productive. We brought in people specifically focused on team health and support. Not HR in the traditional sense, but people who understood that an engineer working alone from a city where they know nobody, during a global pandemic, needs more than a Slack channel and a daily standup.
The Breaking Points
Every scaling organization hits thresholds where the previous way of working stops functioning. They aren't gradual. They're cliffs.
At 50, informal communication dies. You can no longer assume that everyone knows what everyone else is working on. We introduced structured communication: written weekly updates, team-level syncs, and clear ownership of information flow. The overhead feels annoying when you're used to the organic flow of a small team. It's non-negotiable. Without it, teams duplicate work, decisions get made without context, and people start feeling invisible.
At 75, you outgrow individual leadership. This is where we started bringing in senior leaders, first a delivery lead, then a director of engineering. Not because the work couldn't get done, but because too many functions depended on too few people. When one person is covering sales, engineering, design, and product for an 80-person company, every sick day is a risk to the organization. The question isn't whether you can carry it. It's whether the company can survive if you can't.
At 100, the organization needs its own identity. This is the hardest transition. Culture, processes, and standards have to be self-sustaining. Not "what would leadership do?" but "what does the engineering handbook say?" A significant amount of time in this phase went toward making individuals replaceable: documenting decision frameworks, empowering team leads, building the muscle of distributed decision-making so the organization could function without depending on any single person's judgment for everything.
The Part Nobody Talks About
There's a version of this story that ends with "and then we celebrated our success." That's not what happened.
At around 120 people, with the company profitable, growing, and operating well, the founder (who had been largely absent during the hardest phase of the transformation) reappeared. What followed was a series of strategic disagreements that can be summarized without editorializing: when someone else builds the machine you own, and that machine is now very valuable, the incentives get complicated.
I left in early 2022. The specifics aren't the point. What's worth examining, from a scaling perspective, is what happened next.
The company is now hovering around 30 people.
That's not said with satisfaction. Many of those teams, those people, the processes they worked within and the career ladders they climbed were built during this period. Watching an organization shrink by more than 75% is not something anyone who helped build it takes pleasure in.
But it does answer a question that every scaling story should honestly address: were the systems self-sustaining, or were they dependent on the people who built them?
The strategy survived my departure. The sales playbook, the performance audit pipeline, the operational model, all of it stayed in place.
What didn't survive was the person closing the deals. A strategy without execution is just a document. They had the playbook. They just couldn't run it.
What I'd Do Again
The performance audit strategy. Without question. Finding a low-friction entry point for enterprise sales is worth more than any number of cold outreach campaigns or conference sponsorships. If you're a services company struggling with long sales cycles, find your version of the thousand-dollar audit.
Investing early in process and documentation. It felt like overhead at the time. It was the thing that let us absorb 110 new people without quality falling apart.
Paid hiring challenges. The investment in candidate experience paid back in hiring quality and reputation, and it filtered out people who couldn't deliver under real conditions.
Career ladders before they were urgent. Every week you delay building them is a week where your best people are quietly deciding whether they have a future with you.
What I'd Do Differently
Push harder for senior leadership earlier. At 60 people, the budget for senior hires wasn't mine to approve. That autonomy came later, once the revenue justified it. But covering four functions that long stretched the org thin. If you're in a similar position, make the case with numbers early and often, because the longer you wait, the more fragile the structure becomes.
Formalize the business relationship. When you're saving a failing company, you negotiate from a position of urgency. When you've made that company successful, the dynamics change. The lesson is obvious in retrospect: protect yourself contractually when things are good, because you won't have leverage when they're not.
Recognize that strategy and execution aren't separable. The growth strategy was documented. They kept it. It didn't matter. A sales playbook without someone who can close is just a PDF. Building the system felt like enough. It wasn't. Some things transfer through documentation. Closing enterprise deals isn't one of them.
The Actual Lesson
The job of engineering leadership at scale isn't making decisions. It's building systems that produce good decisions without you. That's still true.
But here's the uncomfortable addendum: those systems require people who believe in them. Process without conviction is just paperwork. Career ladders without someone who champions them are just documents. A growth strategy without someone who understands why it works is just a template.
You can build the machine. You can make the people within it replaceable, including yourself. But someone has to keep choosing to run it the way it was designed, or it stops working. That's the part that doesn't fit neatly into a scaling framework. And it's the part worth understanding sooner rather than later.