Populate the state-approved lease form from verified data, assemble the mandatory disclosure packet for that jurisdiction, and hold every term with legal effect for the broker completing the form.
Populate the approved-form blanks from party, premises and term data taken from the source documents.
02
Populate nothing until the state, county and municipality of the premises resolve, and stop rather than default.
Reason
03
Populate a cap-sensitive figure only from a human-attested basis, with its source and effective date beside it.
04
Assemble the disclosure packet from the jurisdiction manifest, with the lead determination evidenced, not inferred.
05
Assemble the pre-1978 lease elements — warning statement, disclosure, records list, acknowledgment, signatures.
Decide
06
Assemble a renewal from the form version in force, never by inheriting the prior term's determinations.
07
Verify each populated field against the source of truth, and report the mismatches rather than resolving them.
Out
08
Verify signature and disclosure status across the envelope, and send non-operative reminders only.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Completing a state-approved form is permitted in most states; drafting bespoke terms or explaining a clause's effect is not, and where that line falls varies by state.
Example workflow
One lease, intake to signature
AgentHuman
1Lease request receivedProperty-management record, application, renewal notice or broker intake
2Jurisdiction resolvedState, county and municipality of the premises, with the form and manifest that apply there
3Form populatedApproved-form blanks, disclosure packet, open gaps and confidence
4Controls appliedField reconciliation, manifest completeness, clause-library allowlist and confidence threshold
No human action required
Stages 1 to 4 run unaided and none of them signs anything — the agent is filling an approved form, and the broker's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the broker completing the form.
Low confidence
Adds an attorney read where the state requires one.
Broker approval
The packet is held with its populated fields, its open gaps and the confidence.
Approve · Correct · Refer to counsel
Approved — released for signature▼
6Lease and forms systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedField accuracy, manifest completeness, execution defects and post-execution corrections
Corrections
Every correction made at approval is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Composing or rewording any substantive lease term.
Choosing between clause options on legal-effect grounds.
Explaining a clause's consequence to any party.
Determining rent-regulation exemption status.
Automation boundaryAgent acts unaided
✓Extract and normalise the party, premises and term data from source documents.
✓Assemble the disclosure packet and flag the gaps.
✓Reconcile populated fields against the source of truth.
✓Track signature status and send reminders that carry no legal effect.
Writes stay inside the boundaries set at implementation; no held act is one of them.
Setting or approving the security-deposit amount.
Approving any deviation from the approved form.
Issuing a default or right-to-cure notice.
Countersigning or releasing the executed lease.
Example output
One lease packet, annotated
Everything the agent populates is attached to the record it was taken from.
Lease output · single tenancyIllustrative example
Tenancy
Populated field
Year built
Source of record
Confidence
Approver
Renewal, standard form
Lead disclosure and pamphlet attached to the approved form
Built 1962
County assessor record
91%
Broker completing the form
As receivedTaken from the assessor record and the executed application — nothing on this side is written by the agent.
Source records usedAssessor year builtJurisdiction manifestPrior executed lease
Why this attachmentCompleting an approved form is permitted; drafting the term is not.
ActionApproveCorrectRefer to counsel
What the score decidesBelow the configured threshold the packet takes a second read before it reaches the broker.
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
Each tenancyFrom the jurisdiction manifest
03Assembly
Populate the approved form
Draw on the verified record, the jurisdiction manifest and the form version in force at that address.
01Approved path
Assemble without the rework
Routine population and packet assembly arrive already done.
02Human review
Point the broker's read at the gaps
Open gaps and unattested exemptions are marked, because after execution a defective term may be unenforceable and the notice predicate may fail.
04Build an evidence trail
The populated field, its source of truth and the reconciliation result stay with the lease.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the executed lease
Each control wraps the one inside it. Once a lease is executed a void rider is not curable by amendment, so what a layer misses is named in the map below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modePull population back to proposal-only when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt, form-version and clause-library changes.Track
L4TraceabilityRecord the form version, the cap source and its date, the manifest and the approver.Record
L3Broker approvalHold the packet for the named broker; it governs release, not whether an approved term is lawful.Gate
L2Policy guardrailsTest populated fields against the jurisdiction manifest and clause allowlist; a failure returns the packet.Restrict
L1Confidence thresholdsRoute low-confidence packets to a second read before the broker sees them.Require review
Model corePacket produced — populated form, disclosure set, open gaps and confidence
L1 – L2Test whether a packet may stand
L3Puts the release in a broker's hands
L4 – L5Keep the record and the version honest
L6Pulls population back when signals degrade
How Nestack evaluates it
Evaluate the whole packet workflow — not only the executed form.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the lease the parties sign
Depth of coverage ▼
E1Final-output evaluationDid each populated field match the record it came from?
E2Step-level evaluationDid the agent use the right jurisdiction, form version and manifest?
E3Tool evaluationDid it write the correct field on the correct document?
E4Confidence calibrationDo low-confidence packets actually attract more broker corrections?
E5Slice evaluationHow does performance change across specific tenancy types?
E6Business outcomeHow many executed leases needed a correction after signature?
Floor — the exposure the brokerage carries
Failure modes
Where each failure originates in the agent
Seven failure modes, each placed where it starts rather than where it shows.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
LX-01
Stale cap figure
A superseded rent-cap percentage is read from cache.
Stage gathersLease record, jurisdiction manifest and form version
02 · Reasoning2 modes
LX-02
Inferred lead exemption
Renovation text is read as an exemption on pre-1978 housing.
LX-03
Missed local ordinance
Ownership data reads as cap-exempt where a city rule is stricter.
Stage proposesPopulated form, disclosure set, gaps and confidence
03 · Tool / write2 modes
LX-04
Wrong deposit figure written
A small-landlord figure is written across a corporate portfolio.
LX-05
Unsigned acknowledgment
Signature tabs land on the lease body but not the lead form.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
LX-06
Excluded notice sent
An operative cure notice goes out through the e-signature platform.
Stage returnsThe packet the broker signs and the parties execute
05 · Change / Version1 mode
LX-07
Superseded rider
A renewal runs on last year's form after the state amended the rider.
Stage tracksModel, prompt, form versions and clause library
Sev-1 · a held act executedSev-2 · a defect reaches the executed leaseSev-3 · source degrades, packet routes to review
Rent-regulated jurisdictions under a stricter city ordinance hold the top row here while the all-lease rate looks steady. Nestack reports the mandatory-disclosure defect rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Stricter local ordinance
4.5%
3.0×
Review
Pre-1978 target housing
3.3%
2.2×
Review
Translation-mandate states
1.8%
1.2×
Watch
Commercial and mixed-use
0.9%
0.6×
Normal
Bar: mandatory-disclosure-defect-rate lift vs. the all-lease baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends when the test exists
Nothing closes until the failure is a regression case the next release has to clear, and the suite it joins is what the next detection is read against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Disclosure-defect rate rises in a lease cohort.
02Diagnose
The supervising broker walks the executed packet back through its manifest, form version and cap source.
03Improve
The fix is recorded against a form version, with the defective packets attached.
04Verify
Release is held until the affected regression cases clear again.
05Learn
The case joins the permanent suite and the jurisdiction manifest.
Learn → DetectThe return edge. Every later detection is measured against a longer suite.
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, form workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Tenancy workflow discovery and boundary definition.
02Forms, PM and e-signature source assessment.
03Jurisdiction manifest and clause-library mapping.
04Lease-record ingestion and field normalisation.
05Form population and reconciliation.
06Confidence scoring and gap routing.
07Broker approval workflow.
08Forms and e-signature integration.
09Regression suite and failure-mode cases.
10Guardrails, allowlists and approval controls.
11Trace instrumentation 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 jurisdiction, one officeProductionProduction lease systemsAdvancedCommercial and mixed-use
Introduced at Pilot
Population from your record and manifest✓✓✓
Broker approval✓✓✓
Disclosure-coverage baseline✓✓✓
Introduced at Production
Defect reporting by jurisdiction—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Execution audit log—✓✓
Introduced at Advanced
Multi-state and local ordinance rules——✓
Multi-brand brokerage approvals——✓
High lease volume——✓
Enterprise forms 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 approved-form set and lease templates→Lease-record ingestion and field mappingWeek 1
02Representative executed leases→Population baseline and source-of-truth reconciliationWeek 2
03The jurisdictions you let in and their local rules→Jurisdiction manifest and automation-boundary definitionWeek 1
04Access to relevant APIs, feeds or exports→Forms, PM and e-signature assessment, then integration setupWeek 2
05Leases that came back with a defect→Regression suite, failure-mode cases and manifest testsWeek 4
06Your signing authority and write-back limits→Confidence scoring, gap routing, guardrails and approval controlsWeek 3
07Named brokers, and counsel where the state requires it→Broker 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
Each phase is drawn on the weeks it occupies. Week 5 carries evaluation and pilot at the same time.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Tenancy discovery, jurisdiction mapping and the automation boundaryW2Source integration and the population baselineW3Form workflow, confidence logic and approval controlsW4Regression suite, manifest checks and failure-mode testingW5E-signature integration, pilot tenancies and targeted correctionsW6A lease cycle executed under broker review, then handover
Reading the bandBars cover only the weeks their work is named in. The week 5 overlap is real, not padding.
At the end of W6Production checks signed, monitoring transferred to Agent Care.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Real Estate AI agent
Build a lease-processing agent around the approved form.
Show us your form set, the jurisdictions you let in and who signs. Completing the approved form is one thing and drafting a term is another, and that line is where we set the automation boundary.
