Services
Implementations delivered, and change management that makes them stick.
This practice pairs the delivery work of implementation management, cutover, training, and documentation with the compliance and change-management scaffolding that determines whether a rollout actually holds a year later. The outcome is a platform that is in real use, understood by the people who use it, and defensible under the regulatory frame that applies to your firm.
How we run it
Four phases, applied to this practice
Phase 1
Discovery & Audit
We baseline the current state: which regulations apply, what the firm is doing today, and where the delivery risks are. For a rollout that is already in motion, we produce a written diagnosis of why it is slipping.
Phase 2
Architecture & Design
We design the delivery plan and the change plan side by side. Milestones, owners, communications, training checkpoints, retention and data-handling policies, all in one document.
Phase 3
Build, Integrate & Automate
We run the implementation as a project with status, blockers, decisions, and cutover rehearsals, while running the change program in parallel: training cohorts, champion network, and executive communication.
Phase 4
Train, Measure & Refine
After go-live we measure adoption by usage rather than attendance, retrain where the numbers say to, and hand the platform over to a named internal owner with a documented operations manual.
What this looks like in practice
Recent work and field notes
Delivery and change work in the field: implementations, migrations, and compliance programs that landed and held.
We're writing more on this practice area. In the meantime, browse the blog.
Engagement models
How this work is scoped
Model
Project Delivery
The natural fit. A scoped implementation, migration, or compliance program with defined milestones.
Model
Audit & Roadmap
For rollouts already slipping. A straight read on why and what to change, delivered in two weeks.
Model
Fractional Leadership
For firms carrying a rolling portfolio of implementations, ongoing oversight prevents the same failure twice.
FAQ
Questions we answer often
Are you compliance consultants or lawyers?
Neither. We are technologists who ship compliance-adjacent implementations: HIPAA-aware M365 tenancy, CCPA-aware data retention, records-retention automation. Legal opinions come from your counsel; we translate their guidance into the systems that enforce it.
How do you keep an implementation from stalling three-quarters of the way through?
By setting the cutover date, the owner, and the rollback plan on day one, then holding a weekly executive checkpoint with three numbers and one decision. In our experience a rollout stalls when the decision cadence stops, so we keep it moving.
What does 'change management' mean in a small or mid-sized firm?
It means a named champion in each team, a short training cadence, one page of visible executive support, and honest measurement of usage after go-live. It is a discipline, not a piece of software.
Can you take over an implementation that is already in motion?
Yes. We start with a two-week diagnostic covering what has shipped, what has not, and where the blockers are, then produce a rewritten plan with a defensible new date. Sometimes the answer is to descope; we say so.
How do you handle records retention and data disposal?
As policy first, then automation. We codify the retention schedule with counsel, then implement it in the storage and case-management layers so retention is not a manual quarterly project.
Considering this work for your firm?
Drew replies personally within three business days.