How Step Fwd IT made security non-negotiable with Kaseya

Reading time: 9 min

Case study Highlights

  • A mandatory security stack for every new customer, built on Kaseya
  • About 80 clients and 2,000 endpoints supported by a 100% Australian team
  • Average response times cut from more than two hours to under one hour
  • About 30 hours a week saved with AI ticket triage in Autotask
  • Fewer than 2% of 2,200 security alerts became customer-affecting incidents in a 12-month period
  • 100% of tickets that can be automated are now automated
  • A large-scale SharePoint deletion caught by SaaS Alerts and resolved within minutes

A Melbourne MSP built on steady growth 

Step Fwd IT is a managed service provider (MSP) based in Melbourne, Australia. CEO and Founder Chris Mannering started the business nearly 17 years ago as a side hustle. At the time, he and his wife had a young child and a second on the way, with about six months of savings socked away. He asked for three months to make it work. Within two months, the business was making money. 

Today, Step Fwd IT employs just under 30 staff and supports about 80 clients across roughly 2,000 endpoints. Customers fall into two groups: K–12 Catholic, independent and private schools, and small and midsize businesses (SMBs). A typical SMB client has 20 to 50 seats, though some have as few as five staff and others have 100 to 200. 

Mannering has never chased fast growth. 

“We’re not a rocket ship. Rockets go up really fast and then explode. We like to glide and keep moving, slow and steady.” 

Chris Mannering, CEO and Founder at Step Fwd IT

Every Step Fwd IT service is delivered from Australia. The MSP team works in two pods of four engineers. Each pod has a service desk engineer for level one requests, a senior engineer and two technical alignment managers. Every client also has a primary engineer. 

Vassily Scepanovic, technical alignment manager and Orange Pod team leader, has worked at three other MSPs. None of them ran this way. “We have a primary engineer for each client, so that primary engineer is able to develop a relationship with the customer, more so than a free-for-all with the whole team going for tickets,” said Scepanovic. 

Tool sprawl and à la carte security 

Before standardizing, Step Fwd IT let engineers pick their own products. The team also inherited software from new customers, so no two environments looked the same. 

“Engineers had their favourite brands and logos, and we inherited some software from customers as well,” said Mannering. “Every customer was different. We had to learn different systems and processes, and you couldn’t be an expert in every single one of them.” 

General Manager of Operations Tim Scholes saw the cost on the service desk. Engineers jumped between interfaces, each with its own login. Every new tool added to the training load. 

Security followed the same pattern. Step Fwd IT recommended protection to all of its clients, but customers decided what to buy, and some refused to pay for endpoint detection and response (EDR). During that period, the business saw an influx of account compromises, more device incidents and more ransomware. 

“From a leadership perspective, it’s quite stressful knowing that your customers are vulnerable and that they’re a moment away from a catastrophic incident.” 

Tim Scholes, General Manager of Operations at Step Fwd IT

Scholes also worried about Step Fwd IT’s reputation if a major client ended up in the media after an incident. 

The customer loss that forced a decision 

Then Step Fwd IT lost a large customer. A postmortem found the customer’s internal IT account had been compromised, one of the most common attack vectors. The attackers sat in the environment for a while, working out when to strike and which systems to cripple. 

Step Fwd IT recovered the environment, but the operational disruption for the customer was huge. The customer agreed the compromise wasn’t Step Fwd IT’s fault and moved on anyway. Mannering puts it down to not being firm enough about what that customer needed. 

“Enough’s enough. We need to have a standard, and we need to be confident to price it and tell them, this is what you have to have to be a customer of ours.” 

Chris Mannering, CEO and Founder at Step Fwd IT

Drawing a line in the sand 

Step Fwd IT built a mandatory security stack around Kaseya. Every new customer gets the same baseline of endpoint, identity, email, security awareness, backup and detection and response. 

Now, Datto RMM handles remote access, patch management, third-party software updates and automated remediation. Datto EDR runs on every managed endpoint as part of the base end-user support pack. Kaseya’s managed detection and response (MDR) service monitors clients 24/7. INKY protects email against phishing and impersonation attacks. SaaS Alerts and Dark Web ID watch for compromised identities inside and outside Microsoft 365. BullPhish ID trains users, and Spanning backs up Microsoft 365 data. Autotask and IT Glue tie the service desk together. 

Mannering explains the stack to customers in three phases: education and prevention, minimizing how wide an attack can spread, and recovery. 

“Nowadays we’re not protecting the corporate environment. We’re protecting the user. They’re the entry point. That’s where most of the attack vectors happen.” 

Chris Mannering, CEO and Founder at Step Fwd IT

Selling the standard to existing customers 

The new standard came with a price increase, and Mannering expected some customers to walk. The team talked openly with each one about why the business was making the shift and what it would cost them. 

“Because we were open and transparent, we found that most of the time they accepted the price. They didn’t even go to market,” he said. 

Some customers already had security subscriptions in place. Step Fwd IT let those run until they expired, then replaced them with products from the new stack. The company also had to invest to bring every customer up to the baseline. Mannering calls the process a slow burn. Standardization also showed which clients were profitable. Before, pricing each customer was a gamble. 

“Now we’ve got a clear line about what it costs us to service that customer from a toolkit perspective,” said Mannering. “Then you put your engineering costs over that.” 

Early detection across 2,200 alerts 

Step Fwd IT’s engineers can’t staff the service desk around the clock, so Kaseya MDR monitors and remediates incidents 24/7. That cuts on-call time for the team and reduces costs for clients. It also gives engineers security experts to escalate to and ask for advice. 

When an attack starts, Datto EDR isolates the device to limit its severity. MDR then shows the history and pattern of the attack across the user account and the device. Scepanovic’s team usually calls the client before locking an account, since some users get upset if they’re locked out without warning. 

Over the past 12 months, about 2,200 security alerts reached the team. Fewer than 2% became incidents that affected a customer. Step Fwd IT shares those numbers in monthly reports and quarterly technical alignment meetings. 

“It definitely helps us as a leadership team sleep easy, knowing that our customers are protected and that our teams are equipped with the right tools, consistent processes and consistent tools to manage any incident.” 

Tim Scholes, General Manager of Operations at Step Fwd IT

Prevention starts in the inbox. INKY’s banners teach users to spot malicious email, which reduces the tickets the team receives. BullPhish ID sends monthly phishing simulations and security awareness training. Right now, much of that training covers using AI safely. 

Mannering sees Step Fwd IT’s role in AI adoption clearly. “As an MSP, we want to keep the environment safe and secure but not be roadblocks,” he said. “We need to be the guardrails to allow them to use this technology.” 

Catching a SharePoint deletion in minutes 

SaaS Alerts flagged a large-scale deletion of SharePoint files at one client before the customer knew their data was disappearing. The alert came fast enough for the team to respond within minutes. Engineers isolated the user account and reviewed the incident. 

The deletion turned out to be non-malicious user error. The team restored the deleted files with Spanning and walked the affected user through what happened. Scholes says the customer was extremely appreciative of both the catch and the speed of the response. 

“That’s what proactive security looks like. Not recovering after the damage has been done, but preventing the problem from getting there in the first place.” 

Chris Mannering, CEO and Founder at Step Fwd IT

One portal, one login, one process 

With the same baseline at every customer, engineers now follow the same process every time. Scholes says the products’ integration made the biggest difference. Device insights appear directly in Autotask tickets, so engineers can see what an alert relates to. Standard operating procedures from IT Glue sit one click away in the ticket. A similar interface across the stack cuts training when the team adds a new tool. 

“We’re not going across multiple applications at a time. We know exactly what stack each customer has,” said Scepanovic. 

IT Glue also changed how new technicians get up to speed. Instead of going in blind or asking colleagues, they can open each customer’s documentation and act on it themselves. “Everyone on the team, it’s like a lifesaver for us,” said Scepanovic. 

Over the past 12 to 24 months, average response times dropped from more than two hours to well under one hour. 

“It’s the saving of the clicks here and there. Having all the information within one, two or three clicks in a consistent platform has improved the efficiency of the team immensely.” 

Tim Scholes, General Manager of Operations at Step Fwd IT

Automation that keeps support 100% local 

Keeping every role at Step Fwd IT within Australia is a commitment to clients. It also makes Step Fwd IT’s support among the most expensive to deliver. Mannering relies on automation to close that gap. 

“We’re now reaching [the level where] 100% of our tickets that can be automated are automated,” he said. “And we’re now looking at how we create more automations.” 

AI ticket triage in Autotask now sorts tickets by issue and sub-issue type. Engineers click apply and move on. Scholes estimates it saves about 30 hours a week. Datto RMM quick jobs handle patching, PowerShell scripts and application installs. 

“We’re not reviewing tickets and categorizing them and assigning them. It allows our team to focus on driving value for our business and for our clients.” 

Tim Scholes, General Manager of Operations at Step Fwd IT

Advice for MSPs ready to standardize 

Mannering says growth is uncomfortable for MSPs, especially when every new hire has to learn so many different applications. A single platform changes that. 

“If we’ve got a single platform with a single training module around it, it just makes life easy,” he said. 

The pod structure means customers keep working with an engineer they know and trust as the business grows. His advice to other MSPs is brief but strong: “Standardization is a key one. That helps you build process, repeatability and scalability.” 

Case studies

Curious to explore more?

How Kalgoorlie IT consolidated its tools and reduced reliance on its owner with Kaseya

How Kalgoorlie IT consolidated its tools and reduced reliance on its owner with Kaseya

Read now
Viadex cuts after-hours alerts 83% with Autotask

Viadex cuts after-hours alerts 83% with Autotask

Read now
Circle Cloud cuts ticket response time in half with Datto RMM

Circle Cloud cuts ticket response time in half with Datto RMM

Read now