Expansion Decisions Shouldn't Be Gut Feelings
Most local service businesses expand into new territories based on intuition: "there are lots of houses in that neighborhood" or "a competitor just left that area." These aren't bad signals — but they're incomplete.
Your existing customer database contains ZIP code data that tells you where demand is already concentrated, where you're already serving customers profitably, and where you're receiving calls you can't fulfill. That data should drive expansion decisions.
Mining Your Customer Database for Expansion Signals
Step 1: Extract ZIP codes from your customer records
Sohovi finds gaps, duplicates, and format errors in your CRM data — so your team is working from records they can trust.
Export your customer database. If your address field is structured (street, city, state, zip as separate fields), this is easy. If it's a combined field, you'll need to parse it.
Step 2: Count customers by ZIP code
A simple pivot table or COUNTIF gives you a customer density map: how many customers do you currently serve in each ZIP code?
Step 3: Cross-reference with job value
Don't just count customers — count revenue by ZIP code. A ZIP with 20 customers who book twice a year at $300 each is more valuable than a ZIP with 30 customers who book once at $100.
Step 4: Look at where requests are declining
Are there ZIP codes where you get calls but can't serve them (outside your radius)? These are natural expansion targets — demand already exists.
Adding External Data for Richer Analysis
ZIP code customer data is even more useful when you layer in:
- Population and household count: Is the ZIP code dense with single-family homes (your target) or primarily commercial/multifamily?
- Median household income: Does it match your target customer profile?
- Competitor density: How many competitors serve that ZIP code? (Google Maps is your data source here)
Tools like Google Maps, the US Census data API, or paid services like Clearbit or Melissa Data provide ZIP-level demographics.
Making the Expansion Decision
Use a simple scoring matrix:
- Customer density in your existing database: 0–3 points
- Average job value for that area: 0–3 points
- Unfulfilled requests from that area: 0–3 points
- Population/household fit: 0–3 points
- Competitor density (fewer = better): 0–3 points
Score each candidate ZIP. Expand into the highest scorers first.
This turns an intuitive decision into a data-driven one — and gives you a clear rationale to share with investors, partners, or a bank if you're financing the expansion.
The Analysis Is Only as Good as the Export
ZIP-level customer counts and revenue totals will be wrong if your address field is inconsistently formatted or your database has undetected duplicates — you'll double-count some customers and miss others entirely. Profile your customer export in Sohovi before building the scoring matrix above. The same clean export is useful for seasonal demand analysis too, since both start from the same job history data.
Sohovi automatically finds every duplicate in your dataset — including near-matches — and shows you exactly which rows are affected.
