Case study · Operations console
Type a ZIP, a site, a rep or an account. Get the answer, not a phone call.
A multi-region sales team kept its reps, accounts, sites and territory maps in separate spreadsheets. Finding out who covered a ZIP code, or which accounts sat near a site, meant knowing which file to open — or calling someone who did. Now one search box answers it, for more than twenty people across the country.
A custom web console for a B2B sales team at a national retailer — resolves any state, city, ZIP, site number, market code, rep or account, works out which you meant, maps it, and pulls its data. Filtering, radius search, route building and export built in.
See it for yourself
A working demo of the console on invented data. Every company, person, address, phone number and figure in it was generated — nothing belongs to a real organization.
Open the live demo →Try typing a state, a ZIP code, a city, or a rep’s name into the search box and watch it work out what you meant.
Why a sales team outgrows the spreadsheet
None of the information was missing. It was just in several different places, each one maintained by a different person, each one with its own idea of what a territory was called. So a simple question turned into a small project:
Who covers this ZIP?
Open the territory map, find the ZIP, read across to the region and pod, then open the roster to find the people in that pod. If the map was stale, ask around.
Which accounts are near this site?
There was no way to ask. Reps pulled account lists, sorted by ZIP, and guessed at distance.
What’s the market code for this city?
Sites, market codes and cities lived in one file; the people responsible for them in another. Matching them up was a lookup in each.
Where is that file, again?
Every rep kept their own copies. The newest version was on somebody’s desktop, and the fastest way to find anything was to call the one person who knew.
Multiply that by twenty-plus people and every working day. The cost wasn’t one big number; it was hundreds of small interruptions — time spent tracking down information instead of using it, and a lot of “quick question” calls to the same few people.
What the console does
One page, one search box. Type whatever you have — a state, a city, a ZIP, a site number, a market code, a rep’s name, an account — and the console works out what kind of thing it is, shows it on the map, and pulls everything connected to it.
Universal search
Territories, sites, accounts and people in one box. Ambiguous input — a number that could be a ZIP or a site — is resolved, not rejected.
Every ZIP mapped
Each ZIP code carries its region and pod, and the people who cover it. The territory map is one place of truth, not a file that drifts.
Account filtering
Narrow accounts by industry, region, ZIP and volume, or draw a radius around any point and see what falls inside it.
Route building
Build a route from any starting point and export it as a CSV, ready for the day’s calls.
Nothing to install
It is a web page. Open the link on a laptop or a phone and it works; there is no software to roll out and nothing to update on anyone’s machine.
Data in one place
Reps, accounts, sites and territories are loaded once and shared by everyone. When the roster changes, it changes for all twenty-plus users at the same time.
Three decisions that made it useful
One box, not a form
The first instinct is a search form with a dropdown for “what are you searching for.” Reps don’t think that way; they have a ZIP on a business card or a site number from a call. So the console takes whatever is typed and figures out the type itself. That one choice is most of why people actually use it.
Show the map, not just the row
A territory answer that says “Pod 3” is correct and useless. Seeing the ZIP shaded on a map, with the neighbouring territories and nearby accounts, is what turns a lookup into a plan for the day.
Built from the team’s own files
The console is built from the rosters, account lists and territory tables the team already maintained. Nobody had to learn a new way of keeping data — the change was that only one copy exists now, and everyone reads from it.
What changed
- Reps stop tracking down information and start using it. The hours saved are spread across twenty-plus people and every day, which is exactly the kind of cost that never showed up on a report and never went away.
- Nobody has to remember where a file lives, whose copy is current, or who to call. The answer is at their fingertips, from any device, in a few seconds.
- The people who used to field the “quick question” calls get their day back too.
- New reps are productive faster: the console is the map of how the team is organised, and it is the same for everyone.
“Having all the data at your fingertips, without struggling to remember where it’s stored, is priceless.”
How it was built, and what it costs to run
A single-page web application: the map, the search and the data views all run in the browser. There is no server to maintain and no per-seat licence, and hosting at this size costs nothing to run.
Because the data is in one place, updating it is a change in one place, not a project. A new rep, a moved territory or a changed market code is live for everyone at once.
Nobody assigned it. It started because those questions kept arriving at my desk, and answering them one at a time was never going to fix the problem. It has taken many personal hours and a fair amount of my own expense over several months, and it is still being refined — which is the honest version of how tools like this actually get made.
The team’s data stays private
The real console holds real accounts and real people, and it is available only to the team that uses it. Nothing about the client appears on this site without their say-so, which is why this page names no company and the demo is built entirely from invented data.
Where else this fits
Any team that has to answer “who covers this?” or “what’s near that?” from a set of spreadsheets:
- Field sales and merchandising teams organised by territory
- Service and installation dispatch across regions
- Franchise and dealer networks with territory rights
- Nonprofits and churches coordinating volunteers by area
- Property, route and delivery operations
More case studies
Volunteer Safety App: 100+ volunteers, three campuses, works with no signal →
Lead Routing: 2 to 3 people, 3–4 hours a day → 1 person, 5 minutes →
Got a team that runs on a stack of spreadsheets and one person who knows where everything is?
Thirty minutes, no charge, no deck. We look at where the time goes and whether there is something here worth building.
Book a free 30-minute call Tell me about your project