Build it with AI
Build the operating layer your sales team needs without buying another rigid suite.
Create focused software for territories, pipeline, approvals, handoffs, forecasting, and manager workflows.
Introduction
What a sales operations platform has to hold.
Most teams end up with a sales operations platform the same way: territory rules in a spreadsheet, approvals in email, and handoffs that depend on someone remembering. Each tool was the right call when it was bought. The cost appears when a territory change has to be made in four places, and the person who knows all four is the constraint on every organisational change.
Every process the CRM does not model gets a spreadsheet, and the spreadsheets are where the handoffs quietly fail. There is no place where a territory, a quota, and an approval threshold are defined once, and no record connecting a rule to the systems that are supposed to enforce it.
What follows covers building a sales operations platform: the records it holds (territories, quotas, approval requests, handoffs between roles, and the state of each), the systems it reads (Salesforce and HubSpot), and what it does not fix.
The problem
Six point tools and a spreadsheet holding the seams together.
Suites solve the seams by owning everything, which is why the parts you did not want are the parts you cannot remove. Point tools each do one thing properly and push the integration cost onto whoever owns the spreadsheet in the middle.
The records are territories, quotas, approval requests, handoffs between roles, and the state of each, and the authoritative copy of most of them already lives in Salesforce or HubSpot. Territory assignments in the CRM, the commission sheet, and the routing rules diverge after every reorganisation, and the divergence is discovered when a rep is paid on a deal that was not theirs.
The cost is not the inconvenience: a discount sits unapproved while the customer's buying window closes.
You're likely here because
- A reorganisation takes weeks because nobody knows every place a territory is defined
- Every process the CRM does not model gets a spreadsheet, and the spreadsheets are where the handoffs quietly fail.
- When it is wrong, a discount sits unapproved while the customer's buying window closes
What gets built
Launch builds it, Grow operates it.
Built in Launch
- • Territory tools
- • Approval workflows
- • Manager dashboards
Operated through Grow
- • Prospecting
- • Follow-up
- • Pipeline actions
Systems it reads
- • Salesforce
- • HubSpot
- • Slack
The record model
What the rules layer holds.
- Territory definition with an effective date
- Rules change and commission disputes are settled against the rule that applied at the time, which means the current value alone is not enough to answer the question.
- Quota and its period
- Held with the plan version, so a mid-year adjustment can be reconstructed rather than argued about from recollection.
- Approval threshold and delegate
- The delegate is the field always omitted and always needed. Without it, one person on leave becomes a two-week stall in every deal above the threshold.
- Rule version history
- Every previous value with its dates. This is the single field that resolves most commission disputes and it is the one no spreadsheet keeps.
- Handoff payload definition
- What the receiving team requires at close. Without it the handoff is a notification and the receiving team reconstructs the context three weeks later.
- Assignment history per account
- Who owned it when, so a deal that closed after a reorganisation is attributed to whoever owned it during the cycle rather than after it.
- Rule owner
- A named person per rule type. Rules with no owner are the ones that survive three reorganisations without anyone being able to say why.
How it runs
From tool sprawl to one operating layer.
Step 01
Describe what a sales operations platform has to do
Start from the rules rather than the tools: who owns which accounts, what needs approval at what threshold, and what happens at each handoff. Those rules are what the platform holds.
Step 02
Connect the systems of record
The CRM stays the system of record for deals, and the operating layer reads it while owning the rules applied on top — territories, thresholds, and routing that the CRM models weakly or not at all.
Step 03
Build the operating surface
Territory definitions, approval workflows with thresholds and delegation, handoff queues, and manager views — generated as one application rather than assembled from four settings panels.
Step 04
Start narrow
Territory definition in one place, with the CRM reading from it. That single change removes the most expensive recurring reconciliation in most sales organisations.
Step 05
Route the exceptions
An approval sitting past its threshold escalates to the delegate rather than waiting, which is the difference between a workflow and a queue of things blocked on one person’s holiday.
Step 06
Measure time an approval waits before someone chases it
Time to execute a territory or quota change end to end, measured from decision to every system reflecting it. That figure is the honest measure of sales ops overhead.
Implementation path
Consolidating sales ops without a big-bang migration.
- 01
Inventory every place a territory, quota, or approval threshold is currently defined. The count is usually higher than anyone expects and is itself the argument for the project.
- 02
Baseline the time to execute a reorganisation and the error rate after the last one — deals mis-assigned, commissions corrected retroactively.
- 03
Consolidate one rule type at a time, starting with territories, and have the other systems read it. Consolidating rules and migrating data at once is how these projects stall.
- 04
Keep the previous definition readable for a full commission cycle after each change, because compensation disputes are resolved against what the rule was at the time.
- 05
Build the narrowest useful version first: the single approval step that most often stalls, with the pending approver named and the clock visible.
- 06
Inventorying every place a territory, quota, or threshold is currently defined takes a day and is usually the argument for the project on its own. Consolidating territories alone — defined once, read by the CRM — is a two to three week build and delivers the largest single reduction in reorganisation cost. Do not consolidate rules and migrate data in the same change.
- 07
After territories, approval thresholds with delegation are the next highest-value rule to consolidate, because the failure mode — a request stalled on one person’s absence — is both common and entirely avoidable. Handoff payloads follow.
Controls
Controls that matter.
Control 01
Rule changes versioned with an effective date, so a commission dispute can be settled against the rule that applied when the deal closed
Control 02
Approval thresholds and delegation paths defined once and enforced by the system rather than restated in a policy document
Control 03
Change history on territory and quota records retained beyond the current period, since the questions about them arrive after the period has closed
Examples
Three seams that stop leaking.
The January reorganisation
Territories defined once and read by the CRM turns a multi-week coordination exercise into a change with an effective date, and removes the class of commission dispute caused by two systems disagreeing about who owned an account in week three.
The discount that needed a VP
Approval thresholds with delegation mean an out-of-policy discount routes to whoever is actually available, with the deal context attached, rather than sitting in an inbox until somebody chases it.
The handoff to customer success
A modelled handoff with a required payload means the receiving team gets what they need at close rather than reconstructing it from the opportunity record three weeks later.
How it goes wrong
Three ways consolidation goes sideways.
The platform starts holding its own copy of accounts, and becomes the seventh system rather than the layer that connected six.
Own rules, read records. The boundary has to be explicit and defended, because every individual case for copying one more field is reasonable and the aggregate is a new silo.
One team keeps a private territory sheet, and the consolidated definition quietly becomes advisory.
Consolidation without adoption is documentation. Either the CRM reads the definition and enforces it, or the reconciliation returns within two quarters with more places to check than before.
Commission calculation is absorbed because it was nearby, and the system acquires an audit obligation nobody agreed to.
Hold the rules and display the resulting figures; leave what people are paid where it already lives. Becoming the system of record for compensation is a decision with legal weight and should be entered deliberately rather than by feature creep.
Limitations and considerations
What consolidation does not simplify.
- Consolidating rules does not reduce the number of systems holding data. The CRM, the billing system, and the commission tool all remain; what changes is where the rules live and how many places have to be edited.
- Commission calculation carries legal and contractual weight. Reading and displaying it is straightforward; becoming the system that computes what people are paid is a decision with an audit obligation attached.
- A rules layer is only as good as its adoption. If one team keeps a private territory sheet, the consolidated definition becomes advisory and the reconciliation returns within two quarters.
- Under about fifteen sellers, the rules fit in one person’s head and a shared document is proportionate. If the last reorganisation was painless, the cost this removes is not one you are currently paying, and the project will be judged against a problem nobody feels.
- Connector coverage varies: Salesforce, HubSpot, Slack are representative rather than guaranteed, and the fields exposed depend on your workspace permissions.
FAQ
Build a sales operations platform with AI: common questions.
Does the CRM stay the system of record?
Yes. The CRM keeps accounts and opportunities. What moves is the layer of rules on top — territories, thresholds, routing, handoffs — that CRMs model weakly and that consequently ends up spread across spreadsheets and settings panels.
Where should we start?
Territories, almost always. It is the rule most often duplicated, the one whose divergence is most expensive, and the one where a single authoritative definition produces a visible result inside one reorganisation cycle.
Can it calculate commission?
It can hold the rules and show the resulting figures, which resolves most disputes. Becoming the system of record for what is paid brings audit and contractual obligations that should be entered deliberately rather than by feature creep.
How do we avoid building another silo?
By making the operating layer read rather than copy. It owns rules and reads records; the moment it starts holding its own copy of accounts, it becomes the seventh tool rather than the layer that connected the six.
What should the first version contain?
The single approval step that most often stalls, with the pending approver named and the clock visible. Everything else waits until that one is genuinely used.
How will we know whether it worked?
Measure time an approval waits before someone chases it against the baseline taken before anything changed.
Start with ARIA
Ask ARIA to build it.
Describe the website, application, workflow, or operating surface you need. ARIA plans, connects, builds, tests, and keeps refining it — inside the permissions you set.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Build a sales operations platform around the process you actually run.
Consolidate the rules rather than the data, start with territories, and measure the time it takes to execute a reorganisation.