import type { FaqItem } from "@/content/types";

export const howWeWorkPage = {
  seo: {
    title: "How We Work: The Revenue Circuit",
    description:
      "How Axidys Media runs growth engagements for SaaS and e-commerce: the Revenue Circuit, a six-phase process, commercial reporting, and documented tests.",
  },
  hero: {
    eyebrow: "How we work",
    title: "How we work: from diagnosis to scale.",
    intro:
      "A clear operating system for growth. Find the constraint, model the economics, test with discipline, and scale what the numbers support.",
    imageAlt: "Colleagues arranging notes in columns while one sketches a loop diagram on a whiteboard",
  },
  principles: {
    title: "Four rules we don't bend.",
    intro: "They decide the order of work when everything feels urgent.",
    items: [
      {
        title: "Economics before channels",
        description: "We agree what a customer is worth and what you can pay to win one before choosing where to spend.",
      },
      {
        title: "Measurement before scale",
        description: "Budgets don't grow on numbers we can't trust. Fixing tracking comes before raising spend.",
      },
      {
        title: "Hypotheses before opinions",
        description: "Every change starts as a written hypothesis with a success metric, so results settle debates.",
      },
      {
        title: "Documentation before memory",
        description: "Decisions, tests, and learnings are written down, so knowledge stays with your business.",
      },
    ],
  },
  reporting: {
    title: "Reports that read like a P&L, not a platform export.",
    intro: "Every report follows the same three layers, read from the top down.",
    layers: [
      {
        name: "Business outcomes",
        question: "Is the business growing in a way it can afford?",
        description: "Pipeline, revenue, new customers, and contribution margin.",
      },
      {
        name: "Efficiency",
        question: "What is that growth costing?",
        description: "CAC, CAC payback, MER, and LTV:CAC.",
      },
      {
        name: "Channel diagnostics",
        question: "Why are the numbers above moving?",
        description: "Conversion rates, impression share, frequency, query mix, and creative fatigue.",
      },
    ],
  },
  experiments: {
    title: "How a test earns its place.",
    intro: "Tests move through a shared backlog. Nothing launches without a hypothesis, and nothing ends without a decision.",
    template:
      "Because we observed [evidence], we believe [change] for [audience] will [outcome]. We'll know it worked when [primary metric] moves in [direction] without harming [guardrail].",
    lifecycle: [
      { name: "Backlog", description: "Ideas logged with the evidence behind them." },
      { name: "Prioritized", description: "Scored by expected impact, confidence, and effort." },
      { name: "Running", description: "Launched with a primary metric and guardrails agreed up front." },
      { name: "Analyzed", description: "Read against the plan, not against hope." },
      { name: "Decided", description: "Rolled out, iterated, or retired, with the learning recorded." },
    ],
  },
  faqs: [
    {
      question: "What does an engagement start with?",
      answer:
        "A diagnostic. We review accounts, tracking, funnels, and customer data, then agree on the constraints to address first. The first phase is planned from what we find, not from a standard package. A [Growth Audit](/growth-audit) is the usual way in.",
    },
    {
      question: "Who owns the experiment backlog?",
      answer:
        "It's shared. We maintain it, your team can see and add to it, and priorities are agreed together. Every test records its hypothesis, status, result, and the decision that followed.",
    },
    {
      question: "How often will we meet?",
      answer:
        "Most teams choose a weekly or biweekly working session, a monthly performance review, and quarterly planning. The rhythm is set to your pace, with async updates in between.",
    },
    {
      question: "What do reports lead with?",
      answer:
        "Commercial metrics: pipeline, revenue, CAC, MER, or contribution margin, depending on your model. Channel metrics sit underneath to explain what changed and why. See how we approach [analytics and attribution](/analytics-attribution).",
    },
    {
      question: "Can you work alongside other agencies or freelancers?",
      answer:
        "Yes. Ownership of each channel and metric is agreed up front, so there's no overlap. Shared measurement keeps everyone working from the same numbers.",
    },
  ] satisfies FaqItem[],
};

export const aboutPage = {
  seo: {
    title: "About Axidys Media",
    description:
      "What we believe about growth marketing, how we make decisions, and what we won't do. A specialist agency for SaaS and e-commerce companies.",
  },
  hero: {
    eyebrow: "About",
    title: "Marketing should make the business easier to understand.",
    intro:
      "Axidys Media is a growth marketing agency for SaaS and e-commerce companies. This page is about how we think, because that is what you would be hiring.",
  },
  beliefs: {
    title: "Five beliefs that shape the work.",
    items: [
      {
        title: "Revenue is the scoreboard.",
        description: "Clicks, impressions, and platform ROAS are useful signals. They are not the result. The result is pipeline, revenue, and margin.",
      },
      {
        title: "Most growth problems live between channels.",
        description: "Ads, pages, tracking, and retention are often managed separately. The biggest losses tend to sit in the handoffs.",
      },
      {
        title: "Depth beats range.",
        description: "SaaS and e-commerce grow differently. Knowing two models deeply is more useful than knowing ten loosely.",
      },
      {
        title: "Trusted numbers are a growth lever.",
        description: "When everyone believes the data, budget decisions get faster and bolder.",
      },
      {
        title: "Clarity is a deliverable.",
        description: "If a report needs a meeting to decode it, the report has failed.",
      },
    ],
  },
  decisions: {
    title: "Evidence in, decision out.",
    intro: "Every recommendation follows the same path, so you can see how we got there and challenge any step.",
    steps: [
      { name: "Evidence", description: "What the data, research, and customer signals show." },
      { name: "Economics", description: "What the change is worth against CAC, payback, or margin." },
      { name: "Hypothesis", description: "What we expect to happen, and how we'll know." },
      { name: "Test", description: "The smallest change that can prove or disprove it." },
      { name: "Decision", description: "Roll out, iterate, or stop, and write down why." },
    ],
  },
  communication: {
    title: "Plain language. Regular rhythm. No surprises.",
    items: [
      { title: "Say what we don't know", description: "Estimates are labeled as estimates. Attribution is described as a model, not a fact." },
      { title: "Lead with the business", description: "Updates start with commercial outcomes, then explain the channel detail behind them." },
      { title: "Share bad news early", description: "If a test fails or tracking breaks, you hear about it quickly, with a plan attached." },
      { title: "Write it down", description: "Decisions, priorities, and learnings are documented where your team can find them." },
    ],
  },
  measurement: {
    title: "Three questions, in this order.",
    intro: "Marketing is measured the way the business is run: outcome first, cost second, explanation third.",
    layers: [
      { name: "Is it growing the business?", question: "Business outcomes", description: "Pipeline, revenue, new customers, and contribution margin." },
      { name: "Is the growth affordable?", question: "Efficiency", description: "CAC, payback, MER, and LTV:CAC." },
      { name: "Why is it moving?", question: "Diagnostics", description: "Channel and funnel metrics that explain the layers above." },
    ],
  },
  wontDo: {
    title: "Things we won't do, even when asked.",
    items: [
      "Report platform ROAS as proof of profit.",
      "Scale spend on tracking we can't trust.",
      "Recommend a channel because it's easy to sell.",
      "Promise results we don't control.",
      "Hide a failed test or a broken number.",
      "Invent case studies, testimonials, or awards to look bigger.",
    ],
  },
  fit: {
    title: "A good fit, and a poor one.",
    good: [
      "SaaS companies with paying customers that want to grow pipeline efficiently",
      "E-commerce brands that want growth to hold up at the margin line",
      "Teams willing to share CRM or store data, not just ad account access",
      "Leaders who make decisions on evidence and are comfortable testing",
    ],
    poor: [
      "Businesses outside SaaS and e-commerce",
      "Teams measuring success only in clicks, leads, or impressions",
      "Projects that require guaranteed results before any diagnostic",
      "Companies that prefer to keep performance data from their marketing partners",
    ],
  },
};
