Two years ago, we started building a company called Territories.ai. The name told you exactly what we did: territory planning and account distribution for revenue teams.
It was a good name for a specific problem. It was also, intentionally, a starting point. Even early on as TAM, Account Scoring, and Capacity Planning were added, the name was a narrow focus of the broader outcome.
If you've been reading the RevOps Rocket for a while, you've watched me pick apart the same problem from different angles over the past several months. The Qualtrics story about structural misalignment that took two missed quarters to surface. The CRO conversation where 40% of a rep's "250 accounts" couldn't actually buy the product. The pattern of confident plans built in November that start breaking by February because nobody goes back to check the assumptions underneath them.
Every one of those stories lands on the same conclusion: the revenue plan is the most important artifact in your go-to-market organization, and nobody has built a system to keep it alive after it ships.
Today, that changes. Territories.ai is now Orbytal, and the reason for the name change is the reason for this newsletter.
The Name Was Always Temporary
When we launched Territories.ai, we knew territories were the entry point. Account distribution and territory carving is the most visible expression of a revenue plan, it's the part reps feel on day one, and it's the part that breaks loudest when it's wrong. It was the right place to start.
But if you've spent any time in a revenue leadership seat, you know territories don't exist in isolation. The quality of your account books depends on your ICP scoring. Your ICP scoring depends on your pricing and packaging model. Your headcount plan depends on capacity modeling that accounts for ramp, attrition, and close rates. Your quota distribution depends on the spend potential sitting inside each rep's book.
Pull any one of those threads and you end up holding the entire revenue plan.
That's exactly what happened as we worked with more revenue teams. We'd get brought in for territory optimization and immediately find ourselves three layers deeper, untangling assumptions about market sizing, capacity modeling, and quota allocation that were baked into the plan but never stress-tested. The territory was the symptom, the full plan was the patient.
So we made a decision: stop being a revenue planning tool and become the system that connects the entire revenue plan to execution. That required a new name, because the old one described a feature. The new one needed to describe a platform.
What I Got Wrong, and We Got Right
When I started this company, I thought the primary problem was data. Revenue teams didn't have good enough data to build accurate territories. Better scoring, better enrichment, better firmographics, and the plans would improve. That was partially right, but it missed the bigger issue.
The data problem is real, but it's not the root cause. The root cause is that revenue planning is treated as an event instead of a system. You spend five weeks building the plan, you present it at kickoff, and then you execute against it for twelve months while the world changes around you.
The data can be perfect on January 1st. By March, two reps have left, a pricing change has shifted spend potential for an entire segment, and a competitor has entered your mid-market. The plan you built doesn't account for any of that, and there's no mechanism to detect the drift, let alone prescribe what to change.
What we got right from day one was the conviction that revenue planning needs to be continuous, not annual. That idea wasn't popular two years ago. Frankly, it's still uncomfortable for a lot of leaders because continuous planning sounds like continuous disruption, and nobody wants to re-carve territories four times a year.
But continuous planning doesn't mean constant upheaval. It means the system underneath your plan is always monitoring whether the assumptions you built on are still holding, and when they're not, it tells you what specifically needs to change. Re-score, don't re-carve. Adjust on material events, not on a calendar. That distinction is the difference between a plan that adapts and a plan that breaks, it's also a difference between a CRO that hits their goal or doesn't.
The Gap That Still Exists
Here's what I keep coming back to: the revenue tech stack in 2026 is remarkable at diagnosis and still fundamentally absent on prescription.
Your forecast tool tells you you're going to miss. Your pipeline tool tells you coverage is thin. Your conversation intelligence tool tells you win rates are declining. Your CRM tells you activity is down. All of that is accurate, useful data. None of it tells you what to change about the structure underneath.
The gap between "your pipeline is thin" and "here's what needs to change in your revenue structure" is where quarters get lost. It's where CROs hold meetings that produce action items instead of actions. It's where RevOps teams spend three weeks rebuilding a plan in spreadsheets that should have been updated in three days.
I've lived in that gap. At Qualtrics, I watched a territory rollout built on flawed account scoring take two quarters to diagnose and fix, not because the people were incompetent, but because there was no system to detect that the plan had drifted from reality while there was still time to do something about it. By the time the signal was clear enough to act on, the damage was already compounding.
That experience is why this company exists. Not because I wanted to build another revenue tool, but because I watched the absence of this system cost real organizations real quarters, and the problem hasn't gone away in the decade since.
Why Now
Two things have converged that make this the right moment.
First, the complexity of revenue planning has outgrown the tools available. Five years ago, a competent RevOps leader could hold the entire plan in their head and manage it through spreadsheets, Salesforce reports, and quarterly check-ins. That worked when you had 30 reps in two segments.
It doesn't work when you have reps across four segments, three geographies, and a pricing model that changed twice this year. It doesn't work when rep tenure is under two years and your ICP is shifting quarter-over-quarter. The number of variables that affect whether a revenue plan holds has grown past the point where manual processes can keep up. Not because the people running them aren't smart enough, but because the combinatorial complexity exceeds what any team can track in spreadsheets and slide decks.
Second, we've reached an inflection point in what's possible with the underlying technology. The ability to continuously monitor plan assumptions against live performance data, model the downstream impact of structural changes before you make them, and prescribe specific adjustments at the account, rep, and segment level, that wasn't technically feasible at scale even three years ago. It is now.
Those two forces, increasing complexity on the planning side and increasing capability on the technology side, are why this is the moment to build the system that should have existed a decade ago.
What Orbytal Actually Is
I've spent the last several issues of the RevOps Rocket talking about the problem. You deserve to know what the solution looks like, without this turning into a pitch deck.
Orbytal is the revenue design and execution platform. It connects the full planning sequence, from market sizing and ICP scoring through capacity modeling, headcount planning, quota allocation, and account distribution, into a single system that stays live after the plan ships.
That means when a rep leaves, you don't spend two weeks manually redistributing their book. When a pricing change shifts spend potential for a segment, the impact surfaces immediately instead of hiding inside a quarterly review. When pipeline generation drops in a region, the system can distinguish between an execution problem and a structural one, and tell you which levers to pull.
It's the prescription layer that the revenue tech stack has been missing. Not replacing your CRM, your forecast tool, or your conversation intelligence platform. Working underneath all of them, making sure the structural foundation those tools operate on is still sound.
The Honest Version
I want to end with something that isn't in most launch announcements.
Building a company through a rebrand is a specific kind of bet. You're telling the market that what you started as isn't big enough for where you're going. That's a confident statement from a company our size, and I'm aware of how it sounds.
Here's why I'm making it anyway: every revenue team I've worked with in the last two years has the same gap. They can diagnose problems with incredible precision. They cannot prescribe structural fixes at speed. The time between "something is wrong" and "here's specifically what to change" is still measured in weeks, not hours. That gap costs quarters, and quarters cost careers.
Territories.ai was always the foundation. The work we did on account distribution and territory optimization taught us how revenue plans actually break in practice, not in theory. It taught us that the problem is rooted in static planning in a dynamic market. More importantly, it taught us that the solution isn't another dashboard showing you what happened, it's a system that tells you what needs to happen next.
That's Orbytal, what we've been building toward and as of today, that's what we are.
If the problems I've been writing about in this newsletter feel familiar, if you've lived through missed quarters caused by structural drift that nobody caught in time, I'd genuinely like to hear from you. Not to sell you something, but because the best version of what we're building comes from the people who've felt the problem firsthand.
Welcome to Orbytal.
— Adam