About XOPS
We spent our careers running enterprise IT. Every year the systems got better, and every year people were still the ones carrying the work between them: help desks, refresh cycles, audit fire drills, contractor offboards that leaked seats for months.
What running IT taught us
Enterprise IT never lacked systems.
It lacked anything responsible for the work between them.
Every tool we bought was good at its part. None of them owned the outcome, so a person always did, reconciling the records and coordinating the next step by hand. We built XOPS to change that operating model: specialized AI agents that take responsibility for IT outcomes, working from a continuously reconciled operating position across the systems you already run, and acting through governed execution.
Agents run the job. XOPS executes the actions. People set the policy and own the exceptions.
Where we are
XOPS emerged from stealth with $40M in funding and was featured in The Wall Street Journal. By the time we announced, we were already in production at the Fortune 500.
Read the WSJ article →$40M
Funding raised
1.4M+
Employees coordinated
$4.8B
IT spend orchestrated
39
Countries deployed
What we believe
1
Workflows remain valuable inside the systems they were built to automate. The problem starts when an outcome spans several of them and a person has to carry the context between systems. They route work. They don’t finish it. The IT estate has been running on routing tooling for two decades, and the people who fill the seams are exhausted. We’re building what comes next.
2
Every Fortune 500 onboards hires, refreshes laptops, recovers devices, rotates licenses, stages deployments. The work is the same everywhere. So we built it once, properly, and ship it pre-loaded.
3
People should set the policy and own the exceptions, not work the queue. The work that requires judgment is real and worth paying for. The work that requires stitching seven systems together belongs to an agent that is responsible for finishing it.
4
We sit before we sell. We co-design before we deploy. We measure what we promised. We earn the next agent. The companies who run on XOPS aren’t buying a vendor. They’re joining a guild of operators.
5
The non-negotiable one
An agent can reason about what should happen. What actually changes in your systems can’t roll dice. XOPS agents act through governed execution: same input, same outcome, every time. Auditable, replayable, reversible. The math comes back to IT, and so does the trust.
Leadership
Our executives have led IT transformations and scaled operations at NTT, Qualcomm, FedEx, Box, and ServiceNow. They’ve held the pager. They’ve owned the budget. They’ve presented to the board. The platform reflects the experience.
Board
How we work
Partnership
Our customers feel supported, confident, and certain they made the right call. We commit to high-touch service at every turn. Not because the contract requires it. Because the work does.
Empathy
Your pain points, your perspectives, your political realities. We listen first because we’ve been there. Understanding the lived experience of an IT operator is how we earn the right to change it.
People
XOPS isn’t built for the C-suite. It’s built for the IT practitioners at every level — and for the employees across the organization who never have to think about IT, because it just works.
Press & media
You now know who built XOPS and why. The rest is operational: AI agents that own IT outcomes, each working from a continuously maintained position for every employee, device and AI agent, and acting through governed execution across the systems you already run. Already in production at the Fortune 500.
Prefer to start with the mechanics? See how it works →
