Name the systems the statement touches
Most operations find four or five. Each one is a login, a report and a copy-and-paste step that the calculator's minutes are made of.
Three numbers from your own operation, and the calculator shows the hours a month that go into assembling owner statements from several systems, and what those hours cost in payroll. It runs in your browser on your inputs. Nothing leaves the page unless you ask for the breakdown, and then only your numbers, your first name and your email are sent.
Got it. Your breakdown goes to within one business day. It is your number, worked through on one page.
The free auditAn owner statement is assembled, not written. Someone opens the property management system for the ledger, the bank for the deposits, a spreadsheet for the reserve and the inbox for the invoice that has not posted yet, then puts them in one document and checks that the totals agree. The minutes per statement are that walk between systems. The calculator multiplies the walk by your statement count, so the hours are yours, not an industry figure.
Statements times minutes each. Reviewing the statement is on top of this; the calculator counts the assembly only.
The same hours as whole days of eight hours. It is the clearest way to see what the first week of the month is spent on.
Hours times the hourly cost of the person doing them. The money is already spent; the question is what else those hours could carry.
The hours go away when the numbers are read from each system by a build instead of a person, and the statement is checked rather than assembled. The Owner Dashboard is the first step: it reads your property management system every morning and shows each number with its source and its as-of time, so the walk between systems happens once, on a screen, before the month closes. The statement still comes out of your property management system. The hours spent getting it right do not.
Most operations find four or five. Each one is a login, a report and a copy-and-paste step that the calculator's minutes are made of.
The build reads each system in place. Nothing is exported by hand and nothing is retyped, so the number on the screen is the number in the system.
The person who built statements now reads them. The hours that come back go to the owner calls and the renewals the month never had time for.
Operators ask whether the inputs go anywhere, what to count in the minutes per statement, whether the hourly cost should include more than wages, and whether the hours really come back. The answers below are the ones we give on the call, in the same words.
Only if you ask for the breakdown. The arithmetic runs on the page. Ask for the one-page breakdown and your numbers, your first name and your email are sent so it can be written up. Nothing else is. Reload the page and the starting numbers come back.
The time from opening the first system to the statement being ready for review: pulling the ledger, matching the deposits, adding the invoices that have not posted, and checking the totals. Time your next three statements and use the average.
Wages are the floor. The fully loaded cost, with taxes and benefits, is the honest figure if you have it. Either way the calculator shows the arithmetic, not a claim about your business.
Only if something else absorbs the assembly. That is what a build does. No time-saved number publishes on this site until a client's hours are measured before and after, so the calculator shows your hours today and nothing else.
The free audit is thirty minutes on a call. Bring one statement and the list of systems it took to build. We look at the numbers you already have, you leave with a one-page map of your operation and the constraint costing you most, and nothing is quoted on the call.