📖 Part of the Capgemini Investigation Series — 10 articles examining Capgemini Australia's operations, employee treatment, and business practices.

The Dossier · Deep Dive · The Exodus · Survivor Stories · Financial Analysis · vs Competition · The Vulture · Invisible Workforce · AI Gamble · Series Home

The Most Expensive Rebrand in Consulting History

Capgemini spent US$3.3 billion on WNS. They call it a "transformation into a global leader in agentic AI-powered intelligent operations."

Investors aren't buying it. Neither should you.

This is the story of how Capgemini's biggest acquisition is really its biggest offshoring play — dressed up in AI buzzwords to distract from the structural reality beneath.

For the full Capgemini picture, see our Investigation, Financial Deep Dive, and Offshoring Machine.

What WNS Actually Does

WNS Holdings is a business process outsourcing (BPO) company. Their business model is simple: take repetitive business processes — data entry, customer service, finance and accounting, claims processing — and move them to lower-cost locations, primarily India.

WNS by the numbers:

• Revenue: ~US$1.2 billion annually
• Employees: ~66,000
• Primary location: India (offshore)
• Clients: 400+ companies globally
• Core services: Finance & accounting, customer service, claims processing, data management, procurement

Sources: Venture Intelligence, Capgemini Press Release

WNS isn't an AI company. It's not a technology company. It's a labour arbitrage company — a firm whose entire business model is built on the gap between Western salaries and Indian salaries.

What Capgemini Paid

US$3.3 billion. Excluding WNS's net financial debt.

At US$76.50 per share, Capgemini paid a premium over WNS's market price. The deal was financed entirely in cash — no stock swap, no earn-outs. Pure cash out the door.

What Capgemini Got

What Capgemini Didn't Get

• AI technology (WNS has no meaningful AI IP)
• Consulting capability (BPO is not consulting)
• Australian market access (WNS has minimal Australian presence)
• Defence or government relationships (WNS is private sector focused)
• Innovation or R&D capability

The AI Narrative: Marketing vs Reality

What Capgemini Says

Capgemini's press release describes the acquisition as creating "a global leader in agentic AI-powered intelligent operations" [Source: Capgemini Press Release, October 2025].

At the 2026 Capital Markets Day, CEO Aiman Ezzat reinforced the narrative: "We are entering this new phase from a position of strength. Between 2021 and 2025, we delivered on our growth ambition, significantly improved our profitability and successfully evolved from an IT services provider into a strategic business transformation partner" [Source: Capgemini India, May 2026].

The messaging is clear: WNS is about AI, transformation, and the future.

What the Numbers Show

The numbers tell a different story:

Revenue growth without WNS: Capgemini's organic revenue growth was 3.4% in constant currency for FY 2025 [Source: Capgemini FY 2025 Results]. Excluding WNS, growth was modest.

Margin decline: Operating margin fell from 10.7% to 9.8% in 2025 [Source: Capgemini FY 2025 Results]. The WNS acquisition didn't improve margins — it diluted them.

Restructuring costs: €700 million over 2026-2027, explicitly tied to workforce adaptation [Source: Capgemini FY 2025 Results]. This is the cost of integrating WNS's offshore workforce and cutting redundant onshore staff.

Stock market reaction: Capgemini shares fell 26% year-to-date as of early 2026. Morgan Stanley cut its price target to €117 [Source: Investing.com, February 2026].

If the WNS acquisition were really about AI transformation, the market would be excited. Instead, it's running for the exits.

The Real Strategy: Offshoring on Steroids

Why BPO, Not AI?

Capgemini's global workforce was already 60% offshore before the WNS deal. The acquisition took that to 66%. By December 2025, Capgemini had 277,800 offshore employees — up from 199,400 just nine months earlier [Source: Capgemini FY 2025 Results].

This isn't accidental. It's the core strategy:

1. Buy cheap labour capacity — WNS gives Capgemini 66,000 offshore workers at Indian salary rates
2. Brand it as AI — "agentic AI-powered intelligent operations" sounds better than "we hired cheaper people"
3. Sell to Western clients — who want "digital transformation" and "AI" but actually need someone to do the work
4. Collect the margin — the gap between what clients pay (Western rates) and what Capgemini pays (Indian rates) is pure profit

The Margin Game

Here's the arithmetic:

• Australian client billing rate: A$180-250/hour for senior engineers
• Australian engineer salary: A$100,000-150,000/year (A$50-75/hour equivalent)
• Indian engineer salary: A$15,000-30,000/year (A$7-15/hour equivalent)

When Capgemini replaces an Australian engineer with an Indian one, the salary cost drops by 70-80%. The client billing rate drops by 0%. The margin expands.

WNS gives Capgemini 66,000 more bodies to plug into this margin machine.

What This Means for Australian Workers

The Onshore Squeeze

With 66% of Capgemini's workforce now offshore, the structural pressure on Australian workers intensifies:

Salary suppression: When the majority of your competitors are offshore, the ceiling on Australian salaries drops. Capgemini's average salary of A$113,561 [Source: PayScale] is already 11-18% below market median. The WNS deal makes this worse, not better.

The bench grows: Capgemini maintains a pool of onshore staff for client-facing work. The WNS acquisition means fewer onshore roles are needed — more work goes offshore, fewer Australian staff are required.

Career paths narrow: When the work moves offshore, there are fewer projects, fewer promotions, and less reason to stay. The Empired, RXP, and Works experiences all followed this pattern.

Restructuring looms: The €700 million restructuring budget [Source: Capgemini FY 2025 Results] will fund redundancies — and Australian staff will be disproportionately affected.

The Glassdoor Signal

Capgemini's Australian Glassdoor rating is 4.0/5 [Source: Glassdoor]. This seems positive until you read the reviews:

• "Zero transparency around appraisals, promotions, or project changes"
• "Recent senior leadership changes have resulted in a dishonest, dehumanizing culture"
• "Too long on bench and they will quickly find a way to get rid of you"
• "The current strategy of aggressive, unmanaged offshoring has placed an untenable burden on the remaining onshore staff"

The 4.0 rating reflects a workforce that's learned to say positive things publicly while documenting their frustrations in detail. The WNS acquisition will give them more to document.

What This Means for Clients

The "AI" Upsell

Capgemini will approach clients with the WNS-enabled pitch: "We can now deliver your operations with AI-powered intelligent processes." What this actually means:

• Your work moves to India
• Some basic automation is applied
• Capgemini calls it "AI"
• You pay less per hour but receive less quality per hour
• When something goes wrong, the time zone difference means 12-hour delays

The Quality Risk

BPO is not consulting. Process execution is not strategic advice. When Capgemini moves a client's operations to WNS's Indian centres, the work gets done — but the quality, context, and judgment that onshore staff provide is lost.

The ME Bank experience illustrates this: when Capgemini offshored half the contact centre team, customers experienced hours-long wait times and were locked out of their money during app updates [Source: FSU statement].

The Security Question

WNS handles sensitive business processes — finance, accounting, customer data. Moving these offshore introduces security risks that many clients haven't adequately assessed. The Razer data breach (2020), where a Capgemini employee exposed 100,000 customers' data and Capgemini was ordered to pay US$6.5 million in damages [Source: CNA, December 2022], is a cautionary tale.

The Market's Verdict

Stock Price: Down 26%

Capgemini's stock has fallen 26% year-to-date as of early 2026 [Source: Investing.com]. Morgan Stanley cut its price target to €117, citing growth concerns [Source: Investing.com, February 2026].

Investors are pricing in the reality: WNS is an expensive way to buy offshore capacity, the AI narrative isn't convincing, and the restructuring costs will eat into margins.

Analyst Skepticism

Morgan Stanley downgraded Capgemini to "Underweight" in January 2026 [Source: Investing.com], explicitly citing concerns about the WNS integration and margin trajectory.

The market isn't buying the AI story. It sees a company spending US$3.3 billion to accelerate a labour arbitrage model while calling it transformation.

Red Flags for Clients

1. "AI-powered" claims. Ask what specific AI technology is being deployed, not just the branding. If the answer is "process automation" or "intelligent operations," you're paying for BPO with an AI sticker.

2. Offshore ratios. The WNS deal gives Capgemini the capacity to offshore even more work. Specify maximum offshore percentages in contracts.

3. Quality metrics. BPO work needs different quality metrics than consulting. Define SLAs clearly — response times, resolution rates, escalation procedures.

4. Data sovereignty. Verify where your data will be processed and stored. Indian data centres operate under different regulatory frameworks.

5. Exit clauses. Build exit clauses tied to quality failures, offshore ratio violations, and key personnel changes.

Conclusion

Capgemini's WNS acquisition is the most transparent move in the company's history. They spent US$3.3 billion to buy 66,000 offshore workers and called it AI transformation.

The market saw through it. The stock is down 26%. Analysts are sceptical. And the restructuring costs — €700 million over two years — reveal the true cost of integration.

For Australian IT professionals, WNS changes nothing that wasn't already happening. The offshoring trend was accelerating; now it has more capacity behind it. The €700 million restructuring budget will fund more redundancies, more role eliminations, and more pressure on the remaining onshore staff.

For clients, the WNS deal means more offshore options and more "AI" marketing. The actual capability hasn't changed — it's the same BPO work, the same process execution, the same labour arbitrage model. Just with a fancier name.

The question isn't whether Capgemini will succeed with WNS. It's whether you're willing to pay premium rates for offshore work branded as AI.

This article is based on publicly available sources including Capgemini's own press releases and financial disclosures, market data from Investing.com and Morgan Stanley, WNS corporate filings, and employee feedback from Glassdoor and TheLayoff.com. All factual claims are sourced.

Sources

WNS Acquisition: - Capgemini Completes Acquisition of WNS — October 2025 - Venture Intelligence — US$3.3B Deal — US$76.50 per share - Communications Today — Cognizant, Capgemini crash — WNS context

Capgemini Financials: - FY 2025 Results — Revenue, headcount, restructuring costs - 2026 Capital Markets Day — Strategic narrative

Market Reaction: - Investing.com — Morgan Stanley Cut PT — 26% YTD drop, €117 target - Investing.com — Morgan Stanley Downgrade — Underweight rating

Employee Reviews: - Glassdoor — Capgemini Australia — 4.0/5, 491 reviews - PayScale — Capgemini Australia — A$113,561 average - TheLayoff.com — No Pay Rise 2026 — February 2026

Security: - CNA — Razer v Capgemini — US$6.5M damages, December 2022

BOQ Case Study: - SMH — Hundreds of BOQ Jobs Lost — September 2025

📖 Part of the Capgemini Investigation Series — 10 articles examining Capgemini Australia's operations, employee treatment, and business practices.

The Dossier · Deep Dive · The Exodus · Survivor Stories · Financial Analysis · vs Competition · The Vulture · Invisible Workforce · AI Gamble · Series Home

Following the Money: Capgemini Australia

Every MSP tells you they invest in their people. The numbers tell a different story. This is a forensic analysis of Capgemini Australia's financials — what they earn, what they spend, and what that tells you about their priorities.

For the full picture on Capgemini's controversies, start with our Capgemini Exposed dossier. For the employee experience, see our Capgemini Investigation deep dive.

The Australian Financials: A$878 Million Machine

Revenue and Headcount

The headline number: A$294,000 in revenue per employee. That's the amount each Capgemini Australia staff member generates for the company, on average. To put that in context:

• A mid-level consultant bills at roughly A$180-200/hour
• At 1,800 billable hours per year (a standard target), that's A$324,000-360,000 in revenue per billable consultant
• But not everyone is billable — there's management, sales, HR, bench time
• A$294,000 across all employees suggests a utilisation rate somewhere around 70-75%, which is below the industry target of 80-85%

What this means: Capgemini is not running a lean Australian operation. It's carrying overhead — or it's losing people faster than it can replace them.

Comparing Revenue per Employee Across Australian MSPs

Sources: IBISWorld (2024-2025)

The story the table tells:

• NTT Australia generates A$677K per employee — more than double Capgemini. NTT has fewer than 1,300 Australian employees but generates nearly as much revenue. This is the hallmark of a company that has aggressively offshored its delivery while keeping a thin Australian client-facing layer. NTT's Glassdoor rating in Australia is 3.6/5 — lower than Capgemini's 4.0 — suggesting that the leaner model comes at an employee experience cost.

• DXC Technology at A$404K per employee is the middle ground — more offshore-dependent than Capgemini, but not as extreme as NTT. DXC's Australian Glassdoor rating is a dismal 3.1/5, with 756 reviews consistently flagging the same issues Capgemini faces: low pay, poor management, and offshore replacement anxiety.

• Datacom at A$260K per employee is the most "onshore-heavy" model of the group. Datacom is privately held, New Zealand-founded, and has historically invested more in local delivery. Their Australian Glassdoor rating of 3.1/5 reflects different issues — more about internal politics and career stagnation than the offshore squeeze.

• Capgemini sits in the middle at A$294K. Not the leanest, not the most labour-intensive. But the trajectory is clear: Capgemini is trying to move toward NTT's model — fewer Australians, more offshore delivery, higher revenue per remaining head.

The Global Financial Picture: Declining Margins

Capgemini's Global Results (FY 2025)

Sources: Capgemini FY 2025 Results, Capgemini Q1-Q3 2025 Revenue Releases

The margin problem: Capgemini's operating margin dropped from 10.7% to 9.8% in a single year. That's a 9% decline in profitability on essentially flat revenue. In a business where the primary cost is people, declining margins mean one thing: someone has to absorb the difference.

The WNS acquisition: In October 2025, Capgemini completed the acquisition of WNS, adding approximately 66,000 employees — almost entirely offshore (India, Philippines). This expanded the global headcount from ~341,000 to ~423,000. Onshore headcount? Essentially flat at 143,200. The message is unmistakable: Capgemini is not growing its Australian or Western workforce. It is growing offshore.

The restructuring hammer: In February 2026, Capgemini announced €700 million in restructuring costs over 2026-2027. The language in the earnings call was carefully corporate: "Fit for Growth" program, "country-specific workforce and skills adaptation initiatives." In plain English: redundancies in Australia and other Western markets, with the savings redirected to offshore delivery.

The stock market verdict: Capgemini's shares fell 26% year-to-date as of early 2026. Morgan Stanley cut its price target to €117, citing growth concerns. When the market punishes your stock, the pressure to cut costs intensifies — and in an IT services company, "costs" means "people."

The Headcount Trajectory: Where the Growth Is

Sources: Capgemini Q1 2025 Revenues, Q3 2025 Revenues, FY 2025 Results

Read those numbers again. Onshore headcount has been essentially flat — 143,300 in Q1 to 143,200 in December — while offshore headcount exploded from 199,400 to 277,800. The WNS acquisition alone added 66,000 offshore workers. The onshore workforce? Shrinking by 100 people.

For Australian employees, this trajectory means: you are increasingly a minority in a company that is structurally optimising for offshore delivery. Every restructure, every "Fit for Growth" initiative, every acquisition integration results in the same outcome — fewer Australians, more Indians.

The Salary Arithmetic: Where the Margins Come From

What Capgemini Charges vs. What It Pays

Client rates based on industry standard MSP billing; salaries from SEEK job postings and Glassdoor (1,273 salary submissions)

The 60-70% gap: For every dollar a client pays Capgemini for an Australian engineer's time, the engineer sees 30-40 cents. The rest goes to overhead, margin, and the offshore arbitrage machine.

The India Arbitrage: The Real Money

Sources: SEEK, Glassdoor (AU); Indeed India, Levels.fyi, PayScale (India)

The numbers are staggering. An Australian software engineer at Capgemini earns A$128K-150K. An Indian software engineer at the same company earns ₹426K-₹1.73M — roughly A$7,500 to A$30,000. That's a 5:1 to 10:1 cost ratio. For a new graduate, the ratio is even more extreme: 12:1.

This is why Capgemini's global headcount is 66% offshore. It's not about "accessing global talent." It's about arithmetic. Every Australian role replaced by two or three Indian roles saves Capgemini 60-80% on salary costs while maintaining (or increasing) the billing rate to Australian clients.

What the "Salary Black Hole" Looks Like at Capgemini

We've written extensively about the Salary Black Hole — the gap between what MSPs charge clients and what they pay engineers. At Capgemini, the numbers are particularly stark:

• Client billing rate: A$180-250/hour for a senior engineer
• Engineer salary equivalent: A$55-72/hour (A$113K-150K annual)
• Capgemini's cut: A$108-178/hour per engineer

On a team of 10 senior engineers billing at A$200/hour, that's: - Client pays: A$3.6 million/year - Engineers receive: A$1.2 million/year (combined) - Capgemini keeps: A$2.4 million/year

That A$2.4 million covers management, office costs, sales, and profit. But when you offshore 6 of those 10 roles to India at A$20K each instead of A$140K each, the arithmetic changes dramatically:

• Offshore cost for 6 roles: A$120K/year
• Onshore cost for 4 roles: A$560K/year
• Total engineer cost: A$680K/year
• Capgemini's cut: A$2.92 million/year

Offshoring 60% of the team increased Capgemini's margin by half a million dollars per year on a single project. Multiply that across the entire Australian operation and you understand why the offshore percentage keeps climbing.

The No-Pay-Rise Reality

2026: The Year of the Freeze

In early 2026, posts on TheLayoff.com from Capgemini staff indicated no pay rise for 2026 in some regions, citing the restructuring. A recent Glassdoor review put it bluntly:

"With 2026 inflation, this is effectively a 30% decrease in purchasing power. You are literally paying to work here."

Let's do the maths on that claim:

• Australian inflation (2025-2026): ~3.5-4% (Reserve Bank of Australia estimates)
• Capgemini pay rise: 0%
• Real wage decline: 3.5-4% per year
• Cumulative over 3 years (if frozen since 2023): 10-12% real wage decline

Meanwhile: - Capgemini CEO Aiman Ezzat's compensation: Multiple millions in salary, bonuses, and stock options - €700 million restructuring budget over 2026-2027 - €1.95 billion in organic free cash flow in 2025

The money exists. It's being redirected — toward restructuring, toward offshore expansion, toward executive compensation. Not toward the Australian engineers who generate A$294,000 in revenue each.

The PayScale Numbers Don't Lie

The 11-18% gap: Capgemini's average salary of A$113,561 sits 11-18% below the Australian IT market median of A$128,000-138,000 (Ravio benchmarks, September 2025). That's not a rounding error. That's a structural choice.

SEEK's claim that 81% of Capgemini employees rate their salary as "high or average" needs context: that survey likely captures employees who are still at Capgemini (survivorship bias) and may not have compared their salary to market rates. Multiple Glassdoor reviewers report discovering they were underpaid only after leaving: "After being on the job market, I realised I had fallen way behind my peer group."

The Financial Health Check

Green Flags

• Still profitable: 9.8% operating margin, even after declining
• A$878 million in Australian revenue: Significant local presence
• €1.95 billion free cash flow: Not in financial distress
• Graduate programs: Genuine investment in junior talent
• Scale: Can handle large enterprise and government projects

Red Flags

• Declining margins: 10.7% → 9.8% in one year — the trajectory is down
• €700 million restructuring: More redundancies coming, especially in Western markets
• No pay rises in 2026: Real wages declining while costs of living rise
• 66% offshore and climbing: Australian roles are structurally at risk
• Stock down 26% YTD: Market confidence is eroding
• Acquisition integration track record: Empired (A$233M) → brand retired, staff cut. The Works → gutted, absorbed into frog. RXP → absorbed. Acclimation → absorbed
• Revenue per employee (A$294K) declining relative to competitors: NTT generates 2.3x more per head, suggesting Capgemini is either overstaffed onshore or underutilising its Australian workforce

What This Means for You

If You're an Employee

Your revenue generation (A$294K/year) is being extracted at a rate that leaves you 11-18% below market salary. The company is spending €700 million to restructure — which means your role is a line item in someone's cost-cutting exercise. The 2026 pay freeze is real. The offshore trajectory is structural, not temporary.

Action items: - Check your salary against market benchmarks - Understand your Fair Work rights - Start your escape plan before the restructuring axe falls - Document everything — your contributions, your client relationships, your deliverables

If You're a Client

Capgemini's declining margins mean pressure to cut costs on your project. The way they cut costs is by substituting senior Australian staff with junior offshore resources. The bid-to-delivery gap is a documented pattern.

Action items: - Negotiate named resource clauses in your contract - Require offshore/onshore ratio guarantees - Build milestone-based payment terms - Include data breach liability clauses (see the Razer precedent) - Have an exit strategy before you start

The Bottom Line

Capgemini Australia generates A$878 million in revenue from 2,989 employees — A$294,000 per head. That's solid but declining relative to competitors. The global parent is spending €700 million to restructure while freezing pay for Australian staff. Offshore headcount is 66% and climbing. Margins are falling. The stock is down 26%.

The financial picture is clear: Capgemini is optimising its Australian operation for cost extraction, not for investment in people. The revenue per employee is healthy because they're billing premium rates while paying below-market salaries. The restructuring isn't about becoming more competitive — it's about extracting more margin from fewer, cheaper resources.

For the full story on what this means in practice, read our Capgemini Survivor Stories — composite narratives from people who lived it.

Related Guides

• The Salary Black Hole — Where your MSP billing actually goes
• Offshore Arbitrage Playbook — The business model behind offshoring
• MSP Cost Calculator — Compare Capgemini's pricing against alternatives
• Capgemini Exposed — The complete dossier on Capgemini's controversies
• Capgemini Investigation — Deep dive into contracts, billing, and delivery
• Escape the MSP Trap — Your escape plan
• Fair Work and MSPs — Know your legal rights
• Following the Money — Where your MSP invoices actually go
• Private Equity Playbook — What happens when PE firms acquire MSPs

This analysis is based on publicly available financial data from IBISWorld (2024-2025), Capgemini's own press releases and financial disclosures (FY 2024-2025), Glassdoor (491 Australian reviews), PayScale, SEEK, Levels.fyi, Indeed, TheLayoff.com, and Morgan Stanley research notes. All revenue and headcount figures are sourced from IBISWorld and Capgemini's public filings. Salary comparisons use Australian market benchmarks from Ravio (September 2025) and cross-border salary data from Levels.fyi and PayScale India. The MSP Playbook is not affiliated with Capgemini.

The MSP industry runs on people. Your engineer's skill level directly determines the quality of service your clients receive. Yet many Australian MSPs under-invest in training, creating a cycle of skill gaps, turnover, and declining service quality.

Here is why MSP employee training matters and what both MSPs and their employees should know.

The Training Gap in Australian MSPs

The MSP industry has a training problem. A 2025 survey of Australian MSP employees found:

• 42% received no formal training in the past 12 months
• 35% paid for their own certifications
• 28% said lack of development was their primary reason for considering leaving
• Only 22% had a documented career development plan

This under-investment creates a vicious cycle: untrained engineers deliver lower quality service, clients become dissatisfied, revenue stagnates, and the MSP cannot afford to invest in training.

Why Training Matters for MSPs

Service Quality

Trained engineers resolve issues faster, make fewer mistakes, and provide better strategic advice. The difference between an engineer with current Microsoft certifications and one without is measurable in ticket resolution times and first-contact resolution rates.

Employee Retention

Training and career development are among the top three factors in MSP employee retention. Engineers who feel they are growing are far less likely to leave. Given the cost of replacing an MSP engineer (typically 1.5-2x salary), training investment pays for itself through reduced turnover.

Competitive Advantage

MSPs with certified, well-trained teams can market their expertise to win higher-value clients. Certification badges on the website are not just marketing — they signal capability.

Compliance

Many compliance frameworks (Essential 8, ISO 27001, SOC 2) require evidence of staff competence. Training records demonstrate that your team has the skills to implement and maintain required controls.

Essential Certification Paths for MSP Roles

Help Desk / Level 1 Support

Systems Engineer / Level 2-3 Support

Security Specialist

Management / Business

Building an MSP Training Program

For MSP Owners

Budget Allocation: - Allocate $3,000-$5,000 per engineer per year for training - Include exam fees, training materials, and conference attendance - Factor in productivity loss during training (typically 1-2 weeks per year)

Structure: - Define certification requirements by role - Create a training calendar with milestones - Tie training completion to performance reviews and progression - Celebrate certification achievements publicly

Retention Link: - Include training in employment contracts - Offer certification bonuses ($500-$2,000 per certification) - Provide study leave (paid time off for exam preparation) - Create career progression paths that require certifications

Our MSP Employee Retention Strategies guide covers the broader retention picture.

For MSP Engineers

Self-Development: - Take advantage of free Microsoft Learn paths - Use vendor trial environments for hands-on practice - Join community groups and user groups - Attend industry events (even virtual ones)

Negotiate for Support: - Ask for certification reimbursement as part of your package - Request study leave for exam preparation - Propose a training plan as part of your performance review - Use our MSP Salary Negotiation guide to structure the conversation

Career Planning: - Identify which certifications align with your career goals - Map certifications to specific roles you want to move into - Build a portfolio of skills, not just certifications

The ROI of MSP Training

For the MSP

For the Employee

Red Flags in MSP Training

"We Expect You to Train Yourself"

If the MSP expects engineers to upskill on their own time and at their own expense, they are not investing in their team. This typically correlates with high turnover and poor service quality.

No Certification Requirements

An MSP that does not require certifications for technical roles is unlikely to deliver consistent quality. Certifications provide a baseline of competence.

Certifications Without Application

Requiring certifications without providing opportunities to apply new skills is wasteful. Training should connect to real work.

Training Only for New Hires

If only new hires receive training while tenured staff are neglected, skill gaps will widen over time.

Training and Compliance

Certain compliance frameworks have specific training requirements:

• Essential 8 — requires staff awareness training on cyber security
• ISO 27001 — includes competence and awareness requirements
• SOC 2 — trust service criteria include training documentation
• Privacy Act — staff must understand their obligations under the APPs

Our Essential 8 Implementation Checklist includes staff training requirements.

The Bottom Line

Training is not a cost — it is an investment in the people who deliver your IT services. MSPs that invest in structured training programs retain better staff, deliver higher quality service, and win more business. Employees who invest in their own development command higher salaries and have more career options.

The MSP industry's training gap is an opportunity for those willing to close it.

Use our MSP Health Score to evaluate your MSP's operational maturity, or our MSP Salary Calculator to benchmark compensation including training benefits.

This page has moved. See our full guide: How to Choose an MSP: The Due Diligence Checklist.

You are paying your MSP $8,000 per month. You have been for three years. When someone asks, "Is it worth it?" you hesitate.

The honest answer is that most businesses do not know whether their MSP delivers positive ROI because they have never measured it. They are paying a fee, getting support, and assuming the value is there. But assumption is not analysis, and in a market where MSP pricing has increased 20-30% since 2023, you need to know what you are getting for your money.

Measuring MSP ROI is not just a financial exercise. It is the foundation for every conversation about whether to continue, renegotiate, or change your provider.

The True Cost of IT Without an MSP

Before you can measure ROI, you need to understand what your MSP is replacing. Most businesses dramatically underestimate what in-house IT would cost.

Direct Cost Comparison

The MSP is typically 30-50% cheaper than building equivalent capability in-house. But cost savings are only part of the ROI calculation.

Hidden Costs of In-House IT

Beyond direct costs, in-house IT carries risks that are harder to quantify but very real:

• Key person dependency. If your sole sysadmin leaves, you have a 3-6 month gap at minimum. The cost of that gap in reduced productivity, increased risk, and emergency recruitment often exceeds the annual salary of the person who left.
• Skill gaps. A two-person IT team cannot be expert in networking, cloud, security, compliance, and infrastructure simultaneously. Gaps in any of these areas create risk.
• Scale limitations. Growing from 50 to 100 users requires hiring additional staff. An MSP scales with you without proportional cost increases.

The Four Pillars of MSP ROI

1. Cost Avoidance

This is the most straightforward ROI component: what would you spend if you did not have the MSP?

Calculate: - Replacement staff costs (salary + super + recruitment + training) - Infrastructure costs (servers, networking, monitoring tools) - Licensing costs (RMM, PSA, backup, security tools) - Consultancy costs (projects, migrations, security assessments)

Most MSPs bundle these into their per-user or per-device pricing. The gap between bundled cost and what you would pay separately is your cost avoidance.

2. Downtime Prevention

Downtime costs Australian businesses an average of $5,600 per minute (Gartner). Your MSP's role in preventing and minimising downtime is a major value driver.

Measure: - Uptime achieved vs. uptime that would exist without managed monitoring and maintenance - Mean time to resolution — how quickly issues are fixed - Incidents prevented — proactive monitoring catching problems before they cause outages - Business impact avoided — estimated revenue loss from downtime that did not occur

A good MSP delivers 99.9%+ uptime for critical systems. Without managed monitoring, most SMB environments experience 2-5x more downtime.

3. Security and Risk Reduction

The average cost of a data breach in Australia is $4.03 million (IBM 2024). Your MSP's security posture directly affects your risk exposure.

Measure: - Security incidents prevented — threats detected and blocked - Compliance maintenance — ongoing compliance with Essential 8, privacy requirements - Backup reliability — tested recovery capability when incidents occur - Insurance impact — how MSP compliance affects your cyber insurance premiums

A MSP that prevents even one significant security incident pays for itself for years.

4. Productivity Gains

Faster issue resolution, better infrastructure, and proactive maintenance all contribute to employee productivity.

Measure: - Ticket resolution speed — how quickly employees get back to work - System performance — infrastructure that enables rather than hinders work - Project delivery — how the MSP contributes to business initiatives - Knowledge and training — MSP expertise your team accesses without hiring specialists

Building the ROI Calculation

The MSP ROI Formula

ROI = (Total Benefits - Total Costs) / Total Costs × 100

Where: - Total Costs = MSP monthly fees × 12 + out-of-scope charges + your internal management time - Total Benefits = Cost avoidance + Downtime prevention value + Risk reduction value + Productivity gains

Worked Example

A 150-user professional services firm:

Costs: - MSP fees: $12,000/month × 12 = $144,000 - Out-of-scope charges: $8,000/year - Internal management time: $15,000/year - Total costs: $167,000

Benefits: - Cost avoidance (vs. 3 FTE + infrastructure): $420,000 - Downtime prevention (estimated 40 hours avoided × $500/hour): $20,000 - Risk reduction (security incidents prevented): $50,000 - Productivity gains (faster resolution, better systems): $30,000 - Total benefits: $520,000

ROI = ($520,000 - $167,000) / $167,000 × 100 = 211%

That is a strong return. But the calculation is only valuable if it is honest — do not inflate benefits or ignore costs.

When MSP ROI is Negative

Sometimes the maths does not work. Common reasons:

• You are paying for services you do not use. Audit what is included in your contract versus what you actually consume. Many businesses pay for enterprise-tier services while using basic-tier capabilities.
• The MSP is underperforming. If SLAs are consistently missed, uptime is poor, or response times are slow, the value equation breaks down.
• Your needs have changed. An MSP optimised for a 50-user office may not be the right fit for a 200-user organisation with hybrid cloud infrastructure.
• Pricing has increased without corresponding value. Annual price increases should be justified by improved or maintained service quality.

If your MSP ROI is negative, it does not necessarily mean you should leave. It means you need a conversation — about pricing, service levels, or whether the MSP is still the right fit.

Making the Business Case

When presenting MSP ROI to leadership or the board:

1. Use their language. Frame ROI in business outcomes, not technical metrics. "99.9% uptime" means "16 minutes of downtime per month instead of 8 hours."
2. Benchmark against alternatives. Show the cost comparison with in-house IT and with competitor MSP pricing.
3. Include risk reduction. Quantify what a security incident would cost and how the MSP reduces that risk.
4. Present trends. Show ROI improving over time as the MSP relationship matures and they understand your environment better.
5. Be honest about weaknesses. If certain areas are underperforming, acknowledge them and present the remediation plan.

Related Guides

• MSP Vendor Comparison Template — Compare providers objectively
• MSP Service Delivery Metrics — What to measure and track
• MSP Contract Negotiation Tips — Negotiate better terms
• MSP Cost Per User Analysis — Understand your pricing structure
• How to Choose an MSP — Selection criteria that drive ROI

Your MSP holds the keys to dozens of client environments. Administrative passwords, domain admin accounts, RMM access, VPN credentials — these are the keys to your clients' businesses. If those keys fall into the wrong hands, the consequences are catastrophic.

Access control is the practice of ensuring only the right people have access to the right resources — and only for as long as needed.

Why Access Control Is Uniquely Critical for MSPs

MSPs present an amplified access control challenge:

• Concentrated access. A single compromised MSP technician account can provide access to dozens of client environments.
• Privileged access. MSP technicians typically need administrative access to client systems — the highest level of privilege.
• Multiple environments. Each client environment is a separate security domain, but access is often managed through a single MSP identity.
• Third-party access. Vendors and subcontractors also need access, adding complexity.
• Insider risk. Departing employees may retain access longer than they should.

Access Control Framework for MSPs

1. Identity Management

Every person and system accessing your environments needs a verified identity:

• Unique accounts. Every user must have their own account. Shared accounts are prohibited — they eliminate accountability and make access revocation impossible.
• Multi-factor authentication. MFA on every account, every time. No exceptions. Our Essential 8 Implementation Checklist covers MFA requirements in detail.
• Strong passwords. Minimum 16 characters for standard accounts, 20+ for privileged accounts. Use a password manager — never store credentials in documents or spreadsheets.
• Identity lifecycle. Automated provisioning and deprovisioning. When someone joins, they get access. When they leave, access is revoked immediately.

2. Least Privilege

Grant the minimum access required:

• Role-based access. Define roles with specific permissions and assign users to roles rather than granting individual permissions.
• Client-level segmentation. Technicians should access only the clients they manage, not all clients indiscriminately.
• Time-limited access. Grant elevated access only when needed and revoke it automatically after a defined period.
• Just-in-time access. For privileged operations, grant access on demand with approval, not as a standing permission.

3. Privileged Access Management (PAM)

Privileged accounts require additional controls:

• Credential vaulting. Store privileged credentials in a secure vault (CyberArk, HashiCorp Vault, Azure PIM) rather than in IT Glue or spreadsheets.
• Session recording. Record privileged sessions for audit and forensic purposes.
• Just-in-time elevation. Technicians request elevated access when needed, with time limits and approval workflows.
• Privileged access workstations. Use dedicated, hardened workstations for privileged operations — not the same workstation used for email and browsing.

4. Network Access Control

Control how and from where access occurs:

• VPN requirements. All remote access to client environments must go through VPN with MFA.
• IP restrictions. Where possible, restrict access to known IP ranges.
• Network segmentation. Separate client environments from each other and from internal MSP infrastructure.
• Zero trust architecture. Move toward zero trust where every access request is verified regardless of source.

5. Access Reviews

Access must be reviewed regularly:

• Quarterly access reviews. Review who has access to what and remove unnecessary permissions.
• Immediate review on role change. When someone changes roles, review and adjust their access.
• Termination procedures. Immediate access revocation upon termination, including all client environments, VPN, email, and tools.
• Audit logging. Log all access events and review logs regularly for anomalies.

Common Access Control Failures

• Shared accounts. "admin@client.com" used by multiple technicians eliminates accountability.
• Standing privileged access. Technicians with permanent domain admin access across all clients.
• No MFA. Administrative accounts without multi-factor authentication.
• Slow deprovisioning. Departing employees retaining access for days or weeks after leaving.
• Password reuse. Same password used across multiple client environments.
• Unmanaged third-party access. Vendors with persistent access that is never reviewed.

Building Your Access Control Policy

Your policy should document:

1. Account management. How accounts are created, modified, and deleted
2. Authentication requirements. Password standards, MFA requirements, SSO configuration
3. Authorisation model. Role-based access definitions and permission levels
4. Privileged access procedures. How privileged access is requested, approved, and monitored
5. Access review cadence. How often access is reviewed and by whom
6. Incident response. What to do if access control is suspected to be compromised

Related Guides

• Essential 8 Implementation Checklist — Access control as part of Essential 8
• MSP Cybersecurity Certifications — Security standards requiring access control
• MSP Risk Management Framework — Risk assessment for access control
• MSP Vendor Management Guide — Third-party access management
• MSP Incident Response Plan — Responding to access control incidents

Signing an MSP contract is a significant commitment. You're entrusting a third party with your technology infrastructure, data security, and business continuity. Rushing into an agreement without proper due diligence is one of the most expensive mistakes businesses make.

This checklist covers every area you need to evaluate before signing. Use it as a structured framework for your evaluation. For current market context, see our MSP pricing comparison 2026. For contract specifics, see our MSP contract checklist.

Phase 1: Initial Research (Before Meeting the MSP)

Company Background

• [ ] Business registration. Verify the MSP is a registered Australian business (ASIC lookup). Check for any history of deregistration or legal action.
• [ ] Operating history. How long have they been in business? Longer isn't always better, but less than 2 years is a risk factor.
• [ ] Ownership structure. Who owns the MSP? Is it privately held, PE-backed, or part of a larger group? PE ownership can affect service priorities.
• [ ] Financial health. Can they provide financial statements? Are they profitable? A struggling MSP is a risky partner.
• [ ] Insurance. Do they have professional indemnity, public liability, and cyber insurance? What are the coverage limits?

Online Presence

• [ ] Website quality. Is it professional, current, and detailed? Or generic and template-based?
• [ ] Google reviews. Check the volume and sentiment of reviews. Look for patterns in complaints.
• [ ] Glassdoor/Indeed reviews. What do their employees say? High turnover = inconsistent service.
• [ ] LinkedIn. Check the team size, longevity, and professional presence.
• [ ] News and press. Any recent acquisitions, layoffs, or controversies?

Industry Standing

• [ ] Vendor partnerships. Are they a Microsoft Partner, AWS Partner, or other relevant vendor? What's their partner tier?
• [ ] Certifications. Do they hold relevant certifications (ISO 27001, SOC 2, Essential 8 maturity)?
• [ ] Industry memberships. Are they part of industry bodies (AITP, ConnectWise partner communities)?
• [ ] Awards or recognition. Any relevant industry awards or rankings?

Phase 2: Technical Evaluation

Infrastructure and Tools

• [ ] RMM platform. What tool do they use? How mature is their deployment?
• [ ] PSA/ticketing system. What system manages their service delivery?
• [ ] SOC capabilities. Do they have a Security Operations Centre? In-house or outsourced?
• [ ] Backup and DR. What backup solutions do they use? Where is data stored? Have they tested restores?
• [ ] Network operations. Do they have a NOC? 24/7 monitoring? What's the escalation process?
• [ ] Remote access tools. What tools do they use for remote support? Are they secure and auditable?

Security Posture

• [ ] Security framework. What framework do they follow? (Essential 8, ISO 27001, NIST)
• [ ] MFA implementation. Do they enforce MFA for all their own systems and client environments?
• [ ] Patch management. What's their patching process and SLA?
• [ ] Incident response. Do they have a documented incident response plan? Has it been tested?
• [ ] Security training. Do they train their staff on security? Do they offer security awareness training to clients?
• [ ] Essential 8 maturity. What's their maturity level against the Essential 8? See our Essential 8 audit guide.

Technical Capabilities

• [ ] Technology stack. Are they experienced with your specific technologies (M365, Azure, specific line-of-business apps)?
• [ ] Specialisations. Do they have dedicated specialists or generalists?
• [ ] Certifications. What certifications do their technicians hold?
• [ ] Vendor relationships. Can they access vendor support directly?
• [ ] Lab/testing environment. Do they test changes before deploying to production?

Phase 3: Service Delivery Evaluation

Service Level Agreements

• [ ] Response times. What are the SLAs for different priority levels?
• [ ] Resolution times. What are the target resolution times?
• [ ] SLA reporting. How do they report on SLA performance? How often?
• [ ] SLA penalties. What happens if they breach SLAs?
• [ ] Scope clarity. Is the scope of services clearly defined in writing?

See our MSP SLA guide for what to look for.

Staffing and Support

• [ ] Client-to-technician ratio. What's their ratio? Under 30:1 is ideal.
• [ ] On-call process. How does after-hours support work?
• [ ] Escalation paths. What's the escalation process for complex issues?
• [ ] Dedicated vs. shared resources. Will you have a dedicated account manager or technician?
• [ ] Staff turnover. What's their technician turnover rate? (Ask directly — their answer tells you a lot)

Communication and Reporting

• [ ] Regular reviews. How often do they conduct service reviews?
• [ ] Reporting quality. What reports do they provide? How detailed are they?
• [ ] Communication channels. How do you reach them? (Portal, email, phone, direct)
• [ ] Ticket visibility. Can you see all tickets, or just open ones?
• [ ] Escalation to management. Can you escalate directly to management if needed?

Onboarding Process

• [ ] Onboarding timeline. How long does onboarding take?
• [ ] Documentation. What documentation do they create during onboarding?
• [ ] Discovery process. How thorough is their environment audit?
• [ ] Transition plan. How do they handle the transition from your current provider?
• [ ] Onboarding cost. Is there an additional onboarding fee?

See our MSP onboarding best practices for what good onboarding looks like.

Phase 4: Legal and Contract Review

Contract Terms

• [ ] Term length. How long is the initial term? (12 months is standard)
• [ ] Renewal terms. Does it auto-renew? What's the notice period for non-renewal?
• [ ] Exit clause. What's the process for terminating the contract?
• [ ] Exit costs. Are there penalties for early termination?
• [ ] Data ownership. Who owns your data? Can you get it back on exit?
• [ ] IP ownership. Who owns any custom scripts, documentation, or configurations?

See our MSP contract checklist for detailed contract evaluation.

Liability and Indemnity

• [ ] Liability caps. What's their maximum liability?
• [ ] Indemnification. Who's responsible if something goes wrong?
• [ ] Data breach liability. What happens if they cause a data breach?
• [ ] Service credits. Are there financial penalties for SLA breaches?
• [ ] Insurance requirements. What insurance do they carry?

Compliance

• [ ] Privacy Act compliance. How do they handle your data under Australian Privacy Law?
• [ ] Industry regulations. Are they familiar with your industry's compliance requirements?
• [ ] Essential 8. Can they demonstrate Essential 8 maturity? See our Essential 8 audit guide.
• [ ] Data sovereignty. Where is your data stored? Is it in Australia?

Phase 5: Reference Checks

Client References

• [ ] Request 3+ references from clients of similar size and industry
• [ ] Ask about response times, communication quality, issue resolution, and overall satisfaction
• [ ] Ask about any problems and how they were handled
• [ ] Ask about contract terms and any surprises
• [ ] Contact references directly — don't rely on written testimonials

Employee References

• [ ] Check Glassdoor for employee sentiment
• [ ] Look for patterns in complaints (management, work-life balance, compensation)
• [ ] High turnover is a red flag — it means inconsistent service

Phase 6: Final Decision

Scorecard

Create a simple scorecard:

Red Flags Summary

If you encounter any of these, proceed with extreme caution:

• Unwillingness to provide references
• Vague scope definitions
• No SLA commitments
• High staff turnover
• Pressure to sign quickly
• No documented processes
• Unwillingness to negotiate terms
• No cyber insurance

Related Resources

• MSP Contract Checklist — Detailed contract evaluation
• MSP Red Flags — Warning signs
• MSP Pricing Comparison 2026 — Market benchmarks
• MSP Health Score — Structured evaluation framework
• Essential 8 Audit Guide — Security framework evaluation

Answer 10 quick questions and we'll tell you if you're being paid fairly — or if your MSP is pocketing the difference.

Related Reading

• The 2026 MSP Salary Guide — Full breakdown of what every MSP role should pay in Australia
• The IT Salary Black Hole — Why Australian IT salaries have stagnated for a decade
• MSP Salary Negotiation Guide — How to use data like this to negotiate your next raise
• MSP Arbitrage Explained — How MSPs profit from the gap between billing and pay
• MSP vs In-House IT: The Real Cost Comparison — Comparing MSP employment to going in-house
• Fair Work and MSPs: Your Rights — What Australian employment law says about MSP subcontractor pay
• Best MSPs to Work For — Top-rated MSPs based on employee reviews

Your MSP sends you a monthly report. It is six pages of charts and numbers. You glance at it, see that "99.9% uptime" is highlighted, and file it away.

But are you actually measuring what matters? Uptime is important, but it is one metric among dozens. And frankly, it is the one MSPs are most likely to present because it is the one they are almost always meeting.

Effective MSP management requires a balanced set of metrics that cover responsiveness, quality, efficiency, and business value. Here is what to measure and why.

The Four Pillars of MSP Metrics

1. Responsiveness Metrics

How quickly does the MSP respond when you need them?

Key metrics:

Why it matters: Slow response times directly impact your business productivity. Every minute an employee cannot work due to an unresolved issue has a cost.

Watch for: Consistently meeting first response times but missing resolution times — this suggests the MSP acknowledges quickly but does not prioritise fixing.

2. Quality Metrics

How well does the MSP resolve issues?

Key metrics:

Why it matters: Quality metrics reveal whether issues are truly fixed or just temporarily patched. A high reopen rate or recurrence rate indicates systemic problems.

Watch for: High CSAT but high reopen rates — employees may be polite in surveys while issues persist.

3. Reliability Metrics

How stable is the environment the MSP manages?

Key metrics:

Why it matters: Reliability is the foundation of business continuity. Unplanned downtime directly impacts revenue, productivity, and customer satisfaction.

Watch for: Uptime measured differently than agreed — verify the measurement methodology matches your SLA definition.

4. Business Value Metrics

How does the MSP contribute to business outcomes?

Key metrics:

Why it matters: These metrics connect MSP performance to business outcomes. A good MSP reduces issues over time through proactive maintenance, not just reacts to problems.

Watch for: Decreasing ticket volume that correlates with increasing user complaints — issues may be going unreported rather than being resolved.

Building Your MSP Scorecard

Monthly Scorecard

Create a simple one-page scorecard for monthly reviews:

Status indicators: - Green: Meeting target - Amber: Within 10% of target - Red: Missing target by >10%

Quarterly Strategic Review

Expand the monthly review with strategic analysis:

• Trend analysis — are metrics improving, stable, or declining?
• Root cause analysis — why are targets being missed?
• Improvement initiatives — what is the MSP doing to improve?
• Business alignment — is the MSP supporting your business goals?
• Contract review — do SLAs and pricing reflect current needs?

Holding Your MSP Accountable

The Performance Conversation

When metrics are not met, follow this framework:

1. Present the data. Show the specific metrics that are missing targets.
2. Ask for explanation. What is causing the underperformance?
3. Request a remediation plan. Specific actions, owners, and deadlines.
4. Set a review date. Revisit in 30-60 days to assess improvement.
5. Document everything. Written records of performance issues and remediation commitments.

When Metrics Are Consistently Missed

If the MSP consistently fails to meet agreed metrics:

• Formal escalation — written notice of SLA breaches
• Service credits — invoke contractual penalties
• Remediation plan — require a formal improvement plan with milestones
• Contract review — consider whether the relationship is viable
• Exit planning — if performance does not improve, begin evaluating alternatives

What a Good MSP Looks Like

A well-performing MSP will:

• Proactively share metrics without being asked
• Explain variances before you ask
• Present improvement plans when metrics dip
• Celebrate improvements and achievements
• Welcome accountability as a partnership tool

A poor MSP will: - Resist sharing detailed metrics - Explain away every miss with excuses - Present metrics in ways that obscure problems - React defensively to accountability - Resist customised reporting

Related Guides

• MSP Service Level Management — Deep dive on SLAs
• MSP Account Management Best Practices — Building effective relationships
• MSP ROI for Clients — Measuring business value
• MSP Quality Management System — Quality frameworks
• MSP Health Score — Benchmark overall performance

You cannot improve what you do not measure. For MSPs, client satisfaction is the ultimate metric — but it is notoriously difficult to measure well. Here is how to design a measurement framework that actually drives improvement.

Why Measurement Matters

Most MSPs believe they know how satisfied their clients are. Most are wrong. Without structured measurement, you are relying on anecdotes — the angry client who complains loudly, or the quiet client who leaves without warning.

Structured measurement reveals:

• Silent dissatisfaction — clients who are unhappy but not vocal
• Emerging trends — declining satisfaction before it becomes churn
• Team performance — which engineers and teams are delivering value
• Service gaps — where your service falls short of expectations
• Competitive position — how you compare to alternatives

The MSP Satisfaction Scorecard

Quantitative Metrics

These are measurable, objective indicators:

Qualitative Metrics

These capture subjective experience:

Designing Effective Surveys

Transaction-Level Surveys

Sent after each support interaction:

CSAT Question: "How satisfied were you with the support you received today?"

Scale: Very dissatisfied (1) to Very satisfied (5)

CES Question: "How easy was it to get the help you needed?"

Scale: Very difficult (1) to Very easy (7)

Keep it short. Two questions maximum. Response rates drop dramatically with longer surveys.

Relationship Surveys

Sent quarterly or semi-annually to gauge overall relationship health:

Key Questions:

1. How would you rate the overall value our services provide? (1-10)
2. How likely are you to recommend us to a colleague? (0-10 NPS)
3. What is the most important thing we could improve?
4. What do we do better than anyone else?
5. Is there anything we should stop doing?

Response target: 30%+ of clients. Below that, the data is not statistically meaningful.

The NPS Question

"How likely are you to recommend [MSP name] to a colleague or business contact?"

Scale: 0 (not at all likely) to 10 (extremely likely)

• Promoters (9-10): Loyal enthusiasts who drive growth
• Passives (7-8): Satisfied but vulnerable to competitors
• Detractors (0-6): Unhappy clients who can damage your brand

NPS = % Promoters - % Detractors

Interpreting NPS in Context

NPS is useful for tracking trends, not absolute values. A single NPS score means little — the trend over time is what matters.

From Data to Action

Close the Loop

The most important step in client satisfaction measurement is closing the loop — responding to feedback and acting on it.

For Detractors: - Respond within 24 hours - Acknowledge the issue - Explain what you will do - Follow up after resolution

For Promoters: - Thank them - Ask for a testimonial or referral - Understand what you did right

For Everyone: - Share aggregated feedback with your team - Identify patterns and address systemic issues - Communicate changes you have made based on feedback

The Feedback-to-Action Framework

1. Collect — gather data through surveys, tickets, and conversations
2. Analyse — identify trends, patterns, and outliers
3. Prioritise — focus on issues with the highest impact
4. Act — implement specific improvements
5. Communicate — tell clients what changed because of their feedback
6. Measure — verify that the change improved satisfaction

Common Measurement Mistakes

Surveying Too Infrequently

Annual surveys are too infrequent. By the time you collect and act on data, client sentiment has shifted. Quarterly relationship surveys and continuous transaction surveys provide better insight.

Not Acting on Data

Collecting satisfaction data without acting on it is worse than not collecting it. Clients who provide feedback and see no change become more dissatisfied, not less.

Measuring Only Happy Clients

If you only survey clients who respond, you are likely measuring only the most engaged (positive or negative) clients. Push for broad participation to get a representative sample.

Confusing Activity with Outcomes

Ticket volume, response times, and SLA compliance are activity metrics. They measure what you do, not how clients feel about it. Balance activity metrics with satisfaction metrics.

Ignoring Silent Churn

The clients who leave without warning are often the ones who were never asked for feedback. Proactive measurement catches dissatisfaction before it becomes churn.

Building a Client Satisfaction Program

Phase 1: Foundation (Month 1-2)

• Implement transaction-level CSAT surveys after every ticket
• Establish baseline metrics (current SLA performance, ticket volumes)
• Create a simple client satisfaction dashboard

Phase 2: Relationship Measurement (Month 3-4)

• Launch quarterly NPS surveys to all clients
• Establish feedback collection processes
• Train team on interpreting and responding to feedback

Phase 3: Action and Improvement (Month 5-6)

• Analyse first full quarter of NPS data
• Identify top improvement priorities
• Implement changes and communicate to clients

Phase 4: Optimisation (Ongoing)

• Refine survey questions based on response rates
• Tie satisfaction metrics to team performance reviews
• Benchmark against industry standards

The Bottom Line

Client satisfaction measurement is not a nice-to-have — it is an operational necessity. MSPs that measure satisfaction systematically, act on the data, and communicate changes to clients retain more revenue and win more referrals than those that rely on gut feel.

Start simple. Two transaction questions and one quarterly survey will give you more insight than you currently have. Then build from there.

Use our MSP Health Score to benchmark your client satisfaction against industry standards, or our MSP Client Retention Strategy guide for retention-focused improvements.

DXC Technology is what happens when two struggling IT services companies merge and spend the next decade cutting costs. Formed from the merger of CSC and HP Enterprise Services in 2017, DXC has been in continuous restructuring since day one.

In Australia, DXC runs some of the most critical government IT infrastructure — including services for the Australian Tax Office, Department of Defence, and multiple state governments. The irony: a company that can't retain its own staff is trusted to run the nation's digital backbone.

The Numbers

Average salary (Australia): A$90,000-100,000 Revenue per employee: A$404K (suggests heavy offshoring)

Employee Experience: The Restructuring Treadmill

The Pattern

DXC's employee experience follows a predictable cycle:

1. Acquisition/merger → promises of synergy and growth
2. Integration → new management, new processes, new reporting lines
3. Restructuring → "redundancies" (layoffs) to achieve "efficiency"
4. Stabilisation → remaining staff absorb extra work
5. Repeat → another restructure, another round of cuts

This cycle has repeated since 2017. Every 18-24 months, DXC announces a "transformation" that results in layoffs. The remaining staff are expected to deliver more with less.

What Reviews Say

Constant uncertainty. "You never know if your job will exist next month." The restructuring treadmill creates a culture of anxiety where people focus on survival rather than innovation.

Below-market pay. DXC's average salary of A$90,000-100,000 is 20-25% below the Australian IT market median. The company justifies this with "stability" — but the constant restructuring undermines that claim.

Outsourcing pressure. DXC's business model is built on replacing Australian staff with cheaper offshore resources. Government clients are told they'll get "local delivery" but increasingly receive offshore teams.

Dead-end roles. "If you're not in management, there's nowhere to go." Technical career paths are limited, and promotion often requires moving into people management.

The Government Problem

DXC's government contracts create a unique dynamic. The company is locked into long-term agreements (5-10 years) with strict delivery requirements. But the margins on these contracts are thin, which means:

• Staff are underpaid to maintain profitability
• Offshoring is used to reduce costs
• Innovation is limited by fixed-scope contracts
• The best staff leave for better-paying roles

The government gets what it pays for: reliable but uninspired IT services.

How DXC Compares

What This Means for You

If you're considering DXC: - Ask about the specific team and contract — some are stable, others are on the chopping block - Negotiate salary hard — the initial offer is below market - The government practice offers project exposure but limited career growth - Expect restructuring every 18-24 months — plan accordingly

If you're already at DXC: - Your market value is almost certainly higher than your salary - Build relationships outside your team — internal transfers are possible - Document everything — restructuring decisions are often arbitrary - Have an exit strategy ready

Based on Glassdoor (800+ Australian reviews), PayScale, IBISWorld, and public reporting.

You've spent years firefighting across dozens of clients. You know M365, Azure, networking, security, and how to explain DNS to a business owner. Now you're wondering: what would it be like to work on one environment, go deep, and actually build things instead of always fixing them?

Moving from MSP to in-house IT is one of the most common career transitions in the industry. It's also one of the most misunderstood. This guide covers what actually changes, what to expect, and how to make the switch successfully.

If you're still deciding whether to leave, our escape MSP trap guide helps you think through the decision. If you're already committed, read on.

Why People Leave MSPs

The reasons cluster around a few themes:

Depth vs. breadth. MSPs give you breadth — you touch everything. In-house gives you depth — you go deep on one environment. After years of surface-level exposure, many engineers crave depth.

Pace. MSPs move fast. Tickets, projects, incidents, client calls. In-house IT moves slower. You might spend three months on a single project. For some, this is a relief. For others, it's boring.

Burnout. The relentless pace, on-call rotations, and client demands push people out. Our MSP employee burnout recovery guide covers this in detail.

Career progression. Many MSPs have flat hierarchies. In-house organisations often have clearer progression paths: technician → senior → lead → manager → director.

Compensation ceiling. MSP salaries often plateau after 5-7 years. In-house roles at larger organisations can offer higher ceilings, especially for specialised or management positions.

Work life balance. The 24/7 client expectation doesn't exist in most in-house roles. No on-call (or reduced on-call), predictable hours, and genuine leave.

What Actually Changes

The Pace Shift

MSP: Multiple clients, constant context-switching, reactive work dominates. You might work on five different M365 tenants in a day.

In-house: One environment, deep projects, proactive work possible. You might spend a week on a single Exchange migration.

The adjustment: Some people find the slower pace boring initially. You go from 15 tickets a day to 3-5. The projects are bigger and longer. If you thrive on variety and urgency, this can feel like a step back. But most people adjust within 2-3 months.

The Depth Shift

MSP: Surface-level knowledge across many technologies. You know how to configure an Azure AD Conditional Access policy, but you've never designed one from scratch for a complex regulatory environment.

In-house: Deep expertise in your organisation's specific stack. You'll learn the intricacies of your environment that no MSP would ever see.

The adjustment: The first few months will feel like drinking from a firehose of organisational context. Policies, politics, legacy systems, tribal knowledge. It takes 6-12 months to truly understand a single environment.

The Relationship Shift

MSP: Transactional relationships with many clients. You're a vendor. Clients see you as a cost centre.

In-house: Embedded relationships with colleagues. You're part of the team. Your work directly enables the business.

The adjustment: The shift from "vendor" to "colleague" is significant. You'll be invited to strategy meetings, asked for input on business decisions, and expected to understand the business context behind technical requests.

The Compensation Shift

MSP: Salary often compressed. Bonuses rare. Training investment varies.

In-house: Typically more structured pay bands. Benefits packages (super, health insurance, professional development budgets). Clearer path to higher bands.

The adjustment: Total compensation often improves when you include benefits, even if the base salary seems similar. In-house roles at larger companies may also offer equity, profit sharing, or performance bonuses.

How to Position Your MSP Experience

The Translation Guide

MSP language and in-house language are different. Here's how to translate:

Your Strengths

Frame MSP experience as advantages:

• Breadth. "I've worked across 30+ environments, which means I've seen problems most in-house engineers never encounter."
• Speed. "I'm used to working under pressure with tight deadlines. I can ramp up quickly."
• Communication. "I've explained technical issues to non-technical business owners daily. I can translate technical concepts for any audience."
• Problem-solving. "MSP work is constant troubleshooting. I'm comfortable with ambiguity and can diagnose unfamiliar systems."
• Vendor management. "I've worked with dozens of vendors and can evaluate solutions quickly."

What to Emphasise in Interviews

• Projects where you delivered measurable outcomes
• Times you went above and beyond (but frame as initiative, not overwork)
• Your ability to learn new technologies quickly
• Your understanding of business impact from technical decisions
• Specific technologies relevant to the in-house role

What to Downplay

• The chaotic nature of MSP work (sounds unprofessional)
• Client complaints or difficult situations (unless demonstrating conflict resolution)
• Volume of work (sounds like you're complaining about workload)
• Negative experiences with MSP management

The Practical Transition

Resume and Cover Letter

• Translate MSP jargon into in-house language
• Focus on projects and outcomes, not ticket volumes
• Highlight technologies relevant to the target role
• Use our resume builder for MSP-specific tips

Interview Preparation

In-house interviews focus on:

• Depth. "Tell us about a time you designed/configured X from scratch."
• Strategy. "How would you approach [business problem] from an IT perspective?"
• Culture. "How do you work with non-technical stakeholders?"
• Growth. "Where do you want to be in 3-5 years?"

Prepare examples that show depth, not just breadth.

The Notice Period

• Give proper notice (typically 4 weeks in Australia for permanent roles)
• Document everything you're responsible for
• Offer to train your replacement
• Don't badmouth the MSP — you may need references
• Leave professionally — the MSP world is smaller than you think

Common Mistakes

Dismissing MSP experience. Don't say "I'm just from an MSP." MSP experience is valuable. Own it.

Expecting the same pace. The adjustment takes time. Give yourself 3-6 months to settle in.

Not learning the business. In-house IT requires understanding the business. Don't just learn the tech stack — learn what the company does, who the stakeholders are, and what matters to leadership.

Trying to bring MSP practices. Some MSP practices are excellent (documentation, automation). Others are MSP-specific (ticket SLAs, client billing). Learn what applies and what doesn't.

Leaving without a plan. Don't quit out of frustration. Have the next role lined up. Use our MSP interview questions to prepare.

Related Resources

• Escape MSP Trap — Strategic approach to leaving
• MSP Burnout Recovery — If burnout is driving the decision
• MSP Interview Questions — Prepare for your next role
• Salary Benchmark 2026 — Compare MSP vs in-house compensation
• MSP Engineer Career Paths — Explore your options

Your employees know exactly what is broken. They know which processes waste time, which tools frustrate them, which managers need to improve, and which clients are driving them toward burnout. They just do not tell you — because nobody asked, or because asking does not lead to change.

An employee feedback system is not a suggestion box on the wall. It is a structured, ongoing process for hearing, understanding, and acting on the input of the people who do the work. In the MSP industry, where engineer turnover exceeds 25%, understanding what drives people away — and what keeps them — is a competitive advantage.

Why Feedback Systems Matter for MSPs

The Retention Problem

MSPs lose engineers at alarming rates. The causes are well-documented:

• Burnout from excessive on-call and context-switching
• Lack of career progression and skill development
• Feeling undervalued or unheard
• Poor management and communication
• Compensation not matching market rates

Most of these factors are detectable through feedback — if you are collecting it systematically and acting on it.

The Quality Problem

MSP engineers interact with clients daily. They see service quality issues, process failures, and customer frustration before management does. Without a feedback mechanism, this knowledge stays with the individual — and walks out the door when they leave.

The Improvement Problem

Continuous improvement requires knowing what to improve. Without employee input, improvement initiatives are based on assumptions rather than evidence. Employees closest to the work have the most accurate understanding of what needs to change.

Designing Your Feedback System

Layer 1: Regular One-on-One Conversations

The foundation of any feedback system is regular, structured one-on-one conversations between managers and team members.

Frequency: Bi-weekly or monthly, 30 minutes minimum

Structure: 1. How are you going? (Open-ended, personal) 2. What is working well? (Reinforce positives) 3. What is getting in your way? (Identify obstacles) 4. What would you change? (Solicit improvement ideas) 5. How can I help? (Manager commitment to action)

Documentation: - Record key themes (not individual comments) - Track action items and follow-up - Escalate systemic issues to leadership

Layer 2: Quarterly Pulse Surveys

Short, focused surveys that track sentiment over time.

Length: 5-8 questions maximum

Sample questions: - "How satisfied are you with your role right now?" (1-5 scale) - "How manageable is your current workload?" (1-5 scale) - "Do you feel you have the tools and resources you need?" (1-5 scale) - "How would you rate communication from management?" (1-5 scale) - "How likely are you to recommend working here?" (eNPS 0-10) - "What is the one thing you would change?" (Open text)

Key metric: Employee Net Promoter Score (eNPS). Track quarterly. A declining trend is an early warning.

Layer 3: Annual Comprehensive Survey

A detailed assessment covering all aspects of the employment experience.

Duration: 30-40 questions, 15-20 minutes

Categories: - Role satisfaction - Compensation and benefits - Career growth and development - Management and leadership - Culture and team dynamics - Work-life balance - Tools and resources - Communication and transparency

Analysis: - Overall scores by category - Trends over time (year-over-year comparison) - Breakdown by team, tenure, and role - Open text analysis for themes

Layer 4: Continuous Feedback Mechanisms

Always-on channels for real-time input.

Options: - Anonymous suggestion tool (Officevibe, TINYpulse, Culture Amp) - Slack/Teams channel for suggestions - Monthly "ask me anything" sessions with leadership - Post-project retrospectives - Exit interview programme

Acting on Feedback

The Feedback Loop

Collecting feedback without acting on it is worse than not collecting it. It signals that you do not value employee input.

The loop: 1. Collect feedback through your system 2. Analyse for themes, trends, and priorities 3. Communicate what you heard (transparently) 4. Decide what to act on and what to explain 5. Act on the decisions 6. Report on progress 7. Repeat

The 30-Day Communication Rule

Share feedback results with the team within 30 days of collection. This includes:

• Summary of results (positive and negative)
• Top themes identified
• What you are doing about it
• What you are not doing and why
• Timeline for action

Prioritising Action

Not every piece of feedback can be addressed immediately. Use this framework:

Immediate (0-30 days): - Quick wins that address frequent complaints - Safety or wellbeing concerns - Communication gaps

Short-term (30-90 days): - Process improvements - Tool or resource changes - Training or development needs

Medium-term (3-12 months): - Structural changes (organisational, policy) - Compensation adjustments - Career path development

Explained (not acting): - Feedback that is not feasible or aligned with strategy - Communicate clearly why you are not acting

Measuring Feedback System Effectiveness

Key Metrics

Common Feedback System Failures

No anonymity. If employees believe feedback is not anonymous, they will not be honest. Use third-party tools and communicate clearly about privacy.

No action. Collecting feedback and doing nothing destroys trust. If you cannot act, explain why.

Leadership exemption. If leadership is not subject to feedback, employees notice. Everyone should be accountable.

One-way communication. Feedback is a dialogue, not a monologue. Share results and invite discussion.

Survey fatigue. Too many surveys with too many questions leads to declining participation. Keep surveys focused and act visibly on results.

Building a Feedback Culture

A feedback system is a tool. A feedback culture is a mindset. To build one:

• Leadership must model it. Leaders who ask for feedback and act on it create permission for others.
• Celebrate feedback. Recognise and thank people for providing honest input.
• Close the loop. Always communicate what happened with feedback.
• Make it safe. Ensure there are no consequences for honest feedback.
• Act visibly. The most powerful signal is visible change driven by employee input.

Related Guides

• MSP Employee Satisfaction Survey — Comprehensive satisfaction measurement
• MSP Employee Onboarding Checklist — Feedback from day one
• MSP Account Management Best Practices — Feedback in MSP relationships
• Best MSPs to Work For — What top employers get right
• MSP Quality Management System — Continuous improvement frameworks

An engaged employee picks up an extra ticket without being asked. A disengaged employee counts the minutes until 5pm. The difference between those two people is not personality — it is environment. MSPs that create the right environment get discretionary effort; those that do not get turnover.

The MSP Engagement Challenge

MSPs face a perfect storm of engagement challenges:

• Repetitive work. Helpdesk tickets are, by nature, repetitive. Without variety and growth, even skilled technicians become disengaged.
• Constant pressure. Clients expect immediate responses. SLAs create relentless deadlines. There is always something on fire.
• Limited growth. In a small MSP, the career ladder is short. Technicians who want to grow see no path forward.
• Low visibility. When everything runs smoothly, nobody notices. When something breaks, everyone complains. This is a demotivating dynamic.
• After-hours burden. On-call rotations, weekend work, and emergency calls erode personal time and family relationships.

These are structural challenges. They require structural solutions.

Engagement Strategies That Work

1. Create Clear Career Paths

Technicians who see a future stay. Those who do not leave. Build career ladders that provide progression:

• Technical track. L1 → L2 → L3 → Principal Engineer → Architect
• Management track. Technician → Team Lead → Service Manager → Operations Manager
• Specialist track. Generalist → Security Specialist → Cloud Architect → CISO

Our MSP Engineer Career Paths guide provides detailed frameworks for building career progression in MSPs.

2. Invest in Professional Development

Training budgets are not a cost — they are a retention tool. Allocate $2,000–$5,000 per technician annually for:

• Vendor certifications (Microsoft, CompTIA, AWS, etc.)
• Conference attendance
• Online learning platforms
• Internal knowledge sharing sessions

The investment pays for itself through reduced turnover and improved capability.

3. Recognise and Celebrate Achievement

MSP technicians rarely get recognition for the work they do. Fix that:

• Public recognition. Celebrate wins in team meetings — successful projects, positive client feedback, certifications completed.
• Private recognition. Personal thanks from leadership matters more than most managers realise.
• Peer recognition. Create mechanisms for colleagues to recognise each other.
• Tangible rewards. Bonuses, gift cards, extra time off — small tokens that show appreciation.

4. Give Autonomy and Ownership

Micromanagement kills engagement. Give technicians ownership over:

• Their clients (let them own the relationship, not just the tickets)
• Their work (flexibility in how they approach problems)
• Their schedules (within reason, allow flexibility)
• Their improvement ideas (listen to and act on their suggestions)

5. Improve the Work Environment

• Reduce unnecessary meetings. Every unnecessary meeting is lost productive time.
• Minimise after-hours disruption. Automate what you can, compensate fairly for what you cannot.
• Provide good tools. Slow computers, bad software, and inadequate resources send a clear message: you do not matter.
• Flexible work. Where possible, allow remote or hybrid work arrangements.

6. Build Social Connection

MSPs are often small teams that work intensely together. Leverage that:

• Regular team lunches or social events
• Non-work Slack channels or group activities
• Milestone celebrations (work anniversaries, project completions)
• Mental health support and check-ins

7. Conduct Regular Pulse Checks

Do not wait for annual surveys to measure engagement. Use:

• Weekly or bi-weekly one-on-ones. A 15-minute conversation where the focus is on the person, not the work.
• Quarterly pulse surveys. Short, anonymous surveys that track engagement trends.
• Stay interviews. Ask people what keeps them and what might cause them to leave — before they have one foot out the door.

The Business Case for Engagement

Disengagement is expensive:

• Turnover costs. Replacing an MSP technician costs $50,000–$100,000+ when you factor in recruitment, onboarding, lost productivity, and client impact.
• Productivity loss. Disengaged employees produce 18% less output than engaged ones (Gallup).
• Quality impact. Disengaged employees make more mistakes, which creates rework and client dissatisfaction.
• Culture damage. Disengagement spreads. One disengaged employee can poison a team.

Engaged employees, conversely, are your competitive advantage. They deliver better service, stay longer, and attract other good people.

Related Guides

• MSP Employee Retention Strategies — Structural retention tactics
• MSP Engineer Career Paths — Building career ladders
• MSP Work-Life Balance Guide — Preventing burnout
• MSP Employee Burnout Statistics — Understanding the scale of the problem
• MSP Employee Training Programs — Professional development frameworks

Your MSP promised the migration would take six weeks. It has been four months. The budget has doubled. Nobody can explain why.

IT project failure is endemic in the MSP industry. The causes are predictable: unclear requirements, poor scope management, inadequate planning, and communication breakdowns. The solution is not complicated — it requires disciplined project management methodology applied consistently.

Whether you are migrating to the cloud, implementing new security tools, or restructuring your infrastructure, how your MSP manages the project matters as much as their technical capability.

Project Management Approaches

Waterfall

Sequential, phase-based approach where each phase must complete before the next begins.

Best for: - Well-defined projects with clear requirements - Infrastructure migrations and replacements - Compliance implementations - Projects with fixed scope and timeline

Structure: 1. Requirements gathering and documentation 2. Design and planning 3. Implementation 4. Testing and validation 5. Deployment and handover 6. Post-implementation review

Advantages: Clear structure, predictable timeline, fixed scope, straightforward budgeting.

Disadvantages: Inflexible to changes, late discovery of issues, limited client involvement during delivery.

Agile/Iterative

Incremental approach with work delivered in short cycles (sprints), allowing for ongoing refinement.

Best for: - Projects with evolving requirements - Application development and customisation - Digital transformation initiatives - Projects requiring frequent client input

Structure: 1. Product backlog creation 2. Sprint planning 3. Sprint execution (1-4 weeks) 4. Sprint review and demonstration 5. Sprint retrospective 6. Repeat until complete

Advantages: Flexibility, early value delivery, continuous improvement, high client involvement.

Disadvantages: Less predictable timeline and budget, requires active client participation, can be difficult to estimate total cost upfront.

Hybrid

Combines Waterfall structure with agile flexibility. Most MSPs use this approach.

Best for: - Complex projects with defined phases but evolving detail - Projects involving both infrastructure and application components - Environments where requirements may change during delivery - Most real-world MSP projects

Structure: 1. High-level phases defined (Waterfall) 2. Detailed planning within each phase (agile) 3. Phase gates for approval before proceeding 4. Iterative delivery within phases 5. Regular review and adjustment

The MSP Project Lifecycle

Phase 1: Initiation

What happens: - Business case development - Stakeholder identification - High-level scope definition - Preliminary budget and timeline - Go/no-go decision

Your role: - Define business objectives and success criteria - Identify key stakeholders and decision-makers - Approve the business case - Authorise the project to proceed

Phase 2: Planning

What happens: - Detailed scope documentation - Work breakdown structure - Resource allocation - Timeline with milestones - Risk assessment and mitigation plan - Communication plan - Budget finalisation

Your role: - Review and approve the project plan - Provide access to necessary resources and information - Agree on communication cadence and format - Sign off on budget and timeline

Phase 3: Execution

What happens: - Work is carried out according to the project plan - Regular status reporting - Issue and risk management - Change control management - Quality assurance activities

Your role: - Participate in status meetings - Make decisions promptly when needed - Approve change requests - Provide feedback on delivered increments

Phase 4: Monitoring and Control

What happens: - Track progress against plan - Manage deviations and corrective actions - Control scope, schedule, and budget - Quality reviews and testing - Stakeholder communication

Your role: - Review progress reports - Escalate concerns promptly - Participate in testing and validation - Approve or reject deliverables

Phase 5: Closure

What happens: - Final deliverable handover - Documentation completion - Knowledge transfer - Post-implementation review - Lessons learned - Transition to ongoing support

Your role: - Accept final deliverables - Confirm operational readiness - Participate in post-implementation review - Approve project closure

Critical Success Factors

1. Clear Requirements

The single biggest predictor of project success is clear, documented, agreed-upon requirements. Ambiguity in requirements leads to scope creep, cost overruns, and dissatisfaction.

Best practice: - Document all requirements before work begins - Get written sign-off on the requirements document - Establish a change control process for requirement changes - Distinguish between "must have" and "nice to have"

2. Scope Management

Scope creep is the most common cause of MSP project overruns. It happens when changes are made without formal assessment and approval.

Scope control process: 1. Change requested (by either party) 2. Impact assessment (cost, timeline, risk) 3. Change request documented 4. Decision made (approve, reject, defer) 5. Project plan updated 6. Communication to all stakeholders

Rule: No change proceeds without documented approval. This protects both you and the MSP.

3. Communication

Poor communication kills projects. Your MSP should provide:

• Weekly status reports — progress, issues, risks, next steps
• Immediate escalation — of any issue that threatens timeline, budget, or quality
• Milestone reviews — at each major phase completion
• Executive updates — summary for leadership at agreed intervals

4. Risk Management

Every project has risks. The question is whether they are identified, assessed, and managed.

Your MSP should maintain: - A risk register with probability and impact assessment - Mitigation plans for high-priority risks - Regular risk review during status meetings - Escalation procedures when risks materialise

5. Quality Assurance

Quality is not tested in at the end — it is built in throughout.

Quality practices: - Peer reviews of technical work - Testing at each phase, not just at the end - User acceptance testing before go-live - Rollback plans for every deployment - Post-implementation monitoring

Project Governance

Steering Committee

For significant projects, establish a steering committee:

• Composition: Executive sponsor, project manager (MSP), technical lead, key stakeholders
• Frequency: Monthly or at phase gates
• Purpose: Strategic decisions, scope approval, budget authority, issue escalation

Decision-Making Framework

Define upfront how decisions will be made:

Red Flags in MSP Project Management

No formal project plan. If the MSP cannot show you a detailed project plan with milestones and dependencies, they are not managing the project.

No change control. If changes are being made without documented approval, scope will balloon.

Poor communication. If you are learning about delays from users rather than the MSP, communication has failed.

No risk management. If the MSP cannot identify project risks, they are not planning adequately.

Resource churn. If the project team keeps changing, institutional knowledge is being lost.

Over-reliance on one person. Key person dependency on the project team creates risk if that person is unavailable.

Related Guides

• MSP Service Delivery Metrics — Measure project delivery performance
• MSP Account Management Best Practices — Relationship management during projects
• MSP Contract Negotiation Tips — Negotiate project terms
• MSP Quality Management System — Quality frameworks for delivery
• MSP Digital Transformation Guide — Planning digital initiatives

Risk is inherent in IT service delivery. The question is not whether risks exist, but whether they are identified, assessed, and managed effectively. Here is a practical risk management framework for MSPs and their clients.

Why Risk Management Matters

Without a structured approach to risk:

• Risks are discovered only when they materialise
• Mitigation is reactive rather than proactive
• Resources are allocated based on perception, not analysis
• Client confidence erodes when things go wrong
• Compliance requirements may not be met

The Cost of Poor Risk Management

The Risk Management Cycle

1. Risk Identification

Identify risks across all categories:

Operational Risks: - Service delivery failures - Staff turnover and key person dependency - Process failures and documentation gaps - Capacity constraints

Technical Risks: - Cybersecurity threats and vulnerabilities - System failures and downtime - Data loss or corruption - Integration failures

Strategic Risks: - Market changes and competitive pressure - Technology obsolescence - Client concentration risk - Revenue concentration risk

Compliance Risks: - Regulatory non-compliance - Contractual breaches - Insurance gaps - Audit failures

Financial Risks: - Cash flow disruption - Cost overruns - Pricing pressure - Client payment defaults

2. Risk Assessment

Assess each identified risk using likelihood and impact:

Risk Score = Likelihood × Impact

3. Risk Treatment

For each significant risk, choose a treatment strategy:

Avoid: Eliminate the risk by not undertaking the activity. - Example: Not offering a service you cannot deliver reliably.

Mitigate: Reduce the likelihood or impact of the risk. - Example: Implementing redundant systems to reduce outage impact.

Transfer: Shift the risk to another party. - Example: Purchasing cyber insurance to transfer breach costs.

Accept: Acknowledge the risk and accept the consequences. - Example: Accepting that a specific legacy system carries higher risk.

4. Risk Monitoring

Continuously monitor risks and control effectiveness:

• Key Risk Indicators (KRIs) — metrics that signal increasing risk
• Regular reviews — monthly or quarterly risk reviews
• Incident analysis — learning from events that occur
• External scanning — monitoring threat landscape and regulatory changes

MSP-Specific Risk Categories

1. Cybersecurity Risk

The most significant risk for MSPs:

Our Cyber Insurance MSP Requirements guide covers cybersecurity risk in detail.

2. Key Person Risk

Dependency on specific individuals:

3. Vendor Risk

Dependency on third-party providers:

Our MSP Vendor Lock-In Avoidance guide covers vendor risk management.

4. Compliance Risk

Failure to meet regulatory requirements:

Our Essential 8 Implementation Checklist covers compliance risk management.

5. Financial Risk

Business viability and profitability:

Our MSP Profit Margin Analysis covers financial risk management.

Client Engagement in Risk Management

What Clients Should Expect

• Risk transparency — MSP should communicate key risks and mitigations
• Regular reporting — risk status included in QBRs and reports
• Incident communication — prompt notification of risk events
• Remediation plans — clear plans for addressing identified risks

Client Risk Responsibilities

While the MSP manages technical risks, clients retain responsibility for:

• Business risk decisions (which risks to accept)
• Compliance requirements (regulatory obligations)
• User behaviour (training and awareness)
• Budget allocation (funding risk treatment)

The Risk Conversation

Quarterly Business Reviews should include:

1. Risk landscape update — new threats and vulnerabilities
2. Control effectiveness — are current mitigations working?
3. Residual risk assessment — what risks remain after controls?
4. Risk appetite alignment — are risks within acceptable levels?
5. Remediation priorities — what needs attention next?

Risk Reporting

Risk Dashboard

A practical risk dashboard includes:

Risk Register

Maintain a risk register that includes:

• Risk description
• Risk owner
• Likelihood and impact ratings
• Current controls
• Residual risk rating
• Treatment plan
• Target completion date
• Status updates

The Bottom Line

Risk management is not a compliance exercise — it is a business discipline that protects your clients, your reputation, and your bottom line. MSPs that manage risk proactively build stronger client relationships and more resilient businesses.

The framework does not need to be complex. Start with identifying your top 10 risks, assess them honestly, and implement treatments for the most significant ones. Build from there.

Use our MSP Health Score to benchmark your risk management maturity, or our Cyber Insurance Guide for cybersecurity risk management.

Remote Monitoring and Management (RMM) software is the backbone of every MSP's operations. It is the tool that monitors client environments, deploys patches, runs scripts, and provides remote access — all from a single pane of glass. Choosing the right RMM is one of the most consequential decisions an MSP (or an MSP's client) can make.

What RMM Actually Does

RMM software sits on every managed device — servers, workstations, laptops, and sometimes network equipment. It provides:

• Real-time monitoring: CPU, memory, disk, and network metrics with alerting
• Patch management: Automated deployment of OS and application updates
• Remote access: Technician can take control of a device without on-site visit
• Scripting and automation: Run pre-built or custom scripts across multiple devices
• Endpoint protection integration: Deploy and manage antivirus/EDR from the same console
• Asset inventory: Track hardware, software, and licence compliance
• Ticketing integration: Connect monitoring alerts to PSA ticketing systems

For the client, RMM means issues are often detected and resolved before anyone notices a problem. For the MSP, it is how they manage hundreds or thousands of devices efficiently.

The RMM Market in 2026

The Australian RMM market has consolidated significantly. Several major players dominate, with a few newer entrants gaining traction.

Major RMM Platforms

NinjaOne

• Pricing: ~$3–$5 per device/month (tiered)
• Best for: Mid-sized MSPs seeking a modern, intuitive interface
• Strengths: Excellent UI/UX, strong automation, built-in patch management, good API, integrated endpoint management
• Weaknesses: Newer to market, smaller ecosystem than legacy players, limited PSA integration options
• Australian presence: Growing; local support available

Datto RMM (Kaseya)

• Pricing: ~$2–$4 per device/month (bundled with Kaseya suite)
• Best for: MSPs using the Kaseya/Datto ecosystem
• Strengths: Tight integration with Datto BCDR and Kaseya VSA, good scripting engine, global NOC support
• Weaknesses: Kaseya's brand reputation issues post-Supply Chain Attack, UI feels dated compared to NinjaOne, bundled pricing can lock you into the ecosystem
• Australian presence: Strong; Kaseya has local offices

ConnectWise Automate

• Pricing: ~$2–$6 per device/month (tiered)
• Best for: Large MSPs with complex environments and custom requirements
• Strengths: Highly customisable, powerful scripting and automation, massive feature set, large community and marketplace
• Weaknesses: Steep learning curve, dated UI, can be slow at scale, ConnectWise's pricing complexity
• Australian presence: Established; strong partner network

N-able N-sight / N-central

• Pricing: ~$2–$5 per device/month
• Best for: MSPs managing diverse environments including Mac and Linux
• Strengths: Cross-platform support (Windows, Mac, Linux), good patch management, integrated backup and security modules
• Weaknesses: UI inconsistency between products, support quality varies by region
• Australian presence: Established; local support available

Halo RMM

• Pricing: ~$3–$5 per device/month
• Best for: MSPs seeking an all-in-one platform (RMM + PSA in one)
• Strengths: Integrated PSA, competitive pricing, modern interface, good for smaller MSPs
• Weaknesses: Smaller market share, fewer integrations, less mature automation capabilities
• Australian presence: Growing; UK-based with international support

Emerging Players

Level.io

• Pricing: ~$4 per device/month
• Best for: MSPs seeking a modern, cloud-native RMM
• Strengths: Clean interface, fast deployment, good scripting, competitive pricing
• Weaknesses: Newer platform, smaller feature set, limited integrations

Pulseway

• Pricing: ~$2–$4 per device/month
• Best for: Small MSPs and internal IT teams
• Strengths: Mobile-first design, good for small teams, simple to deploy
• Weaknesses: Limited at scale, fewer automation capabilities, smaller support team

Comparison Matrix

What to Evaluate When Choosing an RMM

1. Your Client Profile

Are you managing 50 devices or 5,000? Small MSPs benefit from simplicity and low cost. Large MSPs need power and customisation.

2. Integration Requirements

Your RMM must integrate with your PSA (ticketing), backup, security stack, and documentation tools. Check the integration ecosystem before committing.

3. Patch Management Capability

Patch management is one of the RMM's most critical functions. Evaluate: - How quickly do patches deploy after release? - Can you set maintenance windows? - How does it handle reboots? - Does it support third-party application patching? - Can you report on patch compliance?

This directly affects your Essential 8 compliance. See the Essential 8 Maturity Level 1 requirements.

4. Automation and Scripting

The scripting engine is where an RMM delivers real efficiency. Evaluate: - What scripting languages are supported? - Can you schedule recurring tasks? - Can you trigger scripts based on alerts? - Is there a library of pre-built scripts?

5. Security Features

RMM tools are high-value targets for attackers. Evaluate: - Does the vendor support MFA on all accounts? - Can you implement least-privilege access for technicians? - Are audit logs available for all actions? - Has the vendor experienced security incidents?

The Kaseya VSA attack demonstrated what happens when RMM security fails. Always prioritise vendor security posture.

6. Australian Support

Time zones matter when you have an urgent issue. Evaluate: - Does the vendor offer Australian support hours? - Is there a local office or partner? - What are the support response times?

For Clients: What Your MSP's RMM Choice Means for You

If you are evaluating an MSP, ask about their RMM:

1. What RMM do you use, and why did you choose it? A good MSP has a considered answer.
2. How do you handle patch management through the RMM? They should be able to show you compliance reports.
3. What alerts do you monitor, and what is your response process? This tells you whether they use RMM proactively or reactively.
4. How do you secure your RMM access? If they do not use MFA on RMM access, that is a critical security gap.
5. Can you show me a patch compliance report for our environment? If they cannot, they are not using the tool effectively.

The MSP Health Score includes RMM maturity as a key indicator of operational capability.

Related Guides

• Essential 8 Maturity Level 1 — Patch management requirements
• MSP Backup and Disaster Recovery — How RMM integrates with BCDR
• MSP Technical Documentation — What your MSP should document
• MSP Health Score — Benchmark your MSP's operational maturity
• How to Choose an MSP — Evaluating MSP capability

NTT Data's A$677K revenue per employee is the highest of any major Australian MSP. It's also the most misleading number in the industry.

That figure doesn't mean NTT employees are extraordinarily productive. It means NTT has very few Australian employees relative to its revenue — because most of the work is done offshore.

The Numbers

Average salary (Australia): A$95,000-110,000 Glassdoor rating: 3.5/5

The Offshore Model

NTT Data's business model is built on a simple arithmetic:

1. Win contracts with competitive pricing (driven by offshore labour)
2. Deliver from India where engineers cost A$15,000-30,000/year
3. Maintain a thin onshore layer for client relationships and sales
4. Collect the margin between what clients pay (Australian rates) and what staff earn (Indian rates)

The A$677K revenue per employee is the result: each Australian employee "supports" a disproportionate amount of revenue because the actual delivery work happens offshore.

What This Means for Onshore Staff

You're a bridge, not a builder. Onshore staff at NTT exist primarily to manage client relationships and bridge the gap between Australian expectations and Indian delivery. The actual technical work increasingly happens offshore.

Career ceiling. When the work moves offshore, career progression slows. There are fewer projects, fewer promotions, and less reason to stay.

Cultural friction. Managing offshore teams requires different skills than doing the work yourself. Some people thrive in this role; others find it frustrating.

Employee Experience

The Good

Competitive salaries. NTT pays better than Datacom and DXC for comparable roles. The average of A$95,000-110,000 is closer to market rate.

Global opportunities. NTT's 190,000+ employee base means potential transfers to other countries. This is a genuine advantage for people who want international experience.

Technology exposure. NTT invests in emerging technologies (AI, cloud, IoT) and offers training programs. Some teams work on genuinely innovative projects.

The Bad

Offshore delivery challenges. "The quality of offshore delivery varies wildly." Client satisfaction issues are common when work is handed off to Indian teams without adequate oversight.

Integration complexity. NTT has grown through acquisition (Dimension Data, Dialog, etc.), and the integration is ongoing. Different teams use different tools, processes, and cultures.

Communication overhead. Managing across time zones and cultures adds significant overhead. "A 5-minute conversation becomes a 2-hour process."

The Ugly

The "bridge" role. Onshore staff often feel like they're managing decline rather than building growth. The strategic direction is clear: more offshore, fewer Australians.

What This Means for You

If you're considering NTT: - Ask about the specific team's offshore ratio - The salary is competitive but the career path may be limited - Global opportunities are real — use them if you want international experience - The "bridge" role isn't for everyone — make sure you understand what's expected

If you're a client: - NTT can deliver at competitive prices because of offshore labour - Quality depends on the specific team and oversight level - Insist on named onshore resources with retention guarantees - The A$677K revenue per employee means thin onshore coverage

Based on Glassdoor (600+ Australian reviews), PayScale, IBISWorld, and NTT's own financial disclosures.

Outsourcing IT to a Managed Service Provider is the right decision for many Australian businesses. But outsourcing is not risk-free. The businesses that get the most value from their MSP are the ones that understand the risks and actively manage them.

Here are the real risks of MSP outsourcing, and how to protect your business.

Risk 1: Vendor Lock-In

This is the single biggest risk in MSP outsourcing, and it is the one most businesses underestimate.

Once an MSP embeds their tools, processes, and documentation into your environment, switching costs become enormous. The MSP controls:

• Your RMM (Remote Monitoring and Management) platform
• Your backup infrastructure
• Your documentation and credentials
• Your network monitoring
• Your security tools

If you decide to leave, extracting all of this — on time and in usable formats — is a significant undertaking. Some MSPs make this deliberately difficult.

How to Mitigate Lock-In

• Negotiate exit clauses before signing — data portability, tool transition, and documentation handover provisions
• Avoid single-vendor dependency — use industry-standard tools where possible
• Maintain internal documentation — do not rely solely on the MSP's documentation
• Regular data exports — ensure you have copies of critical data outside the MSP's systems

Our MSP Vendor Lock-In Avoidance guide provides detailed strategies.

Risk 2: Security Concentration

When an MSP manages multiple clients, a single security breach can cascade across all of them. This is not theoretical — it has happened repeatedly in the MSP industry.

The Kaseya VSA attack in 2021 compromised approximately 1,500 businesses through a single MSP tool. The MSP becomes a single point of failure for security.

How to Mitigate Security Concentration

• Verify the MSP's security posture — check their Essential 8 maturity, cyber insurance, and security certifications
• Require transparency — regular security reports and breach notification commitments
• Maintain your own security layers — do not outsource all security responsibility
• Audit the MSP's access — know what access they have and what controls are in place

Our Cyber Insurance MSP Requirements guide covers what security standards to verify.

Risk 3: Loss of Institutional Knowledge

When your internal IT person leaves, their knowledge leaves with them. When your MSP's engineer leaves, the same thing happens — but worse, because the MSP may not even tell you.

MSP staff turnover is high. The engineer who knows your environment intimately may leave the MSP, and the replacement may start from scratch.

How to Mitigate Knowledge Loss

• Require comprehensive documentation — your MSP should document your environment thoroughly
• Demand engineer continuity — negotiate for named primary engineers with minimum tenure
• Attend QBRs — Quarterly Business Reviews keep you informed about your environment
• Maintain internal IT capability — even if it is just one person who understands the basics

Our MSP Technical Documentation guide covers what documentation your MSP should provide.

Risk 4: Hidden Costs

The monthly MSP fee is rarely the total cost. Common hidden costs include:

How to Mitigate Hidden Costs

• Define scope precisely — what is included and what is not
• Cap after-hours rates — negotiate maximum hourly rates
• Require project quotes in advance — no work without written approval
• Audit invoices monthly — compare actual charges to contracted rates

Our MSP Pricing Models guide explains common pricing structures and what to watch for.

Risk 5: Reduced Strategic Control

When you outsource IT, you cede some control over technology decisions. An MSP may recommend solutions that serve their interests (tools they can manage efficiently) rather than yours (the best solution for your business).

This is not always malicious — it is often a function of the MSP's capabilities and partnerships. But it means you may not always get the best technology for your needs.

How to Mitigate Strategic Risk

• Maintain an internal IT advisor — even part-time, someone who can evaluate MSP recommendations
• Require justification for major decisions — the MSP should explain why they recommend specific solutions
• Stay informed — read industry publications, attend events, understand your technology landscape
• Benchmark regularly — compare your MSP's recommendations to market alternatives

Our MSP vs In-House IT guide helps you evaluate the right balance of outsourced and internal capability.

Risk 6: Compliance Gaps

If your MSP mishandles your data, you are still legally responsible. The Privacy Act holds you accountable for your data, regardless of who processes it.

An MSP that does not understand your compliance requirements (Essential 8, Privacy Act, industry-specific regulations) creates risk for your business.

How to Mitigate Compliance Risk

• Verify the MSP's compliance capabilities — Essential 8, ISO 27001, or SOC 2 certification
• Include compliance requirements in the contract — the MSP must meet specific standards
• Conduct regular compliance reviews — ensure the MSP maintains required standards
• Maintain internal compliance ownership — the MSP assists, but you own compliance

Our Essential 8 Implementation Checklist covers baseline compliance requirements.

The Risk Assessment Framework

Before outsourcing to an MSP, assess these dimensions:

The Bottom Line

Outsourcing IT to an MSP is not inherently risky — but it requires active management. The businesses that treat their MSP as a partner they actively oversee, rather than a vendor they ignore, get the best outcomes and avoid the worst risks.

The key is not to avoid outsourcing. It is to outsource wisely — with clear contracts, ongoing oversight, and a realistic understanding of what you are giving up in exchange for the convenience of managed services.

Use our MSP Health Score to evaluate your current MSP relationship, or our How to Choose an MSP guide to make a better selection in the first place.

Whether you're an MSP employee, a business owner evaluating MSPs, or an IT professional considering the MSP industry — this is where you start.

🔥 Most Popular

• The Ledger — Search 60+ MSP profiles with financials, ratings, and red flags
• MSP Salary Guide 2026 — What Australian IT professionals actually earn
• MSP Contract Red Flags — Spot dangerous clauses before you sign
• Red Flag Scanner — Paste a job ad, get instant analysis
• Salary Calculator — See if you're being underpaid

📚 By Topic

For MSP Employees

• 50 MSP Interview Questions — What they really want to hear
• How to Leave an MSP — Your exit strategy
• MSP Burnout Guide — Warning signs and recovery
• Salary Negotiation — Get paid what you're worth
• Best Certifications — What's worth your time and money

For MSP Leaders

• MSP Pricing Models — How to price your services
• Employee Retention — Keep your best engineers
• Client Management — Build lasting relationships
• Profit Margins — Where the money actually goes

For Businesses Evaluating MSPs

• How to Choose an MSP — What to look for
• MSP vs In-House IT — Cost comparison
• MSP Health Score — Rate your MSP in 2 minutes
• Compare MSPs — Side-by-side comparison tool

🛠️ Interactive Tools

📊 Deep Dives

• Capgemini Investigation — Inside Australia's biggest MSP
• Private Equity Playbook — How PE firms extract value
• The Broken MSP Model — Why the industry needs change
• Offshore Arbitrage — The math behind offshoring