{
  "ok": true,
  "pilot_room": {
    "id": "catalyst-q-pilot-conversion-room-v1",
    "vertical_id": "freight-field-routing",
    "updated_at": "2026-05-31",
    "positioning": {
      "category": "RouteOps paid pilot conversion layer",
      "buyer_promise": "Know if a paid pilot is worth it before asking a buyer to trust another AI demo.",
      "claim_boundary": "Catalyst-Q is not a TMS replacement. It does not operate vehicles, change routes without approval, or promise fixed savings; it is a paid-pilot proof layer for route decisions with human approval."
    },
    "qualification": {
      "required_inputs": [
        {
          "id": "fleet_size",
          "label": "Fleet size",
          "why_it_matters": "Screens for route volume and operational stakes."
        },
        {
          "id": "weekly_routes",
          "label": "Weekly routes",
          "why_it_matters": "Shows whether repeated decisions justify a paid pilot."
        },
        {
          "id": "annual_route_miles",
          "label": "Annual route miles",
          "why_it_matters": "Creates the mileage and fuel exposure baseline."
        },
        {
          "id": "fuel_spend_usd",
          "label": "Annual fuel spend",
          "why_it_matters": "Quantifies one finance-owned savings lever."
        },
        {
          "id": "labor_spend_usd",
          "label": "Annual route labor spend",
          "why_it_matters": "Quantifies dispatcher and driver time exposure."
        },
        {
          "id": "current_tms",
          "label": "Current TMS or route tool",
          "why_it_matters": "Keeps Catalyst-Q positioned as a proof layer around existing systems."
        },
        {
          "id": "pain_metric",
          "label": "Pain metric",
          "why_it_matters": "Forces the pilot to prove a buyer-owned problem."
        },
        {
          "id": "decision_owner",
          "label": "Decision owner",
          "why_it_matters": "Identifies who can approve the pilot and sign off on value."
        },
        {
          "id": "can_upload_route_file",
          "label": "Route file ready",
          "why_it_matters": "Enables first value in the first week."
        },
        {
          "id": "has_dispatcher_baseline",
          "label": "Dispatcher baseline",
          "why_it_matters": "Gives the proof packet a real opposing row."
        }
      ],
      "scoring_model": [
        "High route volume and fleet size raise readiness.",
        "Annual fuel, labor, and mileage exposure must support the paid-pilot price point.",
        "A route file, dispatcher baseline, pain metric, and decision owner are required for ready_now.",
        "TMS replacement intent lowers fit because Catalyst-Q is a decision-proof layer."
      ]
    },
    "sample_qualification": {
      "ready_state": "ready_now",
      "pilot_readiness_score": 100,
      "economic_exposure": {
        "annual_route_cost_usd": 1836000,
        "annual_route_miles": 1200000,
        "fuel_spend_usd": 680000,
        "labor_spend_usd": 940000
      },
      "missing_data": [],
      "disqualifiers": [],
      "next_best_action": "Send the paid pilot scope and schedule the baseline replay kickoff.",
      "recommended_offer": {
        "price": "$15,000-$35,000 for 4-6 weeks",
        "scope": "One freight or field-routing lane, one historical baseline replay, one shadow-mode route decision cycle, and one finance-ready closeout packet.",
        "success_metric": "Verified change in mileage, lateness, capacity violations, fuel/emissions proxy, and accepted recommendations versus the dispatcher baseline.",
        "required_data": [
          "One route file with orders, stops, vehicles, time windows, capacity, and service times.",
          "Dispatcher baseline or current TMS export for the same route set.",
          "Fuel, labor, lateness, service-failure, or route-change cost assumptions approved by finance.",
          "Decision owner, dispatcher owner, and rollback owner."
        ],
        "deliverables": [
          "Pilot readiness score and ICP decision.",
          "Route Decision Record for each approved candidate.",
          "Hostile solver review against dispatcher, heuristic, OR-Tools, PyVRP, and VROOM rows where available.",
          "CFO ROI packet with accepted, rejected, and pending recommendations.",
          "Case-study skeleton ready for customer approval once verified savings are observed."
        ],
        "acceptance_gates": [
          "CFO or finance reviewer accepts the cost-exposure model.",
          "Dispatcher approves the first Route Decision Record before operational change.",
          "Catalyst-Q must beat, match, or explain the baseline before rollout expansion.",
          "Third-party connectors remain planned or pilot-scoped until credentials, mapping, and validation are complete."
        ],
        "connector_posture": "CSV intake is live today. TMS/API/webhook/telematics connectors are pilot-scoped and require tenant approval, credentials, mapping, and validation.",
        "timeline": [
          {
            "week": "Week 1",
            "buyer_action": "Upload the route file and baseline export.",
            "catalyst_action": "Validate inputs, quantify exposure, and build the first proof packet.",
            "output": "Pilot readiness score and data-gap list."
          },
          {
            "week": "Week 2",
            "buyer_action": "Approve cost assumptions and route constraints.",
            "catalyst_action": "Run dispatcher, heuristic, open-solver, and Catalyst-Q comparison rows.",
            "output": "Route Decision Record with hostile review."
          },
          {
            "week": "Weeks 3-4",
            "buyer_action": "Review shadow-mode recommendations and approve only bounded decisions.",
            "catalyst_action": "Track accepted, rejected, and pending recommendations.",
            "output": "Adoption and risk-delta evidence."
          },
          {
            "week": "Weeks 5-6",
            "buyer_action": "Confirm verified savings and expansion criteria.",
            "catalyst_action": "Build CFO ROI packet and conversion recommendation.",
            "output": "Paid-pilot closeout and customer-approved case-study draft."
          }
        ]
      }
    },
    "paid_pilot_offer": {
      "price": "$15,000-$35,000 for 4-6 weeks",
      "scope": "One freight or field-routing lane, one historical baseline replay, one shadow-mode route decision cycle, and one finance-ready closeout packet.",
      "success_metric": "Verified change in mileage, lateness, capacity violations, fuel/emissions proxy, and accepted recommendations versus the dispatcher baseline.",
      "required_data": [
        "One route file with orders, stops, vehicles, time windows, capacity, and service times.",
        "Dispatcher baseline or current TMS export for the same route set.",
        "Fuel, labor, lateness, service-failure, or route-change cost assumptions approved by finance.",
        "Decision owner, dispatcher owner, and rollback owner."
      ],
      "deliverables": [
        "Pilot readiness score and ICP decision.",
        "Route Decision Record for each approved candidate.",
        "Hostile solver review against dispatcher, heuristic, OR-Tools, PyVRP, and VROOM rows where available.",
        "CFO ROI packet with accepted, rejected, and pending recommendations.",
        "Case-study skeleton ready for customer approval once verified savings are observed."
      ],
      "acceptance_gates": [
        "CFO or finance reviewer accepts the cost-exposure model.",
        "Dispatcher approves the first Route Decision Record before operational change.",
        "Catalyst-Q must beat, match, or explain the baseline before rollout expansion.",
        "Third-party connectors remain planned or pilot-scoped until credentials, mapping, and validation are complete."
      ],
      "connector_posture": "CSV intake is live today. TMS/API/webhook/telematics connectors are pilot-scoped and require tenant approval, credentials, mapping, and validation.",
      "timeline": [
        {
          "week": "Week 1",
          "buyer_action": "Upload the route file and baseline export.",
          "catalyst_action": "Validate inputs, quantify exposure, and build the first proof packet.",
          "output": "Pilot readiness score and data-gap list."
        },
        {
          "week": "Week 2",
          "buyer_action": "Approve cost assumptions and route constraints.",
          "catalyst_action": "Run dispatcher, heuristic, open-solver, and Catalyst-Q comparison rows.",
          "output": "Route Decision Record with hostile review."
        },
        {
          "week": "Weeks 3-4",
          "buyer_action": "Review shadow-mode recommendations and approve only bounded decisions.",
          "catalyst_action": "Track accepted, rejected, and pending recommendations.",
          "output": "Adoption and risk-delta evidence."
        },
        {
          "week": "Weeks 5-6",
          "buyer_action": "Confirm verified savings and expansion criteria.",
          "catalyst_action": "Build CFO ROI packet and conversion recommendation.",
          "output": "Paid-pilot closeout and customer-approved case-study draft."
        }
      ]
    },
    "case_study_skeleton": {
      "status": "pending_customer_evidence",
      "title": "Freight RouteOps paid pilot case study",
      "fields": {
        "baseline": "Current dispatcher or TMS plan, with mileage, lateness, capacity, fuel, and route-change metrics.",
        "catalyst_candidate": "Catalyst-Q candidate from freight-routeops-proof-packet-v1, compared against dispatcher, heuristic, OR-Tools, PyVRP, and VROOM where available.",
        "accepted_decision": "Human-approved Route Decision Record with rollback plan and signature.",
        "verified_savings": "Finance-approved savings, avoided cost, or risk reduction after shadow-mode or controlled rollout.",
        "objections": "Connector readiness, data quality, dispatcher trust, solver-comparison gaps, and rollout risk.",
        "conversion_outcome": "Paid pilot converted, extended, paused, or rejected with reason codes."
      }
    },
    "vc_metrics": {
      "funding_verdict": "seed_watchlist",
      "fundable_when": [
        "3 paid pilots with signed Route Decision Records.",
        "At least one customer-approved ROI packet or case study.",
        "Repeatable first-week onboarding from route file to proof packet.",
        "Clear connector posture that does not overclaim production integrations."
      ],
      "metrics": [
        {
          "id": "paid_pilot_readiness_score",
          "label": "Sample paid-pilot readiness",
          "value": 100,
          "unit": "score",
          "why_it_matters": "Shows whether a buyer can move from interest to paid scope."
        },
        {
          "id": "time_to_first_value_days",
          "label": "Time to first proof packet",
          "value": 7,
          "unit": "days",
          "why_it_matters": "VCs fund repeatable onboarding, not bespoke consulting."
        },
        {
          "id": "proof_packet_completeness_pct",
          "label": "Proof packet completeness",
          "value": 100,
          "unit": "percent",
          "why_it_matters": "Confirms the product can produce the artifact the buyer is paying for."
        },
        {
          "id": "connector_honesty_score",
          "label": "Connector honesty",
          "value": 9,
          "unit": "of 9 connectors accurately scoped",
          "why_it_matters": "Avoids diligence failure from integration overclaims."
        }
      ]
    },
    "links": {
      "page": "https://catalyst-q.strategic-innovations.ai/pilot-room",
      "qualify_api": "https://catalyst-q.strategic-innovations.ai/v1/pilot-room/qualify",
      "routeops_proof_room": "https://catalyst-q.strategic-innovations.ai/routeops-proof-room",
      "freight_proof_packet": "https://catalyst-q.strategic-innovations.ai/v1/freight/proof-packet",
      "pricing": "https://catalyst-q.strategic-innovations.ai/pricing"
    }
  },
  "vc_metrics": {
    "funding_verdict": "seed_watchlist",
    "required_next_signal": "3 paid pilots with signed Route Decision Records",
    "investor_objections": [
      "Will buyers show willingness to pay before native integrations exist?",
      "Can onboarding become repeatable without founder-led services?",
      "Can Catalyst-Q produce customer-approved proof packets from real route files?",
      "Can the company stay in the proof-layer wedge instead of drifting into TMS replacement?"
    ],
    "de_risking_assets": [
      {
        "label": "Pilot Conversion Room",
        "url": "https://catalyst-q.strategic-innovations.ai/pilot-room",
        "signal": "Turns buyer interest into paid-pilot qualification."
      },
      {
        "label": "RouteOps Proof Room",
        "url": "https://catalyst-q.strategic-innovations.ai/routeops-proof-room",
        "signal": "Shows the core proof artifact and claim boundaries."
      },
      {
        "label": "Freight proof packet API",
        "url": "https://catalyst-q.strategic-innovations.ai/v1/freight/proof-packet",
        "signal": "Demonstrates structured baseline-vs-candidate evidence."
      },
      {
        "label": "Buyer-agent manifest",
        "url": "https://catalyst-q.strategic-innovations.ai/llms.txt",
        "signal": "Makes proof surfaces discoverable to AI buyer agents."
      }
    ],
    "metrics": [
      {
        "id": "paid_pilot_readiness_score",
        "label": "Sample paid-pilot readiness",
        "value": 100,
        "unit": "score",
        "why_it_matters": "Shows whether a buyer can move from interest to paid scope."
      },
      {
        "id": "time_to_first_value_days",
        "label": "Time to first proof packet",
        "value": 7,
        "unit": "days",
        "why_it_matters": "VCs fund repeatable onboarding, not bespoke consulting."
      },
      {
        "id": "proof_packet_completeness_pct",
        "label": "Proof packet completeness",
        "value": 100,
        "unit": "percent",
        "why_it_matters": "Confirms the product can produce the artifact the buyer is paying for."
      },
      {
        "id": "connector_honesty_score",
        "label": "Connector honesty",
        "value": 9,
        "unit": "of 9 connectors accurately scoped",
        "why_it_matters": "Avoids diligence failure from integration overclaims."
      }
    ]
  },
  "links": {
    "page": "https://catalyst-q.strategic-innovations.ai/pilot-room",
    "qualify": "https://catalyst-q.strategic-innovations.ai/v1/pilot-room/qualify",
    "routeops_proof_room": "https://catalyst-q.strategic-innovations.ai/routeops-proof-room"
  }
}