What a team actually is (and the roles inside one)
Legally, a team lives inside a brokerage; practically, it's a small business with a brand, a lead engine, and payroll. The standard roles as teams grow: the team leader (rainmaker — owns the brand, the lead generation, and usually the listings), buyer's agents (convert the team's buyer leads — the classic first hire), a listing partner (carries listing appointments as the leader's calendar overflows), an inside sales agent (the phones-and-follow-up specialist — our ISA guide covers when that hire makes sense), a transaction coordinator / ops manager (the contract-to-close machinery), and eventually a marketing person. Most teams are much smaller than the org chart — a leader, one or two buyer's agents, and a TC is the modal real-world team — and the whole model runs on one asset: the leader's lead flow. Everything else is division of labor around it.
How the money splits (and what's actually fair)
The core trade: team members give up a slice of commission in exchange for leads, brand, systems, and support. Real-world arrangements vary enormously, but the recurring shape: team-generated leads split more toward the team (arrangements in the neighborhood of half are common), self-generated business splits more toward the agent, and the team's cut typically covers what would otherwise be the agent's costs — marketing, admin, sometimes transaction coordination — before the brokerage's own split applies. Caps, sliding scales, and salary-plus-bonus ISA models all exist.
The honest evaluation isn't "is 50% outrageous" — it's arithmetic: project your net income per year inside the team (their realistic lead volume × your conversion × your split, minus fees) against your net outside it (your own lead generation, at your own cost and conversion). For a newer agent with no pipeline, half of a real lead flow beats all of nothing by a wide margin; for a producing agent with their own sphere, the same split can be a pay cut wearing a team jacket. Run your numbers, not the percentage.
Joining a team: the honest pros, cons, and the questions to ask
The case for joining: immediate lead flow, real training (the apprenticeship most brokerages stopped providing), shared systems, and income floor while you learn — for many new agents it's the difference between a career and a first-year washout (it pairs naturally with the new-agent playbook). The case against: ceiling (the split persists after you've learned), brand (clients may bond with the team name, not yours), and portability (what happens to "your" clients and pipeline when you leave?). Before joining, ask: How many team leads did your newest agent actually receive last quarter — and what did they net? What counts as team-generated versus mine? What's in writing about my database when I leave? Is there a split ladder as I produce? A leader who answers those cleanly is running a real team; one who bristles is recruiting inventory.
Starting a team: when it's the right move (and the usual mistake)
The right time is embarrassingly concrete: you have more qualified leads than you can serve — you're referring out business or dropping follow-up — and you have a documented way of working someone can be trained into. Then the classic sequence is admin help first (a TC or assistant to buy back your hours — usually the highest-ROI first hire), then a buyer's agent for overflow leads, then an ISA once follow-up volume justifies it. The usual mistake is inverted: hiring agents as a growth strategy while the lead engine is still aspirational — a team without surplus leads is just shared scarcity plus payroll, and it's why so many first teams dissolve inside two years. Build the engine first (that's the whole lead-generation playbook); staff it second. And put the boring things in writing from day one: splits, lead ownership, departure terms — teams end, and the ones that end cleanly wrote it down. Compliance footnote: team names, advertising, and structures are regulated by state rules and your brokerage; this is reporting, not legal advice.