$4.00 per unit per month. Published, because you’d ask anyway.

One price, and it is the whole platform.

The per-unit number covers the analytics and every automation suite. There is no per-seat fee, no per-report fee, and no charge for adding a person who needs to look at it.

Analytics and automation

One line on the invoice

$4.00per unit, per month

11 role-based views, portfolio down to unit, reconciled every morning
All 8 automation suites, 51 automations, phased on a plan agreed before you sign
The approval queue: every resident-facing send waits for a named human
Template governance, with the library owned by your counsel
The weekly ops packet, written for every community
AMI rent-cap checks on every lease event, not at audit time
Heartbeat monitoring, and a monthly report of what ran and what alerted
Branded to your company, on your domain, access by named email address

Platform: $4.00 per unit per month. Analytics and all 51 automations.
Implementation: $45,000 to $75,000, fixed at signature. Half at signing, half at go-live.
Term: Twelve-month initial term, then month to month on sixty days’ notice.
Seats: Not charged. The price moves with your door count and with nothing else.
Your data: One-click export of every dataset in open formats, at any time, including after you leave.
Founding partnerships: A limited number are open and time-boxed, for operators who join early and are willing to be a reference. Those terms belong in a proposal, not on a web page.

Full detail online: the derivation of the hours at noiengine.com/methodology, the security review at noiengine.com/trust, the pricing questions at noiengine.com/pricing

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 and they do not 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.

Do the multiplication here.

You were going to run it in a spreadsheet anyway. This one carries implementation into the per-door number, because $48.00 a unit a year is the platform on its own, and year one is not that. A per-door figure that quietly drops implementation is the kind of thing a CFO finds in under a minute.

Units in your portfolio

At $4.00 per unit per month the platform is $48.00 per unit per year. A 3,000 unit portfolio is $12,000 a month and $144,000 a year. Year one, with implementation, is $189,000 to $219,000, which is $63 to $73 per unit. The per-unit cost falls as the door count rises, because implementation does not move with it.

$12,000Platform, per month

$144,000Platform, per year

$63 to $73Year one, per unit, all in

3,000 units. The platform is $144,000 a year, or $48.00 a unit. Year one, with implementation, is $189,000 to $219,000, which is $63 to $73 a unit. Year two is $144,000.

That is a price, not a return. The hours study sits behind a separate page: task by task, minutes and frequency and loaded rate, normalized per 1,000 units so you can run it against your own door count, with the assumptions I think are weakest labeled as weak. Read how the 1,100 hours were measured before you believe any of it. Nothing you type above leaves your browser. There is no form on this site.

Twelve hours of your people, across three weeks.

Implementation covers the PMS integration, the chart of accounts mapping, template governance setup and training. It is fixed at signature rather than time and materials. What moves the number inside the range is portfolio size, entity structure, and how many suites go live in phase one.

What the fee covers, and what it costs you in hours. The PMS integration, the chart of accounts mapping, template governance setup and training, fixed at signature rather than time and materials. What moves the number inside the range is portfolio size, entity structure and how many suites go live in phase one. Your side of it: one read-only API user, two mapping sessions of ninety minutes, one template review by your counsel, and one hour of training per role. Roughly twelve hours in total across three weeks. Go-live is three weeks from the day the API user exists.

01

One read-only API user

Your Entrata administrator creates a single read-only API user and scopes it. That is the entire access you grant, and it is a contract term as well as a setting.

Week one · 30 min

02

Two mapping sessions, ninety minutes each

Your controller and one operations lead map the chart of accounts, the entity structure and the unit tables to the way you actually report. This is the part that decides whether the output matches your board packet.

Weeks one and two · 3 hrs

03

One template review

Your counsel or your compliance lead reads the resident-facing template library once, approves it, and owns it from that point on. Nothing goes to a resident in language they have not seen.

Week two · 2 hrs

04

One hour of training per role

Training runs by role rather than as one long session, because a controller, a regional and a maintenance director each need a different quarter of it.

Week three · 1 hr each

Roughly twelve hours in total, spread across three weeks and across several people. Nobody on your side is assigned to this full time and nobody writes a requirements document. Go-live is three weeks from the day the API user exists, assuming your team can make the two mapping sessions in the first week. If your entity structure is unusual enough to move that, I will say so before you sign rather than after.

I would rather tell you now than in March.

Published pricing filters people out, which is the point of publishing it. So does this list. Five situations where the honest answer is that you should not buy this.

01

Under about 1,000 units

The implementation does not pay for itself at that size. Keep doing it by hand and spend the money on people.

02

You are not on Entrata today

Entrata is what the connector supports. Yardi is next. If you are on something else we can talk about timing, but I am not going to sell you a connector that does not exist yet.

03

The reporting problem is really a configuration problem

Some of what operators want from a platform is two weeks of PMS configuration and one conversation with their account manager. If that is your situation I will tell you on the call and you can have the twenty minutes back.

04

You are a third-party fee manager

Per-owner billing and separation is a different product with different requirements. This is not that today, and pretending otherwise would cost you a year.

05

Nobody internally will own the approval queue

Every resident-facing send waits for a named human. If no one has the capacity to be that person, the automation suites sit idle and you are paying $4.00 for the $1.50 product. Buy the analytics tier instead, or find the person first.

If two of those describe you, do not buy this. You would get the same answer from me on a call, in week three, after both of us had spent the time. Saying it on a page costs us both less.

The questions that come after the number.

The security and legal questions are answered at length on the trust and security page, which is the one your IT team will want.

Why publish pricing at all?

Because you were going to ask in the first five minutes, and if the number does not work, one of us just saved an hour. Almost nothing in this category publishes a price. That is a sales tactic rather than a pricing model, and I do not have a sales team to feed.

Is the per-unit price negotiable?

For anyone buying it as a product, the published number is the number, and I will not discount it to win a deal against someone who published nothing. There is one exception and I would rather name it than have you discover it: a limited number of founding partnerships, time-boxed and closing, for operators who come in early and agree to act as a reference. That is a different transaction, priced differently, and you are buying it with your name rather than getting a discount for asking. What is negotiable in every deal is scope and timing: which suites go live in phase one and when the rest follow.

What does year one actually cost?

Platform plus implementation. At 3,000 units that is $144,000 of platform and $45,000 to $75,000 of implementation, so $189,000 to $219,000 all in for year one, and $144,000 in year two. Per door that is $63 to $73 in year one and $48.00 every year after. At 6,100 units the same math gives $55 to $60 in year one, because implementation does not move with your door count. Put your own number into the calculator above rather than taking my example for it.

Do you charge per user, per report or per dashboard?

No. One number, per unit, per month. Adding a user, opening another view or pulling another report does not change the invoice. The only thing that moves the price is your door count.

What happens at the end of the twelve months?

It goes month to month on sixty days’ notice. If you leave, you take every dataset in open formats, and you did not migrate a system of record to get here, so leaving costs you a week rather than a year. That asymmetry is deliberate.

What if our system of record ships this itself?

Then tell me and we will scope it at renewal. This is a read-only overlay with a full export, which makes buying it a cheap decision to reverse in both directions. The longer answer, including the cases where waiting is the right call, is on how this compares.

What is deliberately not on this page?

Two billing mechanics: how often you are invoiced, and the date each month the door count is read. I have not published a default for either, because they are the two things operators most often want set to their own close calendar, and publishing a number I then vary in every deal would make everything else on this page worth less. Ask on the call and you get both answers in one sentence, in writing, before you sign. Everything that determines the size of the invoice, rather than its timing, is above.

See the thing before you price it.

The demo is the complete eleven-view platform running on Meridian Residential, a fictional portfolio on synthetic data. No form, no call, and nobody standing between you and it.

Open the live demo Read the security page

If you are weighing this against doing it by hand, hiring an analyst or buying a dashboard engagement, all three are costed on how this compares, including where each of them beats this. If you want the derivation behind the hours, it is on the methodology page. If you would rather just ask, I answer my own phone.