Starting light — Tell us about your portfolio

• How many properties will be in scope for this engagement? Options: 1, 2–5, 6–20, 21–100, 100+
• Which property types best describe the portfolio in scope? Options: Full-service urban, Limited-service, Resort, Boutique/independent, Extended stay, Mixed portfolio, Other
• Which geographic markets or regions are highest priority for RevPAR improvement?
• How would you summarize your segment mix today (pick the single best descriptor)? Options: Transient-dominant (>60% transient), Balanced transient/group/contract, Group-dominant (>40% group), Contract/wholesale-heavy, Highly seasonal/event-driven, Other
• What is your current corporate RevPAR target and the gap versus today (state target and current or % uplift expected)?

If pricing stopped improving, what would you lose?

• If your pricing strategy stopped getting better today, how much revenue or RevPAR would you expect to lose over the next 12 months? Options: Negligible (<1% RevPAR), Moderate (1–3% RevPAR), Material (3–7% RevPAR), Severe (>7% RevPAR), Unsure / need to run numbers
• Which segments or channels do you believe are leaking the most value right now (select all that apply)? Options: Transient/direct, OTA channels, Group blocks, Contract/corporate, Wholesale, GDS
• Can you describe a recent example where pricing or channel mismatch led to a clear revenue miss? What happened and what was the impact?
• How long have you been seeing this level of underperformance or volatility? Options: Less than 3 months, 3–6 months, 6–12 months, Over 12 months, Variable by property
• When ownership or the executive team asks about RevPAR pressure, what specifically do they say they’re most worried about (tone and content)?

How do you actually set rates — behind the scenes

• What would it take for your revenue team to stop relying on spreadsheets for price decisions? Options: Clear proof of uplift from a POC, Seamless PMS/CRS integration, Executive mandate, Easy-to-use workflows and training, I don’t think we can stop using them
• Which systems and tools are you currently using for forecasting and pricing (select all that apply)? Options: Native PMS/CRS reports, Spreadsheets, Commercial RMS (3rd party), In-house forecasting tool, Manual channel manager, No formal tool
• How frequently are rates reviewed and updated across your portfolio? Options: Multiple times per day, Daily, Every few days, Weekly, Seasonally or ad hoc
• Who typically overrides recommended rates and why? Please include titles and the common reasons for overrides.
• Roughly how many hours per property per week does your revenue function spend on manual pricing and rate publication tasks? Options: <5 hours, 5–15 hours, 15–40 hours, >40 hours, Varies widely by property
• If we could automate one manual pricing task this quarter, which would move the needle the most?

Who’s in the room when a rate is decided?

• If there were a heated debate about price in front of ownership tomorrow, who would you expect to defend your recommendation — and who would unexpectedly show up?
• Which roles must sign off on strategic pricing changes (select all that apply)? Options: Revenue Manager / Director, VP of Revenue / Commercial Strategy, Regional GM, COO, CFO / Ownership rep, Sales/Group Director, Other
• What is the typical approval timeline for major rate or channel changes? Options: Same day, 1–3 days, 1–2 weeks, Several weeks, Longer / ad hoc
• Where do pricing disagreements most often occur — channel, segment, or property? Tell us a specific example if possible.
• How are pricing decisions currently documented and communicated to on-property teams? Options: Formal SOPs and tickets, Email threads, Shared spreadsheets, Verbal/tribal knowledge, A mix of the above

What does success actually look like (beyond RevPAR)?

• Is a headline RevPAR lift the only thing that will convince ownership — or are there other signals that matter more? Options: RevPAR lift is primary, ADR improvement matters more, Occupancy at target nights, Forecast accuracy & predictability, Margin/GOPPAR impact, A combination
• Which KPIs besides RevPAR will you use to judge success (select all that apply)? Options: ADR, Occupancy, RevPAR index vs compset, Forecast accuracy, Group pickup vs block, GOPPAR, OTA conversion/market share
• What minimum uplift and timeframe would feel like a clear POC win to you (please state numbers and period)?
• How do you prefer POC results to be presented so leadership trusts them (formats or audience)? Options: Property-level dashboards, Executive summary with topline metrics, Statistical analysis with confidence intervals, Playback workshop with ops and ownership, Raw data + model outputs
• Who has final acceptance authority for POC outcomes and commercial progression? Options: VP Revenue / Commercial, CFO / Owner rep, CEO / Group CEO, Regional Ops + Revenue jointly, Other

Data — the unlock or the bottleneck?

• If we asked for two years of clean booking, rate, and pickup history today, how quickly could you deliver it? Options: Within 1 week, 1–2 weeks, 3–4 weeks, 1–3 months, Longer / not currently available
• Which PMS/CRS and channel managers are in use across the portfolio (select all that apply)? Options: Oracle (OPERA), Cloudbeds, Amadeus/IDeaS, In-house PMS, SiteMinder, SynXis, Other
• Do you maintain a centralized data warehouse or are booking records siloed at property level? Options: Centralized data warehouse, Per-property silos, Hybrid (some centralization), No structured data repository
• Are there contractual, legal, or ownership constraints on sharing data with external partners? Options: No constraints, Requires NDA, Owner approval per property, Legal restrictions / privacy concerns, Unsure — need to check
• Which specific data fields can you provide for modeling (rates, pick-up, OTA source, cancellations, corporate codes, group block details)? Please list gaps.

Change & adoption — can you realize the value?

• What internal resistance is most likely to quietly kill a great pricing model before it can demonstrate impact? Options: Lack of on-property bandwidth, Distrust of algorithms, Conflicting commercial incentives, Slow executive approvals, Data/integration failures
• Think of a past tech rollout that struggled — what specifically derailed adoption and how long did recovery take?
• How do your on-property revenue managers feel about algorithmic or automated pricing today? Options: Enthusiastic and ready, Cautious but curious, Resistant / prefer manual control, Split opinions across properties
• Who would be the internal champion responsible for driving adoption and training during a POC and rollout (please provide name/title if known)?
• What training cadence and support model works best for your teams (select all that apply)? Options: Live workshops on-property, Remote training sessions, Recorded micro-modules, Hands-on shadowing during first weeks, Dedicated success manager
• What incentives or KPIs would help align revenue managers to follow automated recommendations?

Next steps — a small bet that proves a big signal

• Would you prefer to pilot one property that proves uplift, a representative cluster, or aim for an enterprise rollout from day one? Options: Single-property pilot, Cluster of representative properties, Enterprise-wide rollout, Unsure — want advice
• What is your preferred POC length to get reliable results and stakeholder confidence? Options: 30 days, 60 days, 90 days, 120+ days, Depends on seasonality
• Which modules must be included in the POC for you to consider it meaningful (select all that apply)? Options: Forecasting, Rate shopping / competitive intelligence, Channel publishing / auto-publish, Group pricing & displacement, Reporting & dashboards, Custom integrations
• What level of vendor support do you expect during the POC (select one)? Options: Full hands-on support with onsite training, Dedicated success manager + remote support, Light-touch technical onboarding, Only integration support, ops run it
• What is your ideal start date for a POC or discovery phase? Options: Immediately, Within 30 days, 1–3 months, 3–6 months, Unsure / need to align internally
• Who needs to be present at the kickoff session to ensure the POC moves forward (list roles and best contact info if available)?

• Solution Experience Kickoff — Alignment & Data Readiness
• POC Scenario Modeling Workshop — Forecast Accuracy & Baseline Proof
• Competitive Positioning & Rate Shop Benchmarking
• POC Benchmark Review, Acceptance & Operational Validation
• Operational Runbook & Change Management Session

• Confirm operational validation steps and assign on‑property owners for checks and escalation.
• Identify and agree remediation steps for any data quality issues before further modeling.
• Vendor to run extended backtests for agreed segments and deliver a forecast accuracy report with visualizations.
• Customer to provide missing segmentation rules, event lists, and any manual overrides to be modeled.
• Both parties to confirm final scenario list and measurement windows for the POC benchmark.
• One‑Sentence Recontextualization
• Demonstrate competitive benchmarking outputs that directly prove improved competitive positioning.
• Quantify expected ADR/RevPAR impact for prioritized scenarios.
• Agree on compset definitions, channel priorities, and publishing rules for the POC.
• Vendor to deliver a POC rate shop benchmark report showing historical comparisons and modeled uplift by scenario.
• Customer to confirm compset membership and any market intelligence corrections.
• Both parties to finalize cadence for rate shop ingestion during the POC.
• Recap: Current State, Consequence, Future State
• Customer formally accepts (or requests final adjustments to) the POC benchmark and success criteria.
• Agree the measurement plan and reporting cadence for the POC period.
• Introductions & Objectives
• Vendor to deliver the final POC benchmark package and a dashboard template for tracking during the pilot.
• Customer to provide sign-off on acceptance criteria or a prioritized list of required adjustments.
• Both parties to schedule the Pilot Kickoff meeting and assign operational owners for validation checkpoints.
• Future State One‑Liner for Operations
• Agree a documented operational runbook that maps outputs to on‑property actions and owners.
• Set the training schedule and confirm participant lists for enablement sessions.
• Establish validation scripts, escalation rules, and feedback cadence for the POC.
• Vendor to produce the operational runbook, training materials, and validation scripts tailored to the customer's workflows.
• Customer to assign on-property owners, create test credentials, and confirm training attendees.
• Both parties to schedule the training sessions and the first operational validation checkpoint.
• Customer and seller agree to a single-sentence current-state diagnosis.
• Quantify the business consequence of the current state in measurable terms.
• Define the future-state outcome and explicit POC success signals.
• Confirm availability and delivery dates of all required data for modeling.
• Customer to deliver sample PMS extracts, rate shop history, compset definitions, group pickup files, and events calendar by agreed date.
• Vendor to provide data schema checklist and data ingestion instructions within 48 hours.
• Schedule the POC Scenario Modeling Workshop and confirm participants.
• Recap: Current State, Consequence, Future State
• Establish a validated baseline forecast accuracy using customer data.
• Align on the scenarios and segments that will be used to measure POC uplift.
• Modeling Methodology Overview
• One‑Sentence Current State
• Workflow Mapping: From Signal to Published Rate
• Present POC Benchmark Package
• Compset & Channel Data Confirmation
• Validation Scripts & Sample Days
• Acceptance Criteria & Measurement Plan
• Consequence Quantification
• Data Quality & Preprocessing Review
• Rate Shop Benchmark Demo (Customer Data)
• One‑Sentence Future State & Success Signals
• Scenario Impact Analysis
• Run Baseline Backtest on Customer Data
• Operational Validation & Risk Mitigation
• Training & Enablement Plan
• Escalation, Communication & Feedback Loops
• Data Inventory & Access Plan
• Tie Outputs Back to Operational Problem
• Compare Baseline vs. Customer Current Forecasting
• Decision & Next Steps
• Agree Scenarios, Segments & Measurement Windows
• POC Scope, Timeline & Roles
• Agree Compset & Publishing Rules for POC
• Next Steps & Commitments

• PMS/CRS Bi-directional Integration
• Real-time OTA Rate Publishing
• Automated Daily Rate Recommendations Push
• Demand Forecasting Model Deployment
• Competitive Rate Shopping Feed Ingestion
• Price Optimization Engine Activation
• Channel-Specific Pricing Rule Engine
• Group Block Pricing Adjustments
• Contract and Wholesale Rate Uploads
• Automated Rate Parity Adjustments
• Rate Rules Automation (MinLOS/CTA/CTD)
• Portfolio Revenue Dashboard Deployment
• Rate Experiment A/B Execution
• Automated Stop-Sell and Blackout Enforcement

PMS/CRS Bi-directional Integration

• Which PMS/CRS systems are you using today (select all that apply)? Options: Oracle Opera, Sabre SynXis, Cloudbeds, StayNTouch, Agilysys, Amadeus, Other / Custom
• Do you require bi-directional writes (platform -> PMS/CRS) as well as reads? Options: Yes, No
• Which data objects must be synced bi-directionally (rates, availability, inventory, reservations, group blocks, restrictions)? Select all required. Options: Rates, Availability/Inventory, Reservations/Bookings, Group Blocks, Rate Rules (MinLOS/CTA/CTD), Promotions, Other
• What is your required sync frequency and latency for critical objects (e.g., rates/availability)? Options: Real-time (sub-minute), Near real-time (1-5 minutes), Hourly, Daily batch
• Are there any write-restrictions or approvals required at property level before external systems can change rates or inventory? Options: Yes - property must approve, Yes - corporate must approve, No - auto-publish allowed
• Please list any custom fields or non-standard mappings in your PMS/CRS that the integration must support (room type codes, rate codes, market segments, corporate IDs).

Real-time OTA Rate Publishing

• Which OTA channels should be in scope for real-time publishing? Options: Booking.com, Expedia / Hotels.com, Airbnb, Google Hotels, GDS (Amadeus/Sabre), Other OTAs
• Do you want full automatic publishing to OTAs or a recommendations -> manual-approve workflow? Options: Full automatic publish, Recommendations with manual approval, Hybrid (auto for selected segments)
• What is the acceptable publish latency threshold for OTA rate updates? Options: < 1 minute, < 5 minutes, < 30 minutes, Hourly
• Do you require per-OTA mapping for rate plans and room types (e.g., different rate codes per OTA)? Options: Yes, per-OTA mapping required, No, single mapping is fine
• Are there OTA-specific guardrails needed (e.g., no-promo on some OTAs, channel-specific minimums)? Options: Yes - list below, No
• Please describe any OTA contract clauses (e.g., rate parity, promotional restrictions) that affect publishing rules.

Automated Daily Rate Recommendations Push

• Do you want daily rate recommendations pushed to the PMS/CRS or only surfaced in the platform UI? Options: Push to PMS/CRS, Surface in UI only, Both
• What time of day should the daily recommendations be generated and pushed? Options: Pre-day (00:00-05:00 local), Early morning (05:00-09:00), Business hours (09:00-17:00), Custom window
• Should pushes be immediate or staged (e.g., preview -> approve -> publish)? Options: Immediate auto-push, Preview then approve, Staged by property/region
• What format/method do you prefer for recommendation delivery to downstream systems (API write, SFTP CSV, manual export)? Options: API (preferred), SFTP CSV, Email report, Other
• Who owns the daily decisioning and publishing (central revenue team, property revenue managers, third-party management)? Options: Central corporate revenue team, Property revenue managers, Third-party management company, Hybrid
• Define measurable acceptance criteria for the recommendations push (examples: publish success rate > 99%, latency < X minutes, no data mapping errors).

Demand Forecasting Model Deployment

• What forecasting horizons and granularities are required (pick all applicable)? Options: 0-7 days (short horizon), 8-30 days (mid), 31-365 days (long), Daily by arrival date, Hourly/Intraday
• Which forecast dimensions must be produced (occupancy, rooms sold, revenue, ADR, pickup, segmentation by transient/group/contract)? Options: Rooms sold, Occupancy (%), Revenue, ADR, Pickup by segment, Other
• Which external data sources should be included in the model (events, market calendars, weather, competitor pricing, flight schedules)? Options: Local events calendar, Weather, Competitor rates, Flight / transport data, Corporate pickup schedules, Other
• How frequently should models retrain and update (daily, weekly, on-demand)? Options: Daily, Weekly, Monthly, On-demand/manual retrain
• What are your target forecast accuracy thresholds (e.g., MAPE <= X) for primary metrics? Options: MAPE <= 5%, MAPE 5-10%, MAPE 10-15%, Custom target
• Are property-level custom segments or manual forecast overrides required for certain properties or segments? Options: Yes - overrides required, No - standardized models only

Competitive Rate Shopping Feed Ingestion

• Which competitive sources are required (OTA scraped, channel manager feeds, third-party rate intelligence providers)? Options: OTA scraping, Channel manager feeds, Rate intelligence vendor (STR-like), Direct competitor APIs, Other
• What competitor set should be monitored (direct competitors, comp set, market radius)? Options: Corporate comp set (list), Market radius (e.g., 5/10/20 miles), Top OTAs only, Custom list per property
• How frequently must shopping feeds be ingested and refreshed? Options: Real-time, Hourly, Daily, Weekly
• How should room-type and rate-plan mapping be handled when competitor nomenclature differs? Options: Automated mapping with manual review, Manual mapping for each property, Use broad category matching
• What tolerances or fallbacks do you want when competitor data is missing or inconsistent? Options: Use last-known value, Mark as unavailable and skip, Flag for manual review
• Please list any legal or contractual restrictions on competitor monitoring for select markets or channels.

Price Optimization Engine Activation

• What primary objective should the optimizer target? Options: Maximize RevPAR, Maximize ADR, Maximize Occupancy, Maximize GOPPAR, Custom objective
• Which segments should be included in optimization (transient, group, contract, wholesale)? Options: Transient, Group, Contract, Wholesale, All segments
• What hard constraints must the optimizer respect (minimum rate, comp-set positioning, owner-imposed rate floors, channel-specific rules)? Options: Min rate floor, No undercut competitors, Parity constraints, Owner/brand limits, Other
• What risk tolerance or exploration rate is acceptable for the engine to test new recommendations (conservative, moderate, aggressive)? Options: Conservative, Moderate, Aggressive
• Do you require explainability for each recommended price (rationale, drivers, expected impact)? Options: Yes - detailed explanations, Yes - summary explanations, No
• Define acceptance criteria for optimizer activation (examples: expected RevPAR uplift %, no negative booking days, SLA for recommendation delivery).

Channel-Specific Pricing Rule Engine

• Which channels require bespoke pricing rules (direct, OTAs, GDS, wholesale, metasearch)? Options: Direct, OTAs, GDS, Wholesale/Consortia, Metasearch
• What types of rules do you need supported (min/max rate, closed to arrival/departure, promotion stacking, customer-type restrictions)? Options: Min/Max rate, CTA/CTD/MinLOS, Promotion rules, Corporate/Contract restrictions, Other
• How should rule priority and conflict resolution be handled when multiple rules apply? Options: Precedence order by rule type, Most restrictive wins, Manual review on conflicts
• Do you require time-based scheduling for rules (seasonal, day-of-week, event-driven)? Options: Yes - seasonal/day-of-week, Yes - event-driven, No - static rules
• Should properties be able to create local overrides of global channel rules? Options: Yes - local overrides allowed, No - corporate-only rules
• Please provide examples of critical channel rules that must be encoded at go-live.

Group Block Pricing Adjustments

• How are group blocks currently managed (PMS group blocks, CRS, manual spreadsheets)? Options: PMS group module, CRS group tool, Spreadsheets/manual, Third-party block management
• Do you require displacement analysis to evaluate group pick-up vs transient revenue impact? Options: Yes - mandatory displacement analysis, Optional, No
• Should block pricing be dynamically adjusted based on forecasted pickup and displacement thresholds? Options: Yes - auto adjustments, Recommendations only, No
• What approval workflow is needed for group block price changes (sales approves, revenue team approves, auto-approve above threshold)? Options: Sales approves, Revenue team approves, Auto-approve under threshold, Custom workflow
• What data inputs are required for group evaluation (group pickup history, negotiated rates, cut-off dates, attrition policies)? Options: Group pickup history, Negotiated rates, Cut-off/attrition policies, Other
• Are there specific group types to treat differently (corporate vs social vs negotiated tour operator)? Options: Yes - list types, No - treat all same

Contract and Wholesale Rate Uploads

• What formats do contract/wholesale partners provide rates in (flat files, spreadsheets, API)? Options: Spreadsheet (CSV/XLSX), API, Channel Manager feed, Other
• Do contract rates include volume/length-based tiers and blackout/cut-off conditions? Options: Yes - tiers and conditions, Yes - tiers only, Yes - conditions only, No
• How often are contract rates updated or renegotiated (monthly, quarterly, annually)? Options: Monthly, Quarterly, Annually, Ad-hoc
• Do you require automated validation and auditing for uploaded contract rates (conflict detection, expiry alerts)? Options: Yes - automated validation, No - manual review
• Should contract/wholesale rates be included in optimization decisions or excluded? Options: Include in optimization, Exclude from optimization, Include with constraints
• Please describe any special billing or commission handling tied to contract rates that the system must support.

Automated Rate Parity Adjustments

• Which channels are in scope for rate parity monitoring and auto-adjustment? Options: All OTAs, Direct channel only, Selected OTAs, GDS
• Do you permit automated parity corrections or should discrepancies be flagged for manual review? Options: Auto-correct allowed, Flag for manual review only, Hybrid
• How frequently should parity checks occur? Options: Real-time, Hourly, Daily, Weekly
• What is the desired reconciliation workflow when parity conflicts are detected (notify channel manager, push corrected rates, escalate to revenue lead)? Options: Notify channel manager, Auto push corrected rates, Escalate to revenue lead, Custom workflow
• Are there contractual or brand-driven exceptions to parity enforcement (e.g., promotional channels, members-only rates)? Options: Yes - list exceptions, No
• Define acceptance metrics for parity automation (e.g., parity compliance > X%, reduction in parity incidents).

• Non-Disclosure Agreement (NDA)
• Master Services Agreement (MSA)
• Order Form / Commercial Terms
• Statement of Work (SOW)
• POC Success Metrics & Acceptance
• Data Processing & Privacy Agreement (DPA)
• Integration & Data Access Authorization
• Implementation Plan & Timeline
• On-Property Change Management Plan
• Training & Handover Agreement
• Service Level Agreement (SLA) & Support
• Escalation & Governance Matrix
• Change Order & Scope Management
• Payment Schedule & Invoicing
• Renewal, Termination & Exit Plan

• POC Outcomes Review
• RevPAR Impact Validation Deep Dive
• Lessons Learned & Operational Handover
• Backlog Prioritization & Enhancement Roadmap
• Executive Summary & Commercial Confirmation

• Publish the prioritized backlog with business-impact scores and owner assignments to the shared project workspace.
• Define a clear training and knowledge transfer plan tailored to property and corporate roles.
• Establish operational validation checkpoints with owners and measurable acceptance criteria.
• Agree escalation paths and owner responsibilities for day-to-day operations post-deployment.
• Create and distribute a Lessons Learned document with recommended corrective actions and owners.
• Build the training schedule and materials for property RMs and corporate stakeholders.
• Set up monitoring dashboards and assign owners for 30/60/90-day checkpoints.
• Publish an operational runbook and escalation matrix accessible to both customer and vendor teams.
• Review of backlog items from POC
• Establish a jointly prioritized backlog with clear business-impact scores tied to RevPAR or operational risk.
• Assign owners and SLAs so that each item has an accountable party and expected timeline.
• Agree which items will be executed as immediate quick wins and which will enter the product roadmap.
• Set a release and communication cadence so property teams know when to expect fixes or changes.
• Welcome and objectives
• Kick off sprint or patch cycle for agreed quick wins and confirm delivery dates.
• Schedule quarterly roadmap reviews and a monthly backlog triage meeting.
• Draft release notes template and communication plan for property stakeholders.
• One-sentence current state and consequence
• Communicate the business consequence and quantified RevPAR impact in an executive-friendly format.
• Secure commercial approval or a clear list of open commercial items and owners to close them.
• Obtain authorization to proceed with phased deployment or document required escalations for unresolved issues.
• Confirm budget and timeline commitments necessary for the first deployment phase.
• Produce a 1-2 page Executive Summary (with ROI and recommended decision) and distribute to all execs.
• Execute contract amendments or SOW for the agreed deployment phase, or list required approvals and owners.
• Schedule the phased deployment kickoff once approvals are complete and publish high-level timing.
• Document any executive conditions for moving forward and track them in the shared project dashboard.
• Ensure all stakeholders share a single, explicit statement of the current state and consequence that the POC addressed.
• Validate whether each pre-agreed success signal was met and capture precise acceptance status.
• Agree a clear, owner-assigned set of next steps and timeline based on the decision.
• Identify priority gaps that require technical or operational remediation before wider rollout.
• Prepare and distribute final POC results pack (incl. datasets, methodology, segment breakdowns) within 3 business days.
• Assign owners to each identified gap and schedule follow-up deep-dive sessions.
• Document the formal acceptance decision and any conditional criteria in the project record.
• Schedule Executive Summary meeting if POC is accepted or conditionally accepted.
• Pre-work and dataset confirmation
• Reproduce the POC metrics end-to-end so both customer and vendor trust the numbers.
• Quantify statistical confidence and identify assumptions that materially affect RevPAR estimates.
• Agree on final analytics artifacts and sign-off criteria for the POC measurement package.
• Identify any data corrections or additional analyses required before executive review.
• Deliver reproducible analytics package (raw data extracts, scripts, and visualizations) within agreed SLA.
• Remediate any data quality issues and rerun affected metrics, with a change log.
• Produce a short methodology note that ties each metric back to the business question it answers.
• Schedule a follow-up sign-off meeting with revenue leadership once artifacts are updated.
• Structured lessons learned (what worked / didn't)
• Capture a prioritized list of operational lessons with root causes and corrective actions.
• One-sentence current state
• Executive summary of results and RevPAR uplift
• One-sentence future state (operational outcome)
• Methodology walkthrough
• Prioritization criteria and business impact scoring
• Change management impacts and role shifts
• Commercial implications and proposed terms
• POC scope, data inputs, and acceptance criteria recap
• Re-run of key metrics live / share reproducible notebook
• Triage: quick wins vs roadmap work
• Assignment of owners, SLA and expected timelines
• Quantitative POC results (headline)
• Deployment timeline, commitments and required customer inputs
• Training and knowledge transfer plan
• Segment-level sensitivity and confidence