Real estateJourney
The client-facing plan. Every buyer, seller and homeowner sees where they are and what comes next.
Plan Journey · All 50 states
Products
Everything Seam builds, in one place.
Three products for real estate teams and the clients they serve. Not sure which? Start with the comparison below.
01 / Products
Built to be used every week.
Real estate
Real estateJourney Agent + CRM
The real estate agent console: contacts, tasks, documents, transactions and team ownership in one working view.
Plan Journey Agent + CRM, which includes Journey · All 50 states
Real estate · VirginiaSignals
Ownership, permit and assessor movement that says who is about to move, and why, with claimed leads sent to your CRM.
Plan Signals, or inside the Complete Platform · Virginia today
02 / How they fit
One workflow, seen from three sides.
These are not three separate tools that happen to share a login. They are three views of the same transaction, which is why they are priced to be used together rather than assembled. The Complete Platform is Journey, Journey Agent + CRM and Signals in one plan.
| Journey | Journey Agent + CRM | SignalsOn its own, or in the Complete Platform | |
|---|---|---|---|
| What it is | The side your client sees: the plan, the milestones, the documents, the status link and the messages. | The side you work: the console pipeline, contacts and lead management, tasks and activity timeline, deal stages, Journey Templates, Action Plans and reports. | The side the market shows you: ownership, permit and assessor movement, so the question shifts from who might be ready to why this particular person is. |
| How it fits | Your existing CRM stays the system of record, and Seam does not try to replace it. | It includes everything in Journey, because a client plan the agent maintains separately from their pipeline is a client plan that goes stale. | On its own it finds and claims leads, sends alerts, and sends claimed leads to your CRM. With Journey Agent + CRM in the Complete Platform it is also matched against the people already in your database. |
| Choose it when | You are keeping your CRM. It is the whole product if you already have one you have no intention of leaving. | You would rather stop paying for two systems that disagree with each other. | A solo agent usually starts with Journey Agent + CRM and adds Signals once the database is big enough that ranking it matters. Brokerages tend to start with the whole thing, because the reporting only works when every agent is in the same system. |
| Available | All fifty states and the District of Columbia. | All fifty states and the District of Columbia. | Virginia today. It needs certified local parcel coverage. |
The choice is made once when the workspace is bought, and changing it later is a billing change rather than a migration. See plans and pricing.
03 / On a phone
Three apps, because three people need different things.
Native iOS and Android apps are built for each audience: Journey - Home for the homeowner, buyer or seller, Journey - Agent for the console, and Journey - Partner for a partner who works with Seam agents regularly and wants more than a one-off link. Each one opens on what that person actually does — Today and Journeys for an agent, open requests and documents for a partner — rather than hiding one audience's app behind another's navigation.
They are shells over the same workspace rather than a separate mobile product, so what you see on a phone is the system, not a reduced copy of it that drifts out of date.
Journey - Home, Journey - Agent and Journey - Partner are available now. Download the client app, the console app, or the partner app on the App Store and Google Play. Nothing about a one-off invited collaboration changes: the workspace is a web app, so it already works in a phone browser, and a partner handling a single referral or request still needs no account and nothing installed. The app is there instead for a partner who works with Seam agents regularly and wants push notifications on new referrals and a standing view of their open work.
Journey - Home
Journey - Agent
Journey - Partner
04 / Partners
Partners are invited, not signed up.
There is no partner registration form, and that is deliberate. A lender, title company, inspector, attorney, insurance agent or contractor does not create a Seam account and then go looking for work. They are invited into one specific piece of work by someone who already has it: the agent, or the client themselves.
The invitation is the boundary. It arrives as a secure link tied to a named role, scoped to the requests, documents or messages that role needs, and it expires. A partner never receives the client's whole record, and never sees a transaction they were not invited into.
For everyone involved this is the point. The client keeps control of who sees what. The agent stops being a mailbox that forwards documents between parties. The partner gets the thing they actually wanted, which is the document and the deadline, without an account to manage or another portal password to lose. A partner who works with Seam agents regularly enough to want more than a one-off link can install Journey - Partner instead, without changing what a single invitation asks of anyone else.
05 / Proof of work
What these look like in practice.
Relocation guides and lead intelligence
Two static guide sites, a public-records pipeline, and the review queue that decides what an agent ever sees. The parts that survived into Signals were not the clever ones.
Solver-backed clinic scheduling
A CP-SAT solver behind a draft-and-approve workflow, a rule registry split into law and priced preference, and an audit trail over every change.
06 / Next
Not sure which one fits?
Tell us the workflow you want to make clearer and we will point you at the right product, or tell you plainly if we do not have one.