title: “Feature Research and ROI Exploration v2” category: Feature & ROI Analysis status: “active” created: 2026-02-25 updated: 2026-03-09 version: 2.0 related:
- “Product Model v3.0”
- “PRD v3.0”
- “Prioritized ROI Matrix”
- “Revenue Acceleration Addendum”
- “Competitive Parity Checklist”
- “Wego Intelligence Report” doc_id: “FLYMAX-03-Analysis-FEATURE-RESEARCH-EXPLORATION” project_name: “FlyMax V2.0” doc_type: “Analysis” scope: “valid” lifecycle_state: “active” author: name: “George Joseph” role: “Technical Lead / Solution Architect” modified_by:
- name: “George Joseph” role: “Technical Lead / Solution Architect” date: “2026-03-09” approved_by:
- name: “” role: “” date: “” next_review_date: “2026-03-09”
← Section Index · Master Index
Feature Research and ROI Exploration v2 — Direct-Booking Flight Platform Context
[!IMPORTANT] Document role: This is a supporting research and prioritization document, not the governing scope source.
Scope precedence: Where any older research, parity notes, or historical meta-search framing conflicts with the current product definition, Product Model v3.0 and PRD v3.0 take precedence.
Current governing model: The platform is a Verteil-powered, direct-booking, flight retail and servicing platform with on-platform checkout, payment orchestration, booking lifecycle continuity, support operations, reporting, and commercial governance.
Later-by-default only:
- Multiple Providers beyond the initial Verteil-led supply path
- AI capabilities
All other features discussed in current planning should be treated as current scope, current expectation, or gated current capability unless explicitly marked otherwise.
1. Why v2 exists
The earlier research version was valuable, but it was built under a meta-search / redirect-led interpretation of the platform. That made several useful observations about market leaders, search UX, trust signals, retention loops, and monetization patterns. However, it also encoded assumptions that are no longer valid for current planning, including:
- redirect as the governing business model
- referral / CPC / tracked handoff as the core revenue lens
- on-platform checkout as a selective future enhancement
- unit economics centered on search-to-redirect efficiency rather than transaction completion and post-booking continuity
- supplier comparison logic without sufficient weight on payment, servicing, support, finance traceability, and booking state integrity
Version 2 reinterprets the useful research through the correct product lens:
Search → Compare → Reprice / Validate → Traveler Capture → Payment / Credit Reservation → Book → Confirm / Ticket → Manage Booking → Service / Support → Reconcile
That means this document is now optimized for:
- feature prioritization for a direct-booking platform
- transaction-based ROI thinking
- operational and support-aware roadmap sequencing
- commercial governance decisions
- parity analysis that distinguishes table-stakes flight UX from model-defining commerce / servicing capabilities
2. Executive summary
The highest-ROI reality for the current product is not redirect efficiency. It is the compound effect of reducing friction and failure across the owned transaction funnel.
The core economic and strategic drivers are now:
- Search-to-booking conversion
- Reprice / validation accuracy before payment
- Payment success and failure recovery
- Booking / ticket issuance success
- Support and servicing containment
- Commercial yield per booking
- Credit, reconciliation, and exception control
- Retention through booking continuity, alerts, and account-level trust
This changes feature prioritization materially.
2.1 The biggest ROI unlocks now
The largest near-term ROI multipliers are no longer “more redirects” or “higher CPC yield.” They are:
- better results quality and fare transparency that improve search confidence
- reliable reprice / validation before checkout commitment
- robust payment and booking orchestration with low ambiguity
- fast booking confirmation and visible post-booking state
- support workflows tied directly to booking, payment, and servicing events
- strong admin and agent governance for credit, markups, discounts, promotions, and fare access
2.2 What still remains highly valuable from historical meta-search research
The older competitor research is still useful for:
- search and comparison UX parity
- trust-building patterns such as price clarity and quality signaling
- calendar, flexible-date, and discovery UX
- watchlists, alerts, and retention loops
- quality scoring, emissions visibility, and merchandising transparency
- growth concepts such as content, route pages, and commercial surfaces
These remain valid reference patterns, but they are no longer the product’s governing identity.
2.3 Recommended sequencing
journey
title Recommended v2 Sequencing
section Stabilize Owned Transaction Core
Search quality + transparency: 5
Reprice + payment + booking integrity: 5
Booking management + support linkage: 5
Credit / reconciliation / audit controls: 5
section Accelerate Revenue and Retention
Promotions + markup governance: 4
Fare calendar + alerts + saved search: 4
Ancillary / charter / corporate controls: 3
section Build Defensibility
Quality scoring + suppression logic: 4
Price history + demand intelligence: 3
AI and multiple providers later: 2
The strategic rule is:
Integrity before acceleration; acceleration before intelligence.
A direct-booking platform should not scale promotions, sponsored placements, advanced ranking, or intelligence layers on top of an unstable booking and servicing core.
3. Governing assumptions for this version
3.1 Product-model assumptions
This document assumes the following as current truth:
- the platform is flight-first
- the platform is Verteil-first for baseline supply
- the booking flow is on-platform, not redirect-led
- payment collection and/or credit reservation is part of the platform journey
- booking retrieval, booking history, and post-booking servicing matter from day one
- support ticketing is a real product responsibility, not an operational afterthought
- Admin, Agent, and User portals are core operating surfaces
- promotions, discounts, markups, and corporate/private fare controls are part of the current commercial model
- charter/custom inventory belongs in the product model, even if rollout is commercially or operationally gated
- SSO and security controls belong in the current model, with activation timing governed separately
- only Multiple Providers and AI capabilities are later-by-default
3.2 What is current scope vs gated current scope vs later-by-default
| Classification | Meaning in this document | Examples |
|---|---|---|
| Current scope | Must be present in product definition and design | Search UX, checkout, payment orchestration, booking creation, booking retrieval, support ticketing, agent credit, reporting, auditability |
| Gated current scope | In product scope now, but may launch partially enabled due to supplier, ops, finance, or commercial constraints | Corporate/private fares, charter inventory, some servicing actions, some payment methods, some notification channels |
| Later-by-default | Not assumed for MVP/current baseline unless explicitly pulled forward | Multiple Providers beyond Verteil, AI capabilities |
3.2A Scope-completeness note for this research document
This document is intentionally a feature-research and ROI-prioritization artifact, not a line-by-line restatement of the PRD. To avoid accidental omission or later reinterpretation, the following current-scope operating surfaces are also considered in-scope and aligned, even where they are not deeply ROI-scored in later sections:
| Surface | Alignment treatment in this document |
|---|---|
| Admin / Agent / User portals | Assumed as core operating surfaces for workflow ownership, permissions, reporting, and action visibility |
| SSO, MFA/2FA, RBAC, security controls | Treated as current-scope governance and trust foundations, not future hardening extras |
| Notifications and preference management | Treated as part of booking continuity, support reduction, and post-booking trust |
| Profile / traveler / organization management | Treated as enabling infrastructure for repeat booking, agent operations, and role-aware workflows |
| Reports, exports, audit, reconciliation, and operational dashboards | Treated as essential operating and finance surfaces, not back-office nice-to-haves |
| CDC / webhooks / downstream events | Treated as implementation-critical support for state propagation, integrations, and operability |
| Provider / airline / service configuration and health management | Treated as current-scope governance required for Verteil-first operations and controlled rollout |
| Currency, locale, and localization preferences | Treated as part of parity-grade flight UX and market readiness, not optional polish |
| Caching, performance controls, logging, analytics, bug reporting | Treated as baseline reliability and observability requirements that protect conversion and supportability |
| SEO, route pages, content, and external knowledge-base surfaces | Treated as current-scope growth/support surfaces, though not the primary transaction-core ROI focus of this document |
This means the later sections focus primarily on priority, economic leverage, sequencing, and operating risk, while the governing PRD still remains the source of truth for exhaustive scope enumeration and acceptance requirements.
3.3 Deprecated framing from the old research lens
The following should not be used as primary framing in current decision-making:
- “flight meta-search” as the primary product identity
- “search → compare → redirect” as the governing journey
- “no direct booking / no payments” assumptions
- redirect CTR as the main north-star KPI
- partner postback / pixel reporting as the primary commercial truth layer
- “book on platform” treated as a niche later enhancement
Those concepts may still appear as comparative references in competitor analysis, but they do not govern v3-aligned prioritization.
4. How competitor research should be used under the v3 model
The competitors remain useful, but each should be interpreted differently under a direct-booking lens.
4.1 Competitor learning map
| External pattern source | What it is useful for | What not to inherit blindly |
|---|---|---|
| Skyscanner | Search UX maturity, results ranking cues, price-accuracy discipline, provider quality scoring, trust indicators, exploratory pricing concepts | Redirect-led unit economics, provider handoff as primary conversion endpoint |
| Wego | Flexible date UX, fare calendar patterns, localized checkout inspiration, performance marketing surfaces, partner/commercial mechanics | Treating ads or outcome-based bidding as the core business model before booking integrity is mature |
| Google Flights | Explore discovery, alerts, retained interest loops, flexible-date research behavior, clean search UX expectations | Minimal post-booking ownership assumptions |
| Kayak | Forecasting-style guidance, confidence framing, query-scale intelligence patterns | Over-prioritizing prediction before first-party transaction reliability exists |
| NDC / airline-retailing patterns | Fare validation, order servicing, ancillary logic, booking lifecycle realities, airline constraints | Assuming full servicing depth is uniformly available without supplier validation |
| OTA / retail-commerce patterns | Checkout containment, payment trust, booking confirmation, self-service flows, support expectations | Assuming all OTA monetization surfaces fit a trust-first flight platform without governance |
4.2 Reinterpreted lessons that matter most now
- Search UX parity still matters. Users will compare your experience against meta-search leaders even if your business model is different.
- Price trust matters more when the booking is owned. Once payment happens on-platform, price mismatch and unclear fees become operational and reputational liabilities.
- Booking continuity is a strategic asset. Direct ownership of post-payment state creates retention, trust, and support advantages that redirect players lack.
- Supportability is a feature. Anything that creates booking ambiguity increases support cost and damages conversion confidence.
- Commerce controls are differentiators in B2B/B2B2C. Markups, discounts, credit, fare access, and reporting are not “ops sidecars”; they are part of the product value.
- Intelligence should follow data quality. Prediction, advanced ranking, and AI are only worthwhile when search, price, payment, order, and servicing signals are trustworthy.
5. Direct-booking parity and gap interpretation
This section replaces the old “flight meta-search gap analysis” with a v3-aligned interpretation.
5.1 Table-stakes that remain mandatory
These remain table-stakes because users and agents expect them regardless of business model:
- one-way / round-trip / multi-city search where supported
- airport and city autocomplete
- filters and sorting
- baggage and fare-rule visibility
- total-price clarity
- itinerary comparison usability
- flexible dates / fare calendar where feasible
- saved searches and alerts where strategically justified
- mobile-friendly results and checkout experience
5.2 Capabilities that are now model-defining, not optional add-ons
These are no longer “advanced differentiators.” They are part of the product identity:
- on-platform checkout
- payment authorization / capture behavior
- failure and retry handling for payment and booking
- booking record creation and retrieval
- booking confirmation and ticket visibility
- booking management and servicing entry points
- support ticketing linked to orders and payment state
- audit logs and finance traceability
- agent credit lifecycle management
- markup / promotion / discount governance
5.3 Capability interpretation table
| Capability | Why it matters now | Classification | Notes |
|---|---|---|---|
| Search, filters, sort, fare details | Baseline usability and parity | Current scope | Mandatory for trust and conversion |
| Reprice / validate before pay | Prevents downstream booking ambiguity | Current scope | Core integrity feature |
| On-platform checkout | Governing product behavior | Current scope | Not a later experiment |
| Payment orchestration | Converts intent to owned transaction | Current scope | Includes failure handling and reconciliation impact |
| Booking confirmation / retrieval | Core continuity layer | Current scope | Needed for both user and support flows |
| Change / cancel / refund visibility | Reduces operational fragmentation | Gated current scope | Supplier and policy depth may vary |
| Support ticketing | Operational ownership and trust | Current scope | Must be booking-linked |
| Markup / discount / promotion controls | Revenue and governance | Current scope | Critical for B2B/B2B2C and campaigns |
| Agent credit workflows | Commercial operations | Current scope | Needs reservation, release, exception handling |
| Corporate / private fares | Important commercial feature | Gated current scope | Controlled by approvals and supplier support |
| Charter / custom inventory | Strategic product fit requirement | Gated current scope | May launch dark or controlled |
| Price alerts / watchlists | Retention and intent capture | Current scope, later in sequence | Valuable after core stabilization |
| Sponsored placements / ads controls | Revenue acceleration | Current scope, gated rollout | Trust-governed; do not distort unstable core experience |
| Multiple Providers | Coverage expansion | Later-by-default | Not baseline MVP dependency |
| AI capabilities | Intelligence / assistance layer | Later-by-default | Not required for baseline product behavior |
6. High-ROI feature expansion portfolio (v3-aligned)
6.1 Category A — Core transaction conversion and trust
These features are the highest-priority ROI drivers because they increase completed bookings while reducing support and reconciliation drag.
| Feature | Primary value | ROI effect | Priority |
|---|---|---|---|
| Results quality + transparent totals | Improves user trust at search stage | Raises checkout starts; lowers bounce and price skepticism | Very High |
| Fare breakdown, baggage, rules visibility | Improves decision confidence | Lowers abandonment and dispute risk | Very High |
| Reprice / validate before checkout confirmation | Controls price drift | Lowers payment/book failure and trust erosion | Very High |
| Payment orchestration with clear failure handling | Converts intent reliably | Increases paid orders; lowers manual recovery load | Very High |
| Booking confirmation + ticket status visibility | Removes post-payment uncertainty | Reduces tickets and support contacts | Very High |
| Booking retrieval and history | Supports repeat use and support continuity | Improves retention and serviceability | Very High |
| Booking-linked support tickets | Containment and SLA visibility | Reduces operational chaos; supports scale | Very High |
| Self-service servicing entry points | Reduces manual support volume | Improves post-booking experience | High |
| Notification reliability (email first, others gated) | Keeps state visible | Reduces “where is my booking?” load | High |
6.2 Category B — Commercial governance and revenue acceleration
These features increase booking yield and channel control, especially for B2B/B2B2C operations.
| Feature | Primary value | ROI effect | Priority |
|---|---|---|---|
| Agent markup controls | Protects margin by channel / segment | Direct revenue leverage | Very High |
| Promotion / coupon / discount engine | Controlled demand stimulation | Improves conversion when governed correctly | High |
| Agent credit reservation / release / exception controls | Enables travel-seller operations | Supports B2B liquidity and booking throughput | Very High |
| Corporate / private fare access controls | Commercial differentiation | Can materially improve conversion for target segments | High |
| Charter / custom inventory workflows | Strategic fit for specialized sales | Revenue upside on controlled volumes | Medium–High |
| Ancillary attach opportunities | Higher revenue per order | Boosts margin after trust baseline is stable | High |
| Sponsored placements / merchandising controls | Monetization surface | Useful only with governance and transparency | Medium |
6.3 Category C — Retention and re-engagement
These features matter once the transaction core is dependable.
| Feature | Primary value | ROI effect | Priority |
|---|---|---|---|
| Saved searches and search history | Easier return journey | Increases repeat engagement | Medium–High |
| Price alerts / watchlists | Captures delayed intent | Improves reactivation and assisted conversion | Medium–High |
| Fare calendar / flexible-date discovery | Helps users find bookable options faster | Improves search efficiency and conversion for flexible users | High |
| Explore / destination discovery surfaces | Demand generation | Useful for top-of-funnel growth, lower than transaction-core priority | Medium |
| Booking history with actionable status | Retention and trust | Improves repeat booking behavior | High |
6.4 Category D — Operations, finance, and reliability
These are often underestimated in feature research, but they are major ROI drivers for a direct-booking platform.
| Feature | Primary value | ROI effect | Priority |
|---|---|---|---|
| Booking-payment state mapping | Eliminates ambiguity | Reduces manual reconciliation and support cost | Very High |
| Finance-grade reporting and exports | Controls cash, revenue, exceptions | Improves operational visibility and audit readiness | Very High |
| Supplier health / error dashboards | Faster incident response | Lowers downtime and booking failure impact | High |
| Audit logs for booking, payment, promotion, and credit actions | Trust, governance, compliance | Reduces risk and investigation time | Very High |
| Exception queues for payment / booking mismatch | Operational containment | Prevents silent failures and revenue leakage | Very High |
6.5 Category E — Defensibility and intelligence
These features should be built on top of trusted first-party data rather than pursued prematurely.
| Feature | Primary value | ROI effect | Priority |
|---|---|---|---|
| Provider / offer quality scoring | Improves ranking and suppression decisions | Better conversion and fewer complaints | High |
| Price history warehouse | Enables analytics and later prediction | Strategic data asset | Medium |
| Demand / route intelligence for business decisions | Better merchandising and inventory strategy | Medium-term optimization gains | Medium |
| Forecast-style guidance | Helps undecided users act | Useful later, after strong data foundation | Medium |
| AI-assisted ranking / recommendations / support | Advanced leverage layer | Later-by-default, not baseline | Later |
7. ROI model redesign — from redirect economics to transaction economics
7.1 What changed in the measurement model
The old lens optimized the economics of a click-out marketplace. The new lens must optimize the economics of an owned booking journey.
7.2 Primary KPI stack for this document
| KPI | Why it matters |
|---|---|
| Search-to-booking conversion | Core indicator of product effectiveness |
| Checkout start rate | Measures confidence between results and commitment |
| Reprice / mismatch rate | Indicates offer quality and pre-booking integrity |
| Payment success rate | Measures monetary conversion efficiency |
| Booking / ticket issuance success rate | Confirms whether revenue became a usable booking |
| Support contacts per order | Directly affects operating cost and trust |
| Refund / change handling visibility | Impacts post-booking reputation and support load |
| Net yield per booking | Measures economics after discounts, fees, commissions, and payment costs |
| Credit exception rate | Important for B2B risk control |
| Reconciliation accuracy | Protects finance correctness and operational trust |
7.3 Transaction unit-economics formula
A more appropriate framing is:
Net Contribution
= (Search Volume × Search-to-Booking Conversion × Net Yield per Booking)
+ Ancillary Contribution
- Provider / API Search Cost
- Payment Processing Cost
- Support & Servicing Cost
- Promotion / Discount Cost
- Credit Loss / Exception Cost
- Manual Ops / Reconciliation Cost
7.4 Supporting conversion chain
Bookings
= Searches
× Search-to-Checkout-Start Rate
× Payment Success Rate
× Booking / Ticket Issuance Success Rate
This model makes the main optimization target explicit:
It is often more profitable to reduce payment / booking failure and support leakage than to chase more top-of-funnel traffic.
7.5 Practical interpretation of ROI under this model
| Improvement lever | Direct impact | Secondary effect |
|---|---|---|
| Better total-price transparency | More checkout starts | Fewer disputes and lower support cost |
| Strong repricing before pay | Fewer failed / mismatched orders | Higher trust and lower refund pressure |
| Better payment retry / fallback behavior | More completed orders | Lower manual recovery effort |
| Clear booking status and notifications | Fewer support tickets | Higher repeat trust |
| Better credit governance | More stable agent operations | Lower commercial risk |
| Better offer quality / suppression logic | Higher conversion quality | Lower complaint and servicing noise |
7.6 Illustrative scenario bands (non-binding placeholders)
These are not finance-approved projections; they are modeling bands to support prioritization.
| Scenario | Characteristics | Strategic implication |
|---|---|---|
| Conservative | Acceptable search UX, but higher reprice friction, weaker payment recovery, more support dependency | Focus on integrity fixes before scaling growth spend |
| Base | Stable checkout, good booking continuity, manageable support cost, governed discounts and credit | Ready for retention loops and selective acceleration |
| Upside | Strong trust, low mismatch, strong payment success, quality-based ranking, effective retention | Can justify ancillary expansion, deeper merchandising, and intelligence investments |
8. Reinterpreted gap analysis against market leaders
The purpose of this table is not to copy competitors feature-for-feature. It is to understand what users will expect and what the current model must own directly.
| Capability / pattern | Market relevance | v2 interpretation for our platform |
|---|---|---|
| Progressive result loading and search responsiveness | High | Useful for perceived speed, but must not hide booking-state unreliability |
| Fare calendar / flexible date discovery | High | Strong growth and conversion support feature; should follow stable core checkout |
| Explore / inspirational discovery | Medium | Helpful for top-of-funnel expansion; lower priority than booking integrity |
| Provider / offer quality scoring | High | Valuable for ranking, suppression, and trust in a direct-booking environment |
| Price alerts / watchlists | Medium–High | Important retention loop after booking continuity is established |
| On-platform booking containment | Critical | Already core identity; not a later experiment |
| Localized payment methods | High | Important, but may be regionally gated |
| In-app / in-platform booking management | Critical | Current expectation because the platform owns the transaction |
| Sponsored merchandising | Medium | Can be useful later, but only with strict labeling and governance |
| Forecast / guidance layer | Medium | Valuable, but should not outrank operational fundamentals |
| Search / demand intelligence products | Medium | Strategic later-stage asset once first-party data is trustworthy |
9. Priority matrix for roadmap decisions
9.1 P0 — Must stabilize first
| Priority bucket | Items |
|---|---|
| P0A Transaction integrity | Reprice / validation, payment orchestration, booking creation, confirmation, ticket visibility, booking retrieval |
| P0B Trust and transparency | Total-price clarity, fare details, baggage visibility, rules, booking-state visibility |
| P0C Operational containment | Support ticketing, booking-payment linkage, audit logs, exception handling, reconciliation views |
| P0D Commercial control | Markups, discounts, agent credit foundations, permissions, SSO / 2FA |
9.2 P1 — Current-scope acceleration after core stabilization
| Priority bucket | Items |
|---|---|
| P1A Conversion lift | Fare calendar, flexible-date flows, improved ranking, quality-based suppression |
| P1B Retention | Saved searches, alerts, search history, booking history enhancements |
| P1C Commercial growth | Corporate/private fare controls, ancillary attach, governed promotions, charter workflows |
| P1D Ops depth | Deeper servicing flows, agent operational tooling, richer finance exports and dashboards |
9.3 P2 — Strategic leverage once first-party signals are reliable
| Priority bucket | Items |
|---|---|
| P2A Intelligence | Price history, demand analytics, forecast-style guidance |
| P2B Monetization extensions | Sponsored placements with clear governance, richer merchandising surfaces |
| P2C Platform extension | Multiple Providers beyond Verteil, only when justified |
| P2D Advanced intelligence | AI capabilities, only after data quality and workflows are mature |
10. RICE-style prioritization (qualitative v2 view)
The table below intentionally avoids fake numeric precision. It is meant to support decision-making before detailed analytics and finance modeling are available.
| Feature area | Reach | Impact | Confidence | Effort | Suggested priority |
|---|---|---|---|---|---|
| Payment + booking orchestration integrity | High | Very High | High | High | 1 |
| Booking retrieval / management / confirmation | High | Very High | High | Medium–High | 2 |
| Support ticketing linked to orders | High | Very High | High | Medium | 3 |
| Reprice / validation before payment | High | Very High | High | Medium | 4 |
| Total-price transparency + fare clarity | High | High | High | Medium | 5 |
| Agent credit controls | Medium–High | High | High | Medium–High | 6 |
| Audit, reconciliation, and exception workflows | Medium–High | High | High | Medium–High | 7 |
| Markup / promotion / discount governance | Medium–High | High | Medium–High | Medium | 8 |
| Fare calendar / flexible-date UX | High | Medium–High | High | Medium | 9 |
| Corporate/private fare controls | Medium | High | Medium | Medium–High | 10 |
| Price alerts / saved searches | Medium | Medium–High | High | Medium | 11 |
| Charter/custom inventory model | Low–Medium | Medium–High | Medium | High | 12 |
| Offer quality scoring | Medium | Medium–High | Medium | Medium | 13 |
| Ancillary attach flows | Medium | Medium | Medium | Medium | 14 |
| Sponsored placements / ads controls | Medium | Medium | Medium | Medium | 15 |
| Multiple Providers | Medium | Strategic High | Low–Medium | Very High | Later |
| AI capabilities | Unknown | Strategic Medium–High | Low | High | Later |
11. Twelve-month sequencing model
11.1 Stage 1 — Stabilize the owned transaction core
Primary goal:
- make search-to-booking reliable
- make booking state legible
- make support and finance operations controllable
Key deliverables:
- results transparency and search parity baseline
- reprice / validation checkpoints
- payment failure handling
- booking confirmation and retrieval
- booking-linked support ticketing
- audit / reconciliation / exception visibility
- core markup / discount / credit controls
11.2 Stage 2 — Accelerate current-scope growth levers
Primary goal:
- raise conversion quality and repeat engagement
- improve commercial control by segment
Key deliverables:
- fare calendar and flexible-date UX
- saved search and alerts
- corporate/private fare gating
- ancillary / promotion enhancement
- deeper agent tools
- charter / custom inventory controls where approved
11.3 Stage 3 — Build defensibility and later extensions
Primary goal:
- convert first-party search / order / support data into strategic leverage
Key deliverables:
- offer quality scoring
- price history and demand analytics
- forecast-style guidance if data is ready
- multiple-provider decision assessment
- AI capability exploration only after core data quality is proven
gantt
title v2 Roadmap for a Direct-Booking Flight Platform
dateFormat YYYY-MM-DD
axisFormat %b %Y
section Stage 1 — Core integrity
Search transparency + fare clarity :a1, 2026-03-01, 45d
Reprice / validate + payment resilience :a2, 2026-03-01, 60d
Booking confirmation + retrieval :a3, 2026-03-15, 60d
Support ticketing + audit + reconciliation :a4, 2026-03-15, 75d
Credit / markup / discount controls :a5, 2026-04-01, 60d
section Stage 2 — Acceleration
Fare calendar + flexible dates :b1, 2026-06-01, 60d
Alerts / saved search / booking history UX :b2, 2026-06-15, 60d
Corporate/private fare gating :b3, 2026-07-01, 60d
Ancillary / charter controlled rollout :b4, 2026-07-15, 75d
section Stage 3 — Defensibility / later
Offer quality scoring :c1, 2026-09-01, 60d
Price history + demand intelligence :c2, 2026-09-15, 90d
Multiple providers assessment :c3, 2026-10-15, 75d
AI exploration (only if justified) :c4, 2026-11-15, 60d
12. Risk and cost impact analysis (v2-aligned)
| Risk | Why it matters more in a direct-booking model | Mitigation focus |
|---|---|---|
| Price mismatch before payment | Damages trust and creates refund / support load | Strong repricing and clear final totals |
| Payment failures and ambiguous state | Blocks conversion and creates support chaos | Retry, fallback, reconciliation, visible status |
| Booking created but poorly surfaced | Users contact support, lose trust, or duplicate actions | Clear confirmation and booking retrieval |
| Weak support linkage | Incidents become slow and expensive to resolve | Ticketing linked to booking, payment, and servicing data |
| Credit misuse / ambiguity | Direct B2B financial exposure | Reservation, release, approval, ledger visibility |
| Promotion abuse or uncontrolled discounting | Margin erosion and trust issues | Rules, approvals, auditability, segment controls |
| Supplier-dependent servicing depth | Product promises can outrun actual provider capability | Gate features by supplier support and ops readiness |
| Premature expansion into providers or AI | High complexity before baseline stability | Enforce later-by-default policy |
| Sponsored merchandising without governance | Trust degradation in flight results | Clear labels, controls, quality rules, staged rollout |
13. Final strategic recommendations
13.1 Top revenue multipliers
- Reliable owned booking funnel — the strongest revenue multiplier is higher completed-booking yield, not redirect volume.
- Agent commercial control — markups, credit, private/corporate fares, and governed discounts materially increase monetizable flexibility.
- Ancillary and post-search monetization — only after booking trust is stable.
- Retention loops — alerts, saved search, and booking continuity improve deferred conversion and repeat usage.
13.2 Top conversion boosters
- Transparent total pricing and fare rules
- Strong reprice / validation behavior before payment
- Better checkout resilience and recovery
- Fare calendar / flexible-date UX
- Offer-quality-aware ranking and suppression
13.3 Top defensibility builders
- First-party order-linked behavioral data
- Quality scoring across offers, suppliers, and booking outcomes
- Price history and demand intelligence
- Later AI and provider expansion built on stable foundations
13.4 Strategic guardrails
- Do not let growth or merchandising layers outrun transaction integrity.
- Do not use old redirect-era economics as the main prioritization model.
- Do not classify current-scope commerce and support capabilities as optional “future polish.”
- Do use competitor research aggressively for UX parity, retention ideas, and trust patterns.
- Do keep Multiple Providers and AI in the later-by-default bucket unless formally pulled forward.
14. Mapping old v1 concepts to v2 interpretation
| Historical concept | v2 interpretation |
|---|---|
| Search → redirect CTR | Search → checkout start → payment success → booking success |
| Partner yield per redirect | Net yield per booking |
| Pixel / postback attribution | Booking-payment-support-reconciliation linkage |
| “Book on platform” for select inventory | On-platform booking as the current baseline model |
| Referral / CPC marketplace as governing business model | Booking-led commerce with governed promotional / merchandising extensions |
| Redirect event warehouse as the main moat | First-party search + order + support + finance intelligence foundation |
| Meta-search gap analysis | Direct-booking parity and operating-model gap analysis |
15. How to use this document
Use this document for:
- priority discussions
- roadmap sequencing
- business-case framing
- risk-aware feature expansion planning
- interpreting older parity / feature research correctly
Do not use this document as the final authority for:
- scope disputes
- exhaustive feature enumeration
- portal ownership definitions
- payment architecture decisions
- formal acceptance criteria
- current-vs-later precedence decisions where PRD v3.0 or Product Model v3.0 already defines the answer
For those, use the governing product documents directly.
16. Final statement
Feature Research and ROI Exploration v2 preserves the valuable market and feature research from the earlier phase, but re-anchors it to the correct product identity: a Verteil-powered, direct-booking, flight retail and servicing platform. Under this model, the highest-ROI path is to strengthen transaction integrity, booking continuity, supportability, and commercial governance first; then layer conversion accelerators, retention loops, and defensible intelligence; and only later expand to Multiple Providers and AI capabilities by default.
Governance Footer
- Document ID: FLYMAX-03-Analysis-FEATURE-RESEARCH-EXPLORATION
- Canonical Version: 2.0
- Lifecycle: Active
- Scope: Valid
- Source of Truth: docs/
- Related Change Ticket:
- Last Reviewed On: 2026-03-09
- Next Review Due: 2026-03-09
Approval Sign-off
| Role | Name | Date | Status |
|---|---|---|---|
| Product Owner | Pending | ||
| Technical Lead / Solution Architect | George Joseph | Pending | |
| Engineering Lead | Pending | ||
| Commercial / Operations | Pending |
Document Lineage
- Supersedes:
- Superseded By:
Change Log
- 2.0 (2026-03-09) - Header/footer standardized to FlyMax documentation playbook.