The challenge
Large government IT outsourcing contracts rarely fail on technology — they fail on operations. Dozens of task orders running in parallel, unclear ownership across vendors and internal teams, and a security program that gets treated as a once-a-year audit instead of daily practice.
What we ran
Took direct operational and security leadership across a $70M, multi-year state government network-operations contract spanning 22 concurrent task orders.
- Directed a staff of 80+ across team leads, network engineers, database administrators and security specialists
- Stood up and personally ran the contract's security program: firewall and intrusion-detection architecture, plus hands-on penetration testing against the environment it protected
- Coordinated across many simultaneous workstreams and subcontractor teams so 22 task orders moved together rather than blocking each other
- Owned the security and reliability posture directly, rather than delegating it to a separate compliance function
How it ran
Every task order reported into one operational picture rather than 22 separate ones, so a slip on one workstream was visible against the others immediately instead of surfacing at a milestone review. The security program ran the same way: firewall/IDS posture and internal penetration testing were continuous inputs to daily operations, not a once-a-year external exercise bolted on afterward.
Results
- A $70M, multi-year contract run at a zero-tolerance reliability and security bar, sustained across its full term
- A security program — firewalls, intrusion detection, and internal red-team testing — integrated into daily operations rather than treated as a separate audit exercise
- 22 concurrent task orders and an 80-person mixed technical staff kept coordinated without one dropping the others
Let's talk about what you need built.
Custom-engineered solutions — no generic platforms, no compromises.
Start a Project →