FTRE

Architecture

How FTRE is put together

One platform, many brokerages. Agents, brokers, and the FTRE desk share a system and never share another firm’s private files.

System

Workspaces

Agent, broker, and admin shells. Navigation and data follow the signed-in role.

Tenant boundary

Every deal, document, message, and report carries a brokerage id.

Rule engine

Rate, equity, condition, motivation, and days on market produce a structure and a score.

Desk

Status, buyer match, checklist, and the thread live on the file.

AgentsBrokersFTRE deskRule engineRecords

Business flow

1

Read

Agent runs the opportunity through the rule engine.

2

Submit

The guided file lands on the brokerage and the desk.

3

Structure

The desk sets subject-to, seller finance, novation, wrap, or wholesale.

4

Match

Active buyers in that city and price band are scored.

5

Close

The file is marked saved or created and stays in the firm’s report.

Data flow and isolation

Harbor & Pine

Maya, Luis, Priya, and Jordan see Austin files. A broker sees every agent in the firm. An agent sees only their own deals.

Northline Collective

Miami files stay on Northline. They appear for the FTRE desk and never on a Harbor screen.

Brokerage AAgents · deals · messagesBrokerage BAgents · deals · messagesno shared rows

Rule engine

Low rate and equity

Subject-to or wrap when the existing loan is the asset.

Seller will carry

Seller finance when equity can secure the note.

Heavy rehab, tight price

Novation so the contract can be resold cleanly.

Long days on market

Wholesale when a discount is more likely than a new loan.

Thin equity, high rate

Pass. The file waits for a price or term change.

Mixed signals

Hybrid cash plus a short note.

Status path

Draft→
Submitted→
Under review→
Structuring→
Buyer match→
Offer→
Closed

A file can also be declined. Declined and draft files are the ones an agent can withdraw.