Typical scope

Every adoption engagement is custom-scoped. The shape below is what a typical engagement looks like — usually 6–10 weeks, with one sub-team. We adjust phasing, length, and depth based on what your team needs.

  1. Phase 1 · Workflow auditInterviews and observation with one chosen sub-team — contracts, employment, IP, privacy, litigation, or whichever group you pick. We deliver a written summary of the highest-leverage AI opportunities for their work, ranked by impact and ease.
  2. Phase 2 · Custom playbooksDocumented workflows with prompts, tool configs, verification steps, and decision points. Written for your team's actual matters — not generic templates.
  3. Phase 3 · Weekly coachingWorking sessions with the team each week. We work on live matters, refine the playbooks based on real use, and answer the questions that only come up when people start applying things.
  4. Phase 4 · Sustaining-the-practice handoffWho owns what. What to watch for. When the team should come back for the next engagement. A written practice document the team owns going forward.

Common workflows we embed in

What gets locked in depends on the sub-team. Common examples:

Contracts: playbook creation and redlining

Building out your negotiating playbooks. First-pass markup of incoming contracts against those playbooks. Issue spotting, key-term extraction, deviation flagging. Where the team can lean on the AI and where to double-check.

Legal knowledge management

Making your team's institutional knowledge searchable. Templates, prior matters, internal memos — pulled into a structure your lawyers can query in natural language.

Document and brief synthesis

Summarizing long documents, pulling key dates and obligations, drafting first-pass memos. Where AI is genuinely good and the verification step is cheap.

Matter intake and triage

Structured intake from emails or forms, initial classification, routing to the right person. The first 15 minutes of a matter, automated.

Outside counsel management

Reading status updates, flagging anomalies in invoices, summarizing matter reports. Reducing the time partners spend reading versus deciding.

Policy and rollout design

If your team doesn't have an AI use policy yet, we draft one with you. If you do, we make it usable. Either way, we design the rollout so adoption doesn't fade after week three.

Best for

How this fits with the training

Most teams who book this engagement have already done our Custom AI Training Program, or a similar training from another consultancy. The training establishes literacy and gives everyone shared language. The Workflow Adoption Engagement is where that literacy turns into actual practice on real matters. Some teams book both together as a combined engagement.

Ready to scope an adoption engagement?

Book a 30-minute call. We'll talk through which sub-team to start with, what workflows would move the needle, and what an engagement would look like for you.

Common questions

How is this priced?

Every engagement is custom-scoped. Pricing varies with team size, the workflows you want to lock in, and the engagement length. We confirm pricing in writing after the free 30-minute scoping call, when we have enough detail to scope the work properly.

Can we do the adoption engagement without doing the training first?

Sometimes. If your team has already had AI training from another consultancy or has self-taught their way to functional AI use, yes. If your team is starting from scratch, we'll usually recommend starting with the training so everyone has shared vocabulary before we embed.

Which sub-team should we start with?

That's exactly what the workflow audit (Weeks 1–2) is designed to answer. Common choices: contracts (high-volume repetitive work), knowledge management (cross-team value), or whichever sub-team has the most enthusiastic early adopters. We'll help you pick on the scoping call.

How many people from the team are involved?

The engagement is built around a small group — usually 4–10 people from one sub-team. The weekly coaching sessions work best with a focused group. Broader team rollouts happen in subsequent engagements.

Can this be done remotely?

Yes. Most adoption engagements are virtual — weekly sessions over video, async support in between. We can also do hybrid (kickoff and Week 8 handoff in-person, the rest remote) for Austin-area teams.

What if the workflows we want to lock in change mid-engagement?

That's normal — the workflow audit often surfaces opportunities the team didn't know to ask for. The scope is flexible within the 8-week container. If it shifts dramatically (e.g., we need to bring in a second sub-team), we'll scope an extension together.

Will we own the playbooks after the engagement?

Yes. Everything we build during the engagement — prompts, playbooks, the practice document, training materials — is yours. We're not licensing access. You can adapt, rewrite, and distribute internally however you want.

How does this compare to ongoing retainer consulting?

This is a defined-scope engagement with a clear end. We've found that legal teams adopt better when there's an actual "we're done" milestone — otherwise the practice never fully transfers to the team. If you want ongoing support after Week 8, we can discuss it, but the goal is for your team to not need us.

Ready to lock in the practice?

Book a 30-minute scoping call. We'll talk through your team, your workflows, and what an engagement would look like for you.