Extract and reconcile rent-roll and operating-statement line items, tag every input with how it was verified, and hold the package for the investment committee, which decides the acquisition.
Abstract rent rolls, operating statements and leases from the data room, a management export or an upload.
02
Reconcile the line items across those sources into one schedule, each carrying the document and page behind it.
Reason
03
Abstract the economic terms of each lease — base rent, escalations, recovery structure and options.
04
Reconcile the abstracted terms against executed leases and bank records, and record which source confirmed each.
05
Tag every line seller-asserted, lease-confirmed, bank-confirmed or estoppel-confirmed, and keep the tag with it.
Decide
06
Flag diligence artifacts whose standard designation, vintage or shelf life sits outside what the checklist asks.
07
Flag each unverified line to the deal team, and hold the package for the investment committee.
Out
08
Retain the source documents, the abstracts, the tags and the committee's decision against the deal.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent assembles working papers; the investment committee approves the deal, and the Phase I stays with the Environmental Professional.
Example workflow
One deal, data room to committee
AgentHuman
1Deal file receivedData room, property-management export, seller upload or pipeline record
2Documents abstractedRent-roll lines, operating-statement lines and lease terms, each with its page
3Package assembledReconciled schedule, verification tags, open checklist items and confidence
4Controls appliedSource-to-cell checks, verification tagging, standard-and-vintage flags and confidence threshold
No human action required
Stages 1 to 4 run unaided, and no number is called verified at any of them — the agent is assembling, and the committee's lane opens at the confidence gate.
5DecisionTurns on the confidence threshold
High confidence
Goes to the investment committee to read.
Low confidence
Adds an analyst reconciliation first.
Committee review
The package is held with its sources, its unverified lines and the confidence.
Accept · Challenge · Send for verification
Accepted — carried to the memo▼
6Deal systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedUnverified-input rate, challenged lines, reopened items and post-closing findings
Challenges
Every committee challenge is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Approving the acquisition or the assumption set.
Declaring a rent roll or operating statement verified.
Conducting or signing the Phase I and naming RECs.
Determining zoning compliance or entitlement risk.
Automation boundaryAgent acts unaided
✓Extract, normalise and reconcile rent-roll and T-12 line items.
✓Abstract the lease economic terms with a page-level citation to the source.
✓Flag standard designation, vintage and shelf-life dates.
✓Assemble and version the data-room index and the source-to-cell trail.
Extraction, abstraction and indexing run inside the boundaries agreed at implementation.
Certifying boundaries or easements on a survey.
Determining flood zone, seismic PML or ADA status.
Releasing a projected return to a third party.
Waiving a contingency or releasing escrow.
Example output
One rent-roll line, annotated
Everything the agent abstracts stays attached to the page it came from.
Underwriting output · single line itemIllustrative example
Tenant
Abstracted line
Stated base rent
Source of record
Confidence
Verification
Suite 210, retail
Percentage-rent clause above a base-year recovery stop
$27.50 / sq ft
Executed lease, page 14
89%
Estoppel not yet returned
As receivedTaken from the executed lease and the data-room index — nothing on this side is inferred by the agent.
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the committee
Each control wraps the one inside it. Where a layer stops is named in the failure-mode map below it.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modePull the agent back to abstraction-only when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt, checklist and standard-designation changes.Track
L4TraceabilityRecord the source page, the abstract, the tag, the challenge and the decision.Record
L3Committee approvalHold the package for the committee; it governs release, not whether an accepted line is sound.Gate
L2Policy guardrailsTest output against the verification tags, the checklist standards and the investor-facing block; a hit returns the package.Restrict
L1Confidence thresholdsRoute low-confidence packages to an analyst reconciliation before the committee reads them.Require review
Model corePackage assembled — reconciled lines, tags, open items and confidence
L1 – L2Test whether a line may stand
L3Puts the release in the committee's hands
L4 – L5Keep the record and the version honest
L6Pulls the agent back when signals degrade
How Nestack evaluates it
Evaluate the diligence workflow — not only the finished memo.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the package the committee reads
Depth of coverage ▼
E1Final-output evaluationDid each reconciled line match the page it was drawn from?
E2Step-level evaluationDid the agent use the right export, checklist and standard set?
E3Tool evaluationDid it read the correct document and write the correct cell?
E4Confidence calibrationDo low-confidence packages actually attract more challenges?
E5Slice evaluationHow does performance change across specific asset cohorts?
E6Business outcomeHow many lines reached the committee still seller-asserted?
Floor — the outcome the fund answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each set at the stage where it starts.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
DD-01
Marketing rent roll pulled
Pro-forma rents carry forward as in-place rents.
Stage gathersRent rolls, operating statements, leases and artifacts
02 · Reasoning2 modes
DD-02
Recovery clause misread
Percentage rent is read as a fixed base escalation.
DD-03
REC treated as resolved
An NFA letter for another parcel closes the item.
Stage proposesReconciled lines, tags, open items and confidence
03 · Tool / write2 modes
DD-04
Model written without a diff
The committee reads a version nobody reconciled.
DD-05
Checklist cleared on filename
An item is marked complete on a matching filename.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
DD-06
Internal deck reaches LPs
An IC scenario deck is forwarded to prospective investors.
Stage returnsThe package the committee reads and decides on
05 · Change / Version1 mode
DD-07
Superseded survey standard
A survey under the prior ALTA/NSPS version is accepted.
Stage tracksModel, prompt, checklist and standard designations
Sev-1 · a held act runs unaidedSev-2 · an unverified line reaches the memoSev-3 · a source degrades, package routes to review
The aggregate stays calm while one cohort does not
The baseline is every line item reaching committee across the book. Against it, unverified inputs concentrate in a few asset cohorts, so Nestack reports the rate per cohort rather than only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Mom-and-pop managed assets
5.2%
3.7×
Review
Historical industrial-use sites
4.2%
3.0×
Review
Ground-lease and TIC structures
2.1%
1.5×
Watch
Rent-regulated value-add
0.7%
0.5×
Normal
Bar: unverified-input-rate lift vs. all-line-item baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
No cycle closes without a new regression case
Each cycle ends with the failure written as a regression case the next release has to pass, and the detection that follows is measured against that suite.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Unverified-input rate rises in one asset cohort.
02Diagnose
Which document, abstraction step or tag rule let the line through?
03Improve
The fix is bound to a version, with the challenged lines attached to it.
04Verify
The affected regression cases are re-run before anything releases.
05Learn
The case joins the permanent suite and the diligence checklist.
Learn → DetectThe return edge. Detection starts again from a checklist and a suite that both grew.
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, abstraction workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Diligence workflow discovery and boundary definition.
02Document source and access assessment.
03Checklist, standard-designation and vintage mapping.
04Rent-roll and T-12 line extraction.
05Lease abstraction and citation binding.
06Verification tagging and line routing.
07Investment-committee review workflow.
08Model and deal-platform integration.
09Regression cases and cohort evaluation.
10Guardrails and release controls.
11Observability and audit-trail traces.
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 deal, one asset classProductionProduction deal systemsAdvancedInstitutional funds
Introduced at Pilot
Abstraction to your documents✓✓✓
Committee review✓✓✓
Line-item baseline✓✓✓
Introduced at Production
Verification reporting by asset—✓✓
Review workflow in your systems—✓✓
Approved model write-back—✓✓
Source-to-cell trail export—✓✓
Introduced at Advanced
Non-standard ownership structures——✓
Multi-stage committee approvals——✓
High deal volume——✓
Enterprise fund 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 diligence checklist and required standards→Checklist mapping and standard-designation flagsWeek 1
02Representative closed deal files→Extraction baseline, reconciliation and source-to-cell bindingWeek 2
03Your rent-roll and lease document formats→Document-format mapping and automation-boundary definitionWeek 1
04Access to relevant APIs, feeds or exports→Data-room, model and pipeline assessment, then integration setupWeek 2
05Deals where an input was wrong at committee→Evaluation suite, cohort regression cases and failure-mode testingWeek 4
06Your review thresholds and model write-back limits→Confidence scoring, tag routing, guardrails and release controlsWeek 3
07Named committee members to read packages→Committee review 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 sit over the weeks they actually occupy. Week 5 carries evaluation and pilot together.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Diligence workflow discovery, checklist mapping and the automation boundaryW2Document-source integration and the extraction baselineW3Abstraction workflow, confidence logic and review controlsW4Evaluation suite, verification-tag checks and failure-mode testingW5Model and pipeline integration, pilot deals and targeted correctionsW6One deal packaged for IC under committee review, then handover
Reading the bandA bar spans the weeks its work is named in, and no others. The week 5 overlap is real, not padding.
At the end of W6Verified in production, then monitoring sits with Agent Care.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Real Estate AI agent
Build an underwriting copilot around your diligence checklist.
Bring your data room, your checklist and the names against each item. If your rent rolls arrive as scans, that is the workflow we map — and the boundary stops short of every judgment reserved to a professional.
