( How it works )Four steps
You are in one application, at five to five, with one field holding the model. This is what asking looks like.
Choose your module
One application, not all of them. A guess sends the answer hunting through another application's screens and quotes them back at you as though they were yours.
Ask about the screen in front of you
Name it, describe it, or paste the wording. However you say it is how you would say it to a colleague, and that is enough to find it.
Ask in your own words
The way you would ask the colleague who left in March. Not keywords, and not a support ticket.
Get one answer, with the screens named
Not ten links and a forum thread from 2014. One answer, scoped to your module, every caption in the exact wording the software prints.
Every answer names the screens in the exact wording they print, and comes from somebody who has done the work.
( A real published answer )ARGUS Enterprise 10.1 and later
“Why do my percentage rent numbers differ between ARGUS Enterprise and Valuation DCF?”
Because the two products build the breakpoint from different components, and neither one is wrong.
ARGUS Enterprise computes the Natural Breakpoint from Base Rent plus fixed steps plus CPI. Valuation DCF lets you choose which of those components to include. If the two selections do not match, the breakpoint differs, and every percentage rent figure downstream of it differs with it.
If you share models between the two systems, expect the numbers to differ until you replicate the breakpoint components deliberately. This is a difference in method, not a data problem, so it will not resolve by re-importing.
13 modules are answering today, and three more are catalogued so you can say you want them. Every module, and where each one stops.
( Modules )One per application
You subscribe to the one you work in. An answer scoped to a single application is a different product from a search across all of them.
Valuation and asset management
What a standing asset is worth, and running it lease by lease
Development appraisal and delivery
Appraising a scheme, and running it once it is on site
Property and investment management
Portfolios, leases and the operations underneath them
Modelling and method
The craft that sits under every one of these applications
Professional standards
Qualification and competency, not a piece of software
13 modules are answering today, and three more are catalogued so you can say you want them. Every module, and where each one stops.
( Who it is for )Four people, one situation
Every firm has one person who knows where the field is. This is that knowledge, on call, for the application in front of you.
The new joiner told to learn ARGUS by Friday
Nobody has time to sit with you, and the course is next quarter. Ask the questions you would have asked them.
The analyst at five to five
One field is holding the whole model and the pack goes out at five. You need the screen named, not a forum thread.
The valuer moving between applications
You know one of these tools well and are now in another. The habits do not transfer, and the differences cost you an afternoon.
The candidate studying before a licence
You are learning the method before anybody gives you a seat. Bought on a personal card, below any approval threshold.
( Instead of )The three things you try first
Each of those answers a different question from the one you have at five to five, and none of them is sitting next to you.
A course teaches the screens once
Months before the question arrives, and it is not there on the afternoon it does. The questions that matter are the ones you have while working.
Vendor support answers about the software
On a ticket, in their hours, and it cannot tell you the thing you are trying to do belongs in a different application.
A forum thread was written in 2014
By somebody on another release, about a screen that has since been renamed, with no way to know which part still applies to you.
This is the colleague who left
Available now, scoped to your application and your release, naming the screen in the words it prints.
( At the edge )When it does not know
A confident wrong answer inside a model that prices real assets is the failure that matters, and it is the one you cannot detect.
It says so, in plain words
A refusal is written as a refusal, not dressed up as an answer and not padded into a lecture.
It says why, and where to look
What the module is for, therefore why the thing you asked about is not in it, and which application does that instead.
A practitioner picks it up
Somebody who has done the work answers, usually within one business day, meaning 24 hours Monday to Friday, UTC.
Then nobody waits for it again
That answer becomes part of what the service knows, so the next person asking the same thing gets it straight away.
( What you get )Four things
One answer, scoped to your module, with every screen caption in the wording the software prints on it.
Every screen, field, message and step, described
Across every module answering today, in our own words rather than a vendor's.
Written for the version you are running
Answers follow the current release, and say so when something moved or was renamed along the way.
Captions exactly as the screen prints them
A caption that is approximately right is useless to somebody looking at the actual screen, so nomenclature travels exactly.
An honest refusal, then a practitioner
When it does not know it says so, and somebody who has done the work answers, usually within one business day.
( Your data )What leaves your desk
You type a question. Nothing is uploaded, no file is opened and no model is read.
Your model never leaves your desk
No upload, no file picker, no integration with the application you are working in.
Not used to train a public model
Questions go to a model provider in order to be answered, and no further.
Delete a thread and it is gone
Your account and threads stay until you remove them.
Card details never reach us
Payment, when it arrives, is handled by a merchant of record.
( Pricing )One module, one price
Below the threshold that needs anybody's approval, and bought on a personal card.
49
US dollars a month
The module you work in. Cancel any time and keep access to the end of the period you paid for.
490
US dollars a year
The same thing, with two months of the twelve free.
3
questions free, no card
Create an account and ask. Nothing is charged until you choose to subscribe.
( Questions )Before you pay
The short answers. The rest are on the pricing page, and none of them is a surprise.
Is this Altus, or endorsed by them?
No. Propfessor is independent and not affiliated with, endorsed by, or connected to any software vendor. That independence is why it can tell you what a product does badly as readily as what it does well.
Which release does it know?
You say, and “not sure” is a real answer that changes nothing. Each module page lists the releases it holds enough material to be useful about.
What happens when it does not know?
It says so plainly rather than guessing, and offers to put the question to a practitioner, who answers usually within one business day.
Does it see my model or my files?
No. You type a question. Nothing is uploaded and no model is read.
Do I need a card to start?
No. An account, then three questions with no card.
Can I buy more than one module?
Yes. Each is priced the same, and each is scoped separately, which is what keeps an answer about one application from borrowing another's screens.
( Start )No card
Three questions free. No card, nothing to cancel.
Ask your first questionOr read how it works, the modules, the answers, the pricing or why this exists.