Skip to main content

Optional fractional seat

AI Enablement Lead

Defines, role by role, what "AI-enabled" means in the actual workflow, builds the first working versions and measures whether anyone uses them.

If you hired for this full time

You would post for

  • Director, AI Enablement
  • AI Transformation Director
  • Head of Business Technology

The job usually covers

  • Define, role by role, what "AI-enabled" means in the actual workflow
  • Build the first versions of the skills, agents and workflows personally
  • Keep a governed library with owners, versions, test cases and retirement
  • Own adoption: active users, repeat use, workflow coverage, time to first value
  • Turn governance, security and legal requirements into rules people can follow
  • Make build, buy or partner calls on tools
  • Keep a register of what has been built so teams reuse instead of repeating
  • Run a champion network inside the business

What we take on

We own

  • Workflow discovery with each team
  • First builds of skills, agents and workflows
  • The internal MCP layer and control plane over your existing systems
  • The skill and tool library, with owners and tests
  • The adoption report, measured from usage and not from surveys
  • The reuse register

We contribute, you decide

  • Which roles go first
  • Tool selection
  • Governance rules in plain language
  • Training plan

Stays with you

  • Policy, legal and security decisions
  • Budget
  • People management
  • Who is in the champion network

Training is a delivery channel. The product is a working tool someone uses on real data, so this seat builds. Policy and budget stay with you because they outlast us.

What we need access to, and why

  • Your AI workspace admin (Claude, ChatGPT or both)

    Skills, projects and connectors are managed there, and so is usage data

  • The systems each workflow touches, read first

    A skill grounded in the wrong number is worse than no skill

  • Identity provider groups, read

    Tools are assigned by role

  • Time with the people who do the work

    The workflow is in their heads, not in a document

  • Your security contact

    Every new data path is cleared before it’s used

  • Usage and cost reporting

    Adoption and spend are reported together

How you’ll know it’s working

  • Weekly active users of what we built
  • Repeat use
  • Workflows covered per role
  • Time from request to first working version
  • Tools retired

The first 30 days

  1. Interview three roles and pick one workflow each
  2. Ship a first version of each on real data
  3. Stand up the library and the adoption report
  4. Write the one-page rules for what may and may not be connected

The same seat in each lane

Grow

Partner, sales and success teams using the agent tooling.

The Grow lane

Transform

Product and engineering teams adopting agent-assisted development.

The Transform lane

Run

Every team: role by role, workflow by workflow.

The Run lane

How we join

  • Alongside

    When
    Someone owns the function and is stretched thin.
    What we do
    We take the operational half. They keep strategy and relationships.
    How it ends
    Scope shrinks or grows by agreement each month.
  • Interim

    When
    The role is open or not approved yet.
    What we do
    We cover the seat day to day, reporting to whoever the hire will report to.
    How it ends
    Handoff documents and a warm transition to your hire.
  • Embedded

    When
    You want one accountable person without adding headcount.
    What we do
    Your email, your Slack, your onboarding. Paid through one contract.
    How it ends
    A notice period, then the same handoff as interim.

True of every seat

Behind the seat

  • One named person holds the seat and is the only face you and your partners see.
  • Our delivery team stands behind them, so a recommendation can become a shipped build.
  • Where we bring tools of our own, or set up an integration factory, they live in your repository.
  • Agents draft and the seat holder decides. Nothing reaches a partner or a customer without a person sending it.

Access rules

  • Every access request is tied to a task. If we can’t name the task, we don’t ask.
  • Named accounts only, on your single sign-on where you have it.
  • Read access first. Write access is requested per system when a task needs it.
  • Everything is revocable in one step, and the handoff checklist includes revoking it.

Rhythm

  • A weekly written update: what moved, what’s stuck, what we need from whom.
  • One standing meeting with the person who owns the function. Everything else is async.
  • A monthly review against the measures, where scope is adjusted.
  • A decision log that you own, so the reasoning outlasts us.

Guards

  • Non-exclusive. You can hire for the role at any time.
  • A notice period in both directions.
  • Handoff documents are a deliverable.
  • Your right to take the work in-house is written in, including any code in your repository.

Tell us what’s on your plate

Tell us what’s on your plate