No one agrees on what to do about it. Not yet. The conferences, the think pieces, the LinkedIn debates are all circling the same uncomfortable question: what does an organization actually look like on the other side of this?
Here is a framing for how to approach it.
Deploying AI tools and automating individual steps is not a transformation. It's optimization at the edges. The organizations building real advantage are rethinking how work flows, who does what, and how performance is measured — then layering AI on top of a structure designed to run with it.
That requires a framework — not for the technology, but for the organizational change underneath it. Here is how we think about it.
These six pillars aren't a menu — they're a sequence. Each one enables the next. You can't augment work that isn't standardized. You can't govern AI Workers without visibility. You can't right-size the org before you know what the augmented state looks like.
Not all six are always needed. The diagnostic determines the priority and the right entry point for your organization.
A transformation that depends on the consultant staying is not a transformation — it's a dependency. Every engagement is designed with sustainability in mind: the right ownership model for the AI Workers you deploy, and the right skills embedded in your team so they can keep building without us.
We build AI Workers on low-code platforms — primarily the Microsoft ecosystem — so they're accessible, auditable, and maintainable by teams that don't have deep engineering backgrounds. What happens after deployment is a choice, not a constraint.
All three models are built on the Microsoft ecosystem — Power Automate, Dataverse, Azure AI — so your existing IT team can always look under the hood, regardless of who owns the maintenance.
The second technical capability isn't about maintaining systems — it's about changing how your people think when they encounter a problem. The goal is a team that reaches for AI tools the way they currently reach for Excel: instinctively, practically, without needing to call anyone.
The goal isn't to turn your team into developers. It's to give them enough capability that they can solve their own problems — and know when to call us for the harder ones.
Sterling North isn't a client case study. It's a firm designed from day one to operate the way we believe organizations will need to in five years. Every system, every process, every tool reflects a deliberate bet on the future of work — and it's running in production today.
At Sterling North, using AI isn't optional — it's how work gets done. Every team member is expected to leverage Claude to deliver more with less, and that's structural: our staffing model is built around augmented output, not headcount.
The site you're reading was designed and built using Claude — no agency, no developer, no months-long project. The AI-generated videos throughout cost a few dollars and a few hours to produce. We ship things with the same tools and mindset we deploy for clients.
Every Sterling North employee formally spends 10% of paid hours on training, learning, or developing new know-how. Not encouraged — expected. On top of that, the whole firm meets bi-weekly to share what they've learned, what broke, and where the ground is shifting. There's no shame in failing; there's an expectation of it.
Every process at Sterling North is documented using AI tools — meaning our know-how is on paper and up to date at all times. When something changes, the documentation changes with it. New team members and AI systems can both be onboarded from the same source of truth.
We've built our own internal applications to support how we work — proprietary templates, structured workflows, and tools designed around our processes rather than adapted from generic software. The technology serves the work, not the other way around.
Timesheets are automated from calendars — we always know what we're working on and when, without spending a minute filling in forms. Performance visibility is built into how we operate, not bolted on as a reporting exercise at the end of the month.
We're not describing a vision. We're describing how we work today — and what we help organizations build toward.
A chatbot here, an automation there, a pilot project that showed promise and then quietly faded. The structure underneath is exactly the same as it was five years ago — and the tools are sitting on top of it, underperforming.
The bottleneck isn't the AI.
It's the organizational infrastructure around it — the standards that don't exist, the KPIs that aren't tracked, the roles that haven't been redesigned.
A transformation doesn't start with a roadmap. It starts with understanding where your organization actually is. The diagnostic determines which pillars apply, in what order, and what quick wins build the foundation for structural change.
A structured working session to assess current state across all six pillars — where the gaps are, what's costing the most, and what the right sequence of change looks like for your organization specifically.
Before structural change, we identify and eliminate a specific high-cost constraint using an AI Solver. This builds momentum, validates the approach, and funds the next phase of the transformation.
Standards, documentation, and performance infrastructure come next. These are the enablers — without them, AI Workers drift and performance becomes unmanageable. We build the layer everything else depends on.
AI Workers deployment, org redesign, and change enablement. The organization now runs with digital capacity embedded in its structure — and a performance management system that keeps it accountable.
Full AI transformations — the kind that redesign how organizations work from the inside — are genuinely new. Anyone who tells you they've done dozens of them is overstating. What matters is whether they have the components, the operational instinct, and the judgment to navigate it with you.
Not a set of tools. A different operating model — one where human and digital capacity are both deployed deliberately, performance is visible at every level, and the organization can scale without scaling overhead.
I led AI and analytics transformation engagements at McKinsey as an Engagement Manager — at a time when that meant building serious data infrastructure and getting organizations to actually operate differently, not just buy tools. Then I built and operated a VC-backed network of tech-enabled medical clinics where I had to implement it myself, not just recommend it. I've designed the AI Workers, run the Solvers, and built the performance frameworks. Sterling North is where all of those converge into a single engagement model that addresses both the technology and the organizational infrastructure around it.
The diagnostic is a structured working session that assesses your organization across all six pillars, identifies the highest-priority opportunities, and produces a sequenced roadmap for what to do and in what order.
It's valuable regardless of whether we work together further. You leave with a clear picture of where your organization stands and a concrete plan for where to start.
Start with a 30-minute strategy call to discuss your situation and determine whether a transformation is the right fit — or whether a Solver or AI Worker addresses the immediate constraint.
Book a Strategy Call →Investment and format discussed on the strategy call. Engagements are tailored to organization size and scope.
