export type Severity = "Critical" | "High" | "Medium-High";

export interface ProblemData {
  slug: string;
  name: string;
  severity: Severity;
  costLine: string;
  occurrence: string;
  financialHook: string;
  section2Headline: string;
  section2Body: string[];
  scenario: string;
  scenarioClosing: string;
  stats: { value: string; label: string }[];
  solveCopy: string;
  sampleExchange: { user: string; bot: string };
  shortName: string;
}

export const severityColors: Record<Severity, string> = {
  Critical: "bg-primary",
  High: "bg-orange-500",
  "Medium-High": "bg-yellow-500",
};

export const severityTextColors: Record<Severity, string> = {
  Critical: "text-primary",
  High: "text-orange-500",
  "Medium-High": "text-yellow-500",
};

export const problems: ProblemData[] = [
  {
    slug: "response-gap",
    name: "The Response Gap",
    severity: "Critical",
    costLine: "Buyers who don't get an instant answer don't wait. They go to your competitor.",
    occurrence: "Happens daily, across every product page, every weekend, every holiday.",
    financialHook: "Every unanswered inquiry is a closed deal. Just not yours.",
    section2Headline: "This isn't a staffing problem. It's a timing problem.",
    section2Body: [
      "B2B websites were built to display products, not to sell them. Contact forms were added as an afterthought. No real-time response layer exists between the buyer's question and a human being available to answer it.",
      "When a buyer hits your site outside business hours, or during a busy stretch when no one is monitoring the inbox, there is nothing there to catch them. The lead is gone before it was ever created.",
    ],
    scenario: "A buyer lands on the site, can't find what they need fast enough, and leaves without submitting anything. Invisible. No record. Or they push through, submit an RFQ, and wait three days in silence. Either way the competitor wins and the business may never know it happened.",
    scenarioClosing: "Your competitor answered. You didn't know it happened.",
    stats: [
      { value: "3 Days", label: "Average RFQ response time without automation" },
      { value: "$0", label: "Revenue captured from after-hours inquiries" },
      { value: "1 Hour", label: "Time before most buyers move on to a competitor" },
    ],
    solveCopy: "ChatSKU deploys a real-time AI assistant that sits directly on your product pages and responds to buyer questions instantly. It answers spec queries, confirms availability, surfaces alternatives, and routes qualified inquiries into a structured quote pipeline. No staffing required. No business hours limitation. Every visitor gets an immediate, informed response.",
    sampleExchange: {
      user: "Is the 316 stainless version available in 1/2 inch?",
      bot: "Yes. SKU SS316-050 is in stock with a 3-day lead time. Want me to start a quote?",
    },
    shortName: "the response gap",
  },
  {
    slug: "passive-catalog",
    name: "The Passive Catalog Problem",
    severity: "Critical",
    costLine: "A PDF catalog cannot sell. It can only inform, and only during business hours.",
    occurrence: "The default state for most manufacturers, distributors, and wholesalers.",
    financialHook: "Your catalog works 9 to 5. Your buyers don't.",
    section2Headline: "This isn't a staffing problem. It's a catalog infrastructure problem.",
    section2Body: [
      "Product catalogs were designed by operations and engineering teams to document products, not by sales teams to convert buyers. The goal was completeness and accuracy. A PDF or static HTML page was the logical output of that mindset.",
      "No search by spec. No stock confirmation. No interactive path to a quote. Hiring a night-shift rep doesn't fix a dead PDF. The problem is structural.",
    ],
    scenario: "A buyer arrives at 9pm needing specs, MOQ, and lead time confirmation. The catalog is either a PDF they have to dig through or a static HTML page with no interaction. No chat. No self-serve path. No staff online. The catalog cannot respond. Buyer leaves.",
    scenarioClosing: "Your competitor answered. You didn't know it happened.",
    stats: [
      { value: "60%+", label: "Of B2B research happens outside business hours" },
      { value: "0", label: "Self-serve paths on a typical PDF catalog" },
      { value: "1 Line", label: "Of code is all it takes to change this with ChatSKU" },
    ],
    solveCopy: "ChatSKU transforms your static catalog into an interactive buying experience. Buyers can search by spec, ask natural-language questions, get instant stock and lead time answers, and submit quotes without ever leaving the page. Your catalog becomes a 24/7 sales channel that works while your team sleeps.",
    sampleExchange: {
      user: "What's the MOQ on your brass fittings?",
      bot: "Standard MOQ is 100 units. For orders over 500, volume pricing applies. Want me to pull a quote?",
    },
    shortName: "a catalog that can't sell",
  },
  {
    slug: "human-bottleneck",
    name: "The Human Bottleneck",
    severity: "High",
    costLine: "Your reps are answering spec questions when they should be closing deals.",
    occurrence: "Universal across any business with a complex catalog and no self-serve layer.",
    financialHook: "Your best reps are doing work a system should handle.",
    section2Headline: "Every spec question a rep answers is a deal they aren't closing.",
    section2Body: [
      "When no self-serve layer exists on the website, every buyer question gets routed through the same human channel regardless of complexity or value. There is no triage. No automation. No way to separate a $50 reorder question from a $50,000 new account inquiry.",
      "Everything lands on the same rep. The result is expensive human capital systematically misallocated to low-value work while high-value opportunities sit unworked.",
    ],
    scenario: "Sales reps spend the majority of their day fielding repetitive product questions: stock levels, lead times, finish options, MOQs. Buyers have no self-serve path and no choice but to call or email a human. High-value rep time is consumed by low-value lookups while actual deals sit unworked.",
    scenarioClosing: "Your competitor answered. You didn't know it happened.",
    stats: [
      { value: "Hours", label: "Lost daily per rep to repetitive spec queries" },
      { value: "0", label: "Deals worked while reps answer catalog questions" },
      { value: "80%", label: "Of routine inquiries ChatSKU handles automatically" },
    ],
    solveCopy: "ChatSKU handles the repetitive, spec-level inquiries that consume your reps' days. Stock checks, lead times, material options, and MOQ lookups are answered instantly by AI. Your reps only see qualified, high-value inquiries that are ready for human attention. The result is more deals worked per rep, per day.",
    sampleExchange: {
      user: "What's the lead time on galvanized channel strut?",
      bot: "Standard lead time is 5 business days. Expedited available for orders placed before 2pm. Want pricing?",
    },
    shortName: "rep time on the wrong work",
  },
  {
    slug: "black-hole-pipeline",
    name: "The Black Hole Pipeline",
    severity: "High",
    costLine: "Inquiries that aren't tracked don't get followed up. Revenue evaporates silently.",
    occurrence: "Endemic to teams without a CRM or built around email and spreadsheets.",
    financialHook: "If it isn't tracked, it isn't revenue. It's a guess.",
    section2Headline: "Your pipeline exists in people's heads and inboxes.",
    section2Body: [
      "Inquiry channels were never unified into a single system. Email, phone, and contact forms each deposit leads into different places owned by different people. Without a structured intake process, the pipeline has no single source of truth.",
      "It exists as a collection of individual memories, inboxes, and spreadsheets that no one fully owns or can see completely. Sales managers have no visibility into inquiry volume, quote stage, or potential revenue value.",
    ],
    scenario: "Inquiries arrive through scattered channels, get missed, buried, or assigned informally. No tracking. No follow-up. No audit trail. Sales managers have no visibility into inquiry volume, quote stage, or potential revenue value. The pipeline exists only in people's heads and inboxes.",
    scenarioClosing: "Your competitor answered. You didn't know it happened.",
    stats: [
      { value: "Scattered", label: "Inquiries across email, phone, and forms with no single owner" },
      { value: "0", label: "Management visibility into quote status or pipeline value" },
      { value: "100%", label: "Of ChatSKU inquiries captured into a structured dashboard" },
    ],
    solveCopy: "Every conversation ChatSKU handles is captured, structured, and surfaced in a unified dashboard. Inquiry source, product interest, buyer intent signals, and quote status are all visible in one place. Sales managers see the full pipeline for the first time. Nothing gets lost, buried, or forgotten.",
    sampleExchange: {
      user: "I need a quote on 200 units of the titanium hex bolts.",
      bot: "Confirmed. I've started a quote for 200x TI-HEX-025. Your rep will have it ready within the hour. Anything else?",
    },
    shortName: "pipeline you can't see",
  },
  {
    slug: "complex-configuration",
    name: "The Complex Configuration Problem",
    severity: "High",
    costLine: "The queries hardest to handle are attached to your largest order values.",
    occurrence: "Concentrated in industrial, hardware, and specialty manufacturing categories.",
    financialHook: "Your highest-value orders are the ones your site handles worst.",
    section2Headline: "The bigger the order, the harder it is for your site to respond.",
    section2Body: [
      "B2B product catalogs were architected for browsing and reference, not for real-time configuration. The underlying product data exists but was never structured to support multi-attribute queries.",
      "No interface was ever built to let a buyer combine finish, size, quantity, lead time, and pricing tier into a single question and get a single coherent answer. These are often the highest-value orders in the pipeline. Losing them is disproportionately costly.",
    ],
    scenario: "A buyer asks: Do you have the 3/8 inch zinc-plated version, qty 500, net-30 terms, 5-day lead time? A static site returns nothing. A contact form sends an email into a queue. The buyer needed an answer in the moment. They don't get one, and they move on.",
    scenarioClosing: "Your competitor answered. You didn't know it happened.",
    stats: [
      { value: "Multi-attribute", label: "Queries represent the highest order values in your pipeline" },
      { value: "$0", label: "Returned by a static site on a complex spec question" },
      { value: "1 Conversation", label: "Is all ChatSKU needs to match specs, surface alternatives, and route to a quote" },
    ],
    solveCopy: "ChatSKU understands multi-attribute queries natively. A buyer can ask about finish, size, quantity, terms, and lead time in a single message and get a coherent, accurate response. The AI matches against your full catalog data, surfaces exact SKUs or alternatives, and routes complex inquiries directly into a quote workflow.",
    sampleExchange: {
      user: "Do you have 3/8\" zinc-plated bolts, qty 500, net-30?",
      bot: "Yes. SKU ZB-375-500 is in stock. Lead time 4 days. Want me to start a quote?",
    },
    shortName: "complex queries falling through",
  },
  {
    slug: "headcount-ceiling",
    name: "The Headcount Ceiling",
    severity: "Medium-High",
    costLine: "You cannot grow responsiveness without growing payroll. That's a structural trap.",
    occurrence: "Most acute during growth phases and seasonal demand spikes.",
    financialHook: "You're scaling payroll when you should be scaling revenue.",
    section2Headline: "Responsiveness was never decoupled from headcount. It needs to be.",
    section2Body: [
      "Customer responsiveness is entirely dependent on human staffing levels because no technology layer was ever inserted between buyer demand and human fulfillment of that demand. Every unit of growth in inquiry volume maps directly to a unit of growth in staffing need.",
      "Each new rep is a fixed cost, a training investment, and a capacity constraint. The business cannot scale its responsiveness without scaling its payroll. That ceiling gets more expensive to ignore the longer it persists.",
    ],
    scenario: "As inquiry volume grows, the only solution today is adding inside sales or support staff. Each new rep is a fixed cost, a training investment, and a ramp period. The business cannot scale its responsiveness without scaling its payroll.",
    scenarioClosing: "Your competitor answered. You didn't know it happened.",
    stats: [
      { value: "1 to 1", label: "Every inquiry volume increase requires a headcount increase today" },
      { value: "Months", label: "To hire, onboard, and ramp a new inside sales rep" },
      { value: "Same Cost", label: "ChatSKU handles 10 or 10,000 simultaneous conversations" },
    ],
    solveCopy: "ChatSKU breaks the link between inquiry volume and headcount. The AI handles unlimited simultaneous conversations at a fixed cost. As your business grows, your responsiveness scales automatically without adding staff. Your team focuses on closing, not answering. Growth becomes a revenue event, not a hiring event.",
    sampleExchange: {
      user: "Can you handle bulk inquiries during trade show season?",
      bot: "Absolutely. I handle unlimited simultaneous conversations. Your team focuses on closing while I handle the intake.",
    },
    shortName: "growth capped by headcount",
  },
];
