About Latchstead
Latchstead is property-management software for small and accidental residential landlords. It runs the tenant-lifecycle operations that a property manager would normally handle — screening, rent collection, maintenance triage, and books reconciliation — so a one-to- twenty-unit landlord can run the portfolio without hiring a manager.
This page is the place to verify what we’re about, what we will and will not publish, and how to get in touch. Where a fact isn’t ready to publish, the section below names it openly rather than dressing it up.
Scope
The product covers four operational loops a residential landlord runs every month. The first column on the left is the operational posture — the right column is what we actually ship.
Designed FCRA-aligned decision support for residential applicants — documented criteria, review context, and an adverse-action notice draft when a rule needs follow-up. This is a product posture, not a certification or completed compliance determination.
A planned ACH workflow for lease-based timing, retry handling, late-fee context, and state-specific notice review. Provider behavior and local-law requirements remain implementation and landlord responsibilities.
A planned after-hours intake and severity workflow with market-dependent dispatch handoffs and work-order preparation. Latchstead does not claim a vetted vendor network or guaranteed arrival timing.
Planned QuickBooks Online and Xero integration paths for receipt context, category mapping, and month-end review. Connection scope and live sync behavior are integration-dependent and not production proof.
Fit
The same framing we use on the homepage, phrased here as a posture rather than a pitch. If you fall in the right column, the product probably is not for you — and we’d rather say so than guess.
Launch stage
Early access — waitlist only.
Specific to a single operator’s stated choice — not a date we invented. Pending attorney sign-off before being relied on as a consumer-protection statement.
Latchstead is in early access. Accounts open in small cohorts while we qualify the operator-to-workflow fit and prove the integrations against real portfolios. New customers are admitted from the waitlist as capacity allows, not on a first-come-first-served drip.
Until a customer count, certification, or other operating number has been verified by an independent source, we will not publish it on this page. The same rule applies anywhere on the site — we are not going to claim a number we cannot stand behind if a regulator, journalist, or applicant asks about it.
Contact
Until a registration address or a named lobby of people exists, we keep the contact surface minimal: one email, monitored by the operator. Security reports use the same channel — see the Data Security page for the timing commitment.
Product, partnership, security, and press inquiries all route here. One human responds.
latchstead@polsia.appPostal address
We do not publish a postal or registered address on this page yet. Once the operator supplies a verified address and indicates whether it should be masked, it goes here and into the footer fine print.
Publication dependency — awaiting operator
Publication dependencies
Rather than inventing any of these, we publish them here, owner-facing, in the order they would unlock the corresponding line of copy. Once each fact is supplied and verified, the corresponding statement on this page (or on the legal pages) updates; until then, the section is empty or carries the placeholder shown.
Legal entity name
Reason: Not yet supplied by the operator.
Where it will appear: On the "Who runs Latchstead" line and in the footer fine print once provided.
Jurisdiction of formation / registration number
Reason: Not yet supplied by the operator.
Where it will appear: Same line as above. Required before this can be stated as a verified fact.
Principal or mailing address
Reason: Not yet supplied by the operator; we do not publish a fabricated address.
Where it will appear: Contact card on this page once provided (masked or unmasked, at the operator’s option).
Founder or operator name and role
Reason: The operator has chosen to remain unnamed for now.
Where it will appear: First-person-operator voice throughout this page until a name is supplied.
Year the product launched
Reason: Not yet supplied by the operator; we will not invent a date.
Where it will appear: Launch-stage disclosure and any historical-statements claim.
Verified user / portfolio counts
Reason: We will only state numbers we can verify — a specific count or a verified range.
Where it will appear: Any "trusted by N landlords" or "in use in M markets" claim will not appear until verified.
Verified compliance certifications
Reason: We will not claim SOC 2, ISO 27001, FCRA certification, or any other framework unless verified by an outside auditor.
Where it will appear: The Security page and this page; the "FCRA-aligned screening" claim is behavioral, not a certification.
Trademark filing status of "Latchstead"
Reason: Pending confirmation.
Where it will appear: Footer fine print and any exclusivity claim.
Related
Last updated: August 22, 2026