How to Charge $500/Hour as a Support Consultant
Companies with 50 to 500 employees and no VP of Support will pay expert rates for queue audits, tool selection, and team structure. The niche is real and underserved.
A 200-person SaaS company has 6 support agents, a Zendesk account nobody has optimized since 2022, and a VP of Ops who manages support as 10% of their responsibilities. Their CSAT is declining. Their cost per ticket is rising. They know something is wrong but they don't know what.
They don't need a full-time VP of Support. They need someone to come in for a week, audit their operation, tell them what's broken, and give them a plan to fix it. They'll pay $5,000 for that engagement. Happily.
That's the support consulting niche. And almost nobody is serving it.
Why the Niche Exists
Companies between 50 and 500 employees are too big to run support informally (the founder answering emails) and too small to justify a dedicated VP of Support ($200K+ salary). They're in a gap where support is "someone's side responsibility" and the optimization is nobody's job.
These companies spend $200K to $500K per year on support (agents, tools, infrastructure) and have never had a professional review of whether that spending is effective. They chose their help desk 3 years ago based on a blog post. Their routing rules were set up by an agent who left. Their macros haven't been updated since 2023.
A consultant who can walk in, audit the operation, and deliver a 30-day improvement plan is worth $3,000 to $10,000 per engagement. At 2 engagements per month, that's $72,000 to $240,000 in annual revenue. Working 8 to 10 days per month.
The Engagement Types
The queue audit. 2 to 3 days. Export their ticket data, categorize by intent, identify the top 10 volume drivers, calculate cost per ticket, and deliver a report with specific recommendations: "Category X should be automated (saving $Y/month). Category Z needs better documentation. Your escalation rate is 2x industry average because of [specific reason]."
Tool evaluation. 1 to 2 days. The company is evaluating Zendesk vs Intercom vs Freshdesk vs Help Scout. They want someone who's used all of them to give an honest recommendation based on their specific situation. Not a blog post comparison. A recommendation tailored to their team size, ticket volume, integration needs, and budget.
Team structure design. 2 to 4 days. They're hiring their first dedicated support manager. They need a job description, an org structure, a career ladder, a QA framework, and KPI targets. Most companies copy these from Google searches. A consultant customizes them for the company's actual needs.
Process optimization. 3 to 5 days. The full audit: queue management, routing rules, escalation protocols, macro library, knowledge base, SLA design, and agent workflow. Deliver a detailed improvement plan with prioritized actions and expected ROI for each.
How to Package and Price
Day rate: $3,000 to $5,000. This is appropriate for companies with $10M+ ARR where support is a significant expense. The ROI of the engagement (typically 2x to 5x the fee in reduced support costs within 6 months) makes the price easy to justify.
Project rate: $5,000 to $15,000 depending on scope. A full queue audit with recommendations is on the lower end. A full ops review with implementation support is on the higher end.
Retainer: $2,000 to $5,000/month for ongoing advisory. The consultant does a monthly review of support metrics, attends a quarterly planning session, and is available for ad-hoc questions. This works for companies that want ongoing optimization without a full-time hire.
Where to Find Clients
LinkedIn. Write about support operations. Share specific insights (not vague thought leadership). "Companies with 6 to 10 agents typically overspend by 30% on tooling because they're using enterprise features they don't need" is a specific, useful claim that attracts the exact companies that need your help.
Referrals from support tool vendors. Zendesk, Intercom, and others have partner programs. When a customer says "I'm not getting value from your tool," the vendor sometimes refers them to a consultant rather than losing the account. These are warm leads from frustrated buyers.
Content. Blog posts, case studies (anonymized), and talks at SaaS meetups. The content strategy for a support consultant is the same as for any consulting business: demonstrate expertise publicly, attract inbound inquiries, and convert them through discovery calls.
The Skills You Need
Deep operational experience. You need to have run a support team (or been deeply embedded in one) at a company with at least 5 agents. Book knowledge isn't enough. Clients are paying for pattern recognition from hands-on experience.
Data literacy. You'll analyze ticket data, calculate cost per ticket, build ROI models, and present numbers to leadership. If you can't build a spreadsheet that shows "implementing X will save $Y/month within Z months," you can't close consulting engagements.
Tool fluency. You need working knowledge of at least 4 major help desks (Zendesk, Intercom, Freshdesk, Help Scout) and familiarity with AI tools (Supp, chatbots, automation platforms). Clients expect you to recommend specific tools with specific reasoning.
Communication. You're selling recommendations to VPs and C-suite. You need to translate operational details ("your P50 response time is 4 hours because your routing rules don't account for ticket complexity") into business language ("this response time pattern is costing you approximately 8% in preventable churn").
The Support Consulting Market
This market barely exists as a recognized category. There are CX consultancies that serve enterprise (McKinsey, KPMG). There are freelance support agents for hire. But the gap between "enterprise consulting" and "freelance agent" is huge and underserved.
A solo consultant with deep support operations experience, good data skills, and the ability to communicate with executives can build a $200K+ business working 10 days per month. The demand is there. The competition is thin. And the clients are grateful because nobody else is helping them with this specific problem.
If you're reading this and you've spent 5+ years running support teams: this might be your next career.