One over-cap lease
On an attainable or HUD book, a single lease signed above the AMI cap costs more than a year of NOI Engine. Checked on every lease event, not at audit time.
Nightly
For multifamily owner-operators · 1,000–15,000 units · Entrata-native
One lease signed over the rent cap costs more than a year of this.
Fifty-one automations watching the deadlines, the dollars and the compliance windows your team is currently holding in their heads. Read-only into Entrata. A named person on your team approves anything that leaves the building.
Open the live demo No form. No call.Or write to the founder
Read-only into Entrata
Reconciled 06:00 ET
51 automations
8 suites
11 role-based views
~1,100 hrs returned / mo
$4.00 / unit / month
Any one of these pays for the platform.
Hours are the baseline. The catches are the point. Every figure here comes from a methodology you are welcome to audit line by line. None of it is a guarantee, and none of it is borrowed from somebody else’s case study.
One missed notice window
A vendor contract that auto-renews because a 90-day window slipped is a five-figure miss. Every window carries a countdown and a named owner.
DailyOne bleeding unit
“This unit has cost you $3,400 so far.” Every stalled turn is priced per day and ranked before Monday, so the conversation starts with the number.
Per turnOne covenant surprise
DSCR headroom projected 60 to 90 days ahead of the test date. You see a breach coming while there is still time to act on it.
WeeklyThe arithmetic is yours, not mine. Run one of these against your own book. That is the whole argument, and it does not require you to believe a savings estimate. How the 1,100 hours were measured is published in full, including the assumptions I think are weakest.
Eight suites. Every recurring task, watched or written.
The Monday packet. The lease-up checklist. The contract renewal windows. The rent-cap checks. The stalled turns nobody priced. It all gets done by hand, until the week it doesn’t. Hour figures are directional and normalized to about 0.18 hours per unit per month, so you can run them against your own door count.
Lease-Up Command Center
Your full opening checklist live-tracked with owner digests. Contracts abstracted. Collateral and eblasts drafted for approval.
~105 hrs / moReporting and Alerting
The weekly ops packet generated for every community. Exception alerts on your thresholds. Covenant projections before the test date.
~165 hrs / moCompliance Guard
AMI rent-cap checks on every lease event. Recert countdowns. COI and license expiry. Lease-file audit sampling before the auditor.
~145 hrs / moMaintenance and Turn Money
A lost-rent meter on every stalled turn. SLA breach escalations. Triage that flags urgents up, never down. Utility recapture.
~170 hrs / moMoney-Side Audits
Late-fee consistency. Concession audit trails. Tax and insurance exposure flagged before it hits the accrual.
~30 hrs / moLeasing Funnel and Renewals
Renewal and application watchdogs. Speed-to-lead reply drafts. Review responses in your voice. Every send approved by a person.
~275 hrs / moFinancial Narrative
Month-end variance commentary drafted with GL citations. Owner reports assembled. Deposit deadlines tracked to the statute.
~190 hrs / moPlatform and Reliability
Heartbeat monitoring, nightly reconciliation against your PMS’s own reports, and a monthly reliability report. If a check stops running, both of us get paged.
Included36 of the 51 are available today. The rest are phase two or roadmap, and every one of them carries its tier in the catalog. Presenting all 51 as shipping now is a claim that would not survive your diligence, so the tiers are published instead.
51Automations
~1,100Hours returned / month
$500KLabor value / year
ZeroWrites to your system of record
Hours, not headcount. Nobody in this business is overstaffed right now and I will not pitch it that way. The two middle figures were measured on one operating portfolio and yours will be different, which is why the derivation is published task by task rather than asserted. The last one is not an estimate. It is a contract term.
Eleven role-based views, and not the reason to buy this.
Included with every plan. Dashboards do not catch the over-cap lease and they do not write the Monday packet, which is why the automations lead this page and the analytics follow it.
Eleven role-based views over one set of definitions, so the number on the CFO’s screen and the number on the regional’s screen are the same number. Portfolio down to unit. The CFO, the COO, regionals, community managers, revenue, leasing, maintenance and owners each read from their own seat, off the same reconciled data.
Branded to your company, on your domain, gated to named email addresses your team controls. Walk the eleven views on a fictional portfolio before you spend twenty minutes of anyone’s time.
- One set of definitions
- No parallel spreadsheet and no second version of occupancy. If two people disagree about a number, they are disagreeing about the definition, and the definition is written down.
- Reconciled nightly
- Every view carries the timestamp it reconciled as of. A figure that cannot be reconciled against your PMS’s own reports is not displayed at all.
- Exception first
- Views surface the twelve things that moved, not the four hundred that did not.
Plugged into your PMS. Never in its way.
Entrata today, through a purpose-built read-only connector. Yardi is next. The definitions layer is PMS-agnostic by design, which is the whole point of sitting on top of whichever system you already run.
- Connect, read-only. A dedicated read-only API user that your IT team provisions, scopes and can revoke in about a minute without contacting anyone here. NOI Engine never writes to your system of record.
- Reconcile nightly. Every metric is checked against your PMS’s own reports and stamped with the time it reconciled as of. If reconciliation fails, the stamp says so instead of showing you a number nobody checked.
- Watch, write, draft. Reports generate. Watchdogs run. Drafts queue. All from one set of definitions your whole team shares.
- Your people approve. One approval queue. A named human presses send on anything resident-facing or vendor-facing, and the approver, the timestamp, the template version and the final text are recorded on every message.
What it costs you in hours. Roughly twelve hours of your team’s time across three weeks. One read-only API user provisioned by IT. Two ninety-minute mapping sessions with your accounting lead. One template review with counsel. One hour of training per role. No agent installed on anything, no VPN, and no inbound connection to your environment of any kind: the platform reaches out to your PMS, nothing reaches in.
Built to pass your IT and legal review, not just your demo.
Written to be read cold by an IT director and a general counsel with me nowhere in the room. Everything a review normally extracts from a vendor over three calls is on the trust and security page, including the parts that are not finished yet.
- Read-only scope
- The integration cannot write to your system of record. Not a lease, not a charge, not a note, not a status change. That is a contract term, not a setting, and the credential your IT team issues should not carry write scope in the first place.
- Your data stays yours
- Never pooled, blended, benchmarked or resold across clients. Not anonymized, not aggregated, not for model improvement. One tenant, one dataset, one purpose.
- Template governance
- Resident-facing text is never free-written by a model. Facts merge into templates your counsel writes and owns, with identical treatment at every stage of a process, a named approver on every send, and a quarterly send log delivered to your legal team without them asking.
- Continuity, papered
- Source-code escrow, documented schemas and metric definitions, runbooks for every scheduled job, and one-click export in open formats at any time, including after you leave.
- Reliability you can check
- Heartbeat monitoring on every scheduled job, and a monthly report of what ran, what alerted and what did not run. Including the bad months. Silence is treated as a failure, not as a pass.
What NOI Engine will never do, in writing. No collections dunning and no eviction documents. No handling of resident income files. No unattended AI sends, ever. No rent-pricing recommendations of any kind. No writes to your PMS or your Microsoft environment without a separately signed phase. No client data pooled or benchmarked across accounts. These are contract terms, not marketing.
The exact API scopes, the sub-processor list and the exclusions exhibit are published rather than promised. If your organization has a standard vendor security questionnaire, send it before the demo instead of after and it comes back filled out.
Simple, per unit, published.
Published because you were going to ask anyway, and because every conversation it disqualifies early is an hour returned to a founder who has none.
Analytics and all 51 automations
The platform
$4.00
Per unit, per month
- All eleven role-based views, portfolio down to unit
- All eight automation suites, 51 automations
- The approval queue and counsel-owned template governance
- The weekly ops packet, generated for every community
- AMI rent-cap guard and the compliance calendars
- Heartbeat monitoring and the monthly reliability report
- Implementation
- $45,000 to $75,000 depending on portfolio size, entity structure and how many suites go live in phase one. It is fixed at signature, not time and materials, and it is billed half at signing and half at go-live. It covers the PMS integration, chart-of-accounts mapping, template governance setup and training.
- What your team spends
- About twelve hours across three weeks. One read-only API user, two mapping sessions, one template review with counsel, one hour of training per role.
Analytics on its own is $1.50 per unit per month. It is available, and it is the least valuable way to buy this. Dashboards do not catch the over-cap lease or write the Monday packet. If your problem is that nobody can see the numbers, buy it. If your problem is that your team is doing the work by hand, do not.
What implementation includes, and who this is not for. Or read by hand, an analyst, or dashboards, costed honestly, including the cases where each of them beats this.
The ones your legal and IT teams will ask.
Answered here rather than on a call, because the people who ask these are usually not the people who took the demo.
We already have Entrata reporting. Why would we need this?
Entrata reports what happened. It does not watch. It will not tell you on a Saturday that a lease was signed eleven dollars over the cap, it will not price a stalled turn per day and rank it before Monday, and it will not draft the renewal outreach and hold it for a named person to approve.
If your reporting is late but accurate, and nothing is currently slipping through a deadline, you do not need this. That is a real answer and it disqualifies more conversations than it wins.
Does it write to our Entrata?
No. The connection is read-only and that scope is a contract term, not a setting. Any future write capability would be a separately signed phase with its own sandbox testing and its own sign-off. Most operators never ask for one.
What happens when Entrata builds this themselves?
Some of it, eventually, they probably will. PMS vendors build for the median customer across tens of thousands of properties, which is why an AMI rent-cap check that runs on every lease event still is not there. If your needs sit close to the median and you can wait, waiting is the right call and I will say so.
The longer version, including where waiting wins, is on how this compares.
You are one person. What happens if you get hit by a bus?
It is answered with documents rather than reassurance: source-code escrow with named release triggers, documented schemas and metric definitions, runbooks for every scheduled job, and one-click export in open formats at any time. A competent contractor can operate the platform from the documentation.
Ask a funded vendor with forty employees the same question. Having a team is not a continuity plan either. A one-person vendor just has to hand you the plan sooner. More on who builds this.
Will our IT and security team approve this?
Send me your standard vendor security questionnaire before the demo rather than after, and it comes back filled out. Where a control does not exist, it will say so instead of answering around it. There is no SOC 2 report today, and the compensating controls are listed in full on the trust and security page.
Is this safe under fair housing?
AI never free-composes resident-facing text. It merges whitelisted fields into templates your counsel writes and approves, applies identical treatment at every stage of a process, requires a named human approval on every send, and logs every message so the log cannot be edited after the fact.
Your legal team owns the library and receives a quarterly report of exactly what went out, under which template, approved by whom. They do not have to ask for it.
Will this replace our staff?
No, and I will not pitch it that way. Nobody in this business is overstaffed right now. What goes away is the compiling, the chasing and the remembering. What comes back is the hours your team spends on leasing, on residents, and on the judgment calls that need a person.
Which property management systems do you support?
Entrata today, through a purpose-built connector. Yardi is next. If you run something else, ask. The definitions layer is PMS-agnostic by design, but a connector is real work, and you will get an honest timeline rather than a hopeful one.
The person on the demo is the person who writes the code.
You will not be qualified by an SDR, handed to an account executive, then handed again to an implementation team that has never seen your portfolio. There is one phone number on this site and it rings on my phone.
The person on the demo runs the implementation and picks up the phone at 7am when the Monday packet is late. I take fewer clients than a funded vendor does, and the ones I take get an owner instead of a ticket number.
The obvious risk in that paragraph is me, and it is papered rather than argued. The continuity documents are named and dated on the trust and security page, so you can read the exit before you ever speak to me.
Twenty minutes, live in the product, on real screens. Bring your worst reporting problem.
No form. No call. Every number in the demo is synthetic.