Your sphere of influence database is the most important asset you’ll build in real estate. Agents who use a CRM to manage their database report gross commission income 40% higher than those who don’t. But a database only delivers if it’s set up right \u2014 proper fields, consistent tags, smart segmentation. This guide walks the complete SOI database setup, field by field, tag by tag.<\/p>\n
The data is stark:<\/p>\n
Your SOI database is where all of that lives. A well-built database makes nurture systematic, makes nothing fall through the cracks, and turns relationships into a predictable business. A poorly-built database \u2014 missing fields, inconsistent tags, no segmentation \u2014 produces the opposite: missed follow-ups, generic mass emails, and referral business left on the table.<\/p>\n
The setup is a one-time investment that pays for decades.<\/p>\n
Before structure, pick the tool. The 2026 options for real estate agents:<\/p>\n
Real estate-native CRMs:<\/strong> Starting point if you have nothing:<\/strong> even a well-built spreadsheet works for a database under 100 contacts. But move to a real CRM before you hit 150 \u2014 manual tracking breaks down past that point.<\/p>\n Pick one and commit. Switching CRMs is painful; choose deliberately and stay.<\/p>\n Every contact in your database should have these fields. Set the field structure up before you import anything.<\/p>\n Not every field will be filled for every contact. Fill what you know; complete more over time as you have natural touchpoints.<\/p>\n The foundational segmentation: every contact is an A, B, or C contact.<\/p>\n A Contacts (25\u201350 people).<\/strong> B Contacts (75\u2013150 people).<\/strong> C Contacts (everyone else).<\/strong> The tier drives the cadence. Set the tier field for every contact during setup.<\/p>\n Beyond tier, tags capture specifics that let you pull targeted lists. The 2026 best practice: 12 consistent, well-defined tags beat 60 inconsistent ones.<\/strong> Review and prune tags quarterly.<\/p>\n The recommended tag set for a real estate SOI database:<\/p>\n Relationship tags:<\/strong> Intent tags:<\/strong> Timeline tags:<\/strong> Neighborhood tags:<\/strong> Special tags:<\/strong> That’s roughly 12\u201318 tags, all clearly defined. Resist the urge to create a new tag for every minor distinction \u2014 tag sprawl makes the database harder to use, not easier.<\/p>\n Tier + tags together produce segments you can act on. The functional segments every real estate database should support:<\/p>\n Past Clients.<\/strong> Your highest-value long-term contacts. Monthly touchpoints plus birthday and closing-anniversary outreach \u2014 12\u201314 touches\/year minimum.<\/p>\n Active Pipeline.<\/strong> People actively buying or selling now. High-touch, high-frequency \u2014 weekly or more.<\/p>\n Nurture \/ Long-Term.<\/strong> People 3\u201318 months out or with vague future interest. Lower frequency but still regular \u2014 1\u20132 emails\/month.<\/p>\n Sphere of Influence.<\/strong> Personal contacts \u2014 friends, family, colleagues, neighbors. Relationship-maintenance cadence, not a sales sequence.<\/p>\n The principle: a past client who closed two years ago and a buyer who requested a showing today should never get the same email. Segmentation makes that possible.<\/p>\n The database is only as good as the data going into it. Set collection standards before you start:<\/p>\n Standard format for every field:<\/strong> Capture standard for new contacts:<\/strong> The weekly add habit:<\/strong> Once fields, tiers, and tags are in place, set up automation:<\/p>\n Time-based automations:<\/strong> Activity-based triggers (the 2026 standard):<\/strong> When a If you’re migrating an existing database (covered in depth in the Database Audit spoke<\/a>):<\/p>\n A database is a living asset. The maintenance rhythm:<\/p>\n Weekly (15 min):<\/strong> Monthly (30 min):<\/strong> Quarterly (60 min):<\/strong> Annually:<\/strong> Mistake 1: No CRM.<\/strong> Spreadsheets break down past 100\u2013150 contacts. Use a real CRM.<\/p>\n Mistake 2: Inconsistent data formats.<\/strong> Phone numbers in five formats, names in mixed case. Set standards before importing.<\/p>\n Mistake 3: No tiering.<\/strong> Treating all contacts the same means over-investing in C contacts and under-investing in A contacts.<\/p>\n Mistake 4: Tag sprawl.<\/strong> 60 inconsistent tags is worse than 12 consistent ones. Discipline.<\/p>\n Mistake 5: Missing the useful fields.<\/strong> Skipping “how you met,” “timeline,” “life events” \u2014 these are exactly what makes personalization possible.<\/p>\n Mistake 6: No automation.<\/strong> Manual everything fails because life gets busy. Automate anniversaries, birthdays, and overdue-touch alerts.<\/p>\n Mistake 7: Set-and-forget.<\/strong> Databases drift. Without the maintenance cadence, your database degrades over time.<\/p>\n Week 1:<\/strong> Week 2:<\/strong> Week 3:<\/strong> Week 4:<\/strong> After 30 days you have a properly structured SOI database. From there, the Sphere of Influence pillar<\/a> and the Build SOI From Zero spoke<\/a> cover the nurture cadence that turns the database into business.<\/p>\n For the database audit and cleanup process, see the Database Audit spoke<\/a>.<\/p>\n Jon Smith is a 20+ year SEO veteran specializing in real estate agent database and referral systems. He has set up SOI databases for hundreds of agents across North America.<\/em><\/p>\n Sources:<\/strong><\/p>\n SOI database setup for real estate agents \u2014 choosing a CRM, the core fields, A\/B\/C tiering, the 12-tag system, segmentation, and automation setup.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19],"tags":[],"class_list":["post-125","post","type-post","status-publish","format-standard","hentry","category-sphere-of-influence"],"_links":{"self":[{"href":"https:\/\/localrebrand.com\/blog\/wp-json\/wp\/v2\/posts\/125","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/localrebrand.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/localrebrand.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/localrebrand.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/localrebrand.com\/blog\/wp-json\/wp\/v2\/comments?post=125"}],"version-history":[{"count":1,"href":"https:\/\/localrebrand.com\/blog\/wp-json\/wp\/v2\/posts\/125\/revisions"}],"predecessor-version":[{"id":334,"href":"https:\/\/localrebrand.com\/blog\/wp-json\/wp\/v2\/posts\/125\/revisions\/334"}],"wp:attachment":[{"href":"https:\/\/localrebrand.com\/blog\/wp-json\/wp\/v2\/media?parent=125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/localrebrand.com\/blog\/wp-json\/wp\/v2\/categories?post=125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/localrebrand.com\/blog\/wp-json\/wp\/v2\/tags?post=125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n– Follow Up Boss<\/strong> \u2014 strong all-around, popular with solo agents and teams
\n– Wise Agent<\/strong> \u2014 robust, good automation, reasonable price
\n– kvCORE \/ BoldTrail<\/strong> \u2014 comprehensive, team-oriented
\n– LionDesk<\/strong> \u2014 budget-friendly, good for newer agents
\n– RealOffice360<\/strong> \u2014 SOI-focused, simpler
\n– BoomTown \/ Sierra Interactive<\/strong> \u2014 lead-gen heavy, team-oriented<\/p>\nThe Core Fields<\/h2>\n
Contact Basics<\/h3>\n
\n
Relationship Information<\/h3>\n
\n
Transaction History (for past clients)<\/h3>\n
\n
Life Stage Indicators<\/h3>\n
\n
Communication Log<\/h3>\n
\n
Future Plans<\/h3>\n
\n
The Three-Tier Segmentation (A \/ B \/ C)<\/h2>\n
\nYour closest relationships and highest referral potential. Recent past clients who refer. Close friends and family. Top vendor partners. The people who’d show up to your major life events.
\n– Contact frequency: personal touch at least quarterly, ideally more
\n– Touches per year: 36+<\/p>\n
\nWarm relationships, regular but less intensive contact. Past clients (not necessarily active referrers). Acquaintances you see semi-regularly. Vendors you work with periodically.
\n– Contact frequency: personal touch every 4\u20136 months
\n– Touches per year: 24\u201336<\/p>\n
\nPeople who know you but with less regular contact. Older past clients. Casual acquaintances. Newsletter subscribers.
\n– Contact frequency: a few personal touches per year via market updates and community content
\n– Touches per year: 12\u201318<\/p>\nThe Functional Tags<\/h2>\n
\n– past-client<\/code>
\n– sphere<\/code>
\n– vendor-partner<\/code>
\n– referral-source<\/code><\/p>\n
\n– buyer-interest<\/code>
\n– seller-interest<\/code>
\n– investor<\/code><\/p>\n
\n– active-pipeline<\/code> (transacting in the near term)
\n– nurture-3-18mo<\/code> (interested but not imminent)
\n– long-term<\/code> (no near-term plans)<\/p>\n
\n– One tag per priority neighborhood (e.g., stapleton<\/code>, park-hill<\/code>)<\/p>\n
\n– do-not-email<\/code> (for contacts who only want personal touches)
\n– vip-event-list<\/code> (for client appreciation event invites)<\/p>\nThe Segmentation Layer<\/h2>\n
Data Collection Standards<\/h2>\n
\n– Phone: one consistent format (e.g., (303) 555-0100)
\n– Name: First and Last in separate fields, properly capitalized
\n– Address: consistent abbreviation choices
\n– Dates: consistent format<\/p>\n
\nWhen you add a contact, capture at minimum: full name, phone, email, how you met, and where they are in their real estate timeline. The “how you met” and “timeline” fields are the ones agents skip \u2014 and they’re the most useful for personalization later.<\/p>\n
\nAdd 2\u20135 new contacts per week, immediately tagged and tiered. Over a year, that’s 100\u2013250 new SOI members. Set a recurring Friday calendar block.<\/p>\nAutomation Setup<\/h2>\n
\n– Closing anniversary email (triggers on the anniversary date field)
\n– Birthday email (triggers on the birthday field)
\n– Monthly newsletter to the full active database
\n– Overdue-touch alert (flags when an A contact hasn’t been touched in 60+ days)<\/p>\n
\nThe most effective 2026 CRM workflows combine time-based check-ins with activity-based triggers that fire when a contact:
\n– Visits your website
\n– Fills out a form
\n– Engages with a social post
\n– Opens\/clicks emails repeatedly<\/p>\nnurture-3-18mo<\/code> contact suddenly visits your home valuation page three times in a week, an activity trigger should flag them for personal outreach \u2014 they may have moved from “long-term” to “active.”<\/p>\nThe Import Process<\/h2>\n
\n
Maintenance Cadence<\/h2>\n
\n– Add 2\u20135 new contacts
\n– Tag and tier new additions
\n– Log any field updates from the week’s interactions<\/p>\n
\n– Review contacts with no recent contact
\n– Update tags as contacts’ situations change
\n– Verify recently-added emails<\/p>\n
\n– Tag audit \u2014 prune unused tags, fix inconsistent ones
\n– Tier review \u2014 should anyone move up or down?
\n– Full email verification on the quarter’s additions
\n– Review automation performance<\/p>\n
\n– Full database audit (the deep clean)
\n– Re-segmentation review
\n– Archive truly dead contacts<\/p>\nCommon Database Setup Mistakes<\/h2>\n
Your Setup Plan<\/h2>\n
\n– Choose your CRM
\n– Set up the field structure
\n– Define your 12\u201318 tags
\n– Define A\/B\/C tier criteria<\/p>\n
\n– Run the database audit \/ import process
\n– Tag and tier every contact
\n– Standardize data formats<\/p>\n
\n– Set up time-based automations (anniversary, birthday, newsletter, overdue-touch)
\n– Set up activity-based triggers
\n– Test all automations<\/p>\n
\n– Establish the weekly add habit
\n– Set up the maintenance cadence on your calendar
\n– First full month of operation<\/p>\n
\n\n