In part one you added a property, answered four questions and looked at next Saturday. Suppose the number is wrong.
Good. That is the point of day two.
A price you cannot argue with is a price you cannot trust. So every night RateVeld recommends opens into its reasons, in plain words, in the same order every time. Here is how to read one in the time it takes to drink a coffee.
Start where the number starts
The first line is what comparable places near you are charging for that night, blended with the ordinary-night price you gave us. It says how much of the figure comes from those comparables.
If that first line already looks wrong, stop there. Either the comparables are not your kind of place, or your ordinary-night price was a guess. Both are fixable in a minute, and nothing below that line will make sense until you fix them.
If it looks about right, read on. Season moves it. An event nearby moves it. A Friday or Saturday moves it by the weekend uplift you set. Then your floor and ceiling have the last word, and the result is the number you saw on the calendar.
Three things the panel tells you without saying so
A striped night is a thin one. Stripes mean too few comparable listings were found for that night, so the number is a guide with a range beside it, not a precise figure. Read the range, not the point. It sharpens as the suburb's data fills in.
If every day shows your ceiling, your ceiling is doing the pricing. That is not the market talking. Either raise it to where a guest would still say yes, or look at the comparables it is being measured against.
If every day shows your floor, you set the floor too high. The floor is the least you would happily take, not the price you hope for. A floor that never lets the curve move has quietly become a fixed rate again.
Disagree, then record what you did
RateVeld never changes a price on Airbnb, Booking.com, LekkeSlaap or anywhere else. You read the recommendation, you set the rate on your own channels, or you do not.
When you do set one, mark it on the night. A tick records what you charged so the calendar can hold your decision against the market later. It changes nothing on any platform. It is a note to yourself that the system can read.
Over a week, those ticks become the most honest record you have ever kept of your own pricing: where you followed the market, where you overruled it, and what each choice earned.
Two things worth connecting on day two
Neither is required. Both make the argument fairer.
Your Airbnb prices. Type them in or upload them, and the calendar shows your rate beside ours on every night. Where yours sits 15 percent or more under the recommendation, the night gets a red edge, and a tap shows the gap in rand. You stop comparing from memory.
Your calendar feed. The iCal link from your channel carries your booked and blocked nights and nothing else. It cannot see your prices. What it gives you is your own occupancy on the dashboard instead of an area estimate: how full the next 90 nights actually are, read from your calendar, not guessed.
That is day two
You can now read a recommendation, tell a confident night from a thin one, spot when your own guardrails are doing the pricing, and keep a record of what you decided. No course, no settings tour, no new vocabulary beyond floor, ceiling and the night you were always unsure about.
What you have not seen yet is the part this week cannot show: the nights six months out that guests are booking now. That is part three.
If you have not added a property yet, start there. Saturday is waiting to be argued with.