FlowsBook a callSign inCreate free accountSign up
Business and places data

The difference between a place and a company in business data

A place is a spot on the map; a company is who owns it. Why mixing the two inflates counts, sends reps to the wrong door and breaks CRM imports, and how to keep them apart.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

A place is somewhere you can stand: a shop, a branch, a clinic, a depot, with an address and a position on the map. A company is the organisation behind it: the business that owns, runs or franchises one place or hundreds. Location data is built from places. Sales, finance and CRM systems are built around companies. Most confusion in business data comes from treating one as the other, so it is worth knowing which you are holding before you count, call or import.

This article is for anyone who works with lists of businesses: sales operations, marketing, analysts and the people who load lists into a CRM. It explains how the two differ, where each kind of data comes from, three made-up situations where mixing them goes wrong, and the blocks in xMap Flows that turn a list of places into a list of companies and back.

Places: what location data is made of

A record in xMap's places database is one point of interest: a name, a category, an address, a position, a phone and website when known, a rating and reviews, an opening date when known, and a brand when the place belongs to a chain. Two branches of the same bakery are two records. A franchise outlet, an outlet the brand runs itself and an independent shop that happens to share a name all look alike at first: each is a place.

That is exactly right for questions about the ground: how many pharmacies are within a short walk, where a chain is missing, which street has the most cafes. It is the wrong unit for questions about buying decisions.

Companies: what sales and finance think in

A company has a legal name, a website domain, people, a head office and a way of buying. One company can have many places (a supermarket group), one place (a family restaurant), or none that a customer would visit (a software firm in shared offices, an online shop). Job postings are company data: an employer posts a role and a city, and the position you get back is often the city centre, not a building.

PlaceCompany
Counted byLocations on the mapOrganisations
Key for matchingPosition, address, place idWebsite domain, legal name
Good forCoverage, gaps, density, routesAccounts, contracts, contacts, revenue
Typical source in a flowNearby places, Map business scanJob postings, Apollo, your CRM

How the two units differ in practice.

How big the difference can be

Chains make the gap concrete. xMap's places database lists 622 cafes within 10 km of the centre of Toronto (November 2026). Of the 312 nearest the centre, 47 belong to a chain, and the biggest chain among them, Aroma Espresso Bar, has 13 of those places. For someone mapping coffee supply, that is 13 places. For someone selling coffee machines, it is one company, probably one buyer, and possibly a supplier contract that covers all 13.

Pharmacies show it even more. xMap's places database lists 866 pharmacies within 10 km of the centre of London (November 2026); of the 438 nearest the centre, 91 belong to a chain, and 38 of those to the biggest brand alone. A rep who calls each branch of that brand separately is making dozens of calls to people who cannot sign.

Three ways mixing them goes wrong (made-up cases)

  • The inflated market. A team sizing a market in Lisbon counts 400 gyms and plans for 400 customers. Say a third of them belong to four groups: the real number of buyers is closer to 270. The figures here are invented, but the pattern is common.
  • The wrong door. A rep in Cape Town visits a franchise outlet to sell a payment terminal. The franchisee wants it, but the franchise agreement names the terminal supplier. The decision sat with the franchisor all along.
  • The duplicated account. An import from a place list into a CRM in Mexico City creates 30 accounts for one restaurant group, each with a different branch phone number. The group's buyer receives 30 emails in a week.

Turning places into companies

In a flow you can move from one unit to the other on purpose.

  1. Find the places with Nearby places or Map business scan: each comes with a brand and whether it belongs to a chain.
  2. Split the list with a Filter or Branch on the chain field: independents go straight to local reps, chains go to an account list.
  3. For the chains, Remove duplicates on the brand or the website keeps one record per company; a Calculated field can keep how many branches it had in the area.
  4. Apollo, from your own Apollo account, matches each company by its website and adds its details and the people who decide.
  5. Match with my table checks each company against your CRM export by website, so existing accounts are skipped.

Turning companies into places

The opposite move matters too. A list of target companies from your CRM says nothing about where they operate. Upload it to My data and Map business scan, set to look up each place itself, finds each one on online maps with its address, phone and position, so territory planning and visit routes can work from it. For companies hiring, Job postings gives the employer and the city; treat that position as a city, not a building.

AI employees that keep the two straight

Several ready-made templates in xMap Flows are built around this split. Supermarket chains to list my sauces keeps one record per chain and finds its category buyer. Decision makers at new cafes goes from new places to the person to call. Prospects not yet in my CRM compares with your existing accounts, and Companies hiring near you starts from companies and finds their places.

The Learn pages on chain versus independent and deduplication go deeper on the two steps that matter most.

Questions

Is a franchise outlet a separate company?

Legally it often is: the franchisee owns the business. Commercially, many decisions (suppliers, systems, branding) are made by the franchisor. Treat the outlet as a place and check who buys before you treat it as an account.

Why do job postings show the city centre instead of an address?

Employers usually post a role in a city, not at a building. The position is the city's, so use it to filter by area, not to plan a visit.

What is the best key for matching companies across lists?

The website domain. Names change between branches and languages, phone numbers differ per branch, but most companies keep one domain.

Should I import places or companies into my CRM?

Import companies as accounts and keep places as their locations, or as a field with the branch count. Importing every place as an account creates duplicates for every chain.

Templates that do this

Read next

More on business and places data · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.