Virtuosos of Price

Pricing Roles, Clarified

Pricing decisions in a property management business rarely fail because nobody cares. They fail because too many people care, and none of them have agreed on who gets the final call. A rate gets changed by a VA, reviewed by an operations manager, queried by the owner, and then quietly reverted by someone who thought they were helping. By the time a booking comes in, nobody is sure which version of the calendar was live.

The problem compounds as a portfolio grows. With two or three listings, informal coordination is workable. With ten or more, informal coordination is a liability. Decisions that should take minutes stretch into days of back-and-forth, and the cost is not just time. It is the gap between what your pricing strategy says and what your calendars actually show.

Why pricing decisions collapse without a structure

Pricing is unusual among operational tasks because it sits at the intersection of several roles at once. An operations manager cares about occupancy. An owner cares about net return. A VA executing changes cares about not making an error. A channel manager or software tool cares about rules it has been given. When none of these parties has a defined relationship to the others on pricing specifically, every decision becomes a negotiation.

The symptoms are recognisable. You will see them as:

• Rate changes that get made and then undone within the same week, with no record of why
• Owners contacting you directly to ask why their property is priced a certain way, and your team not having a consistent answer
• Minimum stay rules that conflict with base rate logic because they were set by different people at different times
• Seasonal pricing that was set in January and never reviewed because it was unclear whose job the review was
• Discounts applied manually by someone responding to an inquiry, without any approval step

None of these are character failures. They are structural failures. The fix is not to hire better people or to tell the team to communicate more. The fix is to define, in writing, who does what on every pricing decision type before the decision needs to be made.

Introducing the RACI model

RACI is a decision-rights framework used across project management and operations. The name is an acronym for four roles that can be assigned to any task or decision:

Responsible is the person who does the work. For a pricing task, this is the person who makes the actual change in the software or platform.

Accountable is the person who owns the outcome. There is exactly one accountable person per decision. If the rate is wrong, this is the person who answers for it. Accountable and Responsible can be the same person, but in larger teams they often are not.

Consulted is anyone whose input is gathered before the decision is made. Consultation is two-way: the consulted party gives input, and that input is expected to influence the outcome. Being consulted is not the same as being informed after the fact.

Informed is anyone who needs to know the outcome but does not influence it. Owners who have agreed to a managed pricing strategy are often in this category. They receive a report; they do not approve each rate.

The power of RACI is not in the acronym. It is in the discipline of assigning exactly one Accountable role per decision type, and in separating Consulted from Informed so that people stop being pulled into decisions they were never meant to make.

Where RACI breaks down if you are not careful

RACI fails when every role gets assigned to multiple people without distinction. If three people are all listed as Accountable, nobody is accountable. It also fails when the Consulted list is used as a way to avoid making a decision: if you consult everyone, you can always say you are waiting on input. Build your RACI with the smallest number of people in each role that the decision actually requires.

Defining roles for portfolio pricing

Before you can fill in a RACI, you need to name the roles that exist in your business. These will vary, but a typical property management operation working with Airbnb and other short-term rental channels will have some version of the following:

Rate Strategist or Pricing Lead. This is the person who sets the logic: base rates, seasonal adjustments, minimum stay rules, and the parameters given to any dynamic pricing software. In smaller operations this might be the business owner. In larger ones it is a dedicated role or an outsourced function.

Operations Manager or Listing Manager. This is the person responsible for the day-to-day state of listings, including whether calendar settings match the agreed strategy. They may or may not have the authority to deviate from set rates.

Virtual Assistant or Coordinator. This is the person who executes changes in the platform. They work from instructions. They should not be making strategic decisions, but they often end up doing so by default when instructions are absent.

Property Owner. In a managed model, the owner is a stakeholder, not an operator. Their role in pricing decisions depends on the agreement you have with them. Some owners want to be consulted on seasonal strategy. Others want to be informed monthly. Defining this in advance prevents the owner from becoming an unplanned participant in every rate discussion.

Software or Channel Manager. This is not a person, but it holds a role in the RACI because it executes changes automatically. If your dynamic pricing tool adjusts rates daily, it is effectively Responsible for those adjustments. Your Pricing Lead is Accountable for the rules it has been given.

The RACI table for common pricing decisions

The table below shows how these roles map to the most common pricing decision types in a short-term rental portfolio. Adapt the role names to match your own team structure. The principle is that each row has exactly one A.

Read each row as a complete sentence. For minimum stay rule changes, the Rate Strategist owns the outcome, the Ops Manager makes the change, the VA is told what happened, and the owner is asked for input if the change affects their property materially. The software is not involved.

For manual overrides of a dynamic rate, the same person is Accountable, but the Ops Manager executes the change rather than the Rate Strategist doing it directly. This matters because it creates a record: the Ops Manager knows a manual override happened and can flag it in the next review.

Implementing the RACI framework in your operation

A RACI table on a document nobody reads is decoration. Implementation means embedding the framework into the tools and habits your team already uses.

Step 1: Audit your current decision flow

Before you assign roles, document how pricing decisions actually get made today, not how you intend them to be made. For one week, log every pricing-related action taken across your portfolio. Record who initiated it, who executed it, whether anyone was consulted, and whether the outcome was reviewed. You will almost certainly find decisions being made by people who did not know they were making them.

Step 2: Draft the RACI with your team, not for your team

Bring the people who will hold roles into the drafting session. A Rate Strategist who did not participate in defining their own accountability will find reasons to route around it. An Ops Manager who helped write the rules will enforce them. The session does not need to be long. It needs to produce a document everyone has agreed to.

Step 3: Tie each role to a tool or a record

Every Responsible action should leave a trace. If a VA changes a minimum stay rule, that change should be logged in a shared sheet with a date, a reason, and a reference to the instruction they received. If the Ops Manager applies a manual override, it should be noted in the same place. The log is not bureaucracy. It is the evidence you need when a rate question comes up in a monthly owner report.

Step 4: Define escalation paths

Not every pricing decision fits neatly into a pre-agreed category. A large group inquiry with unusual requirements, a competitor property that has dropped rates significantly in your market, a platform policy change that affects your minimum stay logic: these are situations where the normal RACI does not give a clear answer. Define in advance who gets called when a decision falls outside the table. Usually this is the Rate Strategist, but the trigger for escalation should be written down so the Ops Manager does not have to judge it in the moment.

Step 5: Communicate the framework to owners

Owners do not need to understand RACI as a concept. They need to understand what it means for them. A short paragraph in your management agreement or onboarding document is enough: "Pricing decisions are made by our Rate Strategist according to the strategy we agree with you at onboarding. You will receive a monthly report showing rate performance and any significant adjustments. If you want to be consulted on seasonal strategy changes, let us know and we will add you to that step." That is the owner's version of the RACI. It sets expectations and reduces the volume of mid-month rate queries.

Maintaining accountability over time

A RACI is not a one-time document. Roles change, team members leave, software tools get added or replaced, and owner agreements evolve. Without a maintenance habit, the framework drifts back toward informal coordination within a few months.

Schedule a quarterly RACI review. Put it in the calendar now. The review does not need to be long. Its purpose is to ask three questions: Has anything changed about who holds each role? Has the decision log revealed any patterns where the wrong person is making decisions? Are there new decision types that need to be added to the table?

Use the decision log as a diagnostic tool. If you are logging pricing actions consistently, the log will show you where the RACI is being followed and where it is not. A VA who is regularly making base rate changes without an instruction reference is a signal that the Responsible and Accountable roles have drifted. Address it at the process level, not by reprimanding the individual.

Revisit owner agreements when the portfolio grows. An owner who was happy to be Consulted on seasonal pricing when they had one property may become a bottleneck when you manage five of their listings. Renegotiate the agreement before the friction appears, not after.

Document role transitions explicitly. When a team member who holds an Accountable role leaves or changes position, the RACI must be updated before their last day. An undocumented transition is how accountability disappears entirely. The new Accountable person should be named, briefed on the existing decision log, and confirmed in writing.

What this means in practice

The RACI framework is most useful when it is tested against real scenarios before those scenarios happen. Work through these with your team and confirm that the framework gives a clear answer in each case.

Scenario: An owner calls to ask why their property's rate dropped last weekend. With a working RACI, the Ops Manager can pull the decision log, identify whether the change was a software adjustment within agreed parameters or a manual override, and give the owner a factual answer within the hour. Without a RACI, the same question triggers a chain of messages across the team and often ends with a vague answer that erodes owner confidence.

Scenario: A VA notices that a competitor property nearby has dropped its rates significantly and asks whether your listings should follow. With a working RACI, the VA knows their role is to flag the observation to the Ops Manager, who escalates to the Rate Strategist if it meets the escalation threshold. The VA does not make the change. Without a RACI, the VA either does nothing (because they are not sure if it is their call) or makes the change themselves (because nobody told them not to).

Scenario: A new dynamic pricing tool is being added to the stack. With a working RACI, the Rate Strategist is Accountable for configuring the tool's parameters, and the Ops Manager is Responsible for testing the output against the agreed strategy before it goes live. Without a RACI, the tool gets connected and left on default settings because it is unclear who owns the configuration.

Checklist: Signs your RACI is working

• Every pricing change in the last 30 days has a log entry with a named initiator and a reason
• No pricing change in the last 30 days was made by someone whose role is listed as Informed only
• Owner queries about rates were answered with reference to a specific decision, not a general explanation
• The last escalation was handled by the person named in the escalation path, not whoever happened to be available
• The RACI table has been reviewed in the last quarter and reflects the current team structure

Checklist: Signs your RACI needs attention

• You cannot say with certainty who made a specific rate change last week
• An owner was surprised by a rate they did not expect and you could not explain it quickly
• Two team members gave different answers to the same pricing question in the same week
• A manual override was applied and nobody noted it in the log
• The Accountable role for any decision type is currently held by nobody, or by more than one person

Where this becomes someone else's job

If the work of maintaining a pricing RACI, running daily rate reviews, and monitoring listing performance across a portfolio is more than your current team can absorb, that is a structural problem, not a motivation problem. Revande offers two products that take different amounts of the operational load off your plate.

Performance gives you a full software stack with dynamic pricing, daily rate adjustments made by experienced rate strategists, Airbnb listing performance monitoring with email alerts for low visibility or booking conversion issues, and monthly reports. Your team retains the relationship with owners and the operational oversight. The pricing execution and monitoring move to Revande.

Maestro includes everything in Performance and goes further. Done-for-you listing optimisation, proactive Airbnb listing performance monitoring with visibility and booking conversion issues handled for you, compatibility with Airbnb directly or your existing channel manager, and ongoing listing refinements as conditions change. For property managers whose portfolio has grown past the point where internal bandwidth can keep up, Maestro removes the need to hold the Accountable role for pricing and listing performance internally at all.

The RACI framework in this guide is still relevant if you use either product. What changes is which rows of the table are handled by Revande rather than by your team.

Related articles

• How dynamic pricing software fits into a managed portfolio operation
• Setting owner expectations on pricing: what to include in your management agreement
• Building a listing performance review process for property managers
• Minimum stay strategy across a mixed portfolio