Share this
by Josefine.Fouarge on Jul 8, 2026 8:00:05 AM
Small businesses need an IT department, yet most can't justify hiring one. This is precisely the niche that one-person MSPs fill, and some have been doing so successfully for ten, fifteen, or even twenty years. The difference between running a sustainable, profitable business without a team and burning out comes down to a handful of decisions.This blog covers those decisions, including what to take on, what to turn down, and how to structure services, using a managed backup offering as an example, so that work doesn't become overwhelming.
Table of Contents
- What Does a Working One-Person MSP Actually Look Like?
- How Do Solo MSPs Avoid Burnout? Three Structural Problems
- How Do the Solo MSPs Who Last Design Their Businesses Differently?
- How Should a One-Person MSP Set Up A Managed Backup Service?
- The Bottom Line
- Frequently Asked Questions
What Does a Working One-Person MSP (or One-Man MSP) Actually Look Like?
A typical one-person MSP serves small, local businesses with 1–10 employees that don't have, or can't justify, a full-time IT department. These businesses include dental and medical practices, law firms, accounting firms, manufacturing, and trade companies, usually within a 30–50 mile radius. They need someone who can be their expert in all things IT and not just someone who fixes things when they break.
| Client Types | Small local businesses: medical, legal, trades, professional services |
| Endpoint count | Typically, 1–2 servers and anywhere from 1 to 25 workstations depending on client size. It's possible to reach 400–500 endpoints, but only if you're willing to standardize aggressively and limit your client base. |
| Pricing floor | $150–200/user/month and more, depending on location and services included, for a complete managed stack |
| Revenue model | Managed retainer + light projects + selective reselling |
Three examples that illustrate the range.
- Tony Linton has been running TLC Netcon independently since 2009, serving a 50-mile radius around Farmersville, Texas. His clients range from chiropractors to manufacturers, feed stores, and city services. Some have only one workstation. His largest client has 15–25 endpoints and multiple servers.
- Michael Gustine has been running MG Technology for over 20 years, supporting individuals and small businesses in Columbus, Ohio. He started with on-site break-fix work and has transitioned to a managed services model by adding cloud backup and remote management. This allows him to reduce time on the road while building recurring revenue.
- Steve Oldham has been running Oldham Consulting out of Cumming, Georgia, since 1991. He uses one platform with central monitoring and backup for every client across the metro area and supports a redundant local and offsite backup strategy for all of them as standard.
How Do Solo MSPs Avoid Burnout? Three Structural Problems (and What to Do About Them)
Running a one-person MSP means handling support, sales, billing, accounting, vendor management, and engineering simultaneously. There's no one to hand anything off to, and no buffer when multiple things go wrong at once.
While being responsible for everything comes with drawbacks, it can turn into a great business when set up strategically.
Everything Lives in Your Memory
You typically juggle three to six active tasks concurrently, switching between RMM dashboards, remote sessions, client calls, and vendor emails while maintaining a mental inventory of each client's environment. And you know the quirks of each of your clients' settings too: the accounting firm's firewall that drops the VPN connection after a firmware update, the dental practice's server that triggers an alert when the receptionist unplugs the wrong cable, and the manufacturing company's inherited mess that was never documented before you took it over.
If that state only exists in your memory and not in a database, every context switch can cause errors or cause things to fall through the cracks. While you're away due to vacation, illness, or an emergency, work grinds to a halt because no one else is available.
Documentation is the solution.
- Credentials are stored in a vault.
- IP addressing is documented.
- Server roles and application dependencies are written down.
- Vendor contacts are recorded.
Documentation is also relevant even before you consider hiring someone who would need access to that information in the future. For example, if you're on-site with one client and another calls with a critical issue that you haven't worked on in four months, the documentation will prove invaluable.
The Billable-Hours Treadmill
Conversely, any time spent documenting customer details, automating processes, or improving procedures is not billable. Therefore, it always loses to the next ticket.
To break this pattern, do two things.
- First, explicitly schedule non-billable engineering time as a fixed block, typically 30–60 minutes at the end of the week, rather than waiting for "things to slow down."
- Second, identify one task that constantly recurs and costs time every week. For example, it could be a manual user onboarding process, a patching routine that is run manually, or a recurring report that is pulled manually. Then, eliminate it.
It may not feel productive at first, but after six months, you'll see fewer interruptions, fewer errors, and fewer hours spent on work that should have been systematized long ago.
You Still Need a Backup
At some point, a prospective client may ask what would happen if you were unavailable. This is a common objection that one-person MSPs face. The practical answer is to have a peer coverage arrangement with another solo MSP. This person should be someone you trust who serves a complementary geography or client type. They should be able to handle true emergencies while you're out, and vice versa.
This arrangement works best when it's based on an existing relationship. For example, imagine two solo MSPs in the same city who work alongside a complementary IT business, but who offer different services. They have built a relationship based on years of mutual trust, and neither crosses into the other's client base. However, when one is unavailable, the other can step in.
For arrangements that go beyond a handshake, the following elements are worth agreeing on upfront:
- Client ownership: your partner covers emergencies but doesn't solicit your clients
- Communication: how they log tickets, escalate issues, and report back to you
- Billing: whether you pay per incident, per hour, or reciprocate in kind
- SLA alignment: if your contract promises a four-hour response time, your partner needs to know that
This is where documentation also comes in handy. A peer can only help if they can find what they need.
How Do the Solo MSPs Who Last Design Their Businesses Differently?
In order to stay in business long-term, you must make deliberate decisions about what your business is and isn't, and then adhere to those decisions when dealing with clients. If you don't set boundaries, your business will adapt to whatever your clients dream up, which is usually too much for one person to sustain.
Standardize the Stack
Start by standardizing your stack. For example, use one RMM, one security solution, and one backup platform, plus choose consistent hardware across clients.
Next step is to standardize the procedures for each of your solutions. For backup, a solid standard setup for a small business client could look like this (more details on that below):
- Local storage, such as a NAS device, as the primary backup target.
- Dedicated cloud storage for the offsite copy.
- Nightly incremental forever backups to local and cloud storage for standard data, as well as more frequent backups for business-critical files.
- 30-day retention is the standard baseline for most SMB clients. Regulated industries might need longer.
- Light monthly and full quarterly restore tests.
Steve Oldham transitioned from managing separate licenses for each customer to a single platform with a standardized, centralized monitoring service for all of them.
However, standardization only works if it is enforced. Either new clients adopt your stack, or the work is scoped as a project and billed accordingly. Clients who push back on this are showing you how they'll behave regarding everything else.
Curate the Client Base, Which Means Firing Clients if Necessary
Clients who push back on your standard setup usually generate the most support overhead. They insist on using their preferred tool, refuse upgrades, and call outside your SLA. A client with three users at $150 per user per month brings in $450 per month. However, if they consume four hours of your time each month with calls, exceptions, and one-off requests, your revenue disappears before you can cover their fixed costs.
A practical solution would be to introduce a minimum that reflects the actual cost of onboarding and maintaining a client relationship. For example, there could be a $2,000 monthly minimum or a 10-seat minimum, meaning clients below that threshold could be billed as if they had 10 seats. Otherwise, they can be transitioned to a lighter-touch model with a clearly defined, no-SLA offering.
A more drastic option is to terminate a client who doesn't fit your model. It's not worth supporting them if you're paying to keep them.
Set SLAs You Can Actually Hit
A 24/7 response time is unrealistic for a one-person business. Solo MSPs who attempt to consistently deliver it often cite it as the main reason they burn out or leave the business model.
The value you offer isn't round-the-clock coverage, but rather direct access to you, the owner, who has a personal understanding of their environment. This is more valuable to most small business clients than a guaranteed 30-minute response time from an unfamiliar technician.
The practical version looks like this:
- Business hours response with a defined time frame (4 hours is common)
- A clear definition of what qualifies as an after-hours emergency
- An honest conversation with every new client about what a one-person operation can and cannot deliver
Clients who agree to these terms upfront are easier to serve.
Build Toward Recurring Revenue; Step Away From Break-Fix
The break-fix model is exhausting for a one-man MSP. Every job starts from scratch. You have to renegotiate the scope every time and hunt for the next job while handling the current one. With every invoice, you give clients a reason to question your rate or shop around. Monthly recurring models with a defined scope eliminate all that, making your income more predictable and putting less strain on your relationship with clients.
Michael Gustine provided on-site IT support and break-fix services to a loyal client base for most of his career. After seeing NovaBACKUP Managed Backup in use at a colleague's business, he made the switch. Now, he monitors all local and cloud backups from his desk, enjoys a fixed monthly income, and incurs fewer costs from not having to drive around constantly. His goal is to grow his backup customer base by 17–25% by the end of the year without increasing his workload.
Clients respond to the change, too. With a flat monthly fee, they no longer hesitate to call, so problems are reported earlier and small issues don't become emergencies.
The transition from break-fix to managed backup is easier than most IT resellers expect. You don't need to overhaul your entire business model. Start with a few clients and one service at a time.
Michael Gustine's bundled offering includes NovaBACKUP Managed Backup, a solution for endpoint protection, as well as remote management. All of this is packaged together under a single, fixed monthly fee.
For example, most clients of one-person MSPs are small businesses. Think of a dental practice, a law office, or a carpenter. They typically back up one server and one or two workstations. They usually require a maximum of 500 GB of cloud backup storage.
Your cost for the backup solution:
| Per client/month | |
|---|---|
| 1 server @ $20/server | $20.00 |
| 1 PC @ $4/PC | $4.00 |
| Cloud storage (up to 500 GB @ $0.05/GB) | $25.00 |
| Your cost | $49/month |
With a gross margin of 50–70%, you're charging clients approximately $100–$150 per month. With ten clients, you'll earn $1,000–$1,500 per month in recurring backup revenue, compared to a cost of $490 per month. This can be managed with one dashboard and takes approximately 30–45 minutes per week to monitor.
The cost for larger clients with multiple servers or workstations will be higher, but your margin will scale with them. The point is that a modest portfolio of small-business clients can generate significant recurring income with minimal ongoing overhead.
How Should a One-Person MSP Set Up A Managed Backup Service?
A one-person MSP typically sells backup as part of a broader security and managed services offering rather than as a standalone product. This section focuses specifically on backup because it's a concrete example of how to build, price, and manage a recurring service properly, and because backup is our area of expertise at NovaBACKUP. The same principles apply to the rest of your stack, too.
Backup protects your reputation. If a client loses data, you are going to lose that client, and they will become a potential liability. At the same time, backup creates a predictable monthly revenue stream. To achieve this, you need the right pricing structure, a standard setup that can be replicated across clients, and services that require minimal ongoing attention once configured correctly.
Pricing It Correctly: A Worked Example
Begin by establishing your cost baseline, which includes your platform cost per client, the time required to manage each client monthly (including monitoring, testing, and reporting), and your overhead for restore testing. Then, add your margin target. A gross margin of 50–70% is both achievable and standard for a managed backup service.
Solo MSPs tend to undercharge when they treat backup as a per-license sale. This also invites direct price comparisons with any vendor a prospect can find online. However, you're actually selling a defined recovery objective, documented monthly testing, and the assurance that someone is monitoring the process.
Michael Gustine's clients responded positively to switching from hourly billing to a fixed monthly fee because it made their expenses more predictable.
A starting framework for SMB clients could look like this:
- Base: daily backups, 30-day local / 90-day cloud retention, monthly restore verification. Around $75–150/server/month, $10–25/endpoint/month.
- Premium: shorter RPO/RTO commitments, immutable copies, compliance documentation for HIPAA or cyber insurance audits. Around $150–300/server/month.
Another important addition to every contract is an annual price adjustment clause. Clients who have received twelve months of restore test reports are unlikely to leave because of a 5% increase. However, clients who have never seen proof of your work might.
Central Management Is Non-Negotiable
If you have to remotely access every client to check the backup status, then you have already failed the minimal-attention test.
A central backup management console makes all of your clients' backups visible on one dashboard. Failed jobs and jobs with warnings are color-coded on the dashboard, so reviewing last night's jobs in the morning takes less than a minute and covers every client. Additionally, new clients can be onboarded centrally, backup jobs can be edited without touching the endpoint, and agent updates can be pushed remotely.
Michael Gustine sums it up nicely: "With remote management, I can protect my clients' data without leaving my desk. That's exactly what I need."
The dashboard also shows the backup size history for each client. If a client's data is growing faster than expected, the trend will show it before it results in an unexpected cost on your bill.
Design for Your Standard Client, Not Your Worst Case
Your standard backup offering should be based on a hybrid backup strategy that includes both local and cloud backup in a single job. Local backups address everyday losses such as accidental deletion, failed hard drives, and ransomware attacks. Cloud backups handle site-level events, such as fire, flood, or theft, that destroy the local copy entirely.
Steve Oldham has been using this model for over a decade with his Atlanta clients, providing local and offsite backups to multiple storage destinations for each client.
Nightly incremental forever backups keep the backup window short and storage, and consequently, costs, lean. After the initial full backup, only the changed files are sent. For example, if there are a thousand files and only one changes daily, then only that one file is transferred after day one.
Steve Oldham saw his customers' storage costs drop after moving to a centralized managed backup platform because backups were smaller and better managed.
Set the backup retention period to match the clients' actual needs. A typical setup for SMB clients includes 30 days of local backup and 90 days for data stored in the cloud. Regulated clients, such as medical practices, accounting firms, and legal offices, may require longer retention periods. However, avoid storing data beyond what is required, as unnecessary retention wastes money.
Tony Linton monitors backups for a diverse customer base, including chiropractors, city services, manufacturers, clients with HIPAA compliance requirements, and public service clients. Although the compliance obligations differ, the management overhead does not because it all runs through the same console.
Make sure to lock down both your local and cloud storage so that only your backup software can access them. For example, a NAS that is open to general network access is a target for ransomware. Assign a static IP address so that backup jobs don't lose it after a reboot. Also, disable the recycle bin so that the retention cleanup actually frees storage space.
Designing for your standard client also means you can enforce that design. Clients with unusual requirements are given a separate scope, which prevents your standard offering from becoming 15 different configurations that you have to remember.
Recoverability Is the Only Metric That Matters
A backup that runs but cannot restore data provides a false sense of security. A less obvious version of this risk is a job that completes without errors but produces an unusually small backup file. This silent failure won't show as red on the dashboard, but it will be apparent when a client needs their data back. Obviously, that's too late.
The only way to avoid this is to implement a scheduled restore testing cadence. For example:
- Weekly health review of the dashboard
- Monthly light restore test where you check if individual files and folders are recoverable
- Quarterly full system recovery drills
Document every test, including the date, tested workload, restore type, result, and recovery time. Verify that all passwords and encryption keys are accessible and stored somewhere other than your memory. The log serves as proof of service in case a client ever questions the functionality of their backup.
Tony Linton monitors backups for a diverse customer base, including chiropractors, city services, manufacturers, clients with HIPAA compliance requirements, and public service clients. Although the compliance obligations differ, the management overhead does not because it all runs through the same console.
The Bottom Line
Solo MSPs are the ones who last made deliberate decisions about their stack, clients, and time, and they stick to those decisions.
Backup is one of the services that most clearly distinguishes a break-fix model from a managed services business. When done correctly, it generates recurring revenue, requires minimal ongoing time, and provides clients with the assurance that their data is protected and recoverable.
The MSPs featured in this post, Steve, Tony, and Michael, have each run sustainable, one-person businesses for over a decade, serving different markets and client bases. However, they all share the same underlying model: standardization manageable from a desk that leads to recurring revenue.
Are you still logging into separate tools for each client, driving to sites to check the backup status, or unsure if your restores would work? Try NovaBACKUP Managed Backup free for 30 days. Your first call with the team covers your specific environment and how to set it up so it runs itself.
Frequently Asked Questions
FAQ
Can One Person Really Run an MSP Long-Term?
Yes, with the right constraints in place. One-person MSPs that last 10–20 years share a recognizable pattern: a standardized stack, a curated client base, and recurring revenue as the foundation rather than break-fix. They also have SLAs that one person can honor. Steve Oldham has been running Oldham Consulting for over a decade. Michael Gustine has been operating MG Technology for more than 20 years. The model works; it simply requires deliberate design.
FAQ
How Many Clients Can a One-Person MSP Realistically Manage?
The number of endpoints varies widely. Many MSP clients are small businesses with just a server and a laptop, while others have 15–25 endpoints and multiple servers. The constraints are always stack standardization and client selectivity, not a specific number. Tony Linton serves clients ranging from single-workstation businesses to 25-endpoint manufacturers within a 50-mile radius, all from one platform.
FAQ
What Backup Solution Works Best for a Solo MSP?
The requirements for a solo MSP are specific: central management of all clients from one dashboard, automated recoverability verification, remote agent management, and predictable pricing with no unexpected costs. NovaBACKUP Managed Backup is built around these requirements and offers transparent per-device/per-GB pricing, allowing you to determine your margin before quoting clients.
FAQ
How Do I Transition From Break-Fix to Managed Services?
Start with one managed service. Backup is the easiest option. It has a defined scope, generates recurring revenue from day one, and doesn't require you to rebuild your client relationships or update your tools. Michael Gustine's model is a practical blueprint: backup bundled with endpoint protection and remote management as one monthly package. He didn't have to rebuild the business he'd already built.
FAQ
What's a Realistic Price to Charge for Managed Backup as a Solo MSP?
Build your cost baseline from the following: platform cost per client, monthly management time, and restore testing overhead. For a typical small business with one server, one workstation, and up to 500 GB of cloud storage, your NovaBACKUP cost is about $50 per month. With a gross margin of 50–70%, you're charging clients $100–$150 per month. Across ten clients, that's $1,000–$1,500 per month in recurring backup revenue versus $490 per month in costs. Clients with more devices or storage pay more, and your margin increases with them.
FAQ
What Does a Solo MSP Do When a Client's Data Is Lost?
If the backup was set up correctly and if restoring the data was part of the routine, then the recovery process is straightforward. For example, Tony Linton was able to recover a client's data after a complete hard drive failure because the backup was running correctly, and he routinely tests restores. However, if the backup was not set up correctly or was never tested, it's a different story. There will be a conversation with the client, potentially with lawyers, and certainly with yourself. The difference between these two scenarios lies entirely in the setup and verification processes, not in the crisis itself.
Worth Reading
How to Run a One-Person MSP Without It Eating You Alive
Winning New Clients and NovaBACKUP + Impossible Cloud | Data Protection Digest | June 2026
Share this
