Enterprise DNA

Instead of PriceLabs

Stop renting PriceLabs. Own your hotel rate plan.

We build your version around your room types, rate rules and review process, bring your exported PriceLabs rates across and run it for you. Your own occupancy and event records explain every proposal.

PriceLabs’ live hotel calculator shows US$1,048.50 a month for New Zealand with 150 rooms and Single Room Type selected. That is US$12,582 a year before tax, with the calculator’s volume discount included. Your setup and plan determine your actual bill.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

Separate the rate review from the services around it

PriceLabs combines rate calculations, market information and distribution. Your replacement starts with the decisions your hotel makes and the connections it needs.

paid

A charge tied to rooms

With New Zealand, 150 rooms and Single Room Type selected, the live calculator shows US$1,048.50 a month before tax. Bring your own invoice and room-type setup to compare.

trending_up

Rates informed by outside demand

The subscription includes daily rate recalculation using market signals. Our free version uses your own occupancy and event rules. External market information is a separate requirement to scope.

sync

Distribution to booking systems

The standard subscription includes a daily price sync. We scope and test your required booking-system connection as part of a custom version.

schedule

Extra syncs cost extra

The hotel pricing page lists an additional daily sync at US$1 per room per month.

extension

External access has an add-on

The hotel pricing page lists its customer data-access add-on at US$1 per room per month.

analytics

Reports around the same room nights

Pickup, room revenue and rate decisions can sit together in your own database, with the questions and review rules chosen by your hotel.

Your own rate desk

A weekly rate review with its evidence attached

Occupancy

Start with the room nights that need attention

The latest occupancy observation travels with each rate proposal, so stale inputs stay visible.

  • check Sold and blocked rooms checked against capacity
  • check Net booking pickup between observations
  • check Average daily rate from recorded room revenue
  • check Revenue per available room without mixing currencies

Rate rules

Explain the proposed price

Your base rate, occupancy adjustment and event adjustment produce a proposal inside your chosen bounds.

  • check Floor, base and ceiling for each room type
  • check Event dates with source notes
  • check Fixed compulsory nightly fees shown in the total
  • check Low-occupancy dates compared with minimum stays

Decisions

Know when an approval needs another look

Keep the approved price, reviewer and reason together. Changed evidence marks the decision stale.

  • check Missing or old occupancy blocks approval
  • check Tax and fee review recorded before approval
  • check Current approvals separated from stale ones
  • check Overdue follow-up work grouped by its owner

The meeting

Bring one pack to the revenue meeting

Prepare a rate approval working paper and a weekly meeting pack from the same records.

  • check Imported rates kept beside your proposals
  • check Booking movement, event notes and actions together
  • check Read-only reports in your hotel colours
  • check Local drafts for the operator to review

Make it yours

Design your own PriceLabs replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from PriceLabs. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your PriceLabs replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your PriceLabs data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Hotel Rate Planning for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Hotel Rate Planning for Claude Code

Connected to your own database

Which event nights also have high occupancy?

Harbour King

Stay date
2026-11-11
Occupancy pct
85.0
Event percent
15.00
Proposed
NZD 297.00
Total
NZD 307.00
Currency
NZD

Harbour King

Stay date
2026-11-12
Occupancy pct
85.0
Event percent
15.00
Proposed
NZD 297.00
Total
NZD 307.00
Currency
NZD

Ask it anything

Ten questions about your own rate decisions

Each question runs against the fictional hotel today. The answers combine your rules, observations and decisions, with no claim that every other system lacks the same analysis.

chat_bubble Which open nights in the next week have less than half their rooms sold?
chat_bubble Which room types have stale occupancy observations?
chat_bubble Which event nights also have high occupancy?
chat_bubble Which proposed nights hit our rate floor?
chat_bubble Which proposed nights hit our rate ceiling?
chat_bubble Which nights differ most from the current recorded price?
chat_bubble Which nights lost bookings since the previous observation?
chat_bubble Which nightly totals include compulsory fees?
chat_bubble Which low-occupancy nights require more than one night?
chat_bubble Who owns the overdue revenue actions?

Switching

How to switch from PriceLabs

The move involves exporting and checking your rate records, mapping them to your room types and rules, then reconciling the results before you stop using PriceLabs.

  1. 1

    Export your rate records

    Use PriceLabs' account or group rate CSV export. Include the records you want to bring across: listing identifiers, dates, recommended and current prices, minimum stays and availability. Check the exported columns and date formats before you start. If your account offers a different export format or limits what you can export, check with PriceLabs about what it allows.

  2. 2

    Map and load the records

    Set up your room types and currency, then match the listing identifiers and date formats in the export to your records. Run the import's test option first and review whether the records map as expected. Correct any mapping issues before loading the records for real. The import checks the file as a whole, so a problem can stop the full import rather than loading only part of it.

  3. 3

    Review what the import flags

    Check the import report for unknown listings, duplicate dates and invalid prices, then correct the source records and try again. Reconcile the imported prices and stays against your export. Availability in the rate export is not a trustworthy room count, so record occupancy separately from your hotel's booking records. Do not treat the rate import as a substitute for booking history.

  4. 4

    Compare both approaches

    Keep using PriceLabs while you review the new database alongside it for a short period. Compare the imported records and your rate decisions using your own occupancy and rules. Do not expect the new system to reproduce PriceLabs forecasts or market information. It supports internal rate review and does not send prices to booking channels, so keep your existing channel process in place.

  5. 5

    Switch off PriceLabs

    Once you have reconciled the imported records and checked that your room types, currency and rules are set up as intended, decide whether the new internal rate review is ready to use. Before stopping PriceLabs, confirm how prices will reach your booking channels, since this system does not send them. Keep the source export and your booking records available for reference.

construction

Where the real effort goes

The main work is usually mapping your own fields, room types and pricing rules, then deciding which history to bring across and reconciling it. Rate records are in the export, but bookings, guest records, market information and account settings are separate work. Occupancy needs your booking records. If Enterprise DNA builds and runs your version, they map and reconcile the required history for that build.

Not ready for a call?

Get your PriceLabs switch plan by email

We will send you the step-by-step plan for moving your business off PriceLabs, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Run the rate desk your way

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open it with Claude Code, Codex, OpenCode or Cursor and try /propose
  3. 3 Configure your property and room types, then test the PriceLabs CSV import
  4. 4 Record occupancy, review the rules and test the approved-plan workflow before cutover
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your room types, fee calculations and approval rules
  • check Your PriceLabs exports mapped and reconciled
  • check Your booking-system connection and market-data requirements scoped and tested
  • check A web screen or different technology stack when your team needs it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access and backups set up
  • check Your occupancy updates and rate reviews kept on schedule
  • check Reports and connections maintained as the hotel changes
  • check Run through Omni by Enterprise DNA beside the rest of your business
Book a 30-minute call

Questions

Instead of PriceLabs, answered

Does the free version do everything PriceLabs does? expand_more

It handles your internal rate review using your own occupancy and rules. It does not reproduce PriceLabs market information or forecasting, and it does not send prices to booking channels. Enterprise DNA scopes the market sources and booking-system connections your custom version needs, then tests them before a switch.

Can we bring our PriceLabs history with us? expand_more

The account or group rate export carries listing identifiers, dates, recommended and current prices, minimum stays and availability. Those records can be brought across after your room types and currency are checked. Bookings, guest records, market information and account settings are separate work. We map and reconcile the required history for your built version.

How do we know why a price changed? expand_more

Each proposal starts from your base rate and shows the effect of occupancy and event rules within your floor and ceiling. You record the reason for approval. If the evidence changes afterwards, the approval becomes stale and needs another review.

Will it handle taxes and compulsory fees? expand_more

The free version works with tax-inclusive room rates and fixed compulsory nightly fees. Approval waits for a recorded fee review. Whole-stay, per-person and conditional charges need calculations fitted to your terms. We build those checks into your version and verify the actual booking display before cutover.

What do we pay Enterprise DNA, and can we run it ourselves? expand_more

The free version is open source. Running it yourself still has hosting and coding-assistant costs. A version built and operated for you has one setup fee, then a retainer agreed around your scope. We review your actual PriceLabs invoice and required connections before recommending a move.

Bring your PriceLabs invoice and one rate review

Spend 30 minutes with Sam. Bring your bill, your room types and a week of rate decisions. We will work through what you use, which connections matter and what your own version needs. If keeping your current setup is the better choice, we will say so.

Book a 30-minute call Get the free version

Hotel Rate Planning for Claude Code is free and open source, published by Enterprise DNA.

Done paying for PriceLabs?

Get your version built