// Foundations Segment Page

function FoundationsPage({ setRoute }) {
  return (
    <div data-screen-label="07 Foundations">
      <section className="q-svc-hero2" style={{ padding: '0 0 120px' }}>
        <SiteNav route="foundations" setRoute={setRoute} theme="dark" />
        <div className="q-wrap q-svc-hero2-inner" style={{ paddingTop: 120 }}>
          <div className="q-eyebrow q-eyebrow--dark">Foundations</div>
          <h1>For foundation leaders <em>navigating change.</em></h1>
          <p className="lede">
            Independent and community foundations tend to face the same cluster of problems at once: strategy questions the board is pushing on, operational complexity that has outpaced the team, and technology questions that nobody feels equipped to tackle. We work across all of it.
          </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>Independent and community foundations, $100M+ in assets</dd></div>
            <div><dt>Common entry</dt><dd>Initial conversation and assessment</dd></div>
            <div><dt>Who leads</dt><dd>Partner-led, with deep foundation sector experience</dd></div>
          </dl>
        </div>
      </section>

      <section className="q-situation">
        <div className="q-wrap">
          <ChatAnimation questions={[
            "Our board asked about AI at the last meeting and I wasn't sure what to tell them.",
            "We've been taking the same approach for the last five years. I feel like we are out of fresh ideas.",
            "Our team is using ChatGPT though I'm not sure for what. Is that going to be a problem?",
            "We spend so much time on admin, it's become a huge problem. Is this normal?",
            "Our team is completely underwater on grant review. Is there anything we can do to help them?"
          ]} />
          <div className="q-situation-grid">
            <div>
              <div className="q-eyebrow">The situation</div>
            </div>
            <div>
              <p><strong>The strategic questions are getting harder.</strong> Foundations are rethinking what they're for, how they operate, and where they stand on things they didn't have to have a position on five years ago. Those conversations usually need a thinking partner who isn't already embedded in a point of view.</p>
              <p><strong>Operations have outpaced the team.</strong> Grant volume, reporting requirements, stakeholder relationships — the operational load at most foundations has grown faster than staff capacity. The answer is rarely more people; it's usually better systems and clearer workflows.</p>
              <p><strong>Technology decisions in an AI era carry a different kind of weight.</strong> The right investments don't just reduce friction. AI tools built into real workflows, data infrastructure that sharpens grantmaking, systems that free senior staff for the work that matters. Done well, they change what an organization is capable of. Foundations building this kind of operational leverage are pulling ahead of those still treating technology as an IT problem. That gap is real, and it's widening.</p>
            </div>
          </div>
        </div>
      </section>

      <section className="q-foundations-quote">
        <div className="q-wrap">
          <div className="q-foundations-quote-inner">
            <img src="assets/team/amanda.jpg" alt="Amanda Rinderle" className="q-foundations-quote-photo" />
            <div>
              <blockquote className="q-foundations-quote-text">
                "I spent years at FSG working with foundations on the hardest strategic questions they faced. The questions have only gotten harder. The organizations navigating them well haven't just embraced the complexity. They've invested in the operational and technical capacity to actually deliver on it. The daylight between those foundations and the ones falling behind is growing larger."
              </blockquote>
              <div className="q-foundations-quote-attr">
                <span className="name">Amanda Rinderle</span>
                <span className="role">Managing Partner</span>
              </div>
            </div>
          </div>
        </div>
      </section>

      <section className="q-entry-states">
        <div className="q-wrap">
          <div className="q-section-head">
            <div className="q-eyebrow">What we do for foundations</div>
            <h2>Three practice areas, <em>one team.</em></h2>
            <p>Most engagements touch more than one of these. The same team works across all three, which means the strategy informs what gets built, and what gets built sharpens the strategy.</p>
          </div>
          <div className="q-entry-list">
            <div className="q-entry-item" style={{ cursor: 'pointer' }} onClick={() => setRoute('foundations-ai')}>
              <div className="q-entry-num">01</div>
              <div className="q-entry-title">
                <span className="label">AI Adoption</span>
                From informal use to intentional, coordinated practice.
                <span className="q-entry-arrow"><Arrow /></span>
              </div>
              <div className="q-entry-body">
                <p>Most foundation staff are already using AI tools on their own. The question is how to move from individual experimentation to shared practice: the right tools, in the right workflows, with a governance framework the board can actually stand behind.</p>
                <p>We work with the people doing the actual work: program officers, grants managers, communications staff, operations. We build what the assessment identifies, with the same team, end to end.</p>
              </div>
            </div>

            <div className="q-entry-item" style={{ cursor: 'pointer' }} onClick={() => setRoute('foundations-strategy')}>
              <div className="q-entry-num">02</div>
              <div className="q-entry-title">
                <span className="label">Strategy</span>
                Senior counsel for the questions that don't fit neatly into a board deck.
                <span className="q-entry-arrow"><Arrow /></span>
              </div>
              <div className="q-entry-body">
                <p>Foundations come to us when the strategic questions have gotten complicated: positioning reviews, program strategy, organizational direction during leadership transitions, and the multi-stakeholder decisions that don't have an obvious right answer.</p>
                <p>We bring outside perspective and a track record in the sector, and we write the kind of memos that hold up in the room rather than on the shelf.</p>
              </div>
            </div>

            <div className="q-entry-item" style={{ cursor: 'pointer' }} onClick={() => setRoute('foundations-technology')}>
              <div className="q-entry-num">03</div>
              <div className="q-entry-title">
                <span className="label">Technology</span>
                Systems and infrastructure for foundations ready to build.
                <span className="q-entry-arrow"><Arrow /></span>
              </div>
              <div className="q-entry-body">
                <p>Data infrastructure, grants management systems, custom internal tooling, workflow automation. Foundations often have a richer operational picture than they realize, and better systems for working with it can sharpen strategy as much as any external advisor.</p>
                <p>We build what the foundation actually needs because we've spent time understanding how it operates before anything gets designed.</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 engage</div>
            <h2>A thoughtful first step, <em>then the work that follows.</em></h2>
            <p>Almost every foundation engagement begins with an Initial Evaluation: interviews with key staff, an honest read on where the priorities are, and a clear written plan. Most foundation leaders find it produces a document they can actually use with their board. From there, we scope implementation at whatever pace the organization can absorb.</p>
          </div>
          <div className="q-process-phases">
            <div className="q-phase">
              <div className="step">Step 01</div>
              <h4>Listen first</h4>
              <p>Interviews with program, grants, communications, and operations staff, and often a board conversation. We learn how the foundation actually works before we suggest anything.</p>
            </div>
            <div className="q-phase">
              <div className="step">Step 02</div>
              <h4>Assess and prioritize</h4>
              <p>A clear read on where the highest-leverage moves are and where the risks are worth managing carefully. Prioritized, not exhaustive. We cut the list to what will actually move.</p>
            </div>
            <div className="q-phase">
              <div className="step">Step 03</div>
              <h4>Deliver the work</h4>
              <p>The shape varies by engagement: a strategic recommendation the board can act on, an AI tool in real workflows, working technical infrastructure. What doesn't vary is that the same team that did the assessment delivers it.</p>
            </div>
            <div className="q-phase">
              <div className="step">Step 04</div>
              <h4>Train the team</h4>
              <p>Practical training for specific staff roles, specific workflows, specific tools. Sessions designed to change how people work, not just inform them.</p>
            </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. We'll listen before we suggest anything. If an initial evaluation is the right next step, we scope it in writing before you commit.</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, { FoundationsPage });