You set the pace. L5 runs the Drives.

After go-live, L5's forward deployed team keeps working inside your Zendesk platform. A Drive is one week of work that ends in a change in production, and you choose how often Drives run.

How every Drive runs

One week of delivery

  1. Discover

    Priorities set, Drive scoped, dependencies confirmed.

  2. Realize

    Drive output built and moved to production.

  3. Iterate

    Changes tested, performance compared to baseline.

  4. Validate

    Outcome verified live, metrics updated.

  5. Enable

    Change adopted, next priorities set, scorecard updated.

What L5 Operate includes

L5 Operate is an annual plan in which L5 runs your Zendesk platform as a sequence of Drives. A Drive is one week of delivery that ends in a production release or a production change, with Drives defined before work begins. Your plan sets how many Drives run each year.

  1. Drives

    One week of delivery, scoped with your team and approved before work begins.

    What L5 does
    • Build and tune Zendesk AI agents and intent training
    • Configure routing, SLAs, triggers, and Explore dashboards
    • Deliver integrations and apps on the Zendesk Apps Framework
    The benefit
    Every Drive ends with a change in production, measured against your baseline.
  2. Roadmap Sessions

    Architect-led working sessions that review results and set the next Drives.

    What L5 does
    • Review outcomes against your starting baseline
    • Reprioritize the backlog with your stakeholders
    • Approve the next Drives
    The benefit
    The roadmap moves with the business, and both teams approve the next Drives.
  3. Operate Scorecard

    A status report delivered on the same cadence as your Drives.

    What L5 does
    • Drives completed, accepted, and in progress
    • Production changes and performance against baseline
    • Drives remaining and roadmap updates
    The benefit
    Your leadership sees what the platform and its AI are producing.
  4. Integration upkeep

    Ongoing operation of the integrations L5 delivers, scheduled inside your Drives.

    What L5 does
    • Assign each integration a tier, from a built-in connector to an older system that needs custom work
    • Schedule upkeep Drives each year for each tier
    • Keep integrations current as connected systems change
    The benefit
    Integrations stay in the plan after go-⁠live.

Choose your plan

You set the pace. Every plan runs for 12 months, and plans differ by how often L5 runs Drives and how often the roadmap is reset.

Essential

One Drive per month

Best fit

Smaller service teams, or added capacity for an established team

Committed Drives per year
12
Roadmap Sessions per year
2
Operate Scorecard
Monthly
Integration upkeep
Within committed Drives
Additional Drives
Available
Agreement
12 months

Advanced

Two Drives per month

Best fit

Mid-market teams growing AI and automation on Zendesk

Committed Drives per year
24
Roadmap Sessions per year
4
Operate Scorecard
Every two weeks
Integration upkeep
Within committed Drives
Additional Drives
Available
Agreement
12 months

Enterprise

About four Drives per month

Best fit

Multi-team service delivery that needs weekly change

Committed Drives per year
46
Roadmap Sessions per year
6
Operate Scorecard
Weekly
Integration upkeep
Within committed Drives
Additional Drives
Available
Agreement
12 months

Getting started

Start with one use case

We start with one use case in your platform and agree with you how often Drives run.

Talk to our team

Your first conversation

With our team, before the first Drive

We cover

  • How your service desk runs today
  • The first use case worth proving
  • How often Drives should run
  • The roadmap for the first Drives
The roadmap sets your first Drives.

An MSP waits for your ticket. L5 already ran the Drive.

Talk to our team