How MSPs Can Build Better Business Application Partnerships

Listen to this article
Browser text-to-speech
If your MSP doesn't support business applications, you still have clients using them to process orders, manage inventory, and run payroll. Your agreement may exclude that work. You should still know who handles it when the client needs help.
Your MSP needs people who can deliver application support before you add it to your service offering. Before you commit to hiring and training, find out which application providers already work with your clients. You may be able to build a useful partnership with someone the client already trusts.
When I spoke with Peter Conway, Senior Partner Success Manager at Net at Work, we discussed why MSPs have historically kept their distance from business applications. Your service team may lack the expertise to support Sage or an industry-specific ERP system. If you take on the work without that expertise, you have another service to sell and another promise you might struggle to keep.
For a smaller MSP, Peter recommends working with an application provider you trust. Start by understanding the client's applications and meeting the people who support them.
Peter Conway's comments below have been edited for length and clarity.
Contents
- What is an MSP business application partnership?
- Why application recovery needs specialist involvement
- Which client applications should MSPs map first?
- How to choose a business application partner
- How to coordinate support and referrals
- How to start with one client application
- Frequently asked questions
What is an MSP business application partnership?
An MSP business application partnership is a working arrangement between a managed service provider and a specialist who supports software such as enterprise resource planning (ERP), customer relationship management (CRM), or payroll systems. The providers agree on responsibilities, support handoffs, and communication with their shared clients.
That arrangement can begin with an introduction to the provider already supporting a client's software. You don't need to announce a new practice or promise expertise you haven't hired.
Peter recommends this approach for smaller MSPs:
"For smaller MSPs, the more logical path is to partner with a provider they trust to bring business application expertise to their clients." Peter Conway, Senior Partner Success Manager, Net at Work
What does each provider handle?
An application provider may need your team to resolve a connectivity problem. Your team may need that provider to diagnose a failed integration. Establish what each provider will investigate and when they will bring the other one in.
Use the following questions to establish responsibilities. Assign them according to the services each provider has agreed to deliver.
| Area | Responsibilities to establish |
|---|---|
| Infrastructure | Who supports hosting, endpoints, connectivity, and the underlying platform? |
| Application | Who handles configuration, application-specific troubleshooting, and upgrades? |
| Recovery | Who documents dependencies, restores each component, and validates the application with the client? |
| Client communication | Who coordinates the incident, provides updates, and confirms that work is complete? |
A referral relationship alone doesn't answer those questions. Write down the working arrangement so your service team can use it.
Why application recovery needs specialist involvement
Your MSP may be able to restore a server without knowing whether the client's payroll application works correctly. The employee responsible for payroll needs to complete the payroll run. Include that employee and the application provider in deciding how to test recovery.
Apply the same approach to the other applications the client depends on. Confirm who can check that orders process correctly or that warehouse staff can resume their work.
Peter described the potential consequence of leaving the application provider out:
"These systems help businesses sell, make money, and pay their vendors. If they're down for a day or a week, the losses can reach tens or hundreds of thousands of dollars. You might restore the servers and recover a backup, but getting the business running again may still require a service partner who knows that particular application." Peter Conway, Senior Partner Success Manager, Net at Work
The financial consequences depend on the client and the interruption. Ask the client which activities stop, what deadlines they face, and how long they can operate using a workaround.
Ask the application provider to identify the checks their specialist needs to perform. Assign the client someone to verify a transaction or complete another agreed task before employees resume normal work.
Don't leave application recovery planning at "we'll call the vendor." Identify the contact, confirm how to reach them, and test the handoff as part of an agreed recovery exercise.
Which client applications should MSPs map first?
Start with the applications whose failure would stop the client getting paid or meeting an obligation. Ask the employees doing the work; the client's owner may not know every workaround they have adopted.
Start with the systems that interrupt revenue or payroll
For one client, the first priority might be an ERP platform handling inventory and orders. For another, it might be payroll or the CRM their service team uses throughout the day.
Peter identified financial systems, inventory, warehouse management, field service, ecommerce, customer management, and HR as areas MSPs should understand. That doesn't make every application equally urgent for every client.
Ask employees to explain what they can still complete when an application is unavailable, how they do it, and how long that workaround remains practical. Record those limits alongside the technical information.
Record who owns and supports each application
Make an inventory your team can maintain and use during a support incident.
| Field | What to record |
|---|---|
| Application and version | The product, edition, version, and hosting arrangement where relevant |
| Business use | The work employees complete in it and what stops during an outage |
| Client owner | The employee who understands the workflow and can validate recovery |
| Support provider | The company and contact responsible for application support |
| Dependencies | Required integrations, databases, and connected services |
| Recovery contact | How to reach the appropriate specialist during an interruption |
| Known problems | Recurring issues, workarounds, and unresolved support requests |
Ask whether the client is satisfied with the existing provider before recommending someone new. Peter specifically raised this question in our conversation. A client may need an introduction between two capable providers who haven't met. Another may need help finding a replacement.
An introduction between existing providers requires less work than selecting a replacement. Establish what the client needs before you begin evaluating new partners.
How to choose a business application partner
A provider may list the right applications on its website and still lack the capacity to support your client. Ask who would take the account and what experience they have with the client's use of the software.
Verify application expertise and staffing
Ask which products and versions the provider supports, then describe the client's actual use of the application. Experience with the same software doesn't automatically establish experience with that client's configuration or industry workflows.
Find out who performs the work and how the provider handles absences or competing demands. Subcontracting is something to understand, including who supervises the work and who remains accountable to the client.
Peter's suggested questions are useful because they move the discussion into service delivery:
"Ask which applications they support and what their team looks like. How many people do they have? Are they employees or subcontractors? Is application support just a sideline? Ask how many clients they serve and whether you can speak with clients who are happy with their services." Peter Conway, Senior Partner Success Manager, Net at Work
Check client experience and business continuity
Ask references to describe an issue that required the application provider to coordinate with an MSP. Find out how the providers divided the work and kept the client informed. A reference who has been through that process can tell you something a product certification won't.
Peter also recommends asking about ownership and succession. If the owner is preparing to retire, find out how the business plans to continue supporting its clients. A long operating history won't answer that question for you.
If the provider relies on one person to support the application, ask what happens when that person is unavailable. Your MSP needs an escalation arrangement that survives a vacation.
How to coordinate support and referrals
The first joint meeting should produce something your service team can act on. Put the escalation contacts, service boundaries, and communication arrangements into the documentation your team already uses.
Agree on support handoffs before an incident
Use a recurring issue from the client's support history to work through the handoff together. Agree on who investigates first, what information they collect, and when the other provider joins the incident.
Agree on who updates the client and how you'll confirm resolution. Also establish how work outside either provider's existing scope will be quoted and approved. A friendly introduction won't prevent a dispute over an unexpected invoice.
Put the agreed process where your technicians can find it. An arrangement that exists only in the MSP owner's inbox won't help the technician handling the ticket.
Establish how referrals will work
Application providers may serve clients who need managed services. Your MSP may serve clients who need application expertise. That creates a reason to stay in touch, but referrals still depend on a useful fit.
Peter described how those connections can begin:
"Sometimes an MSP calls me about a client running Sage. I'll know the Sage partner they're working with, so I'll call that partner and ask them to help. I encourage MSPs to find out who supports their clients' business applications. Call them up and make friends. Those providers also have clients who might need what you offer." Peter Conway, Senior Partner Success Manager, Net at Work
Discuss how introductions will happen, who follows up, and how each company will explain the relationship. Establish any referral fees or other commercial arrangements before they become relevant to a live opportunity.
An agreement doesn't promise a stream of new business. It gives both providers a way to make an appropriate introduction and follow through.
How to start with one client application
Choose a client with a recurring application issue. Ask the employee dealing with it to explain the task, the interruption, and the workaround. Record enough detail to have a useful conversation with the application provider.
Agree on one improvement and a way to assess it. That might mean fewer repeated support incidents or less time spent reconciling information manually. Use a measure the client understands and can help verify.
Bring this work into the next client review. Ticket counts and hours won't explain why an employee keeps re-entering the same information manually. Ask the client to describe the unfinished work, then determine whether your MSP and the application provider can address it.
Where AI fits into the conversation
AI requests give you another reason to understand the client's applications and workflows. Before discussing tools, ask what the client wants to accomplish and where the required information lives.
Peter described an MSP focusing on construction workflows, including estimating and RFP responses. He also cautioned that AI can produce incorrect results. Treat that as a reason to involve someone who knows the work and can check the output.
Before your MSP sells an AI project, involve the person who understands the application data and the employee who will use the output. Agree on how they will check accuracy and compare the proposed process with the work they do now.
Peter's observation about client-facing staff applies here:
"Some of the most successful client-facing people at MSPs are technical advisors, client success managers, or client strategic advisors. They don't necessarily know a lot about technology, but they know how to have conversations with people and understand their world. That's the path to success." Peter Conway, Senior Partner Success Manager, Net at Work
Before your next client review, identify one application problem you haven't helped resolve. Find out who supports that application. Arrange an introduction and agree on the next step with the client.
Frequently asked questions
What is an MSP business application partnership?
An MSP business application partnership is an arrangement between a managed service provider and an application specialist to coordinate services for shared clients. The agreement should establish responsibilities, support handoffs, and client communication.
Does an MSP need to hire ERP specialists to support business applications?
An MSP can support business applications through a partnership with an ERP specialist. The application partner provides specialist expertise while the MSP delivers its agreed services. Hiring ERP specialists internally is another option.
What should an MSP ask a potential business application partner?
An MSP should ask a potential business application partner which applications they support, who performs the work, and whether relevant clients will provide references. The MSP should also discuss subcontractors, support capacity, escalation procedures, and succession plans.
Why should an MSP involve application providers in recovery planning?
An MSP should involve application providers in recovery planning because restoring infrastructure may leave application dependencies, configurations, or integrations unresolved. Application specialists can help identify those requirements and confirm that the recovered system supports the client's work.
Which business applications should an MSP document first?
An MSP should document business applications whose failure would interrupt revenue-generating work or time-sensitive obligations first. Depending on the client, these may include financial systems, inventory management, order processing, CRM, and payroll.
Can an MSP generate referrals through business application partnerships?
An MSP can generate referrals through business application partnerships when each provider serves clients who need the other's expertise. Providers should agree on how to handle introductions and client relationships. Referral volume is not guaranteed.
