// Business · Operational Support

function BusinessSupportPage({ setRoute }) {
  return (
    <div data-screen-label="08c Business · Operational Support">
      <section className="q-svc-hero2" style={{ padding: '0 0 120px' }}>
        <SiteNav route="business-support" setRoute={setRoute} theme="dark" />
        <div className="q-wrap q-svc-hero2-inner" style={{ paddingTop: 120 }}>
          <div className="q-eyebrow q-eyebrow--dark">Business · Operational Support</div>
          <h1>A technical partner that stays — <em>not a vendor that delivers and disappears.</em></h1>
          <p className="lede">
            Some of the most valuable work we do doesn't fit a project model. For businesses that need ongoing technical leadership, senior judgment available without a full-time hire, or a partner who knows the operation well enough to catch problems before they become crises — we offer structured, ongoing engagement. The work varies week to week. The relationship doesn't.
          </p>
          <div style={{ display: 'flex', gap: 14, flexWrap: 'wrap' }}>
            <a className="qbtn qbtn--paper" href="mailto:info@quarterdeck.io">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>Growing businesses that have outgrown the project model but aren't ready to hire full-time technical leadership</dd></div>
            <div><dt>Entry point</dt><dd>A scoped conversation about what you actually need — no retainer commitment required to start</dd></div>
            <div><dt>Who leads</dt><dd>Senior strategist and technical director, consistently — not rotated staff</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>Most businesses reach a point where project-based engagements stop being enough.</strong> The systems are live. The tools are built. But the operation keeps moving — new requirements emerge, technical decisions compound, and the team that was great at launching things isn't always the right team for keeping them running well and evolving them thoughtfully. The gap between "we have someone for big projects" and "we have technical leadership on staff" is large, and it's expensive to cross before you're ready.</p>
              <p><strong>Vendors fill a transaction. Partners fill a role.</strong> The difference matters in practice: a vendor responds to what you ask for; a partner notices what you haven't thought to ask about. Businesses that want the second thing — proactive judgment, institutional knowledge that accumulates over time, someone who picks up the phone and actually knows the situation — need a relationship model, not a ticket queue.</p>
              <p><strong>The businesses we work with on retainer share a common characteristic.</strong> They are good at what they do and serious about how technology supports it. They want a senior partner who is genuinely invested in the outcome, not a managed service that measures itself by uptime. If that's what you're looking for, this is worth a conversation.</p>
            </div>
          </div>
        </div>
      </section>

      <section className="q-entry-states">
        <div className="q-wrap">
          <div className="q-section-head">
            <div className="q-eyebrow">Three shapes this takes</div>
            <h2>The work is different every week. <em>The structure isn't.</em></h2>
            <p>Ongoing support engagements look different depending on where the business is. Most of the work we do in this model fits one of these three shapes — and some clients need all three at different times.</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">Fractional technical leadership</span>
                Senior technical judgment, available without a full-time hire.
              </div>
              <div className="q-entry-body">
                <p>For businesses that need a CTO-level perspective but aren't ready to make that hire — or where the work doesn't warrant one — fractional technical leadership provides senior judgment on a structured schedule. Architecture decisions, vendor evaluations, team direction, technology strategy: the work that requires experience to do well and that accumulates in costly ways when it's done poorly or deferred.</p>
                <p>We've been in enough technical situations to know what the warning signs look like before they become crises, and to ask the questions that don't get asked when no one in the room is playing the long-term technical ownership role. That's the job. We do it alongside you, in the operation, on an ongoing basis.</p>
              </div>
            </div>

            <div className="q-entry-item">
              <div className="q-entry-num">02</div>
              <div className="q-entry-title">
                <span className="label">System stewardship and ongoing development</span>
                Systems that evolve with the business, not just survive the launch.
              </div>
              <div className="q-entry-body">
                <p>Websites, custom tools, data systems, and integrations need more than maintenance — they need someone who understands why they were built the way they were and can evolve them as the business changes. Most businesses discover this after a project ends and the team that built the thing is no longer in context. We stay in context.</p>
                <p>Ongoing development retainers give you a consistent team and a consistent pace: planned work that moves the operation forward, plus the capacity to respond when something unexpected happens. The team that built the system is the team that maintains and evolves it. That continuity changes what's possible — and what's economical — over time.</p>
              </div>
            </div>

            <div className="q-entry-item">
              <div className="q-entry-num">03</div>
              <div className="q-entry-title">
                <span className="label">Strategic technical advisory</span>
                A senior partner for the decisions that compound.
              </div>
              <div className="q-entry-body">
                <p>Some businesses don't need ongoing development work — they need a senior technical partner available for the decisions that matter. New platform evaluations, AI strategy, data infrastructure direction, major vendor relationships: decisions that get made once and live with the business for years. Getting them right is worth more than the cost of the engagement. Getting them wrong is expensive in ways that aren't always immediately visible.</p>
                <p>Advisory engagements are structured around availability and regular check-ins rather than a fixed scope of deliverables. We stay close enough to the business to give useful counsel, and far enough from the day-to-day to give honest counsel. The goal is to be the person you call before you sign the contract, not after.</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 relationship works</div>
            <h2>Start right. Build rhythm. Expand over time.</h2>
            <p>Ongoing engagements require a strong foundation. We invest in getting oriented before committing to a cadence — and we structure the relationship so it gets more valuable as our understanding of the business deepens.</p>
          </div>
          <div className="q-process-phases">
            <div className="q-phase">
              <div className="step">Phase 01</div>
              <h4>Intake & orientation</h4>
              <p>Before anything is scoped, we get oriented: systems, team, current pain points, and goals. This isn't billed as a deliverable — it's the investment we make to ensure the retainer is actually useful. We come out of this phase knowing what matters and what doesn't.</p>
            </div>
            <div className="q-phase">
              <div className="step">Phase 02</div>
              <h4>Rhythm & scope</h4>
              <p>We establish a cadence that fits the operation — weekly check-ins, a standing backlog, agreed response expectations for urgent work. The scope is explicit so you know what you're getting and we know what we're accountable for. No ambiguity about what's included.</p>
            </div>
            <div className="q-phase">
              <div className="step">Phase 03</div>
              <h4>Ongoing work</h4>
              <p>The work happens. Systems get maintained and improved. Decisions get made with a senior partner in the room. Technical debt gets managed rather than accumulated. We track what we're doing and what it's producing so the value of the relationship is visible and accountable.</p>
            </div>
            <div className="q-phase">
              <div className="step">Phase 04</div>
              <h4>Quarterly review</h4>
              <p>Every quarter, we step back from the work and look at the relationship itself: what's going well, what should change, what's coming up that should be planned for. The engagement evolves as the business does. We stay honest about where we're adding value and where we're not.</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">How we start</div>
            <h2>A 90-day engagement to <em>establish the relationship.</em></h2>
            <p>We don't ask clients to commit to an open-ended retainer before we've established whether it's the right fit. A structured 90-day engagement gives both sides the time to find out — and gives us the orientation we need to be genuinely useful.</p>
          </div>
          <div className="q-offer-card">
            <div>
              <div className="what">90-Day Operational Support Engagement</div>
              <h3>A real start to a real relationship — scoped, structured, and honest about whether it's working.</h3>
              <p>Three months of structured engagement at an agreed cadence. We get oriented, establish the rhythm, do real work, and assess at the end whether an ongoing retainer makes sense for both sides. No commitment to continue beyond the 90 days — though most clients do.</p>
              <p>Fixed monthly rate, agreed in advance. Scope is explicit. Adjustments are made at the quarterly review, not in the middle of the month.</p>
            </div>
            <div>
              <dl className="q-offer-specs">
                <div><dt>Duration</dt><dd>90 days (3 months)</dd></div>
                <div><dt>Team</dt><dd>Senior strategist + technical director</dd></div>
                <div><dt>Cadence</dt><dd>Weekly check-in + standing async availability</dd></div>
                <div><dt>Output</dt><dd>Ongoing work product + quarterly written review</dd></div>
              </dl>
              <ul className="q-offer-includes">
                <li>Intake and orientation session with leadership and relevant team members</li>
                <li>Documented scope and agreed cadence before work begins</li>
                <li>Weekly standing check-in (video or async, your preference)</li>
                <li>Priority access for urgent decisions and time-sensitive questions</li>
                <li>Written quarterly review covering work delivered and relationship health</li>
              </ul>
              <a className="qbtn qbtn--primary" href="mailto:info@quarterdeck.io">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 is this different from hiring a part-time contractor?', a: 'A contractor fills a defined role and executes to spec. This is closer to a senior partner who is invested in the outcome, brings judgment to decisions you haven\'t fully formed yet, and accumulates institutional knowledge over time. The relationship compounds in a way that transaction-based work doesn\'t.' },
              { q: 'What does "fractional" actually mean in practice?', a: 'It means you get a predictable block of senior capacity on a recurring basis — typically a set number of hours per month, structured around your operation\'s needs. We\'re available on a schedule and for urgent questions between meetings. The scope defines what\'s included so there are no surprises on either side.' },
              { q: 'We have an internal technical team. Does this still make sense?', a: 'Often yes. Internal teams benefit from senior external perspective — especially on decisions with long-term consequences, where organizational dynamics can make objectivity difficult. We\'ve worked alongside internal teams productively in most of our ongoing engagements. The question is whether there\'s a gap we\'re filling, not whether the gap has to be total.' },
              { q: 'What if we need more capacity for a specific project during the engagement?', a: 'Project work is scoped and priced separately from the retainer. If something comes up that goes beyond the standing scope, we scope it explicitly and agree before it starts. The retainer isn\'t a bucket — it\'s a defined relationship. Additional work is a different conversation.' },
              { q: 'What happens after the 90 days?', a: 'We do a written review and have an honest conversation about whether an ongoing retainer makes sense. If it does, we agree the terms and continue. If it doesn\'t — if the 90 days addressed what you needed, or the fit isn\'t right — we part as well as we started. We don\'t design the 90-day engagement to manufacture dependency.' },
            ].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 need <em>to stop worrying about.</em></h2>
            </div>
            <div>
              <p>A first conversation is twenty minutes, specific, and free. We'll tell you honestly whether this model fits what you're describing — and if it does, we'll scope the 90-day engagement 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, { BusinessSupportPage });