// Business · AI & Automation

function BusinessAIPage({ setRoute }) {
  return (
    <div data-screen-label="08a Business · AI & Automation">
      <section className="q-svc-hero2" style={{ padding: '0 0 120px' }}>
        <SiteNav route="business-ai" setRoute={setRoute} theme="dark" />
        <div className="q-wrap q-svc-hero2-inner" style={{ paddingTop: 120 }}>
          <div className="q-eyebrow q-eyebrow--dark">Business · AI & Automation</div>
          <h1>AI and automation built for <em>the way your operation actually works.</em></h1>
          <p className="lede">
            Off-the-shelf AI tools are designed for the median use case. Businesses with specific operations, proprietary workflows, and real complexity need something more tailored — and a partner who understands the operation well enough to build it. We identify the highest-leverage opportunities, build what's needed, and train the team that will actually use it.
          </p>
          <div style={{ display: 'flex', gap: 14, flexWrap: 'wrap' }}>
            <a className="qbtn qbtn--paper">Start a conversation <Arrow /></a>
            <a className="qbtn qbtn--outline-dark" onClick={() => setRoute('business')}>Back to Business <Arrow /></a>
          </div>
          <dl className="q-svc-hero2-meta">
            <div><dt>Typical client</dt><dd>Businesses with specialized operations and real workflow complexity</dd></div>
            <div><dt>Entry point</dt><dd>AI & Automation Assessment — scoped, specific, written</dd></div>
            <div><dt>Who leads</dt><dd>Senior strategist and technical director</dd></div>
          </dl>
        </div>
      </section>

      <section className="q-situation">
        <div className="q-wrap">
          <div className="q-situation-grid">
            <div>
              <div className="q-eyebrow">The situation</div>
            </div>
            <div>
              <p><strong>The gap between knowing AI is relevant to your business and actually doing something useful with it is wider than the market would have you believe.</strong> The vendor pitches make it sound simple. The conference case studies are usually about companies with internal engineering teams and AI budgets your operation doesn't have. The gap in practical guidance for businesses with specialized, non-technical operations — where the workflows are complex and the staff are experts in something other than technology — is significant.</p>
              <p><strong>Most AI projects in traditional businesses fail for the same reasons.</strong> They start with the tools rather than the workflows. They train on generic use cases rather than the specific things your staff actually does every day. They optimize for launch rather than adoption. The result is a pilot that worked in the demo and quietly stopped being used six weeks later.</p>
              <p><strong>The businesses that get real value from AI investment share a common approach.</strong> They start with the workflows that carry the most overhead, build or configure tools that fit those workflows exactly, and measure success by whether the people doing the work are actually using the tools — not by whether the tools were deployed. That's how we work.</p>
            </div>
          </div>
        </div>
      </section>

      <section className="q-entry-states">
        <div className="q-wrap">
          <div className="q-section-head">
            <div className="q-eyebrow">Three ways in</div>
            <h2>The AI opportunity is usually <em>one of three things.</em></h2>
            <p>Where the engagement starts depends on where the highest return is. Most of the business AI work we do fits one of these shapes.</p>
          </div>
          <div className="q-entry-list">

            <div className="q-entry-item">
              <div className="q-entry-num">01</div>
              <div className="q-entry-title">
                <span className="label">Workflow automation and staff efficiency</span>
                Hours of staff time freed — in specific, measurable ways.
              </div>
              <div className="q-entry-body">
                <p>The AI opportunity for most businesses is not in grand transformation — it's in the work that currently takes skilled staff hours and doesn't need to. Document processing, research and synthesis, reporting, communication drafts, internal knowledge retrieval, client-facing preparation. Done right, this frees the capacity for the work that actually requires human judgment and expertise.</p>
                <p>We start with the workflows that consume the most time and carry the most overhead. We identify where AI reliably outperforms or accelerates, and we build the automations that stick — not as pilots, but as deployments that become part of how your team actually works every day. Early wins matter; we design for them deliberately rather than treating them as a byproduct of a long implementation.</p>
              </div>
            </div>

            <div className="q-entry-item">
              <div className="q-entry-num">02</div>
              <div className="q-entry-title">
                <span className="label">Custom AI tooling for specialized operations</span>
                Built for your specific business — not adapted from something generic.
              </div>
              <div className="q-entry-body">
                <p>Businesses with proprietary processes, specialized knowledge domains, or complex operational requirements often find that off-the-shelf AI tools get them partway there and no further. The last mile — the part that actually fits the specific operation — requires custom work. That's where the real value is, and it's where most vendors stop.</p>
                <p>Our work with Revere Auctions is the reference case: proprietary AI tooling built for a specialized item processing workflow, designed around the auction house's own grading standards and institutional knowledge, and integrated into the existing operation so that the people using it didn't have to change how they worked to benefit from it. The result was hours of senior staff time freed daily on work that required expertise to describe but not to execute. That model applies across industries with similarly specific operational requirements.</p>
              </div>
            </div>

            <div className="q-entry-item">
              <div className="q-entry-num">03</div>
              <div className="q-entry-title">
                <span className="label">Data, intelligence, and GTM automation</span>
                The data you already have — made useful.
              </div>
              <div className="q-entry-body">
                <p>Most businesses are sitting on more operational data than they're using. Customer history, sales patterns, operational performance, pipeline and prospect information — it exists in different systems, or in spreadsheets, or in the heads of the people who've been doing the work for years. Connecting those sources and making them queryable produces business intelligence that changes how leadership makes decisions.</p>
                <p>We build data connections, dashboards, and AI-assisted intelligence tools that turn what the business already knows into something it can act on. We also build GTM automation — AI-assisted prospecting, outreach, follow-up, and qualification workflows — for businesses where the sales and growth function is running on manual effort that could be significantly accelerated. The goal is always the same: better information and less overhead on the work that doesn't require a human touch.</p>
              </div>
            </div>

          </div>
        </div>
      </section>

      <section className="q-process">
        <div className="q-wrap">
          <div className="q-section-head">
            <div className="q-eyebrow q-eyebrow--dark">How the work flows</div>
            <h2>Assess. Build. Train. Expand.</h2>
            <p>The sequence is consistent. We don't recommend before we understand the operation, and we don't deploy before the team is ready to use what we built.</p>
          </div>
          <div className="q-process-phases">
            <div className="q-phase">
              <div className="step">Phase 01</div>
              <h4>Assess</h4>
              <p>Workflow mapping and staff interviews. We identify the highest-burden tasks, the places where skilled time is being spent on work AI can accelerate, and the organizational readiness to adopt what we build. We come out of this phase with a specific, ranked set of priorities.</p>
            </div>
            <div className="q-phase">
              <div className="step">Phase 02</div>
              <h4>Build</h4>
              <p>We build the tools, automations, and integrations the assessment identified. Off-the-shelf configuration where the standard tools serve the workflow. Custom development where they don't. The same team that did the assessment does the building — no translation loss in the handoff.</p>
            </div>
            <div className="q-phase">
              <div className="step">Phase 03</div>
              <h4>Train</h4>
              <p>Role-specific training for the people who will actually use the tools, on the specific workflows that changed. We measure adoption, not attendance — and we stay close enough after launch to catch the places where behavior hasn't changed and understand why.</p>
            </div>
            <div className="q-phase">
              <div className="step">Phase 04</div>
              <h4>Expand</h4>
              <p>Once the first workflows are running and the adoption is real, we identify what's next. Many of our business relationships grow into ongoing partnerships — because businesses that move on one set of workflows find the appetite for the next ones.</p>
            </div>
          </div>
        </div>
      </section>

      <section className="q-offer">
        <div className="q-wrap">
          <div className="q-section-head" style={{ marginBottom: 40 }}>
            <div className="q-eyebrow">The entry offer</div>
            <h2>Start with an <em>AI & Automation Assessment.</em></h2>
            <p>A contained first engagement. We map the workflows, identify the highest-leverage opportunities, and produce a written plan that tells you where to start, what to build, and why — whether or not we end up being the ones to build it.</p>
          </div>
          <div className="q-offer-card">
            <div>
              <div className="what">AI & Automation Assessment</div>
              <h3>A clear picture of where AI can move the needle in your operation — and a specific plan for getting there.</h3>
              <p>One to two weeks. A senior strategist and technical director working together. We interview the people doing the actual work, map the highest-burden workflows, and produce a written assessment with a specific, sequenced plan for the highest-return opportunities.</p>
              <p>Fixed price, quoted in the first conversation. Useful whether or not you continue working with us — not a loss leader for a larger engagement.</p>
            </div>
            <div>
              <dl className="q-offer-specs">
                <div><dt>Duration</dt><dd>1–2 weeks</dd></div>
                <div><dt>Team</dt><dd>Senior strategist + technical director</dd></div>
                <div><dt>Format</dt><dd>Staff interviews + workflow mapping</dd></div>
                <div><dt>Output</dt><dd>Written assessment and sequenced build plan</dd></div>
              </dl>
              <ul className="q-offer-includes">
                <li>Interviews with leadership and operational staff across functions</li>
                <li>Inventory and mapping of current workflows and tools</li>
                <li>Identification of highest-leverage AI and automation opportunities</li>
                <li>Build vs. buy assessment for each priority</li>
                <li>Written deliverable with sequenced recommendations and rationale</li>
              </ul>
              <a className="qbtn qbtn--primary">Start the conversation <Arrow /></a>
            </div>
          </div>
        </div>
      </section>

      <section className="q-faq">
        <div className="q-wrap">
          <div className="q-section-head" style={{ marginBottom: 24 }}>
            <div className="q-eyebrow">What clients usually ask</div>
            <h2>Common questions.</h2>
          </div>
          <div className="q-faq-list">
            {[
              { q: 'How quickly will we see results?', a: 'Faster than most engagements promise. The first measurable changes — workflows that are visibly faster, staff time visibly freed — typically happen within the first engagement. We design for early wins deliberately, because early wins drive the adoption that makes everything else possible.' },
              { q: 'Our operation is specialized. How do you get up to speed on how we actually work?', a: 'We learn it before we recommend anything. The assessment phase is specifically designed to get us to a real understanding of the workflows — not just what the org chart says happens, but what the people doing the work say actually happens. Specialized operations require that investment. We make it.' },
              { q: 'We\'ve tried AI tools before and the team didn\'t use them. How is this different?', a: 'The tools your team didn\'t use were probably deployed before the workflow was mapped, on generic use cases that didn\'t fit the specific work. We build for the exact workflow, train on the exact change, and measure adoption after deployment rather than calling it done at launch.' },
              { q: 'Do you have experience in our specific industry?', a: 'We\'ve worked across a range of industries — auction, architecture, manufacturing, construction — and the workflow analysis skills transfer. We don\'t claim sector expertise we don\'t have. What we do have is the ability to learn an operation quickly and identify where the AI opportunity actually is, versus where it\'s theoretically interesting.' },
              { q: 'We\'re a large organization building internal AI capability. Is this relevant to us?', a: 'Yes, in different ways. For larger organizations, we can serve as an external partner for specific workflow or tooling challenges that internal teams don\'t have the bandwidth or expertise to tackle, or as an accelerant for building the internal capability itself. Tell us where you are and we\'ll tell you honestly where we fit.' },
            ].map((f, i) => (
              <div className="q-faq-item" key={i}>
                <div className="q">{f.q}</div>
                <div className="a">{f.a}</div>
              </div>
            ))}
          </div>
        </div>
      </section>

      <section className="q-svc-cta">
        <div className="q-wrap">
          <div className="q-svc-cta-inner">
            <div>
              <div className="q-eyebrow q-eyebrow--dark">Next step</div>
              <h2>Tell us what you are <em>trying to change.</em></h2>
            </div>
            <div>
              <p>A first conversation is twenty minutes, specific, and free. If an AI & Automation Assessment is the right next step, we scope it in writing before you commit to anything.</p>
              <div style={{ marginTop: 24, display: 'flex', gap: 14, flexWrap: 'wrap' }}>
                <a className="qbtn qbtn--paper" href="mailto:info@quarterdeck.io">Email info@quarterdeck.io <Arrow /></a>
                <a className="qbtn qbtn--outline-dark" onClick={() => setRoute('business')}>Back to Business <Arrow /></a>
              </div>
            </div>
          </div>
        </div>
      </section>

      <SiteFooter setRoute={setRoute} />
    </div>
  );
}

Object.assign(window, { BusinessAIPage });