Does Strkr replace IDeaS, Duetto, or similar automated revenue systems?
No. IDeaS Revenue Solutions, Duetto, and similar automated pricing engines run transient-rate decisioning across continuous demand signals and remain the right tool for properties with the volume and complexity to justify the deployment. What Strkr replaces is the revenue manager workflow stack that wraps around the automated pricing engine and the PMS: Excel for the weekly pace review, email for the group approval ping-pong, separate STR dashboard for comp-set, and shared Google Sheet for the group-vs-transient mix analysis. Strkr integrates with Opera, Amadeus, Delphi.fdc, and STR via native connectors so pace flows into Strkr, approval context loads automatically, and the group-vs-transient mix analysis runs natively. For properties running IDeaS or Duetto, the automated pricing recommendations surface in Strkr for revenue-manager context. For properties without an automated engine, Strkr runs the manual decision support with full context pre-loaded.
How does group-vs-transient mix analysis work?
The group-vs-transient mix dashboard shows every future month with current group room nights (definite plus tentative), current transient room nights on the books, target mix percentage per property policy, implied blended ADR, and the directional guidance (accept more group, protect transient, promote transient, hold position). On every group inquiry, the system runs a displacement analysis against the transient pace forecast and surfaces the displacement cost on the approval queue so the revenue manager approves or counters with real context. For properties where group booking at 150 dollars ADR on Thursday to Sunday consistently displaces transient at 220 dollars ADR, the pattern surfaces across quarters so the revenue strategy adjusts. The target mix is tunable per property and per demand period so a convention property and a leisure resort both run the same math with motion-appropriate targets.
How does the group approval queue reduce the sales-manager ping-pong?
A sales manager rate quote request fires an approval routing flow with the full context pre-loaded on the queue: pace for the specific dates (definite plus tentative room nights, transient on the books, pickup forecast), comp-set rate from STR with the lag flagged, group history (repeat vs new, past stay ROI, past F and B attach), F and B package attach on the current inquiry, meeting-space-vs-sleeping-room contribution analysis, and the group displacement estimate against transient pace. The revenue manager has three one-click actions: approve at the proposed rate, counter with a specific rate and specific terms, or deny with reason. The approval cycle that used to take two days of email back-and-forth collapses to 20 minutes with full context. SLA tracking surfaces unapproved requests over 4 hours old. Audit trail preserves every decision so the quarterly strategy review runs with real pattern data.
How does length-of-stay optimization work for high-demand nights?
The LOS optimizer surfaces length-of-stay restriction opportunities and risks across demand periods. For every high-demand night (per the demand signal and the last-year pattern), the system calculates implied blocked demand (searches that would have booked at the shoulder but got turned away because of the restriction) vs captured demand (compression driven by the restriction extending booking length). The revenue manager sees that a two-night minimum on Super Bowl week blocks 20 shoulder-night transient at 180 dollars ADR while capturing 60 extra room nights at 320 dollars ADR, and refines the restriction (e.g., one-night Thursday minimum, two-night Friday minimum). The restriction logic flows to the booking engine on approval and the historical LOS restriction performance view trends the actual outcome vs the model prediction so the restriction math refines over time. For properties running IDeaS or Duetto, the LOS recommendations from the automated engine surface in Strkr alongside the manual optimizer for context.
How does Strkr handle the meeting-space-vs-sleeping-room trade-off?
Every group inquiry with meeting space (ballroom, meeting rooms, breakout space) runs the meeting-space-vs-sleeping-room contribution analysis: ballroom rental revenue, F and B spend, sleeping-room contribution (room nights times ADR), displacement of smaller groups that would have booked the ballroom with higher sleeping-room pickup, and implied blended ADR. The revenue manager sees the 400 attendee corporate conference producing 20,000 dollars in ballroom rental and 180 sleeping-room nights, vs three 100 attendee weddings that would have produced 15,000 dollars in ballroom rental and 300 sleeping-room nights with higher F and B spend. The quarterly meeting-space utilization trend view surfaces the pattern of ballroom-only bookings underperforming vs ballroom-plus-sleeping-room bookings so the sales strategy routes accordingly. For venues where ballroom and sleeping rooms sell independently, the trade-off view runs the ballroom opportunity cost in parallel with the sleeping-room opportunity cost.
How does STR comp-set data integrate with the quoting surface?
STR (Smith Travel Research) comp-set rate and occupancy data pulls into the quoting surface on the brand or independent-subscription cadence (typically every two days) with the lag flagged explicitly so the revenue manager sees the data vintage. The system projects the implied current comp-set rate forward from the STR snapshot based on day of week, demand period, historical comp-set pricing behavior, and current demand signal from the subject property. The revenue manager quotes transient rates and approves group pricing with the current implied comp-set rate on the surface instead of a two-day-old snapshot. Comp-set rate movement over 5 percent fires an alert to the revenue manager with the specific comp-set properties driving the movement so the pricing response happens in 10 minutes instead of the Monday review. The quarterly comp-set penetration trending preserves the ADR and RevPAR penetration by segment (corporate, leisure, group) so the revenue strategy adjusts to shifting market share.
