Methodology
Every number reproducible. Every input cited. Every file reviewed.
Landwrit files are produced by a deterministic underwriting engine — pure arithmetic on your stated inputs, reproducible line by line. No figure in a Landwrit file is generated by a language model.
01 / The guardrails
Deterministic checks, on every run.
The checks below are mechanical — pure code, never an AI model — and a run that fails any of them is blocked and routed to a human with the failure attached. The same checker also enforces firm-wide conduct rules on Landwrit's internal agents (banned cold-outreach channels, mandatory AI disclosure); those guard the firm, and these guard your file.
Independent math recheck
Any number about to be presented externally is independently recomputed by the deterministic engine. If the recomputation disagrees by more than a cent, the run is blocked. No exceptions, no overrides.
Completeness check
Every piece of work must be complete before it moves — a run with a missing field stops right there instead of producing a file with a hole in it.
Mechanical flags
Fixed thresholds on the stated numbers — coverage below 1.20x, any failed stress, negative cash-on-cash, occupancy below 60% — raise named flags, and each flag is delivered with the specific diligence step it calls for.
Stress integrity
Three independent mechanical stresses — rate +200 bps, occupancy −10%, expenses +10% — and the rate stress re-prices every floating-rate loan in the stack individually before coverage is re-derived. It is never approximated from the senior loan alone.
Human gate
Anything involving money, legal commitments, or sending material outside the firm is routed to a human review queue. It is never auto-executed — a person approves it or it doesn't happen.
02 / The discipline
Built to be checked.
Input provenance
Section 8 of every file lists each input the engine used, its value, and the client-provided source document it came from. Anything we could not verify against your documents is explicitly marked unverified — so you always know which numbers are load-bearing assumptions.
The report registry
Every file carries a Report ID derived from a cryptographic digest of its complete inputs — same inputs, same ID — and is recorded with a timestamp in Landwrit's registry when it is produced. To verify any Landwrit file is genuine and unaltered, email hello@landwrit.com with the Report ID.
Human review gate
A person reviews every finished file before it is delivered. Consequential actions — sending files out, quoting fees, anything touching money or legal terms — are structurally gated behind human approval; the system cannot skip the gate.
Testing discipline
The engine and the report renderer are covered by an automated test suite, and the formatting helpers the PDF uses are the very same ones the tests check — so "matches engine output exactly" is tested with the renderer's own code. The renderer also carries hard layout guards: every page-edge string is measured, and one that would overflow its allotted span fails the render rather than rendering wrong.
03 / The firm
A methodology with a company around it.
Landwrit is an underwriting firm built for one niche: RV parks and manufactured housing communities, where creative structures — seller carry, subject-to, wraps, stacked notes — are common and most underwriting tools handle them badly. The firm's operating rule is that autonomy is only safe where verification is deterministic: software does the arithmetic and the checking, and people make every consequential call. Landwrit was founded by Eva Mechelle.
Landwrit files are analytical work product — not an appraisal, and not investment, legal, or tax advice. See the Terms of Service for the full scope of work.