Propose rate moves from your own demand data alone, show the inputs behind each one, and hold every move for the revenue manager who releases it and owns the decision.
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and your rate
The controls sit inside one another. What none of them catches is set out below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modeNarrow the copilot to demand reporting when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt, governor and input-source configuration changes.Track
L4TraceabilityRecord the inputs, the proposal, the flags, the adjustments and the release time.Record
L3Manager releaseHold moves for the named manager; it governs release, not whether a released rate is right.Gate
L2Policy guardrailsTest proposals against configured provenance and governor rules; hiding a rival's rate from the screen is not keeping it out of the model.Restrict
L1Confidence thresholdsRoute low-confidence moves to a commercial read before the manager sees them.Require review
Model coreMove proposed — the rate change, its inputs, flagged lines and confidence
L1 – L2Test whether a move may stand
L3Puts the release in a manager's hands
L4 – L5Keep the move and the inputs behind it
L6Narrows to demand reporting when signals degrade
How Nestack evaluates it
Evaluate the pricing workflow — not only the number at the end.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the rate the market sees
Depth of coverage ▼
E1Final-output evaluationDid every input behind the move come from a permitted source?
E2Step-level evaluationDid the agent use the right dates, governors and segment configuration?
E3Tool evaluationDid it read and write the correct date and the correct rate plan?
E4Confidence calibrationDo low-confidence moves actually attract more manager adjustments?
E5Slice evaluationHow does performance change across specific date and segment groups?
E6Business outcomeHow many moves needed an adjustment or a correction after release?
Floor — the price the operator answers for
Failure modes
Where each failure originates in the agent
Seven ways a rate move goes wrong, by stage.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
CU-03
Input outside provenance
A rate input arrives from a source the boundary excludes.
Stage gathersYour own pace, inventory and public calendars
02 · Reasoning2 modes
CU-04
Coordination-shaped output
A move is framed as what the market ought to hold.
CU-06
Governor breach
A proposal exceeds the rise or fall the manager set.
Stage proposesThe move the manager reads and releases
03 · Tool / write2 modes
CU-02
Move published unreleased
A rate reaches a channel with no manager behind it.
CU-05
Personalised price unlabelled
A guest-specific price is shown without its disclosure.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
CU-01
Rival rate in the loop
A rival's non-public rate reaches a runtime input.
Stage returnsThe rate the manager releases and guests pay
05 · Change / Version1 mode
CU-07
Silent governor regression
A model or rule change widens what the agent will propose.
Stage tracksModel, prompt, governors and input-source config
Sev-1 · a rate moves without releaseSev-2 · a wrong move reaches a channelSev-3 · input degrades, move routes to review
An aggregate adjustment rate and the adjustment rate for one slice are different measurements The cohorts that carry it are named, not averaged away Nestack reports it by slice rather than in aggregate..
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Compression and event dates
8.0%
3.7×
Review
Group and contract blocks
4.5%
2.1×
Review
Personalised and member rates
3.2%
1.5×
Watch
Stable midweek dates
1.7%
0.8×
Normal
Bar: manager-adjustment-rate lift vs. stable-midweek baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends in the regression suite
The cycle ends when a case exists in the suite, not when the miss was discussed. That suite is what the next rate move released is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Manager-adjustment rate rises in a date slice.
02Diagnose
If the rise sits in one slice, the inputs behind those dates are read first, before any rule is touched.
03Improve
Changes carry a version and the moves that prompted them.
04Verify
Release is held until the affected cases pass.
05Learn
The case is kept permanently, and the pricing rules move with it.
Learn → DetectThe return edge. The next detection runs against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, pricing workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Pricing workflow discovery and boundary definition.
02Revenue and property source assessment.
03Governor, segment and input-provenance rule mapping.
04Demand-input ingestion and normalisation.
05Proposal logic and input binding.
06Confidence scoring and flag routing.
07Revenue-manager release workflow.
08Revenue-system and channel integration.
09Input-provenance cases.
10Guardrails and release controls.
11Rate-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne property, one marketProductionProduction revenue systemsAdvancedMultiple properties / brands
Introduced at Pilot
Proposals from your own data✓✓✓
Manager release✓✓✓
Move-quality baseline✓✓✓
Introduced at Production
Reporting by segment and date—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Revenue-system integration—✓✓
Introduced at Advanced
Multi-market pricing rules——✓
Multi-stage commercial approvals——✓
High date and segment volume——✓
Multi-property pricing controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your rate structures and segment definitions→Demand-input ingestion and source mappingWeek 1
02Representative dates you have already priced→Proposal baseline, segment extraction and input bindingWeek 2
03Your governors and the bands you price inside→Governor, segment and input-provenance rule mappingWeek 1
04Access to relevant APIs, feeds or exports→Revenue, property and channel assessment, then integration setupWeek 2
05Moves you would not want published→Provenance cases and failure-mode testingWeek 4
06What no model may take as an input→Confidence scoring, flag routing, guardrails and release controlsWeek 3
07Named revenue managers to release moves→Release workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The bands follow the actual work, which is why the fifth week doubles rather than pads.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Pricing workflow discovery, governor mapping and the automation boundaryW2Source integration and the proposal baselineW3Pricing workflow, confidence logic and release controlsW4Provenance cases, disclosure checks and failure-mode testingW5Revenue-system integration, pilot dates and targeted correctionsW6One pricing period run under revenue management, then handover
Reading the bandEvery bar covers the weeks its own work runs and no others. The fifth week genuinely doubles up.
At the end of W6The period closes validation and Agent Care owns the running agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Travel & Hospitality AI agent
Build a revenue-management copilot on your own data and a manager's signature.
Show us where each pricing input comes from and who releases a rate. Get that boundary wrong and the cost is not one bad night — a federal appeals court has held that keeping final authority with a person does not answer an agreement claim, and that a high acceptance rate supports the inference, so the adoption slide in your board pack becomes the exhibit. We map the inputs, set the governors and name the manager who decides.
