PropEaze

Unverified work costs you nothing.

PropEaze is outcome-based maintenance infrastructure for multifamily operators. Every job is tied to a specific unit, measured against a published verification standard, and verified before payment releases. Our rate is 30% of verified savings.

Read-only at intake. No vendor onboarding, no process migration, no seat rollout.

TKT-█████Verification record

sample · unit ███ · vendor ████

01ticket.ingestedT+00:00

02vendor.dispatchedT+00:11

03vendor.assignedT+00:26

04work.resolvedT+04:15

05kpi.capturedT+04:38

06payment.releasedT+04:41

UnitVerified · Standard passed

OutcomeVerified · Pass

InvoiceWithin NTE

Gainshare30% of verified savings

01The underwrite

One rate. Published, not quoted.

30% of verified savings. Nothing on unverified work, nothing on disputed work, and nothing on work that fails the verification standard. No seat license, no per-unit fee, and no implementation charge

Savings are measured against a baseline frozen at enrollment: your own trailing twelve months in the same cost categories, on the same units, adjusted only for documented scope change. You approve the baseline before anything is billable. We do not set it, and we do not revise it after the fact.

If the savings don't verify, we don't get paid. Our economics are directly tied to yours.

02Who it's for

Built for multifamily operators.

Multifamily owner-operators running 5,000 to 25,000 units spend like an anchor account and get priced like scattered small landlords. Vendors close their own tickets. Scopes drift off the unit. Invoices clear before anyone confirms the work held. The gap between what you paid for and what actually got fixed is the chaos premium, and it is paid every month in rework, callbacks, and turn days nobody reconciles.

PropEaze closes that gap: consolidated ticket flow, unit-scoped work, verified completion, and payment released only when the agreed standard is met.

03The mechanism

Payment releases only on verified completion.

Every job is evaluated against a defined verification standard, not simply marked complete because a vendor says it is done. No self-reported closes. No unverified spend.

Before an outcome can be measured, the work must be tied to the specific unit it belongs to. The record remains auditable and correctable, and any corrected input is re-evaluated through the same standard.

In shadow mode, the same verification process runs read-only: we produce the verification record on every ticket while you continue paying through your current process. Payment gating begins only after the standard clears and you contract against it.

Ticket intake→Dispatched→Resolved→Captured→Verification→Released

See the verification methodology →

Vendors keep their recourse. A failed verification does not end in a withhold. It opens a documented cure window during which the vendor can return, correct the work, and re-submit, and an appeal path if they dispute the grade. Nothing becomes final until the cure window closes and the appeal resolves. The same event chain that fails a ticket is the record the vendor argues against, so the dispute runs on shared evidence rather than on competing recollections.

TKT-█████Verification record

sample · unit ███ · vendor ████

01ticket.ingestedT+00:00

02vendor.dispatchedT+00:14

03vendor.assignedT+00:31

04work.resolvedT+03:52

05kpi.capturedT+04:20

06payment.heldT+04:22

Unit scopeMatched · Gate passed

OutcomeCaptured · Fail

Cure windowOpen · vendor appeal live

PaymentHeld pending re-verification

04The standard

A verification standard, not a tool.

PropEaze measures maintenance outcomes to a settlement grade: the bar a counterparty would demand before accepting a number as fact. Vendor scorecards report averages. A settlement standard has to survive being a wrong in public, so the predicate is stated in advance, measured conservatively and graded on live tickets.

The predicate

Verified callback rate, Wilson 95% CI upper bound below 5%, sustained on live tickets.

Denominator: verified completions across the cohort, pooled, minimum 1,500. No single operator over 45% of the pooled denominator. Callback is any return visit to the same unit for the same fault within 30 days of verified completion. Callbacks count against us whether or not the vendor agrees.

In plain terms: fewer than 5% of verified completions come back as repeat work, and we hold ourselves to the pessimistic end of the confidence interval rather than the point estimate, the same convention an actuary would apply. The guarantee activates when the predicate clears. Until it does, the rate still only applies to savings that verify.

Published methodology. Graded on your tickets, not ours.

05Who built it

Built by an owner-operator.

You know the gap if you approved the invoice, seen the callback three weeks later, and run the math on what it would cost to prove they were the same job. Nine years operating real estate assets, value-add acquisitions, and the vendor, contractor, lender, and engineering coordination that comes with them is how we learned to see it. PropEaze is the verification layer we wanted and could not buy.

No third-party model provider trains on your data. PropEaze retains the evidentiary record itself, in your tenant, because the record is what makes the witthheld payment defensible.

PropEaze holds the right to use deidentified outcome data in aggregate to improve the verification model. That pool is what makes the predicate gradeable and the guarantee priceable at all, and every operator in it is on the receiving end. Nothing identifiable to you or your vendor enters it: no cell is modeled or published below a minimum threshold of contributing operators and vendors, and no vendor performance data attributable to your portfolio is ever disclosed to another operator. SOC 2 Type I engagement is underway. The Type II observation window opens with the first live customer.

06The cohort

Shadow cohort. Four operators.

Shadow mode runs on your live tickets, read-only. We ingest real work, run the full event chain, and produce a verification record for every ticket, with no payment gating, no vendor-facing change, and no disruption to your current process. You see exactly what our predicate says about your portfolio before anything is contracted against it.

Verification resolves when the cohort reaches 1,500 verified completions, measured under the published denominator rules. That print is the first benchmark of this standard graded on live operator tickets, and cohort operators are named as its founding participants.

Enrollment closes when the cohort fills.

No demo. No discovery call. Send ticket volume and your PMS and we'll come back with what the predicate says about your portfolio.