Fractional

Engagement Models

Two different capabilities — not two options for the same thing.

These aren't alternatives you pick between. Embedded is Sam's own strategy and communications judgment, delivered on an ongoing basis — that judgment doesn't get handed off, and it's the whole point of the model. AI Capacity Building and Change Management is something else entirely: building your own team's capacity to run an AI-enabled operating layer, for whatever function you run. Many organizations need both, at the same time.

● Model 01

Embedded Strategy & Communications Executive

Ongoing fractional retainer

Place Fractional functions as your organization's Chief Strategy & Communications Officer, on an ongoing basis — setting narrative and advocacy strategy, running government and coalition engagement, and producing the collateral a full department would, at a fraction of the cost and with none of the hiring risk. It runs on the same AI-enabled operating layer described on How This Works, but the tooling isn't the value here — the fractional strategist's judgment is. This is the model currently running at APAP.

What this draws on

  • Advocacy infrastructure & government affairs
  • Program & platform architecture
  • Executive narrative & thought leadership
  • Corporate & philanthropic partnership architecture
  • Board & governance advisory

Every one of these still runs through the same AI-enabled operating layer — full department capability, at a fraction of the overhead.

Scoped and priced by which of these you actually engage — not a flat package.

See it running at APAP →

● Model 02

AI Capacity Building and Change Management

Four-stage AI adoption engagement

Not comms. Not strategy — that stays exclusive to Embedded, because it's judgment that can't be handed off. This is a different capability: implementing Place Fractional's AI-enabled operating layer inside your own organization, for whatever function you run — programs, operations, finance, anything — so your team builds the capacity to work this way itself, rather than watching it get done for them.

  1. 01

    Assess

    A full read of where AI could actually help your team — and where it can’t. Current workflows, tooling, staff readiness, and the gaps actually worth closing.

  2. 02

    Design

    The AI-enabled workflow gets architected for your function, whatever it is — tool selection, process design, and the guardrails that keep it trustworthy.

  3. 03

    Implement

    Tools get configured and staff get trained hands-on, working the system alongside your team until it’s second nature, not a one-time demo.

  4. 04

    Sustain

    The documentation, ownership, and internal practice that keep the system running and improving long after the engagement ends.

What this draws on

  • Notion — single source of truth
  • Claude — synthesis & drafting
  • Claude Code — build & deployment
  • Fireflies.AI — capture & intelligence
  • Gamma — production
See the operating layer this is built on →

● Next

Need one, the other, or both?

Every engagement starts with a conversation about your terrain, not a sales pitch about ours.

Start a Conversation