Operational problem solving for properties.
We look at how a property actually runs, then change the parts that create friction: unclear processes, scattered information, and decisions made without the right data.
Where we make the difference.
Property management is where operations, guests, and revenue meet. We work on the parts that are hard to see from the outside: how requests are handled, how information moves, and how pricing responds to demand.
Maintenance and operations
Requests are tracked, assigned, and reported instead of handled from memory.
Guest and tenant experience
The experience stays consistent as the property and the number of bookings grow.
Revenue and occupancy decisions
Pricing and channel decisions are made from the data, not from habit.
Those three areas run on one process, not three separate fixes.
Next02How we workData should lead to a decision.
This is the process behind the revenue case, and the way we approach operational problems in general.
- 01
Market
Understand the environment the property operates in.
- 02
Performance
See what the property is actually achieving.
- 03
Booking channels
Understand how each distribution channel performs.
- 04
Booking behaviour
Understand how and when guests book.
- 05
Pricing
Decide the appropriate pricing response.
- 06
Monitoring
Measure whether the decision produced the intended result.
Market
Understand the environment the property operates in.
Performance
See what the property is actually achieving.
Booking channels
Understand how each distribution channel performs.
Booking behaviour
Understand how and when guests book.
Pricing
Decide the appropriate pricing response.
Monitoring
Measure whether the decision produced the intended result.
The tools provide the data. The work is turning that data into a decision.
The process is easier to see in a real property, with real numbers.
Next03Use casesRead the work.
Each case walks through the problem, the data, and the decision that followed.
When good occupancy is not enough
A property with active listings, regular bookings, and strong reviews was still not earning what it could. The question was not how to get more demand, but where the revenue was being lost.
- Property
- 2-bedroom serviced apartment
- Market
- Canggu, Bali
- Channels
- Airbnb and Booking.com
- Analysis period
- April to September 2026
- 01
The owner’s problem
The property was already listed on Airbnb and Booking.com, with regular bookings, good reviews, and strong occupancy. The owner asked why it was not earning more.
- 02
What the data revealed
Airbnb visibility was strong and the property held an average daily rate above the Booking.com market benchmark. Booking.com room-night volume stayed well below the benchmark.
70.2%
Airbnb occupancy
8,315
Airbnb page views
+31.4%
Occupancy vs similar listings
+43.6%
Booking.com ADR vs market
+9%
Canggu demand over the prior period
- 03
The diagnosis
Reading the funnel showed where the problem was not. Demand was positive, visibility was strong on Airbnb, channel performance was mixed, and pricing had room to respond. The answer was not simply to lower the price.
- Market
- Positive
- Visibility
- Strong on Airbnb
- Channel performance
- Mixed
- Pricing
- Opportunity
- 04
The key insight
A month with lower occupancy earned more than a month with higher occupancy. Maximizing occupancy is not the same as maximizing revenue.
Occupancy is not the same as revenue optimization.
April
96.7% occupancy
Rp33.7M net revenue
July
83.9% occupancy
Rp43.2M net revenue
July generated about Rp9.4M more net revenue than April, at lower occupancy.
- 05
From static pricing to revenue decisions
Pricing moved from a relatively static minimum-rate approach to one that responded to demand and timing. Weak and close-in dates were stimulated. Dates with stronger demand had rate protected.
Be aggressive when inventory is at risk of being lost, but protect price when demand gives us leverage.
- 06
The outcome
September dates were assessed by revenue risk instead of cutting rates across the whole calendar. New September bookings began to appear, including stays of 3, 2, 3, and 11 nights.
Rp1.5M to Rp2.1M
Published ADR for the early September bookings
- A stronger position measured against market demand, ADR, booking volume, booking pace, and revenue
- Pricing discipline, with different dates given different strategies
- Channel data used as a decision input, not only a monthly report
- Earlier warning on weak future dates through pickup monitoring
The source describes this as evidence of a positive response, not proof that pricing alone caused every booking.
The owner’s problem
- The owner’s problem
- What the data revealed
- The diagnosis
- The key insight
- From static pricing to revenue decisions
- The outcome
- 01
The owner’s problem
The property was already listed on Airbnb and Booking.com, with regular bookings, good reviews, and strong occupancy. The owner asked why it was not earning more.
- 02
What the data revealed
Airbnb visibility was strong and the property held an average daily rate above the Booking.com market benchmark. Booking.com room-night volume stayed well below the benchmark.
70.2%
Airbnb occupancy
8,315
Airbnb page views
+31.4%
Occupancy vs similar listings
+43.6%
Booking.com ADR vs market
+9%
Canggu demand over the prior period
- 03
The diagnosis
Reading the funnel showed where the problem was not. Demand was positive, visibility was strong on Airbnb, channel performance was mixed, and pricing had room to respond. The answer was not simply to lower the price.
- Market
- Positive
- Visibility
- Strong on Airbnb
- Channel performance
- Mixed
- Pricing
- Opportunity
- 04
The key insight
A month with lower occupancy earned more than a month with higher occupancy. Maximizing occupancy is not the same as maximizing revenue.
Occupancy is not the same as revenue optimization.
April
96.7% occupancy
Rp33.7M net revenue
July
83.9% occupancy
Rp43.2M net revenue
July generated about Rp9.4M more net revenue than April, at lower occupancy.
- 05
From static pricing to revenue decisions
Pricing moved from a relatively static minimum-rate approach to one that responded to demand and timing. Weak and close-in dates were stimulated. Dates with stronger demand had rate protected.
Be aggressive when inventory is at risk of being lost, but protect price when demand gives us leverage.
- 06
The outcome
September dates were assessed by revenue risk instead of cutting rates across the whole calendar. New September bookings began to appear, including stays of 3, 2, 3, and 11 nights.
Rp1.5M to Rp2.1M
Published ADR for the early September bookings
- A stronger position measured against market demand, ADR, booking volume, booking pace, and revenue
- Pricing discipline, with different dates given different strategies
- Channel data used as a decision input, not only a monthly report
- Earlier warning on weak future dates through pickup monitoring
The source describes this as evidence of a positive response, not proof that pricing alone caused every booking.
The owner’s problem
The property was already listed on Airbnb and Booking.com, with regular bookings, good reviews, and strong occupancy. The owner asked why it was not earning more.
What the data revealed
Airbnb visibility was strong and the property held an average daily rate above the Booking.com market benchmark. Booking.com room-night volume stayed well below the benchmark.
70.2%
Airbnb occupancy
8,315
Airbnb page views
+31.4%
Occupancy vs similar listings
+43.6%
Booking.com ADR vs market
+9%
Canggu demand over the prior period
The diagnosis
Reading the funnel showed where the problem was not. Demand was positive, visibility was strong on Airbnb, channel performance was mixed, and pricing had room to respond. The answer was not simply to lower the price.
- Market
- Positive
- Visibility
- Strong on Airbnb
- Channel performance
- Mixed
- Pricing
- Opportunity
The key insight
A month with lower occupancy earned more than a month with higher occupancy. Maximizing occupancy is not the same as maximizing revenue.
Occupancy is not the same as revenue optimization.
April
96.7% occupancy
Rp33.7M net revenue
July
83.9% occupancy
Rp43.2M net revenue
July generated about Rp9.4M more net revenue than April, at lower occupancy.
From static pricing to revenue decisions
Pricing moved from a relatively static minimum-rate approach to one that responded to demand and timing. Weak and close-in dates were stimulated. Dates with stronger demand had rate protected.
Be aggressive when inventory is at risk of being lost, but protect price when demand gives us leverage.
The outcome
September dates were assessed by revenue risk instead of cutting rates across the whole calendar. New September bookings began to appear, including stays of 3, 2, 3, and 11 nights.
Rp1.5M to Rp2.1M
Published ADR for the early September bookings
- A stronger position measured against market demand, ADR, booking volume, booking pace, and revenue
- Pricing discipline, with different dates given different strategies
- Channel data used as a decision input, not only a monthly report
- Earlier warning on weak future dates through pickup monitoring
The source describes this as evidence of a positive response, not proof that pricing alone caused every booking.
If this looks like your property, the next step is a conversation.
NextContactBring us the operational problem.
Tell us how the property runs today. We will look at where the work and the data are getting stuck.