Financial Software Company Maps Territory Planning Success With Sales Cloud
FinancialForce was planning account distribution and assignment in spreadsheets, which made every territory change a labor intensive exercise for the sales operations team. We delivered a Sales Cloud solution that overhauled the process, built on a Salesforce Enterprise Territory Management implementation with automated assignment rules and Territory Planning for modeling. The spreadsheet is gone, territories are optimized and balanced across North America, Latin America, EMEA, and APAC, and labor hours spent on the territory planning process fell 75%.
A Financial Software Company Planning Global Territories in Spreadsheets
FinancialForce sells financial software across four regions, which means account distribution is a recurring problem rather than a one-time decision. Territories shift as the business grows, reps join and leave, segments get redefined, and every one of those events raises the same question of who owns which accounts.
Doing that in spreadsheets works right up until it does not. A spreadsheet holds the plan but not the system of record, so every change becomes two jobs, deciding what should happen and then making it happen in Salesforce. At the scale of four regions the reconciliation between the two is where the hours go, and it is also where the errors live, because a territory that exists in the plan but not in the CRM is a set of accounts nobody is working.
The Challenge: Take Account Distribution Out of the Spreadsheet
FinancialForce came to us needing to do four things:
• Plan account distribution and assignment without spreadsheets
• Reduce the labor intensive elements of account distribution and planning
• Create plans for change management when introducing a new system and new processes to the sales operations team
• Develop a standard process for managing edge use cases in account assignment
The first two are about the tool and the second two are about the people using it. That combination is what makes territory work hard to fix. A better system that the sales operations team does not adopt changes nothing, and a system that handles the common cases but leaves every exception to manual judgment recreates the spreadsheet by another name.
Our Approach: A Salesforce Enterprise Territory Management Implementation, With the Rules Built In
We implemented Salesforce Enterprise Territory Management as the foundation, inside FinancialForce’s Sales Cloud environment. That put territory structure into the system of record rather than alongside it. A territory became an object with a definition, a hierarchy, and accounts attached to it, which is the difference between describing a plan and running one.
We advised on Territory Planning best practices alongside the build. FinancialForce had years of accumulated logic about how accounts should be split, and some of it was worth keeping and some of it existed only because a spreadsheet made it easy. Separating the two before configuring anything is what kept the new structure clean.
We then created assignment logic and rules for automated account assignment within territories. This is the piece that removed the recurring labor. Accounts land in the right territory because the rules put them there, so a new account or a changed attribute no longer starts a manual sorting exercise. It also gave the team a defined way to handle the edge cases they had asked about, since an exception written into a rule is an exception the whole team applies the same way.
For modeling, we used Territory Planning to lay account segments out on a map. The sales operations team can carve out a region, create a new territory, or reallocate resources and see the effect before committing to it. Planning on a map instead of in rows is a different kind of work, because balance and coverage are visible properties of a map and invisible properties of a spreadsheet.
With that in place we eliminated the spreadsheet from account planning and distribution entirely, and optimized and balanced territories across North America, Latin America, EMEA, and APAC. Four regions balanced against one another is a problem worth solving in a system, because a change in one region has consequences in the next, and the Salesforce Enterprise Territory Management implementation is what made those consequences visible while the change was still a draft.
Tools and Products Used
This build centered on Sales Cloud and two territory capabilities within it:
• Salesforce Sales Cloud: the platform the territory structure and account assignment now live in
• Salesforce Enterprise Territory Management: implemented as the foundation for territory structure, hierarchy, and account ownership
• Territory Planning: used to model account segments on a map, carve out regions, create new territories, and reallocate resources
• Assignment logic and rules: automated account assignment within territories, including a standard path for edge cases
Enterprise Territory Management holds the structure, the assignment rules keep it populated, and Territory Planning is where changes get tested before they are made. The three together are what replaced the spreadsheet.
The Results: 75% Fewer Labor Hours on Territory Planning
Labor hours spent on the territory planning process fell 75%. The automated assignment rules account for most of that. Work that used to mean opening a spreadsheet, deciding where each account belonged, and then repeating the decision inside Salesforce now happens once, in the system, according to rules the team agreed on in advance.
The modeling work explains the rest. When a territory change can be drawn on a map and reviewed before it is committed, the planning cycle stops including the round of corrections that follows a change made blind. Fewer corrections is fewer hours.
The structural result is that territories across North America, Latin America, EMEA, and APAC are optimized and balanced against each other rather than maintained separately. That is only possible once all four sit in the same system with the same rules, which is what the spreadsheet made impossible.
| Area | Outcome |
| Territory planning | 75% reduction in labor hours spent on the territory planning process |
| Account assignment | Automated assignment logic and rules place accounts within territories |
| Planning method | Spreadsheet eliminated from account planning and distribution |
| Global coverage | Territories optimized and balanced across North America, Latin America, EMEA, and APAC |
| Modeling | Territory Planning used to model account segments on a map and carve out regions or reallocate resources |
Territory Planning Belongs in the System That Owns the Accounts
Most sales operations teams plan territories somewhere other than their CRM, then spend the following weeks making the CRM match. The gap between the two is where the hours go, and it is also where coverage quietly breaks.
FinancialForce closed that gap by moving the planning into the platform that already owned the accounts. The plan and the assignment became the same action, and the sales operations team got their weeks back.
If your territory planning still runs on a spreadsheet that never quite matches Salesforce, our team can help. Get in touch to talk through what a Salesforce Enterprise Territory Management implementation would look like for your sales operation.
