// Non-Profits Segment Page

function NonProfitsPage({ setRoute }) {
  return (
    <div data-screen-label="10 Non-Profits">
      <section className="q-svc-hero2" style={{ padding: '0 0 120px' }}>
        <SiteNav route="nonprofits" setRoute={setRoute} theme="dark" />
        <div className="q-wrap q-svc-hero2-inner" style={{ paddingTop: 120 }}>
          <div className="q-eyebrow q-eyebrow--dark">Non-Profits</div>
          <h1>For nonprofits with the scale <em>to do this seriously.</em></h1>
          <p className="lede">
            Serious, operationally complex nonprofits — national in scope, substantive in program, and increasingly aware that the gap between where they are and where they should be on technology and AI is real. We work with organizations ready to close that gap with a partner who understands the sector and can actually build things.
          </p>
          <div style={{ display: 'flex', gap: 14, flexWrap: 'wrap' }}>
            <a className="qbtn qbtn--paper">Start a conversation <Arrow /></a>
          </div>
          <dl className="q-svc-hero2-meta">
            <div><dt>Typical profile</dt><dd>National or major regional scope, complex operations, dispersed staff</dd></div>
            <div><dt>Common entry</dt><dd>AI Adoption assessment or Technology engagement</dd></div>
            <div><dt>Reference clients</dt><dd>The Women's Edge and a national conservation organization</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 getting a lot of AI advice right now.</strong> Most of it is designed for smaller organizations with simpler operations. The tools being promoted and the frameworks being offered don't always translate to the complexity you're managing — dispersed staff, federated program structures, earned revenue, complex data environments, and boards and donors who are beginning to ask harder questions about efficiency and modernization.</p>
              <p><strong>At your scale, the stakes are different.</strong> An AI rollout that gets adoption wrong doesn't just waste budget — it affects programs, staff morale, and potentially the populations you serve. A digital infrastructure project that loses organizational context in the handoff between strategy and execution creates a system nobody actually uses. Getting this right matters in a way that generic consulting advice doesn't account for.</p>
              <p><strong>Leadership is usually aware they're behind.</strong> What's harder to find is a credible partner who understands the sector, can assess the situation honestly, and can actually build the things they recommend. The common alternative — a large consulting firm that hands off to implementation vendors, or a technology vendor that shapes the strategy toward its own tools — tends to produce expensive outcomes with limited adoption. We're neither of those things.</p>
            </div>
          </div>
        </div>
      </section>

      <section className="q-entry-states">
        <div className="q-wrap">
          <div className="q-section-head">
            <div className="q-eyebrow">What we work on</div>
            <h2>Three areas where complex nonprofits <em>find the most traction.</em></h2>
            <p>Most engagements start with one of these. In practice, the work often spans more than one — the same senior team handles all three.</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">AI adoption</span>
                Doing more with the team you have — without burning them out.
              </div>
              <div className="q-entry-body">
                <p>Serious nonprofits are almost always running lean. Staff carry broad responsibilities and have limited bandwidth for new initiatives, even valuable ones. AI adoption that doesn't account for this either doesn't happen or creates more work before it creates less.</p>
                <p>We design for the organization that exists — not the one with a change management budget and an internal innovation team. That means starting with the highest-burden workflows, moving carefully, and measuring by whether people's working lives actually got easier. The deliverable is adoption, not a training log.</p>
              </div>
            </div>

            <div className="q-entry-item">
              <div className="q-entry-num">02</div>
              <div className="q-entry-title">
                <span className="label">Digital infrastructure</span>
                Technology built for the complexity of mission-driven work.
              </div>
              <div className="q-entry-body">
                <p>Many nonprofits are running on a digital presence and internal tooling that reflected the right choices years ago and don't anymore. Donor-facing websites that don't reflect the organization's actual sophistication. CMS platforms that require technical staff to maintain, and therefore don't get maintained. Internal tools patched together from software that was never designed to work together.</p>
                <p>We build and rebuild digital infrastructure for complex nonprofits — websites, content systems, internal tools, and workflow integrations — with mission context built into the decisions from the start. Our work with The Women's Edge, a global women's leadership organization, is one reference: a full website and CMS rebuild designed to serve a sophisticated audience and hold up operationally over time. We also build for AI readiness — content infrastructure that can support the tools your organization will want to layer on as those capabilities develop.</p>
              </div>
            </div>

            <div className="q-entry-item">
              <div className="q-entry-num">03</div>
              <div className="q-entry-title">
                <span className="label">Strategic consulting</span>
                Thought partnership when the organization needs to make a real choice.
              </div>
              <div className="q-entry-body">
                <p>Not every strategic need fits a scheduled five-year planning cycle. The moments that matter most often arrive faster than that — a leadership transition, a funding model that isn't working, a program expansion with unclear organizational implications, a board asking harder questions than the organization has answers for. These moments require clear thinking from outside, and they don't always wait for the next planning season.</p>
                <p>Amanda Rinderle, our Managing Partner, has done this kind of strategic consulting with complex organizations across the nonprofit-adjacent sector — foundations, academic centers, and mission-driven institutions operating in similar governance environments. The work is scoped to the actual question, produced in writing, and designed to be useful whether or not we end up being the ones to execute what follows. Nimble, specific, and priced to reflect what a contained engagement actually costs.</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 we typically engage</div>
            <h2>Scoped to the actual question. <em>Built by the same team end to end.</em></h2>
            <p>We scope to fit the organization's capacity and timeline, not the other way around. The same people who assess the situation are the ones who build the answer.</p>
          </div>
          <div className="q-process-phases">
            <div className="q-phase">
              <div className="step">Step 01</div>
              <h4>Understand the operation</h4>
              <p>We learn how the organization actually works — not just the org chart but the real workflows, the staff capacity, the change readiness, and where the friction actually lives. We ask the questions a generalist wouldn't think to ask.</p>
            </div>
            <div className="q-phase">
              <div className="step">Step 02</div>
              <h4>Identify the right entry point</h4>
              <p>Not everything is the right place to start. We identify the highest-leverage opportunity given what the organization can actually absorb — and we're honest when the timing isn't right or the scope we'd recommend isn't what's being asked for.</p>
            </div>
            <div className="q-phase">
              <div className="step">Step 03</div>
              <h4>Build and implement</h4>
              <p>Same team, end to end. Whether the work is AI adoption, strategic consulting, or technology infrastructure — the people who scoped it are the people who do it. No handoff, no translation loss.</p>
            </div>
            <div className="q-phase">
              <div className="step">Step 04</div>
              <h4>Leave capacity behind</h4>
              <p>We design for the organization to be less dependent on us, not more. Training, documentation, and knowledge transfer are part of every engagement — not add-ons you negotiate for at the end.</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">Where to start</div>
            <h2>A contained first engagement — <em>specific and priced in the first conversation.</em></h2>
            <p>We start with an assessment scoped to the actual question — whether that's AI adoption, technology infrastructure, or a strategic challenge. Both the scope and the price are set in writing before you commit to anything.</p>
          </div>
          <div className="q-offer-card">
            <div>
              <div className="what">Initial Assessment</div>
              <h3>A clear picture of the opportunity and an honest read on the path forward.</h3>
              <p>Two to four weeks. A senior strategist and, where the work calls for it, a senior technical partner. We interview the people doing the actual work, review the current state honestly, and produce a written deliverable your board or leadership team can read and act on.</p>
              <p>We quote these engagements in the first conversation — a fixed price for a scoped deliverable, not a range that becomes the high end. We don't use the initial engagement as a loss leader for a larger project. The assessment stands on its own.</p>
            </div>
            <div>
              <dl className="q-offer-specs">
                <div><dt>Duration</dt><dd>2–4 weeks</dd></div>
                <div><dt>Team</dt><dd>Senior strategist + technical partner as needed</dd></div>
                <div><dt>Format</dt><dd>Staff interviews + written assessment</dd></div>
                <div><dt>Output</dt><dd>Prioritized recommendations, board-ready</dd></div>
              </dl>
              <ul className="q-offer-includes">
                <li>Interviews with leadership and operational staff</li>
                <li>Review of existing tools, workflows, and data systems</li>
                <li>Honest assessment of organizational readiness and risk</li>
                <li>Prioritized recommendations with clear rationale and sequencing</li>
                <li>Written deliverable your board can read and act on</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: 'How do you price your work for nonprofits?', a: 'Transparently and in the first conversation. We quote a fixed price for scoped engagements — not an hourly rate that grows, not a range that turns into the high end. We scope to fit the organization\'s actual capacity and budget, which means we sometimes recommend a more contained entry point than what\'s being asked for. That\'s a feature, not a limitation.' },
              { q: 'We\'re worried about staff bandwidth. How do you run engagements that don\'t overload the team?', a: 'We design for this from the start. Engagements that require heavy staff participation either move slowly or create resentment. We structure the work to get what we need efficiently and respect that the people we\'re interviewing have jobs to do that aren\'t this project. The organizations that work best with us have enough organizational capacity to engage thoughtfully — not a large change management team, but leadership with the bandwidth to be real partners.' },
              { q: 'Our board has questions about AI that we can\'t fully answer. Can you help us prepare for those conversations?', a: 'Yes. Board-ready deliverables — written, clear, and honest about what\'s actually possible — are a regular part of what we produce. We\'re comfortable helping leadership prepare for board AI conversations, and we know what the board is likely to ask because we\'ve been in those rooms.' },
              { q: 'We\'ve had consultants before who handed us a plan we couldn\'t execute. What\'s different here?', a: 'We build and implement. The same people who think through the problem are the people who execute the answer — so there\'s no version of our recommendation that assumes a team or budget that doesn\'t exist. And we don\'t design deliverables that require us to be hired again to make them useful.' },
              { q: 'Is strategy consulting available separately from the technology work?', a: 'Yes. Some engagements are purely strategic — a specific organizational question that needs clear thinking and a written answer, scoped and priced for what that actually requires. Amanda Rinderle leads this work. It doesn\'t have to be tied to a technology project.' },
              { q: 'Are you a fit for smaller organizations?', a: 'Probably not, or not yet. We work best with organizations that have real operational complexity — typically national or major regional scope, meaningful staff infrastructure, and the resources to do this work seriously. If you\'re earlier-stage or smaller, we\'ll say so in the first conversation, and we may be able to point you somewhere more appropriate.' },
            ].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 about <em>your organization.</em></h2>
            </div>
            <div>
              <p>A first conversation is twenty minutes, specific, and free. We'll ask honest questions about your operation, your capacity, and what you're trying to figure out. If we're a fit, we'll scope something 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('home')}>Back to home <Arrow /></a>
              </div>
            </div>
          </div>
        </div>
      </section>

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

Object.assign(window, { NonProfitsPage });