A property management company evaluating AI-first HOA software almost always asks a version of the same question before they ask about features: "What happens to my bill if the AI runs more than expected?" It's a reasonable worry. Usage-based AI pricing has a well-earned reputation for surprise invoices — a chatbot that fields more questions than projected, a busy month that quietly costs three times a quiet one. A PMC running thirty communities on thin per-unit margins cannot afford a vendor whose bill is a mystery until it arrives.
LotWize's answer isn't a promise — it's a page. /pmc/ai-costs gives every portfolio owner a running, per-community accounting of how much AI activity happened this month, what it's estimated to cost, and where it's concentrated across the portfolio. Paired with a daily spend guardrail that flags any single day that looks abnormal, it turns "trust us, it's included" into something a manager can actually verify.
The fear behind "AI-powered" pricing
Every property management software vendor now claims to use AI somewhere in the product. Almost none show what that AI actually costs to run, because most don't meter it internally in a way they could show a customer even if they wanted to. That opacity cuts two ways: vendors skip the engineering work of tracking usage per customer, and PMCs are left assuming AI features are either priced into a black box or destined to become a new line item once the vendor needs to recoup its own model bills.
LotWize's PMC tier is priced flat — $0.50 per unit per month, $200 minimum — and the platform's AI features, from the resident chatbot to violation drafting to vendor benchmarking, all run inside that rate. No per-query metering, no AI add-on tier. That's the commercial promise. The cost dashboard is what makes the promise checkable instead of just stated.
What the dashboard actually shows
Every AI call anywhere on the platform — a resident's question to the assistant, a violation photo run through detection, a vendor invoice checked for anomalies, a financial narrative generated for a board packet — gets logged with its estimated cost and token count, tagged to the community that triggered it. /pmc/ai-costs rolls that log up for the current calendar month and shows three things:
- Portfolio AI spend — a single dollar figure, plus the total number of AI calls behind it, for the current month.
- Communities with AI activity — how many communities in the portfolio generated any AI usage this month, against how many exist in total.
- A per-community breakdown table — each community's call count, token total, and estimated cost, sorted highest spend first, so whichever community is driving the number is visible instead of buried in an average.
A portfolio with quiet communities and one unusually active one shows that lopsidedness directly in the table rather than hiding it in a blended total. A community with zero rows isn't an error — it just hasn't generated AI activity that month.
The page states its own framing directly: AI usage and spend across the portfolio, "for your visibility, not a separate charge." That line is doing real work — it tells the manager up front that nothing here is a bill they'll be asked to pay. It's the receipt for a rate they're already paying.
The rollup is arithmetic, not a black box
It's worth being specific about how little magic is involved, because a "transparency" feature only earns trust if the math behind it is auditable rather than another opaque model output. The rollup — aggregateAiCost() — is a pure function: it sums cost and tokens per community from the raw usage rows and sorts by spend. No AI estimates the numbers on the page. The dashboard reports on AI usage; it doesn't use AI to summarize that usage. A cost dashboard that itself required trusting a model's arithmetic would defeat its own purpose.
The daily guardrail: catching a bad day before it becomes a bad month
A monthly rollup answers "where did the money go," but it doesn't catch a spike while it's happening. That's the job of the daily guardrail. Once a day, a scheduled job sums each portfolio's AI cost for the current day and checks it against a threshold — $2 per portfolio per day by default. Cross it, and the system raises one deduplicated alert per portfolio per day, landing in the same alert stream a portfolio owner already checks for other automated exceptions, not a separate inbox to remember.
The dedup matters: without it, an ongoing spike would generate a fresh alert every time the job runs instead of one flag a manager can act on and dismiss. And because the threshold check runs on the same aggregateAiCost() math as the monthly dashboard, the two numbers always agree. $2 a day is deliberately conservative — a tripwire for the scenario that actually worries PMC operators, not "the assistant was popular this month" but "something is stuck in a loop, burning tokens no one asked for."
What this dashboard is honest about not doing
Overstating a feature does more damage to trust than the feature is worth, so the scope is worth stating plainly. The dashboard reports calendar-month-to-date, not a rolling 30-day window — checking on the 2nd of the month will show a small number, correctly. It breaks spend down by community, not yet by which specific AI feature drove it; a manager can see Community C spent more than Community D, but not whether that was the resident chatbot or violation detection without checking the underlying logs. That finer-grained tagging is on the roadmap, not shipped today.
The guardrail alert is also just that: an alert. It doesn't pause features or cap usage automatically when a portfolio crosses the threshold. It surfaces the number to a human who decides what to do, consistent with how LotWize's autonomy ladder treats every other automated decision on the platform — AI surfaces information and, at higher autonomy settings, takes bounded action, but it doesn't make unilateral financial decisions on a portfolio's behalf.
Why this matters more once you're managing a portfolio
A self-managed board running one community has a much smaller version of this worry, and it's easy to resolve by watching whether the bill changes — those plans are flat too. The stakes are different for a PMC. A manager fields the "why is our software bill higher this month" question not from their own board but from a client relationship they're trying to keep, across communities they can't personally watch line by line. Opening a dashboard and showing a client's treasurer exactly how many AI calls their community generated — and that the number rolls into the flat rate, not a surprise invoice — is a different conversation than saying "the platform handles that" and hoping it's true.
Competing PMC platforms in the same tier — CINC Systems at $0.80–$1.20/unit, Vantaca at $2.00–$4.00+/unit — either offer minimal AI or price agentic automation at rates that assume the AI cost is folded in somewhere upstream, without a customer-facing accounting of it. LotWize's bet is that showing the math, even when the number is small, builds more trust than a marketing page claiming "AI included" with no receipt behind it.
Key Takeaways
/pmc/ai-costs shows a portfolio's total AI spend, call count, and a per-community breakdown for the current month — sourced from the same aiUsageLog every AI feature on the platform writes to.
The framing is explicit: this is visibility into usage already covered by LotWize's flat $0.50/unit/month PMC rate, not a separate or metered charge.
The cost rollup itself is plain arithmetic (aggregateAiCost) — no AI estimates the numbers on the page; AI generates the usage being measured, not the measurement.
A daily guardrail (default $2/portfolio/day) raises a deduplicated alert if a day's AI spend crosses the threshold — a tripwire for runaway usage, not an automatic spending cap.
The dashboard is monthly and per-community today; per-feature/per-agent cost breakdown is on the roadmap, not yet shipped.
Frequently Asked Questions
Does LotWize charge extra for AI features on the PMC plan?
No. LotWize's PMC tier is flat — $0.50 per unit per month, $200 minimum — and all AI features run inside that rate. The AI cost dashboard reports usage for visibility; it isn't a separate or metered bill.
What does the AI cost dashboard actually track?
It rolls up every logged AI call across a portfolio's communities for the current calendar month: total estimated cost, total calls, how many communities had any AI activity, and a per-community table sorted by spend.
How does the daily AI-spend alert work?
A scheduled job sums each portfolio's AI cost for the current day against a $2/portfolio/day default threshold, raising one deduplicated alert per portfolio per day if it's crossed. It's a notification, not an automatic throttle or spending cap.
Can I see which specific AI feature is driving a community's cost?
Not yet. Today the dashboard breaks spend down per community, not per feature — separating, say, chatbot cost from violation-detection cost within one community isn't shipped yet.
Is this available to self-managed HOA boards, or only property management companies?
It's a PMC portfolio feature. A self-managed board with one community has no multi-community rollup to view, but the same flat-rate promise applies: AI runs inside the plan's price, with no separate usage billing.
If "AI-powered" pricing has made you nervous before, the fix isn't a longer FAQ page — it's a dashboard you can actually check. Explore LotWize for property managers or start a free trial to see what your own portfolio's AI usage looks like, or read how Cross-Portfolio Intelligence turns that same usage data into vendor benchmarks and best-practice leads across your communities.
