What a free transaction-management plan actually carries: Real Deal Pro’s free plan, boundary by boundary

What the plan carries, where it stops, and what the server checks before each action.

Published November 10, 2026

Three open deals at a time, one hundred clients, one person in the workspace, and a History list that reaches back ninety days. Those are the boundaries on Real Deal Pro’s free plan, and the rest of this page is where each one is enforced, what happens when you reach it, and which parts of a transaction file the plan runs with no plan check.

A plan table can tell you a tier exists. It cannot tell you where that tier stops, which is what decides whether an evening of setup is worth spending. Every price below is read from the module that prices the product, and the three record-and-history caps are checked against the plan table by a test.

1. What the free plan carries

An agent deciding whether to spend an evening on setup wants one question answered first: can this carry a real deal from contract to close, or is it a shell with a dashboard?

In Real Deal Pro

  • The free plan is a plan in its own right rather than a timed trial: the plan table defines it alongside the paid tiers.
  • It carries no clock — activation writes the subscription row with no trial end and no period end, so there is no date at which it lapses.
  • The sample deals and clients the onboarding loader can seed are marked at creation, and the deal and client counts exclude anything carrying that marker — so the sample set you load to look around never spends your allowance.
Free$0/mo

No credit card required

What the plan carries

  • Up to 3 active deals
  • Up to 100 clients
  • Auto-fill contract templates
  • E-signatures included
  • Task management & calendar
  • Deal history (last 90 days)
The free plan as pricingData.ts states it. The price and the lines beneath it are read from that module, which is the same source the pricing page renders.

2. The four boundaries of the free plan, and where each is enforced

Where does the plan stop — precisely enough to work out in advance whether a normal month runs into it?

In Real Deal Pro

  • The four boundaries are on records and history: open deals, clients, people in the workspace, and how far back the History list reaches. The plan table also leaves three feature flags off that a paid tier switches on — CSV export, team collaboration and priority support — and switches document generation and e-signature on.
  • The deal and client caps are checked on the server before the record is written, so a cap is not something the interface merely hides a button for.
  • The one-person boundary runs through a different path — a seat admission check on the invite route — rather than through the record-cap middleware.
  • The counts behind them are taken live from the deals and clients tables at the moment you act rather than read from a cached usage column, which is what keeps a cap from silently failing to fire.

The four boundaries

  • Open deals at a time
  • Clients in the workspace
  • People in the workspace
  • How far back the History list reaches
The four boundaries this page is about. Section 2 states what each one is set to and where the server enforces it.

3. Three open deals at a time, and what “at a time” means

“Three deals” reads two ways, and the two are very different propositions for someone who closes a dozen a year: three in total, or three at the same time?

In Real Deal Pro

  • The cap counts deals in the open status, so closing or archiving a deal frees its slot and the next one can be created immediately.
  • It counts the status and not the phase: a deal is open from the moment you create it, so a live listing and a buyer still being shown homes each hold a slot long before anything is under contract.
  • Because of that, the number of DEALS a workspace can take through a year on this plan is not capped at three — three is how many may be open at once. The client cap is the one that accumulates, since a client record is never closed.
  • Four routes consume the open-deal cap — creating a deal, restoring an archived one, reopening a closed one, and accepting a collaboration invite that creates a deal — and the cap is checked at all four rather than only at creation.
  • The fourth of those is on the collaboration-accept route rather than the deal routes, and it runs its own copy of the same check.
  • At the boundary the request is refused with a named limit error rather than partially applied, so a deal is never half-created against a full workspace.

Worked example

Four steps over your own last twelve months

  1. Count the transactions you took from accepted offer to closing in the last year. That number is not what the cap measures, and reading it as the cap is the usual mistake.
  2. Now go month by month and count every deal file that was open at the same time — and count a file from the day you opened it, not from the day it went under contract. A live listing and a buyer you are still showing homes to each hold a slot, because the cap counts a deal’s status and not how far along it is.
  3. Take the highest of those twelve numbers. That is the figure the three-deal boundary applies to.
  4. If the highest month is three or under, the free plan carries your year as it stands — provided your book of clients is under the hundred-client cap, which is the one that accumulates. If the highest month is four or more, the plan carries everything except your busiest stretch, and the question becomes whether to move up for those weeks or stagger what you keep open.

Four routes into “open”

  • Creating a deal
  • Restoring an archived deal
  • Reopening a closed deal
  • Accepting a collaboration invite that creates a deal
The four routes that can put a deal into the open status. Section 3 states what each one checks first.

4. What “90 days of deal history” narrows, and what it leaves alone

“90 days of deal history” sounds like a retention limit, as though a deal evaporates after three months. Whether it is one decides whether a free plan can hold a compliance record at all, so it is worth knowing exactly what the ninety days applies to.

In Real Deal Pro

  • The ninety-day window applies to the History list, which is the browse view over deals that have already finished.
  • A finished deal outside the window stays reachable at its own address, with its timeline and its documents — the window is applied to the list query, not to the deal.
  • The deal closing-binder routes carry no plan gate, and the plan table records a written instruction beside the feature flags not to add one.
  • The data-subject export routes carry no plan gate either; the plan table treats that as a statutory right rather than a plan feature.
  • The number is a single named constant that the query enforcing the window, the API’s plan response and the in-app History notice all read.

The History list

The browse view over deals that have already finished

is not the same thing as

A finished deal’s own record

  • Its own page
  • Its timeline
  • Its documents
  • Its closing binder
Two different things, which the phrase “90 days of deal history” runs together. Section 4 states which of them the window applies to.

5. The transaction-management work the free plan runs with no plan check

The question that decides an evening of setup is not how large the caps are. It is whether the action the whole exercise was for runs at all — so, route by route, here is where a plan check exists and where there is none.

In Real Deal Pro

  • The document-generation route carries no plan check — the gates on it are a payment-status check and the licence checks that apply to affiliated accounts, none of which is a plan tier.
  • The signature-send route has the same shape, with no plan check of its own, and e-signature is switched on for the free plan in the plan table.
  • The task routes carry no plan check.
  • The calendar routes carry no plan check.
  • Creating and sending an invoice is not plan-gated either; the one paid convenience on that surface is the CSV export of invoices.
  • Every route that mounts the plan-feature middleware mounts it for one feature only, data export, and the one other plan feature the API consults anywhere is the history window on the History list. The deal and client caps are plan checks too, and they are the ones section 2 covers.

Checked route by route in section 5

  • Generating a document from a template
  • Sending a document for signature
  • Tasks
  • The calendar
  • Creating and sending an invoice
  • The deal closing binder
  • CSV export
The surfaces section 5 goes through, route by route. Which of them carries a plan check — one does — is stated there, beside the file it is enforced in.

6. Who can start on the free plan, and the refusals a reader here could meet

Finding out at the end of a signup that a plan is not open to you is worse than reading it now. So: who is the free plan open to, and on what does the request get refused?

In Real Deal Pro

  • Starting needs no card: the activation route makes no payment-processor call, and the subscription row it creates carries no payment-processor identifiers at all.
  • It is refused when the account carries a subscription that is neither canceled nor expired — a past-due or unpaid one counts, while a lapsed no-card trial is admitted — when the plan that ended was a team plan, and when the email address has already used a trial. Each refusal carries its own named error code rather than a generic failure.
  • The team refusal exists to protect the workspace rather than the price: dropping a team to a single seat would strand the members already in it.
  • Those three are not every condition the route can refuse: one further account type and one workspace-role check sit outside this page’s subject.

Three refusals a reader here could meet

  • A subscription on the account that has not fully ended
  • A lapsed team trial
  • An email address that has already used a trial
Three of the conditions the activation route can refuse — not all of them, for the reason section 6 gives. What each one is is stated there.

7. When a paid plan starts earning its price

Whether a paid tier is worth anything to a particular agent follows from which boundary above they actually meet, rather than from a feature grid.

In Real Deal Pro

  • The single-agent plan lifts the deal and client caps out of the way — the plan table sets both to 999,999 — drops the history window and switches CSV export on.
  • Its monthly and annual rates, and the Team plan’s, are the ones the pricing module currently exports — the same module the pricing page renders.
  • The team plan adds seats, team collaboration, deal assignment, a team dashboard and priority support on top of that, and is priced per seat.
  • Seats are purchasable on the Team plan. The free plan’s single seat is its capacity rather than a starting allowance, so a second person arrives by moving the workspace to Team.
Solo$59/mo

or $49/mo billed annually

What Solo carries

  • All platform features
  • Unlimited deals & clients
  • Auto-fill your own contract templates
  • E-signatures
  • Full deal history
  • CSV export
Team$59/seat/mo

or $49/seat/mo billed annually

What Team carries

  • Everything in Solo
  • Up to 50 team seats
  • Team collaboration
  • Deal assignment
  • Team dashboard
  • Priority support
The two paid software tiers this page covers, with their rates and their lines as pricingData.ts states them — the same source the pricing page renders. The annual rate is the per-month figure when the year is paid up front.

Try it before you decide

The Free plan is a live product tier, not a countdown: up to 3 active deals and 100 clients, with contract generation and e-signatures included. No credit card.

Free plan · No credit card required · Upgrade anytime · Set up in 5 minutes

Want the whole Iowa toolkit in your inbox?

Not ready to sign up? Get the free Iowa toolkit by email. One email with every free tool, nothing else unless you ask.

Wrapping up

Three open deals at a time is a real limit, and whether you meet it is arithmetic rather than a judgement: it depends on your busiest month, not on your year. The month-by-month count in section 3 is a ten-minute exercise that settles it before any setup time is spent.

What separates a usable free tier from a demo is not the size of the caps but whether the thing you came to do runs. Generating a document and sending it for signature are the two actions a transaction file exists for, and neither carries a plan check here.

Next step

The boundary test in section 3 tells you whether the free plan fits your year. This calculator answers the other half of the question — what the tools you already pay for cost you against the transactions you actually close.

Work out what your current tool stack costs per closing