Deals

The kanban that tracks every application from first interest through signed lease.

Last updated: 2026-05-10

What a deal is

A deal is the funnel record for one tenancy you're working on. It starts the moment a prospect raises their hand and ends when you either sign a lease or close the deal as backed-out or denied. One deal equals one pursued tenancy — if a prospect walks away and a different prospect picks up the same unit later, that's a new deal.

Why this matters: the deals board is the single place to see what's actually in flight. The dashboard won't tell you how many applications are sitting with landlords right now — only the Deals kanban does.

Find it at /deals in the sidebar.

The stages, in order

Open lane (a deal in flight):

1. lead — initial interest. Someone wants to apply but you haven't sent anything yet.
2. about_to_submit — you're assembling the application package.
3. submitted — application is with the landlord, waiting on a decision.
4. approved — landlord said yes, lease document not yet out.
5. leases_out — lease has been sent for signature.
6. rented — signed and finalized. The deal is closed in success.

Closed lane (a deal that ended without a lease):

• backed_out — the prospect or your side pulled out at any earlier stage.
• denied — the landlord declined the application.

The chips are colour-coded so you can read the lane at a glance: warm yellow as a deal opens, sliding through orange and into soft red as risk builds, then green for rented. Each chip also carries an n/6 step indicator (1/6, 2/6, …) so the order reads without relying on colour.

Active and Closed tabs

• Active — every deal still in an open stage.
• Closed — defaults to the last 30 days of rented / backed_out / denied deals. Use the date range for older retrospectives.

Moving a deal through the funnel

Drag a card from one column to the next. The board confirms with a toast.

Deals also get created automatically when a unit moves into submitted, approved, or leases_out and there isn't already a live deal on that unit. So if you flip a unit's status from the unit page, a matching deal appears on the kanban without anyone having to remember. This auto-create is idempotent — it never duplicates.

Finalizing — "Mark signed"

When the lease is signed and the deal is in leases_out, click Mark signed. In one atomic step:

1. The proposed rent is checked against the legal cap for this unit. Over-cap rents are blocked unless a brokerage admin has filed an override.
2. The lease is recorded (see Leases).
3. The unit moves to rented.
4. The deal closes as rented.

The panel takes the whole party, not just one person: fill in the tenant at the top, then click Add co-tenant for each additional person signing the same lease. The tenant at the top is the primary contact — the welcome packet and renewal notices go to them. A row you leave empty is ignored, and a row with only a phone number is refused (we need a name or an email to put someone on a lease). The same rows appear on the "Mark rented" panel in inventory.

If anything fails, nothing changes — the deal stays in leases_out and the unit stays put. Fix the problem (most often a rent above the cap) and try again.

Capturing an exit reason

When you drag a deal to backed_out or denied, the board prompts you for a short reason — "prospect chose a different building," "credit declined." That reason shows on the Closed tab so you can run retrospectives: which buildings lose deals, which landlords decline most often, what falls apart late.

Who can see and edit what

See also

• Leases — what happens after Mark signed
• Renewals — the other side of the funnel, for tenants already in place