What it does. You drop a pin, pick a drive time, and it draws the area you can actually reach by car in that many minutes, then estimates how many people live inside it. Filter by age, sex, and income, or draw a shape to exclude an area you don't care about.

What's under the hood. Three services, stitched together:

• Drive-time area comes from a real road network with predictive traffic, so the shape follows real roads, not a lazy circle. Pick a traffic level (Low, Medium, High) and it models a Sunday morning, a weekday midday, or a weekday 5pm rush hour from 90 days of historical traffic. The reach visibly shrinks as traffic climbs, and it fingers out along freeways because that's where you actually get far, leaving holes over places you can't reach in time (steep hills, parkland, water).
• Population comes from U.S. Census neighborhood data. The tool pulls every census neighborhood near your area and counts the ones whose center falls inside the drive-time shape.
• Address search uses open mapping data (OpenStreetMap).

Honest limitations. The population figure is a solid estimate, not a headcount. Because it counts a neighborhood as in or out based on its center point, the total is accurate to within a few percent, which is the right tradeoff for sizing a market. Traffic is predicted from historical patterns for the day and time you pick, so it's a typical Sunday morning or a typical Tuesday rush hour, not a live feed of this exact minute. And the numbers run conservative on purpose: a rush-hour reach can be well under half its off-peak size, because the model actually respects the chokepoints (a backed-up bridge or tunnel really does cut you off). That's the point. It's more honest about how far you really get when the roads are full.

Built by a fractional COO. I made this in a couple of days because a client needed to answer one question: how many people can actually reach a location I'm scouting. That's the job, taking a fuzzy operational question and turning it into a tool that answers it. If you're running a business and there's a number you keep guessing at, a workflow that eats your week, or a report you rebuild by hand every month, that's the kind of thing I build.

A map like this looks finished, but really it's a starting point. Once the data is flowing, the shape on the screen is the least of what it can do. Here are a few places I've taken tools like this for people running actual businesses. Any one of them could be your version.

Pick the best location instead of just measuring one. Right now you check a single spot. Hand it a list of ten addresses instead and it scores every one, how many people can reach it, what they earn, whether a competitor is already sitting on top of it, then ranks them. You stop arguing over which storefront to sign and just look at the list.

See where your competitors leave the door open. Put your locations and theirs on the same map. It shades where their reach overlaps yours, and the part that matters more, where nobody is serving anyone at all. Those empty pockets are usually where the next location should go, and most people never see them because they've never had them drawn out.

Make it a report that runs itself. A number like this usually gets pulled once and then quietly goes stale. This version can re-run on its own every month, email you a clean one-page summary, and poke you when a market has shifted enough to care about. Nobody has to remember to check anything.

Connect the data you already have but can't see together. Your bookings live in one system, your customer list in another, this map in a third. When they don't talk, a question like "which neighborhoods actually bring me money" just gets a shrug. I pull them into one place so it gets an answer.

The map is just the example I happened to build. The real work is the same either way: you describe the thing you keep guessing at or redoing by hand, and I figure out how to make it answer itself. If you've got one of those, let's talk.