How Many Contacts Do You Need in Your Sphere to Close 12 Homes a Year?

How many contacts do you need in your sphere to close 12 homes a year?

Roughly 300 real contacts, worked from two verifiable numbers instead of a round-number guess: a national annual mover rate and the share of sellers who use a referral or repeat agent. The exact math is below, with every input sourced and dated, so you can check it against your own list size rather than take a nice-sounding number on faith.

Working sphere: the subset of your full contact database that you actively track and contact on a schedule, distinct from every name that has ever ended up in your phone or a past CRM export.

Where does the "300 contacts" number actually come from?

Two dated figures do the actual work here. The U.S. Census Bureau's 2024 geographic mobility release put the national annual mover rate at 11.8% of the population moving between 2023 and 2024 (Census Bureau, 2024). Separately, NAR's 2025 Profile of Home Buyers and Sellers found that 66% of sellers found their agent through a referral or an agent they'd worked with before (NAR, 2025).

Multiply them against a sphere of 300 people. Take 300 contacts and apply the 11.8% annual mover rate: about 35 people in that sphere will buy or sell somewhere in a given year. Apply the 66% referral-or-repeat share to that group of 35 movers and the math lands around 23 transactions your sphere touches annually, some closed directly and others handed to you as a referral. Twelve homes a year out of that 23-transaction pool is a plausible outcome for an agent who stays in front of that sphere consistently. It is a range this arithmetic supports, never a guarantee the arithmetic alone can deliver.

Run the same two rates against your own list size and the number changes proportionally. That's the entire value of showing the math in the open: an agent with a 150-contact sphere can see exactly why their pipeline looks thinner than a colleague working 600, instead of wondering if something less visible is wrong with their approach.

One honest limit on this math: the Census mover rate counts every kind of move, including renters who never buy or sell through an agent. Treat the 35-mover figure as an upper bound on how many people in a 300-contact sphere relocate in a given year, with the real number of agent-relevant transactions somewhat smaller once renters are excluded. The post keeps the simpler version because a precise renter-versus-owner split isn't published at this granularity, and an honest approximation beats a false precision the data doesn't actually support.

Is a bigger sphere always better?

Quality outperforms raw count every time this gets tested against real numbers. A database of 3,000 names nobody has spoken to in three years produces fewer closings than a tracked list of 300 people who get a real touch on a regular schedule, because the math above only works on contacts who still know you're in real estate. An untouched name sits in a spreadsheet. A worked contact sits in your pipeline.

This shows up constantly in practice: agents inherit or purchase a large list, run one mass email, and conclude their sphere "doesn't convert." The 3,000 names were never a working sphere to begin with. A working sphere is the subset that actually gets a call, a text, or a handwritten note on a cadence, and that subset is almost always smaller than the full database an agent thinks they have.

What's the difference between your database size and your working sphere?

Your database is every name that has ever entered your systems: past clients, old leads, expired contacts, someone you met once at an open house three years ago. Your working sphere is the smaller, deliberately maintained group inside that database that you commit to contacting on a real schedule, because they're the people most likely to move, refer, or hire you again. A database of 4,000 rows might contain a working sphere of only 250 people; the other 3,750 rows are worth cleaning up eventually, but they don't belong in this math until they've been re-engaged and added back into the tracked group.

This distinction matters because the 300-contact math in this post holds specifically for a working sphere. Running the same math against a full, untended database instead of the actual worked subset overstates what to expect, which is exactly how "sphere marketing doesn't work for me" complaints usually start.

How do you find out how big your working sphere already is?

Most agents have never actually counted their contacts in one place and are surprised by the real number once they run it. The count takes four steps:

1. Export or scroll through your phone contacts and flag anyone you'd genuinely call a past client, friend, family member, or regular referral source.
2. Add email and social media connections that overlap with that same group, since a lot of real relationships live in inboxes and DMs rather than a phone's contact list.
3. Pull any old CRM exports or spreadsheets from prior brokerages and merge them in, watching for duplicates.
4. Cross-check the merged list against your actual closed-transaction history so every past client is represented, even the ones who never made it into a phone contact.

Getting contacts out of your phone, Gmail, and old CRMs walks through the mechanics of pulling that list into one place before you run the count.

Is a smaller-than-300 sphere still worth working?

Yes, and the same math simply scales down. A sphere of 150 contacts at the same 11.8% mover rate and 66% referral share points to roughly 12 touched transactions a year instead of 23, still a meaningful pipeline for an agent building from scratch or early in their career. The ratio holds regardless of starting size; a new agent with 80 contacts sees a smaller number, and that number grows as the sphere grows and gets worked consistently. Run your own count through the sphere calculator to see the math at your actual list size instead of the 300-contact example used throughout this post.

Sphere size versus estimated annual transactions

Sphere size	Estimated annual movers (11.8%)	Estimated referral/repeat transactions (66% share)
100	~12	~8
300	~35	~23
600	~71	~47

These figures are directional estimates built from two cited, dated rates, describing what a sphere of that size touches in a typical year. What any individual agent actually closes depends heavily on relationship quality and contact consistency, factors the arithmetic alone can't capture.

Does cadence matter more than the count?

Cadence is what converts this arithmetic into real closings instead of a number sitting on a page. The weekly sphere touch plan covers exactly who gets a call or text each week once you know your sphere's actual size, and it's worth reading right after you run your own count. See the complete sphere-of-influence system for how sizing, tiering, and cadence work together as one system rather than three separate tactics.

Agents ask me for the magic number constantly, as though 300 were a fixed target everyone has to hit before their sphere counts for anything. Running these numbers with agents for years has shown me the same pattern every time: a 150-contact sphere worked every single week outproduces a 600-contact sphere worked twice a year, by a wide enough margin that list size stops being the interesting variable. The number in this post exists to make the arithmetic legible, giving you a way to sanity-check your own pipeline expectations against a real sphere size instead of a hunch. It says nothing on its own about whether the list actually gets called, texted, or shown up for, and that's the part the math can't do for you.

Run your own numbers against your actual contact count to see where you land.