15 min read

Why SMEs Should Ask Their MSP How They Make Money

Why SMEs Should Ask Their MSP How They Make Money

When an SME chooses a managed service provider (MSP), the conversation often focuses on service levels, cybersecurity, response times, and monthly pricing. Those are important questions—but there is another question business owners should understand:

How does the MSP earn its revenue?

This is not an accusation. MSPs need sustainable business models to hire skilled staff, maintain tools, provide support, and invest in security. Different providers use different combinations of recurring fees, project charges, product sales, commissions, and usage-based billing. None of these models is automatically good or bad.

The important issues are whether the arrangement is clear, whether prices are fair, and whether the MSP’s financial incentives are aligned with your business needs. Understanding the model helps you compare proposals, budget accurately, and evaluate technology recommendations with greater confidence.

Why the Revenue Model Matters

An MSP’s revenue model describes how it gets paid. It may earn money directly from services, indirectly from products it supplies, or through a combination of both.

The model can affect:

  • how your monthly bill is calculated;
  • whether an “included” service has limits;
  • how hardware and software prices are presented;
  • whether vendor relationships influence recommendations;
  • how upgrades and renewals are handled; and
  • whether your IT costs are predictable over time.

For example, two MSPs may both quote S$3,000 per month. One may include most support and infrastructure costs in that fee. The other may charge a lower monthly fee but bill separately for cloud subscriptions, project work, after-hours support, and hardware procurement. Neither approach is necessarily unsuitable—but comparing only the headline monthly fee would not give you the full picture.

Techease Solutions, for example, describes a fee-only model in which core revenue comes from transparent service fees rather than hardware, software, or cloud-vendor commissions. Its published service packages also distinguish recurring managed services from additional services such as project consulting, cloud migrations, procurement, and vendor management.

The lesson is not that every MSP should follow one particular model. It is that customers should know which model they are agreeing to.


Common MSP Revenue Models

1. Recurring Managed-Service or Support Fees

The most familiar MSP model is a recurring monthly fee. This is sometimes called a managed-service fee, support subscription, or monthly recurring revenue.

The fee may be based on:

  • the number of users;
  • the number of devices or endpoints;
  • the number of servers;
  • the size of the business;
  • the level of support required; or
  • a fixed package of services.

Typical inclusions may include:

  • helpdesk support;
  • remote troubleshooting;
  • device monitoring;
  • patch management;
  • antivirus or endpoint detection and response;
  • backup monitoring;
  • Microsoft 365 or Google Workspace administration;
  • network and firewall support;
  • user onboarding and offboarding;
  • reporting and strategic reviews.

A recurring fee can make IT expenditure easier to plan. It may also encourage the MSP to prevent problems proactively rather than simply responding to incidents after they occur.

However, “unlimited support” or “fully managed” does not always mean the same thing from one provider to another. A contract may limit:

  • support hours;
  • response times;
  • supported applications;
  • the number of included devices;
  • on-site visits;
  • project work;
  • after-hours assistance; or
  • the amount of cloud storage or backup capacity.

For example, an MSP might charge S$100 per user per month for helpdesk support and device monitoring, while charging separately for on-site visits, major migrations, and new-office deployments. Another provider might include several on-site visits but charge more per user. The right comparison is the total expected cost and service coverage—not merely the per-user rate.

Questions to ask

  • What exactly is included?
  • Is the fee calculated per user, device, site, or service?
  • Are there minimum user or device commitments?
  • What happens when employees join or leave?
  • Are support hours, response times, or ticket volumes limited?
  • Are security tools, backup storage, and licenses included or separate?

2. One-Time Project and Professional-Service Fees

Many MSPs charge separately for work outside day-to-day support. These fees may be hourly, fixed-price, milestone-based, or based on a formal statement of work.

Examples include:

  • cloud migration;
  • office relocation;
  • server deployment;
  • network redesign;
  • firewall replacement;
  • email or productivity-suite migration;
  • cybersecurity assessments;
  • penetration testing;
  • compliance preparation;
  • business-continuity planning;
  • automation projects;
  • system integration; and
  • technology strategy consulting.

Professional-service revenue is not inherently a problem. Projects require concentrated effort, planning, specialist expertise, and sometimes subcontractors or equipment. Separating project fees from recurring support can also make costs easier to understand.

The main risk is ambiguity. A provider may describe a project as “included” but later classify substantial portions of the work as billable. Conversely, a very broad fixed-price project may create disagreements about what is in scope.

A well-defined project proposal should identify:

  • the business objective;
  • the work to be performed;
  • assumptions and dependencies;
  • deliverables;
  • milestones;
  • customer responsibilities;
  • estimated or fixed costs;
  • exclusions;
  • change-control procedures; and
  • post-project support arrangements.

Example

Suppose an SME moves from an on-premises file server to a cloud platform. The recurring fee may cover ordinary administration after the migration, while the migration itself is billed as a one-time project. A clear proposal should explain whether data cleanup, user training, permissions redesign, testing, and post-migration support are included.

3. Hardware, Software, and Licensing Markups or Product Margins

An MSP may supply equipment, software, or licenses and earn money through the transaction. Two terms are particularly important here: markup and margin.

A markup is the amount added to the provider’s cost to determine the selling price.

  • MSP’s cost: S$800
  • Selling price: S$1,000
  • Markup: S$200, or 25% of cost

A gross margin is the selling price minus cost, expressed as a percentage of the selling price.

  • Selling price: S$1,000
  • Cost: S$800
  • Gross profit: S$200
  • Gross margin: 20% of selling price

Markup and margin describe related but different calculations. A 25% markup produces a 20% gross margin in this example.

An MSP may apply a markup to:

  • laptops and desktops;
  • servers;
  • networking equipment;
  • firewalls;
  • warranties;
  • software subscriptions;
  • Microsoft or Google licenses;
  • backup storage;
  • security products; or
  • implementation-related products.

A product margin can compensate the MSP for procurement, configuration, inventory management, financing, warranty coordination, and administrative work. A customer may also value the convenience of having one party source and support the equipment.

The important question is whether the price and commercial arrangement are clear. Some MSPs disclose the purchase price and a procurement fee. Others provide a bundled price without itemizing the underlying margin. Both structures may be commercially workable, but the customer should know which one applies. For a deeper look at why transparency on markups matters, see Why Your IT Partner Shouldn’t Profit From Hardware or Software Markups.

Techease Solutions, for instance, describes transparent procurement and lists a separate equipment-procurement service fee for certain services. It also says that vendor recommendations are intended to be based on business requirements rather than manufacturer incentives.

Questions to ask

  • Is the quoted price the MSP’s cost, a resale price, or a bundled price?
  • Is there a markup or procurement fee?
  • Are discounts or volume rebates passed on to the customer?
  • Who owns the equipment?
  • Who manages warranties and returns?
  • Can we purchase the product directly?
  • Are alternatives from other brands or cloud services being considered?

A markup is not automatically unfair. The relevant issue is whether the total price is reasonable for the value provided and whether you can evaluate alternatives.

4. Referral, Reseller, or Vendor Commissions

Some MSPs participate in partner or reseller programs operated by technology vendors. Under such programs, the MSP may receive compensation when a customer:

  • purchases a product;
  • signs a subscription;
  • renews a contract;
  • consumes cloud services;
  • adopts a security platform; or
  • is referred to another provider.

This compensation may be called a:

  • commission;
  • referral fee;
  • rebate;
  • partner incentive;
  • reseller discount;
  • back-end incentive; or
  • marketing development payment.

These terms are not interchangeable.

A commission is generally a payment calculated by reference to a sale or contract.

A referral fee is compensation for introducing a customer to another business.

A rebate is usually a retrospective discount or payment based on purchases, volume, or program conditions.

A partner incentive is a broader term for benefits offered through a vendor program. It may include money, discounts, credits, training, marketing support, or other advantages.

A reseller discount is a price reduction granted to a partner that may or may not be passed to the customer.

The existence of such compensation does not prove that an MSP is providing poor or unethical service. Partner programs can give MSPs access to technical training, support resources, certifications, and volume pricing. They may also simplify procurement for customers.

The concern arises when the relationship is undisclosed or when it materially influences advice without the customer understanding the incentive. For a deeper dive into commissions and why SMEs should prioritise transparency, see Uncovering IT Service Commissions: Why SMEs Need Transparency.

Example

An MSP recommends Security Platform A. It is a capable product, but the MSP receives a recurring partner payment for every customer subscription. That does not necessarily make the recommendation wrong. A transparent discussion might include:

  • why Platform A fits the customer’s requirements;
  • what alternatives were considered;
  • the total cost over the contract term;
  • whether the MSP receives compensation; and
  • whether the customer can buy the subscription directly.

This gives the customer enough information to assess the recommendation.

Disclosure practices and legal requirements vary by jurisdiction, industry, contract, and vendor arrangement. Business owners with concerns about disclosure obligations should verify the position with a qualified legal, accounting, or other appropriate professional in their jurisdiction.

5. Cloud, Backup, Security, and Other Usage-Based Charges

Some IT costs rise or fall according to consumption. This is common with cloud computing and other services that depend on storage, data transfer, users, devices, or activity levels.

Usage-based charges may apply to:

  • cloud hosting;
  • storage;
  • backup capacity;
  • backup retention;
  • data transfer;
  • email security;
  • endpoint-security licenses;
  • log collection;
  • vulnerability scanning;
  • telephone or collaboration services;
  • virtual machines;
  • database usage; and
  • disaster-recovery capacity.

Usage-based pricing can be appropriate because it connects cost to actual consumption. It can also allow a small business to start with modest capacity and expand as it grows.

The disadvantage is variability. A backup policy change, data-growth spike, prolonged retention period, or accidental cloud configuration can increase the bill unexpectedly. To keep bills predictable, consider a transparent tiered approach to pricing.

Ask whether the MSP provides:

  • usage dashboards;
  • spending alerts;
  • monthly forecasts;
  • capacity limits;
  • approval thresholds;
  • explanations for material changes; and
  • recommendations to reduce unnecessary consumption.

Example

An SME pays a fixed management fee for backup administration but pays separately for 2 TB of backup storage. If the business expands to 4 TB, the monthly cost increases. That may be entirely reasonable, provided the pricing formula and approval process are clear.

6. Combinations of Revenue Models

Most MSPs use a combination of models rather than relying on only one source of income.

A typical arrangement might include:

  • a monthly managed-service fee;
  • separate cloud and software subscriptions;
  • project fees for migrations;
  • an hourly rate for out-of-scope work;
  • a markup or procurement fee on equipment; and
  • vendor-program compensation.

Another provider might use a higher monthly fee that includes more licenses, backup, and support, while charging fewer separate project or procurement fees.

Neither structure is automatically superior. The question is whether the package matches your requirements and makes the total cost understandable.

A combined model may provide flexibility, but it can also make invoices difficult to evaluate. Request a sample invoice or a breakdown of expected charges before signing.


Comparison of Common MSP Revenue Models

Revenue model
How the MSP is paid
Common customer benefit
Main point to clarify
Recurring managed-service fee
Fixed monthly or annual payment
Predictable support and proactive management
What is included, and what are the limits?
One-time project fee
Fixed price, hourly rate, or milestone payments
Specialist work for migrations, upgrades, or consulting
What is in scope, and how are changes charged?
Hardware or software markup
MSP sells products above its acquisition cost
Convenience, procurement, configuration, and support
What is the price structure and are alternatives available?
Product margin
Difference between selling price and product cost
May fund account management or procurement services
Is the margin disclosed or replaced by a separate fee?
Commission
Vendor pays based on a sale, subscription, or renewal
Access to partner expertise and vendor support
Does the MSP receive compensation for the recommendation?
Referral fee
MSP is paid for introducing the customer to another provider
Access to specialist services
Is the referral relationship disclosed?
Rebate
Retrospective payment or discount based on purchases or volume
Potentially lower acquisition costs
Is the benefit passed on to the customer?
Usage-based charge
Payment varies with storage, users, devices, data, or consumption
Scales with actual use
What causes the price to change, and are alerts provided?
Combination model
Two or more of the above
Flexibility and tailored service
What is the complete expected cost over the contract term?

Questions Every SME Should Ask Its MSP

You do not need to interrogate your provider or understand every vendor contract. A straightforward commercial discussion is usually enough to establish the basics. You can also use this 7-question checklist when comparing Singapore IT providers.

1. What services are included in the recurring fee?

Ask for a plain-English description of:

  • support channels;
  • operating hours;
  • response targets;
  • covered users and devices;
  • monitoring;
  • patching;
  • security;
  • backups;
  • reporting; and
  • strategic reviews.

Also ask what “unlimited” means and whether fair-use restrictions apply.

2. Which costs are billed separately?

Request a list of exclusions, such as:

  • licenses;
  • cloud subscriptions;
  • storage;
  • hardware;
  • on-site visits;
  • projects;
  • after-hours work;
  • emergency response;
  • training; and
  • third-party services.

3. Do you receive rebates, commissions, referral fees, or partner incentives from vendors?

The purpose is not to demand that the MSP avoid all vendor relationships. It is to understand whether a financial incentive exists and how it is handled.

Ask whether the compensation:

  • is paid once or recurring;
  • is retained by the MSP;
  • reduces your price;
  • affects renewal recommendations; or
  • is available for competing products.

4. Do you resell products or apply markups?

Find out whether hardware, software, cloud services, and licenses are:

  • passed through at cost;
  • sold with a disclosed markup;
  • subject to a separate procurement fee; or
  • included in a bundled price.

5. How are after-hours work, projects, and emergency support charged?

Clarify:

  • hourly rates;
  • minimum billing increments;
  • emergency surcharges;
  • travel or on-site fees;
  • approval requirements; and
  • whether urgent work is included in the package.

6. Are there cheaper or independent alternatives?

A responsible provider should be able to explain the trade-offs among options, including:

  • price;
  • security;
  • reliability;
  • compatibility;
  • supportability;
  • migration effort;
  • compliance requirements; and
  • long-term ownership cost.

The cheapest product is not always the best option, but you should understand why a more expensive choice is justified.

7. Can we review our contract, invoice structure, and renewal terms?

Review:

  • initial term;
  • renewal period;
  • price-adjustment clauses;
  • notice periods;
  • minimum commitments;
  • license ownership;
  • data access;
  • exit assistance;
  • termination charges; and
  • treatment of prepaid services.

If the arrangement is complex, ask for a commercial summary in addition to the formal contract.


The Benefits of Asking These Questions

Better Budgeting

A clear revenue model helps you distinguish fixed costs from variable costs. For ballpark figures in Singapore, see how much managed IT services typically cost. You can forecast recurring fees while allowing for projects, renewals, equipment replacement, and cloud growth.

For example, a budget might show:

  • recurring MSP fee: S$2,500 per month;
  • cloud and software subscriptions: S$900 per month;
  • average backup usage: S$250 per month;
  • planned annual security assessment: S$1,500;
  • occasional project reserve: S$5,000 per year.

This is more useful than treating every IT expense as an unexplained monthly bundle.

Fewer Surprises

Many disputes arise not because a charge is inherently unreasonable, but because the customer did not know it would occur. Written explanations of included and excluded services reduce this problem.

Improved Trust

Transparency creates a healthier relationship. An MSP that explains its commercial model gives the customer an opportunity to make informed choices. A customer who understands the model is also better positioned to recognize the value of legitimate service fees.

More Informed Technology Decisions

Technology decisions involve trade-offs. A higher-priced platform may offer better integration, security, or support. A lower-priced product may require more administration or have limitations. Understanding the MSP’s incentives helps you ask the right questions without assuming that the recommendation is biased.

Easier Provider Comparisons

When proposals use different pricing structures, normalize them over a meaningful period—often three years. Include:

  • recurring fees;
  • licenses;
  • cloud consumption;
  • support;
  • projects;
  • hardware;
  • renewals;
  • migration costs; and
  • exit or transition costs.

This produces a more realistic total-cost comparison.


Warning Signs to Investigate

The following signs do not automatically prove misconduct, but they justify asking for clarification:

Unexplained charges

Invoices contain vague descriptions such as “IT services” or “cloud support” without dates, quantities, or references to the contract.

Undisclosed incentives

The MSP strongly recommends a product but refuses to explain whether it has a reseller relationship, commission arrangement, rebate, or other partner benefit.

Bundled services that cannot be evaluated

A package combines support, licenses, backup, security, and cloud services into one amount, but the provider cannot explain the scope, quantities, or renewal assumptions. Consider the benefits of transparent, service-based pricing when you encounter this.

Pressure to buy unnecessary products

You are urged to purchase equipment, licenses, or upgrades without a clear business, security, operational, or compliance justification.

No meaningful alternatives

The MSP presents only one product and will not discuss comparable options, direct purchasing, cloud alternatives, or the consequences of choosing another vendor.

Ambiguous renewal terms

Prices, license counts, automatic renewals, minimum commitments, or cancellation requirements are difficult to determine.

Resistance to reasonable documentation

The provider will not supply a statement of work, pricing schedule, service description, or explanation of material invoice changes.

Again, these are prompts for investigation, not automatic conclusions. A provider may have a legitimate explanation—for example, a complex vendor contract, a pass-through cloud bill, or a bundled service designed to simplify administration.


A Practical Review Checklist

Use this checklist when selecting or reviewing an MSP:

  • We know how the MSP earns revenue.
  • The recurring fee and its service limits are documented.
  • Separately billed items are listed.
  • Project and professional-service rates are clear.
  • After-hours and emergency charges are explained.
  • Hardware, software, license, and cloud pricing is understandable.
  • Any relevant commission, rebate, referral, or partner incentive has been discussed.
  • We know whether discounts or rebates are passed through.
  • The MSP can explain its product recommendations.
  • Alternatives and their trade-offs have been considered.
  • Usage-based charges have monitoring or approval controls.
  • Renewal, price-change, and termination terms are clear.
  • We have reviewed a sample invoice or pricing schedule.
  • We know what happens to our data, licenses, and equipment if we change providers.

Choosing the Right Commercial Model for Your Business

Different businesses may prefer different arrangements.

A small professional-services firm with stable requirements may value a fixed monthly package. A fast-growing company may prefer usage-based pricing that scales with users and storage. A business undertaking a major cloud migration may want recurring support separated from a clearly priced implementation project.

Consider:

  • how predictable your IT requirements are;
  • whether your staff and device count changes frequently;
  • how much internal IT expertise you have;
  • whether you need on-site support;
  • how critical downtime is;
  • whether you require specialist security or compliance assistance;
  • how much procurement work you want the MSP to handle; and
  • whether you prefer predictable bundled costs or itemized consumption.

The best arrangement is one you can understand, budget for, and review. For help right-sizing a plan, see our guide to choosing the best managed IT service plan for Singapore SMEs.

A Note on Fee-Only and Vendor-Agnostic Models

Some MSPs deliberately avoid vendor commissions and earn their core revenue from service fees. This is sometimes described as a fee-only model. Other providers operate as resellers or partners and may receive compensation from vendors. Not sure what a vendor‑agnostic MSP is and why SMEs should care?

A fee-only model can reduce certain conflicts of interest and make procurement costs more explicit. A reseller model may provide access to volume pricing, specialized support, bundled services, and procurement convenience. The label alone does not determine service quality.

The practical test is whether the provider:

  • explains how it is paid;
  • gives advice connected to your requirements;
  • offers commercially reasonable pricing;
  • distinguishes service fees from product costs;
  • discloses relevant incentives; and
  • respects your ability to make an informed choice.

Conclusion: Make the Commercial Model Part of the Conversation

Your MSP’s revenue model is not merely an accounting detail. It affects how services are priced, how invoices are structured, and how technology recommendations should be evaluated.

Recurring support fees, project charges, product margins, commissions, rebates, referral payments, and usage-based charges can all be legitimate parts of an MSP’s business model. The key questions are whether the arrangement is transparent, whether the pricing is fair, and whether recommendations are guided by your business needs.

Before signing or renewing an MSP agreement:

  1. Request a clear description of included services.
  2. List all separately billed items.
  3. Ask about markups, commissions, rebates, and referral fees.
  4. Review project, emergency, and after-hours rates.
  5. Compare meaningful alternatives.
  6. Examine invoice, renewal, and termination terms.
  7. Revisit the arrangement at least annually as your business changes.

A transparent discussion does not undermine the provider relationship. It strengthens it. When both sides understand how the arrangement works, you can make better technology decisions, plan your budget more confidently, and focus on whether the MSP is delivering genuine value. If you’d like to see a transparent example, review our Services & Pricing.