Draft tenant and owner communication from the lease of record, hold anything with legal effect for the licensed property manager or broker of record, and log what was sent and who approved it.
Read the executed lease, its amendments and the ledger of record, each carried with its source.
02
Read each inbound message for accommodation, habitability, legal-process and money triggers first.
Reason
03
Summarise the lease's stated terms back to the reviewing broker, clause by clause.
04
Summarise the tenant's request in their own words, in the language and channel they used.
05
Assemble a draft owner report from the ledger of record, with trust balances read, never recomputed.
Decide
06
Assemble the renewal packet for the licensed manager, who sets the rent and signs it.
07
Route anything carrying legal effect to the named licensed human, and send nothing.
Out
08
Retain the message sent, the records it drew on, the template version and the approver.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Property management is licensed brokerage activity in most states; the agent carries the workflow, and the licensed manager decides what binds the tenancy.
Example workflow
One message, inbound to approval
AgentHuman
1Inbound message receivedResident portal, SMS, email or owner enquiry
2Records assembledExecuted lease, amendments, ledger of record and the property's jurisdiction
3Draft preparedMessage text, the clause it cites, trigger flags and confidence
4Controls appliedTrigger checks, template-version pinning, legal-effect classification and confidence threshold
No human action required
Stages 1 to 4 run unaided and nothing is sent at any of them — the agent is drafting, and the manager's lane opens at the confidence gate.
5DecisionBranches on the legal-effect test
High confidence
Goes to the property manager to approve.
Low confidence
Picks up a compliance read first.
Manager approval
The draft is held with the records it cites, its trigger flags and the confidence.
Approve · Revise · Refer to counsel
Approved — released to send▼
6Property systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedRevision rate, trigger-flag outcomes, escalation accuracy and post-send corrections
Revisions
Every manager revision is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Signing or issuing a lease, renewal or addendum.
Drafting, dating or serving a statutory notice.
Determining or conditioning a reasonable accommodation.
Moving, offsetting or disbursing trust funds.
Automation boundaryAgent acts unaided
✓Summarise the executed lease's stated terms back to the reviewing broker.
✓Send logistics for a visit a human has already approved.
✓Assemble a draft owner report for human reconciliation.
✓Acknowledge a message with the named human and the timeframe.
A workflow message that acquires legal effect has already crossed the boundary.
Itemising a security-deposit disposition.
Setting or justifying a renewal rent.
Answering questions about legal rights or eviction.
Communicating a decision that ends or alters a tenancy.
Example output
One message, annotated
Everything the agent drafts is attached to the record it was read from.
Workflow message · single tenancyIllustrative example
Tenancy
Drafted reply
Stated rent
Source of record
Confidence
Disclosure
Renewing tenant
Your lease states a term ending 31 March and a fixed rent
$1,850.00
Lease + amendment 2
91%
Automated · named manager
As receivedRead from the executed lease and its amendments — nothing on this side is written by the agent.
Records usedExecuted leaseAmendment on fileLedger of record
Why this wordingIt restates a term already agreed and takes no view on renewal.
ActionApproveReviseRefer to counsel
What the score decidesBelow the threshold the draft picks up a compliance read before the manager sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every messageFrom the lease of record
03Drafting
Draft from the record
Draw on the executed lease, its amendments and the ledger the firm reconciles to.
01Approved path
Keep routine out of legal reach
Routine lease questions and status replies arrive already drafted.
02Human review
Send review to the legal-effect lines
Trigger-flagged and low-confidence drafts are marked, so the manager's read starts where the tenancy is at stake.
04Build an evidence trail
What was sent, what it was drawn from and who approved it stay on the tenancy file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Legally-operative-communication escape rate counts messages that carried legal effect — notice, term, accommodation, money — without a licensed human's recorded approval. Nestack reports it by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Accommodation-adjacent requests
3.3%
3.7×
Review
Limited-English tenants
2.4%
2.7×
Review
Renewal decisions with arrears
1.6%
1.8×
Watch
Long-tenured legacy leases
0.8%
0.9×
Normal
Bar: legal-effect escape-rate lift vs. the all-message baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What ends a cycle is a new test
A served notice starts a clock and an accommodation denial has no post-hoc cure, so a cycle closes only once the failure is a case the next release must pass.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Escape rate rises in a tenant cohort.
02Diagnose
Which record, rule or trigger let it through? Drafts and sources are read together until one answer holds.
03Improve
The change is version-stamped, with the messages that exposed it attached.
04Verify
No release goes out while an affected regression case still fails.
05Learn
The case becomes a standing test and a line in the trigger list.
Learn → DetectThe return edge. Every closed cycle leaves the suite harder to pass.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, message workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Communication-workflow discovery and boundary work.
02Lease, ledger and portal source assessment.
03Held-act list and escalation-trigger mapping by state.
04Lease and ledger ingestion with binding.
05Drafting logic and clause-level citation.
06Confidence scoring and legal-effect routing.
07Manager approval workflow.
08Property-system and portal integration.
09Evaluation suite and slice reporting.
10Guardrails and send controls.
11Message tracing and observability.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne portfolio, one stateProductionProduction property systemsAdvancedMulti-owner portfolios
Introduced at Pilot
Drafting to your lease of record✓✓✓
Manager approval✓✓✓
Message-class baseline✓✓✓
Introduced at Production
Message-class reporting—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Communication audit log—✓✓
Introduced at Advanced
Multi-state rule configuration——✓
Broker and counsel review chains——✓
High message volume——✓
Enterprise trust controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your lease templates and amendment history→Lease and ledger ingestion with source bindingWeek 1
02Representative tenant and owner threads→Drafting baseline, clause citation and record bindingWeek 2
03Your held-act list and escalation triggers→Held-act list and escalation-trigger mappingWeek 1
04Access to relevant APIs, feeds or exports→Lease, ledger and portal assessment, then integration setupWeek 2
05Messages a manager had to correct after sending→Evaluation suite, slice reporting and failure-mode testingWeek 4
06Your send thresholds and write-back limits→Confidence scoring, legal-effect routing, guardrails and send controlsWeek 3
07Named property managers and your broker of record→Manager approval workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases cover the weeks they occupy. Week 5 doubles up: evaluation and pilot overlap.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Workflow discovery, held-act mapping and the automation boundaryW2Lease and ledger integration, then the drafting baselineW3Message workflow, confidence logic and send controlsW4Evaluation suite, legal-effect checks and failure-mode testingW5Portal integration, pilot threads and targeted correctionsW6One month-end run under the broker of record, then handover
Reading the bandEach bar covers only the weeks its work is named in. The week 5 overlap is real, not padding.
At the end of W6Validation complete; Agent Care holds the monitoring from week seven.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Real Estate AI agent
Build a property-management agent around your broker of record.
Show us your lease templates, your triggers and your systems. Your broker of record answers for every message that carried legal effect, so that is where we set the automation boundary.
