A practitioner forum, not a feed
A place for operators to ask questions, share ideas and get feedback. The forum is planned; the areas and example threads below show what it is for.
Where conversations will live
Eight areas, each with a job. Posting will be open to members; reading will be open to everyone.
Discussions
Open conversation about revenue management practice.
Questions
Specific problems with specific answers.
Build Feedback
Show what you made and ask what is wrong with it.
Module Ideas
Propose the module you wish already existed.
Troubleshooting
When the tool runs but the numbers look wrong.
Revenue Management Concepts
The vocabulary, argued out properly.
Showcase Threads
Finished work, with the reasoning attached.
Standards
How car rental systems should exchange data.
What a thread looks like
The threads below are written examples showing the kind of question the forum is for. They are not real posts, and no member identities, counts or engagement figures are shown anywhere on this site.
My competitor comparison says I am 12% high. Should I believe it?
Depends entirely on what it compared. Same location pair, same pickup and return dates, same mapped class, same currency, same treatment of taxes and fees? Change any one and the 12% is describing something else.
Fleet pressure looks fine but we sold out on the 14th
Check whether the tool counts pickups or occupied days. A five day rental starting on the 10th takes a unit out on the 14th too, and a pickup-based count will not show it.
Where should I put my freshness threshold?
On screen, as a control, with the age of every observation visible next to it. Hard-coding it in the script means nobody reading the output knows what was excluded.
Is average rate the average of quoted, booked or realised?
All three are used, and they answer different questions. Pick one, define it on the page, and be consistent. Most arguments about performance are really arguments about this.
How to ask a good question
The forum works better when a question carries enough context to be answerable.
Say what you were trying to find out, in business terms.
Say what the tool did, and what you expected instead.
Show one row of synthetic data that reproduces it. Never paste real customer or pricing data.
See what others have built
Member builds show the shape of a finished tool and the decisions behind it.