Customer Operations
Start where repeat contact reasons are stable, triage rules can be defined, and knowledge quality determines response time.
Former McKinsey Consultant • Former Senior Strategy & Operations Manager at Turo
Every company is asking how AI will change their business. Few know where to start.
11+ years leading operational transformation initiatives across McKinsey, Turo, and high-growth startups.
Experience includes
I have shipped the work, not just assessed it.
What that means in practice:
The result is fewer recommendations that sit in PowerPoint and more operational improvements that keep working after the launch.
The expensive failures are usually the ones that look routine on the surface.
AP automation collapses when exceptions live in email threads instead of a controlled workflow
Support automation disappoints when every ticket gets the same priority because triage rules are vague
Dispatch breaks when branch-level capacity data is stale and nobody owns the handoff
Reporting still depends on spreadsheet stitching because nobody trusts the source of truth
Teams buy software that leaves the manual handoff in place, so the work just moves somewhere else
Leadership knows the pain is real but cannot isolate which workflow is worth automating first
Not every workflow deserves automation. These are the ones that usually do.
Start where repeat contact reasons are stable, triage rules can be defined, and knowledge quality determines response time.
Best for invoice intake, approval routing, duplicate detection, payout controls, and any workflow with a clear audit trail.
Useful when work crosses teams, locations, or systems and the current process depends on manual handoffs or tribal knowledge.
Worth fixing when leaders cannot agree on metrics, reporting takes too long, or downstream automation needs clean data to work.
Start with repetitive labor, then layer in error reduction, avoided hires, faster cycle times, and the cost of manual handoffs.
If a workflow is high volume, rule-driven, and painful to audit by hand, it is usually a candidate. If the inputs are chaotic or the owner is undefined, it usually is not.
Request an AI Opportunity Assessment →Example ROI calculation
The same logic applies to support, dispatch, billing, intake, and vendor management.
WHY NOW
AI tools are more powerful and more accessible than ever. But the companies seeing real returns are not using more AI. They are using it in the right places.
They identify a small number of high-ROI workflows, redesign them, and implement solutions that work in the real world.
Trying to automate everything results in impact on nothing.
Automating broken workflows only makes them faster.
AI can’t deliver value when the underlying data is messy.
Without clear ROI, projects lose momentum and funding.
Getting AI right isn’t about more technology. It’s about making smarter operational decisions.
Systems I helped ship in production, not hypothetical concepts.
Challenge
Support operations had to scale without breaking service quality, reporting, or the five critical integrations underneath it.
Solution
Led migration of 1,900 users and 12 million customer cases while redesigning support workflows and the operating model around them.
Impact
Challenge
Support volume was growing faster than the team could absorb because repeat contacts were not being routed or deflected well.
Solution
Redesigned intake, routing, and automation around the reasons customers actually contacted the team.
Impact
Challenge
Invoice intake, coding, and approval routing consumed recurring finance effort and created too many places for exceptions to stall.
Solution
Designed and implemented an LLM-powered workflow integrating document extraction, approval routing, business rules, and ERP workflows.
Impact
The goal is not automation for its own sake. The goal is a workflow that is cheaper, faster, and easier to trust.
Automate repetitive work that keeps showing up every day
Better routing and self-service where the issue is obvious
Fewer invisible exceptions and fewer manual approvals buried in inboxes
Less waiting on approvals, handoffs, and report pulls
Workflows that keep working as volume increases
Week 1
Week 2
Deliverables
Start here
Most companies know AI matters. Fewer know which workflows are worth touching first.
The AI Opportunity Assessment identifies the workflows, systems, and operational bottlenecks where AI, automation, data infrastructure, or custom software can produce the highest ROI.
You leave with a practical roadmap showing where AI can reduce cost, increase capacity, improve visibility, or eliminate manual work before you commit to a full implementation.
Fixed-Fee Assessment
Includes:
Contact for pricing.
Fee credited toward implementation if we move forward.
Request an AI Opportunity AssessmentI'll respond within one business day.
About
Former McKinsey consultant with 11+ years leading operations, product, and AI transformation initiatives in environments where the workflow had to survive production, controls, and handoffs.
I help organizations redesign workflows, implement AI, and build custom software that keeps working after the first exception shows up.
The prompt is the easy part. The hard part is redesigning the workflow, connecting your systems, handling the exceptions, creating auditability, managing adoption, and measuring what changed. That is where most internal attempts stall.
Almost never. The opportunity is usually in connecting what you already have, automating the handoffs, eliminating manual steps, and making the data flow where it needs to go without a person in the middle.
QuickBooks Enterprise, NetSuite, Sage, HubSpot, Salesforce, Airtable, Google Workspace, Slack, and most common ticketing, CRM, and ERP systems. If you have an API or a webhook, there is usually a path.
Both, but the value is in implementation. The assessment surfaces the opportunity. The engagement builds and deploys it. Strategy without a working system is just a deck.
Simple workflow automation can show measurable impact in weeks. More complex systems with multiple integrations or approval workflows take longer, typically two to four months to full deployment.
Most companies are looking in the wrong places. The highest ROI is usually in the workflows that feel normal because they have been done manually for so long, no one questions them.
Request an AI Opportunity Assessment