// Non-Profits · AI Adoption

function NonProfitsAIPage({ setRoute }) {
  return (
    <div data-screen-label="10a Non-Profits · AI Adoption">
      <section className="q-svc-hero2" style={{ padding: '0 0 120px' }}>
        <SiteNav route="nonprofits-ai" setRoute={setRoute} theme="dark" />
        <div className="q-wrap q-svc-hero2-inner" style={{ paddingTop: 120 }}>
          <div className="q-eyebrow q-eyebrow--dark">Non-Profits · AI Adoption</div>
          <h1>AI adoption designed for the way <em>your organization actually works.</em></h1>
          <p className="lede">
            Serious nonprofits don't need generic AI advice. They need a partner who understands dispersed staff, complex workflows, and the organizational dynamics of mission-driven work — and who can actually build the tools and processes that make adoption real, not just recommended.
          </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('nonprofits')}>Back to Non-Profits <Arrow /></a>
          </div>
          <dl className="q-svc-hero2-meta">
            <div><dt>Typical client</dt><dd>National or major regional nonprofits with complex operations and dispersed staff</dd></div>
            <div><dt>Entry point</dt><dd>AI Adoption Assessment — scoped, written, actionable</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 nonprofit sector is receiving a flood of AI advice right now.</strong> Most of it is calibrated for smaller, simpler organizations. The frameworks being promoted, the tools being recommended, and the training programs being sold don't account for the actual operating environment of a complex nonprofit — federated program structures, dispersed staff across geographies, compliance requirements, earned revenue alongside philanthropic income, and governance dynamics that shape what change is actually possible.</p>
              <p><strong>At your scale, the adoption problem is the real problem.</strong> The tools exist. The use cases are increasingly well understood. What's harder is getting an organization of real complexity to actually change how it works — consistently, across programs and functions and geographies, without burning out the staff who were already running lean before anyone asked them to learn something new.</p>
              <p><strong>Leadership is usually aware they're behind.</strong> The question they can't answer internally is: where do we start, what does real adoption look like for an organization like ours, and who can help us build it — not just recommend it. That's the work we do.</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 adoption question is usually <em>one of three things.</em></h2>
            <p>Where the engagement starts depends on where the organization is. Most of the nonprofit 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 and staff capacity</span>
                The administrative burden is real — AI can reduce it.
              </div>
              <div className="q-entry-body">
                <p>Donor communications, grant reporting, program documentation, knowledge management — these are the workflows that consume staff time without advancing mission. In a well-resourced nonprofit, they're also the workflows where AI can have an immediate, measurable impact on staff capacity if the implementation is done with the actual workflow in mind rather than a generic use-case list.</p>
                <p>We map the workflows first. We look for the places where AI saves real time, where adoption is feasible given the staff's current tools and skill levels, and where the benefit will be visible enough to build momentum across the organization. Then we build the tools and processes that make it happen — not a training binder, but working infrastructure.</p>
              </div>
            </div>

            <div className="q-entry-item">
              <div className="q-entry-num">02</div>
              <div className="q-entry-title">
                <span className="label">Training and organizational readiness</span>
                Building AI literacy that actually changes how people work.
              </div>
              <div className="q-entry-body">
                <p>Generic AI training produces awareness, not adoption. Staff who sit through a workshop leave knowing more about AI in the abstract and return to their workflows essentially unchanged. The training that changes behavior is specific to the role, grounded in the actual tools the organization uses, and structured around practice rather than presentation.</p>
                <p>We design and deliver AI training programs built for the organization's actual workflows and staff profile — from leadership orientation sessions that help executives ask better questions to role-specific workshops that change how program staff, communications teams, and administrative functions do their daily work. The goal is durable change, not awareness metrics.</p>
              </div>
            </div>

            <div className="q-entry-item">
              <div className="q-entry-num">03</div>
              <div className="q-entry-title">
                <span className="label">AI strategy and tool selection</span>
                Cutting through the vendor noise to find what's actually right.
              </div>
              <div className="q-entry-body">
                <p>The AI tool market is moving fast and the vendor claims are aggressive. Organizations making decisions now — about platforms, about integrations, about where to build versus where to buy — are doing so with incomplete information and real financial stakes. The wrong choices create technical debt and staff frustration that can set AI adoption back by years.</p>
                <p>We help organizations make those decisions clearly: which tools are actually ready for organizational deployment at your scale, which use cases are mature enough to invest in now versus ones to monitor, and how to build an AI infrastructure that can evolve without starting over every eighteen months. We don't sell tools and we don't have platform relationships that shape our advice.</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. Design. Build. Sustain.</h2>
            <p>The sequence is consistent. We don't recommend before we understand, and we don't hand off a document and disappear.</p>
          </div>
          <div className="q-process-phases">
            <div className="q-phase">
              <div className="step">Phase 01</div>
              <h4>Assess</h4>
              <p>Workflow mapping, staff interviews, tool inventory, and an honest read on organizational readiness. We learn the organization before we recommend anything — which workflows carry the most burden, where adoption is realistically possible, and where it isn't yet.</p>
            </div>
            <div className="q-phase">
              <div className="step">Phase 02</div>
              <h4>Design</h4>
              <p>A specific, sequenced adoption plan — not a menu of possibilities but a ranked path with rationale. Which workflows to start with, which tools to use, what training the staff actually needs, and how to measure whether adoption is happening rather than just being reported.</p>
            </div>
            <div className="q-phase">
              <div className="step">Phase 03</div>
              <h4>Build</h4>
              <p>We build the tools and infrastructure the plan requires — integrations, automations, custom AI assistants, prompt libraries, internal knowledge systems. The same team that designed the plan builds the implementation. No handoff, no translation loss.</p>
            </div>
            <div className="q-phase">
              <div className="step">Phase 04</div>
              <h4>Sustain</h4>
              <p>Adoption that depends on us isn't adoption. We train the staff, document the systems, and design for the organization to maintain and extend what we built without needing us in the room.</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 Adoption Assessment.</em></h2>
            <p>A contained first engagement. We map the workflows, assess the organization's readiness, and produce a written plan that names where to start and why — whether or not we end up being the ones to execute it.</p>
          </div>
          <div className="q-offer-card">
            <div>
              <div className="what">AI Adoption Assessment</div>
              <h3>An honest read on where AI can actually move the needle for your organization.</h3>
              <p>Two to three weeks. A senior strategist and technical director working together. We interview staff across functions, map the highest-burden workflows, and produce a written assessment with a specific, sequenced plan for where to start.</p>
              <p>We quote a fixed price in the first conversation. The assessment is useful whether or not you continue working with us — it is not designed to require a follow-on engagement to be actionable.</p>
            </div>
            <div>
              <dl className="q-offer-specs">
                <div><dt>Duration</dt><dd>2–3 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 adoption plan</dd></div>
              </dl>
              <ul className="q-offer-includes">
                <li>Interviews with leadership, program staff, and operational functions</li>
                <li>Inventory and assessment of current tools and workflows</li>
                <li>Honest read on organizational readiness and adoption risk</li>
                <li>Ranked adoption priorities with rationale for sequencing</li>
                <li>Written deliverable suitable for board or leadership presentation</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 nonprofit leaders usually ask</div>
            <h2>Common questions.</h2>
          </div>
          <div className="q-faq-list">
            {[
              { q: 'Our staff are already stretched thin. How do you run an AI adoption process without adding to their burden?', a: 'Carefully, and we design for it from the start. We structure the assessment to get what we need efficiently — not long workshops or lengthy surveys but focused conversations with the right people. And the adoption plan we produce is sequenced around staff capacity, not an ideal implementation timeline that assumes bandwidth the organization doesn\'t have.' },
              { q: 'We\'ve already done some AI training. Do we need to start over?', a: 'Probably not. We assess what\'s been done, what\'s actually stuck, and where the gaps are. Most organizations have done some awareness-building that didn\'t translate into changed workflows. We pick up from where things actually are, not where the training log says they should be.' },
              { q: 'How do you approach AI tools for organizations with strict data and compliance requirements?', a: 'Carefully and specifically. We know the difference between AI tools that can be responsibly deployed with sensitive organizational data and those that can\'t, and we make those distinctions explicit in our recommendations rather than leaving them for the IT team to figure out later.' },
              { q: 'Our board wants to understand our AI posture. Can you help us prepare for that conversation?', a: 'Yes. Board-ready materials — written, clear, and honest about both the opportunity and the risk — are a regular part of what we produce. We know what boards typically ask about AI and we know how to help leadership answer those questions credibly.' },
              { q: 'Do you have to do the implementation, or can we take the plan internally?', a: 'Either works. The assessment is designed to be actionable on its own. If we\'re the right partner for implementation, we\'ll say so. If the organization has internal capacity to execute, we\'ll structure the deliverable to support that.' },
            ].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 figure out.</em></h2>
            </div>
            <div>
              <p>A first conversation is twenty minutes, specific, and free. If an AI Adoption 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('nonprofits')}>Back to Non-Profits <Arrow /></a>
              </div>
            </div>
          </div>
        </div>
      </section>

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

Object.assign(window, { NonProfitsAIPage });