How it works

Plain English first. The engineering is underneath.

Here's what PMStack does inside your operation. At the bottom is the detail your IT and security team will ask for.

jump to technical detail
Aerial view of a suburban neighborhood at golden hour
01

Works with what you already run.

You keep your property management software, your phones and your inboxes. We pull together the information scattered across them — the same resident spelled three ways, maintenance history in an email thread, lease terms inside a PDF — into one clean picture of every home, lease, resident, vendor and dollar.

We build it from the data your company owns and the access your agreements allow, not from any one software vendor's integration program. If you change systems later, everything we've built comes with you.

Your systemsScheduled reports and exports, plus approved connections where your vendors offer them
ConversationsShared inboxes, phone lines, texts and resident messages
DocumentsLeases, addenda, inspections, invoices and notices
MoneyBank activity, payments, payables and owner ledgers
MarketListings, comparable rents and public property records
FieldVendors, work orders, access and inspections
No scraping, no workaroundsNothing that puts a vendor agreement at risk.
Yours to keepThe data and everything built on it belong to you.
02

Held to your best people's standard.

Before anything touches a resident, we sit with the people on your team who have the judgment — your best leasing manager, your maintenance coordinator, your controller — and turn what “good” looks like into tests.

The AI has to pass them before it goes live, and keep passing them every time anything changes. Quality becomes a number you can see, not a feeling.

behavioral, outcome and compliance evals; past failures become permanent regression cases
03

Follows your rules. Every time.

You decide what the AI can do on its own, what needs a person, and what it never touches. Those rules are enforced separately from the AI, so no clever wording from a resident — or from the AI itself — can get around them.

Spending limitse.g. repairs under $350 dispatch automatically; above that, a person approves.
Emergency rulesActive leaks, no heat, gas smells: act first, then notify.
Always reviewedLegal notices, disputes, denials and anything unusual.
NeverDiscuss protected characteristics. Promise concessions. Guess at the law.
04

Gets better every month.

Every time your team edits a draft or overrides a decision, the system records why. That becomes knowledge it draws on next time — and a test it has to keep passing.

A year in, it knows your portfolio the way a long-tenured employee does: which vendor actually shows up, which owner wants a call instead of an email, which homes flood every March. And it belongs to you.

05

Your team stays in charge.

Your staff don't learn a new system. They work one queue of decisions, each with its facts, its sources and the rule that applied. Approve, edit or redirect; everything is recorded.

Workflows start fully supervised. As they prove themselves, you choose what graduates to running on its own.

Why it lasts

Built to get better, not obsolete.

AI changes every few months. Your operation shouldn't have to.

01

Never locked into one AI vendor

When better AI ships, you get it. Nothing to migrate, nothing to renegotiate.

model-agnostic; every upgrade re-tested on your cases first
02

Your data stays yours

Everything we build on your operation belongs to you, and it goes where you go.

built from data you own, not one vendor's integration program
03

Better every month

Every correction your team makes teaches the system — and becomes a test it has to keep passing.

every override becomes a permanent regression case
04

Compliance built in

Fair-housing safeguards, current state rules, and a permanent record of every decision.

rules enforced outside the model; full audit trail
Technical detail

For your IT and security team.

PMStack is an agent harness tuned for residential property management: the layers between a foundation model and a production operation.

Architecture

Five layers. Models underneath.

SkillsWorkflows
Lead responseLeasingRenewalsMaintenanceTurnsCollectionsNoticesOwner reporting
PMStack harnessResidential-tuned
Data layerEvalsPolicy engineMemoryReviewRoutingAudit logRBAC
ModelsSwappable
Frontier reasoningFastVisionVoiceOpen-weight
Model routing

The model is a component.

Each job is routed to the model that wins on your evals: a fast model for triage, a frontier reasoning model for lease and notice questions, a vision model for condition photos. New models are scored against your suite before any traffic moves. Prompts, policies, evals and memory are portable across providers; nothing depends on a fine-tune.

Policy engine

Enforced outside the model.

Policies are declarative and evaluated deterministically on every proposed action, before execution. The model proposes; the policy engine disposes.

# Illustrative policy — maintenance dispatch workflow: maintenance.dispatch auto_approve: max_spend: 350 categories: [plumbing, hvac, appliance, lock] emergency: conditions: [active_leak, no_heat_below_50f, gas_odor] action: dispatch_now_then_notify require_review: - spend_over_limit - resident_dispute - any_legal_notice never: - discuss_protected_characteristics - promise_rent_concessions
Data & security

Yours, scoped and logged.

OwnershipYour data layer, evals and operating memory are yours and exportable.
Least privilegeAgents get scoped, per-workflow permissions; nothing broader.
Audit trailEvery proposal, policy decision, approval and action is logged immutably.
Sanctioned accessNo scraping or credential sharing that breaches vendor terms.
A smart lock and keys on the front door of a rental home
See it on your operation

Bring us your messiest workflow.

In a free working session, we'll show you how it would run — and what we'd leave alone.