The person running a management company and the person running one of its communities open the software on the same Monday morning.
They are not asking the same question.
The owner's question is whether the business is working. Revenue, orders and refunds over any range they pick. Which communities actually drive the volume. What's stuck and waiting on a person. That screen exists — post 33 took it apart.
The community manager's question isn't a business question at all.
Theirs is: what is going on in my community, today?Nine open violations. Four architectural requests waiting on somebody. Six work orders. Eleven accounts behind. Their community's own revenue, products sold and refunds — theirs and nobody else's. Units, owners, board members. Recent orders down one side, recent violations down the other.
Money and compliance aren't two departments to a community manager. They're the same Tuesday.So that dashboard puts them on one board. It isn't a report. It's a shift handover.
The old version of both screens is a phone call. Upward it's called a status update, downward it's called a check-in, and neither one has ever produced a number.
Now the tempting shortcut: build one dashboard, show it to everybody, let permissions sort it out.
It fails both of them.
Give the manager the portfolio chart and they scroll straight past it hunting for their nine violations. Give the owner ninety community boards and they're reading ninety of them, looking for a pattern that only exists added up.
A screen built for everybody is a screen built for nobody in particular.Both dashboards share the same date presets — this week, last week, this month, last month, or dates you pick yourself. And both only ever show what the person in the chair is allowed to see, which is the unglamorous rule from post 38 doing its job quietly.
Same data underneath. Two altitudes. Two entirely different Mondays.
Next: the one page in this whole product that has to convince somebody who has never heard of you.