Support operations · Automation · AI

Your support team is growing faster than your revenue.

I find where your support operation loses time and money, then fix it with the right mix of process, automation, integrations and AI. Results are measured in the numbers leadership already watches: cost per contact, service levels, customer satisfaction and backlog.

For support and customer experience teams of 20 to 200 people, in house or outsourced.

The problem

Most support cost hides in work nobody measured.

Volume grows, so you hire. Costs grow with it, service levels still slip, and nobody can say exactly where the time goes.

Repeat contacts nobody traced

Customers ask the same questions again and again because the cause, in the product, a policy or billing, never gets fixed.

Manual work between systems

Agents copy details between the helpdesk, CRM (customer relationship management), billing and spreadsheets on every ticket.

Reports that arrive too late

Service level agreement (SLA) breaches show up at the end of the week, in reports someone built by hand.

Tools switched on, not paying off

Self-service, macros, chatbots or AI features were bought, but nobody owns whether they actually take work off the team.

What I use to fix it

Four tools, used where they pay off.

I pick each fix by what it will do to your numbers. Often that includes AI; sometimes a process change or an integration does more.

Process and self-service

Fix the causes of repeat contacts, and give customers answers they can find on their own.

Automation and integrations

Remove copy-and-paste work between the helpdesk, CRM, billing and your other systems.

AI agents and agent assist

Put AI on the contacts it handles well: answering common questions, drafting replies, summarising tickets. Tested before it goes live, with clean handoffs to your people.

Real-time reporting

Live SLA, backlog and cost-per-contact views, so problems show up the same day instead of the end of the week.

Who you would work with

I have run support operations, and I build the systems behind them.

Most consultants know either the operation or the technology. I spent years on the operations floor before I became an engineer, so I start from your service levels, staffing and cost, not from a tool.

  • Ran BPO support operations at Bell Canada, first leading 176 agents, then directing 900+ across several lines of business.
  • Raised SLA attainment 15%, replaced lagging reports with real-time KPI dashboards and redesigned staffing to cut overtime.
  • Senior cloud engineer building automation, integrations and infrastructure on AWS; AWS Certified Solutions Architect.
  • Builds and tests AI systems (retrieval, evaluation, agents) in personal projects; AWS Certified Generative AI Developer, Professional, in progress.
How it works

Find the waste, fix it, then keep it fixed.

Every engagement is fixed scope and fixed fee. The diagnostic fee is credited against the sprint if you continue within 30 days.

Step 1

Support Operations Diagnostic

2 weeks

I analyse 90 days of your tickets, workflows and reports, and show you where time and money go and what to fix first.

  • Contact drivers mapped, with volume and cost
  • Manual work and handoffs mapped
  • Fixes ranked by value: process, self-service, automation, AI
  • Reporting and visibility gaps
  • Cost-per-contact business case and 90-day roadmap
$2,500Founding client price (standard from $4,000)

See a sample diagnostic report

Step 3

Ongoing optimisation

Monthly, 3-month minimum

Products, policies and volumes change. I keep the operation tuned as they do.

  • Monthly review of contact drivers and SLA
  • New automations and fixes each month
  • Staffing and forecasting support
  • Monthly metrics report and review call
From $2,500 / monthFounding client price (standard from $3,500)

Founding prices apply to my first three clients, in exchange for a short case study and a reference. Prices in US dollars.

Proof

Results from my professional roles.

Operations results show I understand the business you run. Engineering results show I can build what it needs.

+15%
SLA attainment
Bell Canada · support operations
900+
BPO agents directed
Bell Canada · support operations
−30%
Failed deployments
Bell Media · automation
−20%
Compute cost
CallTek · cloud engineering
I am new to consulting under my own name, so I will not show you invented client logos or results. What you get instead is my operations track record, a working method, founding pricing and a clearly defined scope. Client case studies will appear here as engagements finish.

See how I work before you hire me: a full sample diagnostic run on 26,872 public support tickets, with the code, the editable rules and a record of every decision. Also an LLMOps reference platform (personal project) and more projects on the portfolio.

Fit

Is this for you?

A good fit

  • 3,000 or more support tickets a month
  • On a modern helpdesk with exportable ticket history
  • Support cost or headcount growing faster than revenue
  • You need to show a business case to a COO, CFO or founder

Not a fit

  • No ticket history, or data you cannot share
  • A one-off chatbot or website widget build
  • A goal of replacing your whole support team with software
Questions

Common questions

Which helpdesks is this for?

Zendesk, Intercom, Freshdesk, Gorgias and Salesforce Service Cloud. If you use something else, ask; the method works on any system that can export ticket history.

Where does AI fit?

Wherever it pays off. AI is often one of the biggest levers, for example answering common questions, drafting replies or summarising tickets for agents. I set it up alongside the process, content and integration fixes it depends on, test it before customers see it, and measure it like any other change.

Will this mean cutting my team?

The goal is to handle growth without headcount growing at the same rate, and to give your people better work. Most teams redeploy time rather than cut roles.

Do you need my engineering team?

Not for the diagnostic. For integrations, for example checking an order or updating an account from the helpdesk, I need an engineering contact and API access, and I build them myself.

What access do you need?

A ticket export and your current reports for the diagnostic, plus read access to your helpdesk. For the sprint, admin access to the helpdesk and help centre, with your approval on changes.

How is my data handled?

I work from exports or read-only access, remove personal details before analysis wherever possible, sign a non-disclosure agreement (NDA) on request, and delete your data when the engagement ends.

Can you guarantee results?

Not before I have seen your data. After the diagnostic, I agree specific targets with you for the sprint and report against your baseline every week.

Find out where your support operation loses time and money.

Book a 20-minute call, or email me your monthly ticket volume and helpdesk. I reply within 48 hours and tell you honestly whether I can help.