Real estate team websites

A solo agent’s website has one job: capture. A team website has two: capture, then route — because a lead that three people can see and nobody owns is a lead that goes cold in the gap. That second job is where most team sites fail, since routing lives in the CRM and the website is usually a different vendor. BrokerFold builds team sites where the two are the same system. Here is the engagement in full: inclusions, process, price.

What the team site includes

• One branded site, many producers. The team brand fronts the site; agents get individual presence on it. Templates and the visual editor work the same as on a solo site — no team-tier design downgrade.
• Listings and sold data under your board agreements. Full MLS® search with our minutes-scale sync, photos served from our own CDN, and the VOW sold-price layer behind visitor registration with compliance handled automatically. TRREB is in production today; the Vancouver tri-board stack is built and awaiting production approval.
• Seat-based CRM with routing. Leads route to seats by claim or round-robin, every contact carries a behaviour timeline from the site, and Conversations lets signed-in visitors message the team directly from listing pages.
• Five seats included. The Team plan ships with five, and extra seats are $70 CAD/month each — flat, published, no forced upgrade.

Deliverables

At the end of onboarding you have: the team site live on your domain; listings flowing; the registration wall feeding a shared pipeline; routing rules set to your choice of claim or round-robin; each seat logged in with its own notifications (web push included); and nurture plans staged in draft for the team lead to approve. What you notably do not have: a stack of per-agent website invoices.

One brand, many faces

The design problem every team site has to solve is presence without chaos: the team identity owns the chrome — colours, type, voice — while each agent gets a real face inside it, wired to routing so an inquiry about a listing reaches the person who carries it. Done right, nobody needs a separate personal site to feel visible. Done wrong, personal sites multiply, and that’s precisely how leakage starts: the personal site captures a lead, the personal CRM keeps it, and the team never learns it existed.

How onboarding runs

1. Trial first. Fourteen days free, no credit card, full product.
2. Build the site. Template, brand, copy — one afternoon, honest.
3. Add your seats. Invite the team, decide routing: claim rules reward speed, round-robin guarantees fairness. You can change your mind later.
4. Clear the board paperwork. We drive the vendor side; your broker of record signs off. Live data replaces sample data on approval.

What it costs

$449 CAD/month for the Team plan, five seats in. Additional seats $70/month. Month to month, CAD, cancel anytime with a 90-day data retention window and full export. Compare tiers on pricing; if you outgrow five-plus seats economics, the Brokerage plan’s twelve-seat allowance is the next step, not a negotiation.

Who should buy this

Teams whose lead flow already exceeds what one inbox can honestly serve — that is the point where routing stops being a luxury. Teams running paid acquisition especially: if you spend on lead generation at team scale and then let responses depend on who happens to check email, the ad budget is subsidizing your competitors’ follow-up. And teams tired of the two-vendor stitch, where the website vendor and the CRM vendor each blame the other for the integration.

Who shouldn’t: a two-agent partnership with modest web volume runs fine on a lower tier until the routing problem is real. Start there and move when the seats matter.

Growing past five seats

Seat six costs $70 a month — and so does seat sixteen. That linearity is deliberate: headcount changes shouldn’t open repricing negotiations, and nobody should postpone a good hire over a platform tier. Domain allowance scales with seats as well, which matters the day a pod inside the team earns its own address. If growth carries you to brokerage shape, the twelve-seat plan is a lateral move on the same platform: nothing rebuilds, nothing migrates, the routing history comes along.

Why teams pick one system

The argument is accountability. When the site and the CRM share a spine, “who has this lead and what have they done” is a dashboard question, not a meeting question. Claim events are timestamped. Behaviour timelines show what the lead did on the site before and after contact. The team lead sees distribution and response across seats without collecting screenshots. None of that is possible when the website mails a form submission to an inbox and the CRM hears about it later — the data is born connected here because both halves are the same product.

Proof, stated carefully

We operate production board infrastructure first-hand: direct feed agreements as a registered vendor, continuous property and media sync, our own image pipeline, and a completeness hold that keeps any listing dark until its data and photos have fully arrived. We won’t hand you a wall of team logos or invented lead multipliers — run the trial against a real week of your team’s traffic and let the routing sell itself.