Scaling to 500 People and Selling the Company: What I'd Do Again and What I'd Do Sooner

BLUF/Summary

I spent thirteen years helping build a government technology company from a small services firm to over 500 employees, serving in roles from COO to CTO to CIO/CISO, before the company was acquired by SAIC in 2021. The company was valuable for many reasons — strong client relationships, critical contract vehicles, deep technical talent, a growing reputation in key federal markets, and consistent delivery that earned trust over years of performance. None of those things happened by accident. They happened because the amazing founder, owner, and CEO of the organization, who I worked for, chose to invest in the operational infrastructure: the planning systems, operating cadences, documented processes, and accountability rhythms. These investments made excellent delivery repeatable rather than heroic. If I were doing it again, I'd invest in all the same things, as soon as financially feasible, to buy down risk.

The Arc

Halfaker and Associates was founded in 2006 by Dawn Halfaker, a West Point graduate, Army Military Police Officer, incredible leader, and wonderful person. I joined Halfaker in 2008, very early in the company's journey.

Over the next thirteen years, I served in a series of executive roles — COO overseeing service delivery, CTO focusing on customer-facing solutions, and finally CIO/CISO focusing on enterprise technology, process framework engineering, and cybersecurity. Those title changes reflected the company's evolving needs as it scaled, but underneath all of them was the same question: how do we build an organization that can grow this fast without losing the quality, trust, and talent that got us here?

The trajectory looked something like this: from foundation through 2013, we were a small company running on strong relationships, excellent people, and the energy that comes from a tight team building something together. In 2014, we achieved CMMI Maturity Level 2 and ISO 9001 certification. By 2015, we had reached CMMI ML3. Between 2016 and 2018, the company won several significant contract vehicles and prime awards and grew past 200 employees. By 2020, we had achieved ISO 27001 certification, surpassed 500 employees, and added ISO 20001 the following year. SAIC acquired Halfaker in July 2021.

That timeline is factual but misleading, because it makes the journey look linear. It wasn't. There were stretches where growth outpaced infrastructure and the organization strained. There were periods where we invested heavily in process maturity while the business continued to accelerate, and leaders wondered whether the process work was worth the time it consumed. There were moments where the choice between "move fast" and "build the foundation" felt like a genuine tradeoff rather than a both/and proposition.

Looking back, every period where we chose foundation over speed paid dividends later. And every period where we skipped the foundation work created pain that eventually had to be addressed — usually at a more expensive moment.

What I'd Do Again: The Things That Created Value

The company was valuable because of several things that reinforced each other, and I want to be clear about all of them — because organizational infrastructure alone doesn't make a company worth acquiring.

Winning and performing on the right contracts. Halfaker invested deliberately in pursuing contract vehicles that gave us access to large, long-term opportunities. Winning a spot on a $23 billion IDIQ wasn't a lucky break. It was the result of years of capability building, relationship development, and strategic positioning. The contracts were the visible signal that the company had earned trust in the market.

Building and retaining exceptional talent. In the federal services business, your people are your product. The talent we recruited, developed, and retained (e.g., engineers, project managers, security professionals, quality managers) was the reason clients kept renewing and expanding our work. Retention wasn't just an HR metric. It was a direct measure of whether people felt supported, challenged, and valued in their roles.

Earning client trust through consistent delivery. Client relationships in the federal space are earned over years, not months. The trust we built with customers, reflected in customer satisfaction (e.g., CPARS) scores, recompete win rates, and the willingness of clients to expand our scope was the most tangible proof that the company was doing excellent work. No amount of internal infrastructure matters if your clients aren't satisfied.

Building a reputation that opened doors. Over time, the company developed a reputation in specific federal markets (e.g., health IT, cybersecurity, agile delivery) that attracted both talent and business development opportunities. That reputation was built on delivery, relationships, and thought leadership, not on internal processes.

All of these were critical. All of these were real value drivers that a buyer assessed and paid for. But here's what I've come to understand since: each of these value drivers was sustained by something underneath them. And that something is what I'd invest in sooner.

What I'd Do Sooner: The Infrastructure That Made Everything Else Work

The contracts, the talent, the client trust, the reputation – these were the visible results. The less visible cause was the organizational infrastructure that made excellent delivery repeatable instead of dependent on individual heroics.

Planning systems that reduced chaos and delivery failures. When the organization was small, a smart project manager could keep everything in their head and deliver beautifully. When we had dozens of projects across multiple clients, that approach broke. The cascading planning system we built, annual strategy flowing through quarterly reviews through monthly operational check-ins through weekly priority emails, is what kept delivery on track across the entire portfolio. Strategic objectives were decomposed into measurable goals assigned to specific leaders, tracked with acceptance criteria, and reviewed at defined intervals. Leaders could see problems forming before they became client-visible failures. That planning discipline is what allowed us to maintain high CPARS scores and a strong recompete win rate even as the organization's complexity exploded.

There were times when we had underinvested in process and systems in specific domains and had to go through the painful work of juggling the operational chaos while retroactively building those systems. These were powerful reminders of how critical it is to build operational infrastructure runway before the company needs it.

Documented roles and expectations that let people succeed. As we scaled, new hires would join and spend weeks figuring out how things worked by asking around. Leaders would make decisions they didn't have authority to make or fail to make decisions they did have authority to make, because nobody had documented who owned what. The Roles, Responsibilities, and Authority Matrix we built solved this. It wasn't bureaucracy — it was clarity. And clarity is what let talented people move fast with confidence instead of hesitating or escalating everything to the top.

Better role clarity earlier would have meant faster onboarding, fewer bottlenecks, and less frustration for good people who wanted to do great work but couldn't figure out the invisible rules.

An operating cadence that kept leaders connected to reality. The operating cadence, the Battle Rhythm of recurring meetings, each with a defined owner, purpose, and output, is what prevented the leadership team from losing touch with execution as the company scaled. Weekly operations, executive, Business Development, and resource planning meetings keep tactical operations running cohesively. Monthly In-Progress Reviews (IPRs) and business performance reviews kept leaders informed and discussing the most strategic issues facing the company. Weekly priority emails kept everyone aligned. Quarterly strategy reviews forced the organization to check its heading and adjust.

This cadence is what allowed us to maintain engaged employees and strong client relationships at 500 people with the same intentionality we had at 50. Without it, leaders would have drifted into reactive mode, putting out fires instead of steering the ship. And reactive leaders produce reactive teams, which produce inconsistent delivery, which erodes client trust.

A knowledge management system that built organizational resilience. We maintained a living wiki with welcome pages for every team, checklist repositories, email templates for standard communications, runbook catalogs for system maintenance, and a Knowledge Asset Matrix tracking everything active, in development, and retired. This infrastructure meant that when a key person went on vacation, or left the company, the organization didn't skip a beat. The knowledge wasn't in one person's head. It was in the system.

That resilience is directly connected to client trust. Clients notice when their point of contact leaves and everything falls apart. They also notice when their point of contact leaves and the transition is seamless. The difference is knowledge management and organizational culture, and it's invisible until it matters.

A compliance program that was real, not performative. By the time of the acquisition, we held certifications in CMMI (CMMI-DEV ML3), ISO 9001, and ISO 27001. But the certifications themselves weren't what mattered. What mattered was that the certification efforts were used to get better, not get icons to put on the website. The process assets were living documents. The quality program ran continuous internal audits that fed process improvement cycles. The security program was architected into our permissions model, not maintained as a parallel set of documents for auditors.

This meant that as the company was growing larger and more complex, we were actively investing in reducing operational risk and variability.

The Connection I Almost Missed

Here's the thing I didn't fully appreciate until after the acquisition: the organizational infrastructure wasn't separate from the things that created value. It was the reason those things existed at scale.

We had strong client relationships because our planning systems caught delivery problems early, before they became client-visible failures. We retained excellent talent because people worked in an environment with clear expectations, defined roles, and leaders who could coach instead of micromanage. We earned high customer satisfaction scores because our quality program proactively and systematically reviewed delivery against client expectations, not just when an audit was coming. We won recompetes because the institutional knowledge survived personnel transitions, and the clients received consistent service.

Take away the infrastructure, and every one of those value drivers becomes fragile. Client trust depends on whichever PM happens to be having a good quarter. Talent retention depends on whichever leader happens to create a good team culture. Delivery quality depends on whichever hero happens to catch the problem in time.

The infrastructure is what turned individual excellence into organizational capability. It's what made the value drivers repeatable.

The Keel Connection

I didn't have the sailing metaphor during most of my time at Halfaker. The Keel Framework came later, as I tried to organize what I'd learned into something I could teach to others. But in retrospect, the framework describes exactly what we built, and what made the company capable of carrying as much sail as it did.

The contracts, the talent, the client relationships, the reputation — that's the sail. It's what makes you fast. It's what the market sees. But the keel, the operating cadences, the documented processes, the roles and authority structures, the knowledge management systems, the compliance programs, the designed culture — is what lets you carry that sail without tipping over.

When I look at the organizations I advise and invest in today, I value the ones who have invested in clarity of vision and culture and building systems to operationalize how they pursue that vision.

Without great leadership at the top of an organization, this is all irrelevant. And great leaders without a valuable business offering isn't going anywhere exciting. But, once you have great leadership and a great business offering, you need to be able to scale without just hiring smart people and crossing your fingers.

Where to Start

If you're leading a growing organization and this story resonates, you don't need to build everything at once. We didn't. The operating manual can start as a single welcome page for new hires. The roles matrix started as a table covering just the leadership team. The weekly accountability email started with one department before it became an enterprise expectation. The compliance certifications came in sequence over seven years, not all at once.

Start with the thing that's causing the most pain right now. If new hires are taking too long to get productive, build a welcome page. If decisions are bottlenecking at the top, build a roles and authority matrix. If strategy dies between January and December, build a quarterly review cadence. If delivery quality is inconsistent across projects, build a quality review process. If nobody knows what anyone else is working on, implement a weekly priority email.

Each of these is a weight added to the keel. None of them will transform your organization overnight. But compounded over months and years, they build something that's hard to replicate — an organization where excellent delivery is the system's output, not the hero's burden. Where client trust is earned through consistency, not luck. Where talented people stay because the environment lets them do their best work.

That's what I'd do again. And that's what I'd do sooner.

This is part of an ongoing series on building enterprise operating systems. Read more about the full approach in the Keel Framework, or explore related posts on the ambiguity tax of unclear roles, your operating cadence as strategy's immune system, the Friday 3pm accountability rule, and why process comes before technology.