MSP Pricing Models: Flat Rate, Per-Device, or Tiered? The Complete 2026 Guide

Introduction: The Pricing Decision That Defines Your MSP

After building and selling two managed service providers, I have made nearly every pricing mistake possible. I have underpriced security until a ransomware attack wiped out three months of margin. I have used flat-rate pricing with a client whose environment grew from 30 to 300 endpoints without a contract renegotiation. I have lost deals to competitors charging half my price — only to watch those competitors churn the client a year later when they realized the account was unprofitable.

Pricing is not just a financial decision. It is a strategic one that shapes everything: which clients you attract, what services you can sustainably deliver, how your business scales, and whether you build equity or just a job.

In this guide, I want to be more direct than most MSP pricing resources. Not just "here are the models" but "here is when each model works, when it breaks down, and what the numbers actually look like."

The Fundamental Tension in MSP Pricing

Every MSP pricing model is trying to resolve a fundamental tension:

Clients want predictability. They do not want surprise IT bills. They want to budget a fixed monthly amount and not think about IT costs until renewal.

MSPs need profitability. A client whose environment is more complex, larger, or higher-maintenance than average must generate more revenue than one whose environment is simple and stable. Otherwise, you are subsidizing your most demanding clients with your easiest ones.

The pricing model you choose determines how you navigate this tension. Some models favor client predictability at the expense of MSP margin predictability. Others do the reverse. The best models align client incentives with MSP sustainability.

The Five Main MSP Pricing Models

Model 1: Per-Device Pricing

How it works: You charge a fixed monthly fee for each monitored and managed device. Desktops, laptops, servers, and network devices typically have different rates.

Example pricing:

• Workstations: $45/month each
• Servers: $125/month each
• Network devices (switches, firewalls): $25/month each
• Mobile devices: $15/month each

A client with 50 workstations, 3 servers, 2 switches, and 1 firewall pays: (50 × $45) + (3 × $125) + (3 × $25) = $2,250 + $375 + $75 = $2,700/month.

Why it works:

Revenue scales automatically with the client's growth. When they add 10 more laptops, your revenue increases proportionally without a contract renegotiation. This is the most natural alignment between MSP cost and client size.

Per-device pricing is also easy to explain and audit. Clients can count their devices. You can count their devices. There is no ambiguity.

When it breaks down:

Per-device pricing does not account for usage intensity. A server that hosts mission-critical applications and requires constant monitoring, frequent patching, and occasional emergency support costs the same as an identical server that runs a backup job once a week. The model does not distinguish between a complex, demanding environment and a simple one.

Some clients also try to minimize billable device counts by removing monitoring agents from infrequently used machines — a misaligned incentive.

Ideal for: MSPs with diverse client sizes, primarily workstation-focused environments, clients who add/remove devices frequently.

Margin analysis: With a fully loaded technician cost of $75/hour and an industry benchmark of one hour of labor per device per month (for a well-run MSP with good automation), your break-even is around $37.50 per workstation. At $45, you have approximately 17% gross margin before overhead — tight but manageable. Many successful MSPs target $50–65 per workstation for comfortable margins.

Model 2: Per-User Pricing

How it works: You charge a fixed monthly fee per user (employee) rather than per device. Typically, each user fee covers all devices that user owns.

Example pricing:

• Standard users: $85/month each
• Power users (developers, executives): $150/month each
• Servers: still billed separately, $125/month each

A client with 50 employees (45 standard, 5 power users) and 3 servers pays: (45 × $85) + (5 × $150) + (3 × $125) = $3,825 + $750 + $375 = $4,950/month.

Why it works:

Per-user pricing simplifies billing — one line item per employee is easier for clients to understand and budget than a device inventory. It also naturally covers the reality that modern users have multiple devices (laptop + desktop + phone) under a single fee.

Per-user pricing encourages the client to provision monitoring across all devices (since additional devices do not increase their bill), which is good for your visibility and security posture.

When it breaks down:

Per-user pricing breaks down with server-heavy environments. A hosting company with 5 employees and 200 servers cannot be priced on a per-user model — the servers dominate the cost of service delivery.

Some clients game per-user pricing by creating shared accounts for contractors and part-time staff to avoid per-user fees.

Ideal for: Professional services firms (law, accounting, consulting), healthcare practices, any organization where device count per user is high and variable.

Model 3: Tiered / Bundled Pricing

How it works: You define service tiers — typically three (Good, Better, Best or Silver, Gold, Platinum) — and price each tier as a package with defined inclusions.

Example tiers:

Why it works:

Tiered pricing is the closest to how clients think about purchasing decisions. They understand "basic, standard, premium" and naturally anchor to the middle tier (decoy pricing). Well-designed tiers drive upsells organically — clients start on Silver and grow into Gold as their security concerns increase.

Tiered models also simplify your quoting process. You are not building custom proposals for every client; you are selecting a tier and applying it.

When it breaks down:

Tier creep: clients on Silver who expect Gold-level services because "it is just this once." Without clear SLA documentation attached to each tier, tier boundaries blur over time and you end up delivering Platinum service at Silver prices.

Tier design requires discipline. Too many tiers create confusion. Too few force square clients into round holes.

Ideal for: MSPs with a well-defined service catalog, clients that can be naturally segmented by complexity/risk, markets where competitive differentiation on features matters.

Model 4: All-You-Can-Eat Flat Rate

How it works: A single fixed monthly fee covers unlimited support for the client. All devices, all users, all issues — one price.

Example: $3,500/month flat for a 50-person office, all-in.

Why it works (for clients):

Absolute cost predictability. Clients love it. They know exactly what IT will cost this year. There is no invoice anxiety.

It also creates aligned incentives around efficiency: the MSP benefits from keeping the client's environment healthy (fewer support calls = more margin), and the client benefits from a low-maintenance environment too.

When it breaks down (for MSPs):

Flat rate is catastrophically risky if you do not scope properly. That $3,500/month all-you-can-eat client who hired 20 employees, migrated to a new ERP system, and opened a second office is now consuming 40 hours/month of technician time — $3,000 in cost, leaving you $500 gross margin to cover your platform costs.

Flat rate also attracts the wrong clients: high-maintenance organizations that know they have complex needs actively seek all-you-can-eat pricing to offload risk onto the MSP.

How to make it work if you choose flat rate:

1. Never quote flat rate without a thorough environment assessment first
2. Build hard exclusions into the contract (major projects, new locations, employee counts above X)
3. Include annual repricing clauses tied to device/user count benchmarks
4. Track actual hours carefully so you know which clients are profitable

Ideal for: Small, stable environments where you have done a thorough assessment and have high confidence in the scope. Not suitable as a general pricing model.

Model 5: À La Carte (Time and Materials)

How it works: Clients pay for IT support as they use it. Monitoring may be a fixed fee, but labor is billed by the hour or incident.

Why it exists:

Some clients — particularly small businesses or those with infrequent IT needs — resist committing to a monthly retainer. À la carte is a foot-in-the-door model that gets you into an account while demonstrating value.

Why MSPs should not rely on it:

À la carte breaks every rule of building a sustainable MSP:

• Revenue is completely unpredictable
• It attracts reactive relationships ("call when broken") rather than proactive ones
• Hourly billing undervalues expertise (a senior engineer who fixes something in 5 minutes would be paid for only 5 minutes of a junior's 4-hour struggle)
• Clients resist maintenance work because it costs them money
• You cannot invest in tooling or automation because it reduces your billable hours

Use à la carte only as a transition pricing model for clients you are qualifying for a managed services agreement.

Hybrid Pricing: The Real-World Answer

In practice, most mature MSPs use hybrid pricing — a combination of models that captures the benefits of each:

Base fee + variable components:

• Fixed monthly base: $X for monitoring, helpdesk, and patch management (per-device)
• Variable component: Security bundle, backup, vCISO, cloud management priced as add-ons

This is arguably the most financially sound approach:

• The base fee provides predictable revenue
• Add-ons align additional revenue with additional value delivered
• Clients can start with the base and add services as their needs grow

MSPs billing at this level:

• Small SMB client: $45/device base + $15/device security bundle = $60/device
• Mid-market client: $55/device base + $20/device security + $10/device backup = $85/device
• Compliance-focused client: $65/device base + $25/device security + $15/device compliance = $105/device

Calculating Your True Cost Per Endpoint

Most MSPs underprice because they do not know their true cost per endpoint. Here is a framework:

Step 1: Calculate Total Technician Cost

For each technician, sum:

• Annual salary
• Benefits and payroll taxes (typically 1.25–1.35× salary)
• Training and certifications
• Tools and equipment

For a technician with a $75,000 salary: $75,000 × 1.3 = $97,500 fully loaded annual cost

Divided by productive hours (1,800 hours/year after PTO, meetings, training): $54.17/hour

Step 2: Calculate Hours Per Endpoint Per Month

Track this carefully for 90 days. Industry benchmarks:

• Well-run MSP with good automation: 0.5–0.8 hours/device/month
• Average MSP: 1.0–1.5 hours/device/month
• Poorly tooled or poorly scoped MSP: 2.0+ hours/device/month

At 0.75 hours/endpoint/month and $54/hour: $40.50 labor cost per endpoint per month

Step 3: Add Platform Costs

Divide your total monthly software costs (RMM, PSA, security tools, backup) by your total managed endpoint count. This is typically $8–15 per endpoint per month for a well-priced stack.

Total variable cost per endpoint: $40.50 + $12 = $52.50

Step 4: Add Overhead Allocation

Sales, marketing, management, office, insurance: typically 20–30% of revenue. If targeting 25% overhead, you need to mark up by 1.33× to cover overhead and achieve your target margin.

Target price for 30% gross margin: $52.50 ÷ (1 - 0.30) = $75/endpoint/month

If you are charging $45/device, you now understand why you might be struggling with profitability.

The Psychology of MSP Pricing

Understanding pricing psychology helps you structure proposals that maximize acceptance rates and contract values.

Anchoring

Always present your highest-tier option first, even if you expect the client to choose mid-tier. The high anchor makes the mid-tier feel like a bargain.

Decoy Pricing

A three-tier model where the top tier is significantly more expensive than the middle creates a "decoy" that makes the middle tier look like the obvious choice:

• Silver: $45/device
• Gold: $65/device ← most clients choose this
• Platinum: $120/device (the decoy that makes Gold look reasonable)

Value Framing

Never quote prices without anchoring them to value. "Your 50-device environment will cost $3,250/month for comprehensive management" is less effective than:

"We will monitor your 50 devices 24/7, patch them automatically, and resolve most issues before your team is even aware of them. Compared to the $150,000 annual cost of a full-time IT person — plus the cost of a breach, which averages $197,000 for a company your size — $3,250/month is the most cost-effective way to protect your business."

The Danger of Discounting

Every $1 of discount costs you more than $1 in margin because your costs are fixed. If you have 50% gross margin and you discount 10%, you lose 10% of revenue but your costs stay the same — you have lost 20% of your profit.

Discount only when:

1. It secures a multi-year contract that improves your revenue predictability
2. It secures an anchor client in a new vertical you are targeting
3. It closes an account that has significant upsell potential

Never discount because the client "just asked." Train your sales team that the question is not "can we do better on price?" but "what would need to be true for this investment to make sense for you?"

Communicating Price Increases

Every MSP must raise prices periodically. How you do it matters as much as what you charge.

Build Repricing Into the Contract

Every MSP agreement should include:

• An annual CPI (Consumer Price Index) adjustment clause: "Pricing adjusts annually by the greater of 3% or CPI"
• Milestone-based repricing: "If managed device count increases by more than 20%, pricing will be renegotiated"

This normalizes price increases. They are not a surprise — they are a contractual term the client signed.

Lead With Value, Not Apology

"Given all the additional cybersecurity services we have added this year, and given that our labor costs have increased with market wages, we will be adjusting your monthly investment by 8% effective March 1" is better than "I am sorry but we need to raise prices."

You are not raising prices. You are adjusting the investment to reflect the value delivered.

Give 60–90 Days Notice

Surprise price increases damage trust. Give clients enough notice to plan their budget.

Know Your Walk-Away Rate

Not every client is worth keeping at a discounted rate. A client who argues against every renewal increase is typically unprofitable and difficult — losing them may actually improve your margins.

Pricing by MSP Stage

Your optimal pricing model depends on where you are in your MSP journey.

Stage 1: Launch (0–10 clients)

At this stage, you need clients more than you need perfect margins. Focus on:

• Getting into accounts with competitive but not giveaway pricing
• Using per-device pricing for simplicity
• Tracking hours meticulously so you build cost data for future pricing refinement
• Avoiding flat-rate until you have deep understanding of your costs

Stage 2: Growth (10–30 clients)

• Implement tiered pricing to drive upsells
• Start charging properly for security — this is where most MSPs undercharge catastrophically
• Build a documented service catalog so you can quote consistently
• Hire dedicated account management so pricing is not driven by technician relationships

Stage 3: Scale (30+ clients)

• Move toward hybrid pricing with well-defined base and add-on modules
• Implement quarterly business reviews to identify upsell opportunities
• Develop vertical-specific pricing packages (healthcare pricing that includes HIPAA compliance differs from general business pricing)
• Consider per-user pricing for professional services clients

The Pricing Mistakes That Kill MSPs

Underpricing security: In 2026, every managed environment needs endpoint protection, email security, and backup. These are not optional add-ons — they are the minimum standard of care. MSPs that do not include security in their standard pricing are setting themselves up for breach liability.

Ignoring scope creep: Every "quick favor" that falls outside the contract trains clients that scope is negotiable. Document out-of-scope work and bill for it, or explicitly discount it as a one-time courtesy — never perform it silently.

Not tracking time: You cannot price correctly if you do not know your actual cost. Implement time tracking (even lightweight tracking) for all MSP labor.

Annual contracts with no price escalation: A fixed-price annual contract in an environment where labor costs are rising 5–7% per year means you get less profitable every year. Always include price escalation mechanisms.

Pricing based on what competitors charge: Your costs are not your competitor's costs. Your service quality is not your competitor's quality. Price based on your value and your costs, not on a race to the bottom.

NinjaIT and MSP Pricing Optimization

A core driver of MSP profitability is the cost and efficiency of your tooling. NinjaIT's per-device pricing model is designed to align with how MSPs price their own services — you pay per monitored device, making it straightforward to calculate your tool costs as a component of your client pricing.

Automation capabilities — automated patching, self-healing scripts, intelligent alerting — directly reduce the labor hours per endpoint, improving your gross margin. An MSP that automates 30% of its routine work creates capacity for growth without additional headcount.

For MSP business and operations guidance, also see building a profitable MSP in 2026, MSP SLA guide and templates, and client onboarding best practices.

Frequently Asked Questions

Should I charge differently for servers vs. workstations? Yes. Servers are more complex, have higher criticality, require more careful patch management, and consume more monitoring resources. A 2–3× multiplier over workstation pricing is standard. Some MSPs also charge differently for domain controllers versus member servers.

How do I handle clients with contractors and temporary workers? Define device categories that include contractor-used devices, or use per-user pricing with a "contractor" tier at a lower price point. The key is to ensure every device you monitor generates revenue — do not allow clients to have unmonitored devices in their environment.

Is it okay to have different rates for different clients? Within reason, yes. New clients signed during a promotional period may have legacy rates. High-volume clients may have negotiated discounts. What you want to avoid is having no pricing discipline — where every client is on a custom one-off negotiated rate that you cannot even track.

How do I transition existing clients from one pricing model to another? Grandfather existing clients at their current rate while implementing new pricing for new clients. Give existing clients a clear timeline for transition (6–12 months) and communicate the value improvements they will receive. Bundle the transition with a service tier upgrade where possible.

What gross margin should I target? Industry benchmarks: 40–50% gross margin on managed services (revenue minus direct cost of delivery) is healthy for a growing MSP. Above 60% suggests underpricing for growth investment opportunities. Below 30% suggests pricing or operational efficiency problems.

Conclusion

There is no single "best" MSP pricing model. The right model depends on your cost structure, your client base, your growth stage, and your operational efficiency.

What is universal: you must know your true costs, price above them with sufficient margin for overhead and profit, and review pricing regularly as your costs and capabilities evolve.

Start with per-device pricing for its simplicity and scalability. Layer in tiered service bundles to drive upsells. Build toward hybrid pricing as your service catalog matures. And always, always track the hours.

The MSPs that build sustainable businesses are not those that compete on price — they are those that compete on value and have the numbers to prove it.

Explore NinjaIT's pricing for MSP tooling costs, and read our related guides on how to build a profitable MSP and MSP SLA templates.

Pricing for Specific Client Segments

Pricing for Healthcare Clients

Healthcare clients have higher compliance requirements (HIPAA) and higher risk profiles, which justify premium pricing. The additional services required for healthcare — HIPAA risk assessment, BAA management, ePHI system documentation, enhanced backup verification, workforce security training — genuinely cost more to deliver.

Healthcare premium framework:

• Base managed services rate: $80–$120/user/month (vs. $60–$90 for general business)
• Add: HIPAA compliance management: $500–$1,500/month flat
• Add: Backup for ePHI systems (verified, immutable): $15–$25/server/month
• Add: Annual HIPAA risk assessment: $2,500–$8,000/year as project work

Position this honestly: "Healthcare clients have specific regulatory requirements that require more time and more specialized tools. Our healthcare managed services rate reflects the additional compliance management we provide."

Pricing for Legal Firms

Law firms have strict confidentiality obligations and often specific legal matter management systems (Clio, MyCase, practice management platforms). Security requirements are high; price accordingly.

Legal firm considerations:

• Matter-specific data isolation requirements may require segmented network architecture
• E-discovery readiness requirements (data retention, legal hold)
• Bar association ethics requirements for technology providers handling client data

Legal premium: 15–25% above standard managed services pricing, plus bar association ethics compliance documentation as a billable add-on.

Pricing for Manufacturing (OT/ICS Environments)

Manufacturing environments often include Operational Technology (OT) — industrial control systems, SCADA, PLCs — that have different security and management requirements than IT systems. OT systems often cannot be patched (vendor restrictions, production uptime requirements) and require specialized monitoring.

Manufacturing pricing considerations:

• IT environment: standard per-device/user pricing
• OT environment: premium per-device pricing (1.5–2× IT rate) reflecting specialized expertise
• OT security assessment: $5,000–$20,000+ as project work
• If supporting CMMC compliance (many manufacturers are defense contractors): significant premium

Pricing for Startups and Small Teams

Small businesses (< 25 users) often struggle to afford full managed services pricing. Options:

Minimum monthly engagement: Set a floor — "our minimum is $1,500/month" — to ensure the engagement is economically viable. Below this floor, you are probably losing money after factoring in onboarding and account management overhead.

Essentials-only tier: Strip managed services to the core: remote monitoring (no 24/7 NOC), automated patching, basic security (endpoint protection), and helpdesk during business hours only. Priced at $40–$60/user/month to be accessible while maintaining margin.

Growth pricing: Explicit commitment to hold pricing as the client grows. "Your rate will not increase for the first 50 users." This gives startups confidence that IT costs are predictable as they scale, removing a common objection.

Handling Price Increases

Raising prices with existing clients is uncomfortable but necessary. Failing to raise prices means your margins erode as your costs increase (tool vendor price increases, labor market inflation, compliance requirements).

When to Raise Prices

• At renewal (annual or multi-year contract expiry)
• After a significant scope increase (new location, headcount growth, new services added)
• When you identify a client significantly below market rate (acquisition pricing that was never corrected)
• Annually, in line with inflation (3–5% annual adjustment)

How to Communicate Price Increases

Give appropriate notice: 60–90 days is the professional standard. Surprises in billing damage trust.

Provide context, not apology: "We are adjusting managed services rates by 8% effective [date] to reflect increased tool costs and the expanded security services we have incorporated into your standard package over the past year."

Quantify the value you have delivered: A price increase conversation is an opportunity to remind the client of what you have done. "In the past 12 months, we resolved 347 tickets, deployed 1,289 patches, detected and remediated 3 security incidents, and maintained 99.7% uptime on your critical systems."

Soften with a multi-year commitment option: "If you prefer to lock in current pricing, we can offer a 2-year agreement at today's rates."

Accept some client losses: Price-sensitive clients who leave over modest increases are often the lowest-margin, most demanding clients. Losing them may improve your overall business health.

Price Increase Template

Subject: Managed Services Rate Adjustment — [Month Year]

Dear [Client Contact],

Thank you for your continued trust in [MSP Name] as your managed services partner.

Effective [Date], we are adjusting our managed services rate from $[current]/month 
to $[new]/month for your [X]-user environment. This represents an [X]% adjustment.

This change reflects:
• Increased tool and infrastructure costs across our security stack
• Enhanced security capabilities we have added to your standard service (EDR, 
  advanced email filtering) over the past year
• Continued investment in our team's training and certifications

In [Year], our team delivered [X] support tickets resolved, [X] patches deployed, 
and [X] security threats identified and remediated — maintaining your environment's 
operational excellence and security posture.

We value your long-term partnership. If you would like to discuss this adjustment 
or explore a multi-year commitment at current pricing, please reach out to your 
account manager [Name] at [contact details].

Thank you for your continued partnership.

[Signature]

Building a Pricing Review Process

Pricing should be reviewed systematically, not ad hoc. A quarterly pricing review process prevents the drift that leads to underpriced clients.

Quarterly Pricing Review

Step 1: Gross margin by client (from your PSA time tracking):

• Total hours delivered per client last quarter
• Revenue received from client last quarter
• Direct cost (technician labor, tool allocations)
• Gross margin per client

Clients below 30% gross margin are underpriced or over-served. Identify the root cause before addressing it — sometimes it is a pricing problem, sometimes it is a scope problem.

Step 2: Hours vs. contract:

• What does the contract include (unlimited helpdesk? limited hours?)
• How many hours did you actually deliver?
• Which clients are consistently consuming above their contract level?

Clients systematically above their contract hours need either a scope conversation or a pricing adjustment.

Step 3: Market comparison:

• What are comparable MSPs in your market charging for equivalent services?
• Are you positioned where you want to be (premium/value/mid-market)?
• Are there services you are delivering at no cost that the market would pay for?

Step 4: Pricing decisions:

• Which clients need rate adjustments at renewal?
• Which clients should be offered new service tiers?
• Which clients are potentially underpriced even within their current tier?

This systematic review prevents the common pattern of discovering at renewal that you have been undercharging for two years. Regular attention keeps pricing current.

The Psychology of Pricing

Understanding pricing psychology helps structure proposals and conversations more effectively.

Anchoring: The first price a client sees anchors their perception of value. Always present your highest tier first. After seeing the enterprise tier at $12,000/month, the professional tier at $7,500/month feels reasonable.

Charm pricing: $99/device vs. $100/device makes a small perceptual difference. More relevant for managed services: "$4,750/month" may feel different from "$5,000/month" to some clients even though the difference is negligible.

Decoy pricing: A middle option that is clearly inferior to the top option (but priced close to it) makes the top option feel like better value. If your Professional tier is $7,500 and your Enterprise tier is $8,500, the Enterprise tier looks like excellent value for $1,000 more.

Value-based framing: $7,500/month sounds expensive. "$7,500/month to replace a $120,000/year IT director salary, plus a team of specialists available 24/7" sounds like a bargain.

Risk reduction framing: For clients who have experienced a security incident or compliance failure, pricing framed around risk reduction is compelling. "The average ransomware recovery for a company your size costs $85,000. Our managed security services at $6,500/month include backup, EDR, and proactive monitoring that statistically reduces your incident risk by 70%."

Understanding which frame resonates with a specific client requires listening in the discovery call — what are they worried about? Frame your value in those terms.

Frequently Asked Questions About MSP Pricing

What is the lowest I should ever charge per user per month?

The floor depends on your cost structure, but as a general market guidance: below $50/user/month for full managed services (monitoring, patching, helpdesk, security), you are almost certainly either losing money or delivering a service level that will result in client churn. The math: at $50/user and 15 users, you have $750/month. A single hour of a senior technician at $75/hour fully loaded, and you have used 10 hours just in labor before tool costs, account management, or overhead. If a client cannot afford your minimum, they are not a fit.

How do I price add-on security services without clients feeling nickel-and-dimed?

Bundle security essentials into your base managed services package rather than offering them as add-ons. Endpoint protection, DNS filtering, and email security are baseline services in 2026, not optional extras. Reserve the "add-on" label for genuinely premium services: 24/7 SOC monitoring, compliance management, SIEM. When everything security-basic is included in the base package, clients feel they are getting comprehensive coverage, not paying extra for every protection.

Should I offer month-to-month or require annual contracts?

Annual contracts (or longer) provide business stability and client commitment. Month-to-month clients have much higher churn rates. Industry best practice: annual contract minimum, with multi-year options at modest discounts. Offer month-to-month at a 15–20% premium to the annual rate — this appropriately prices the additional risk you are taking on, and most clients convert to annual when they see the cost difference.

How do I approach a client who is over-budget but genuinely needs your services?

Explore what you can remove from scope to hit their budget: can you deliver essential services only and leave optional services for a later phase? Can you phase the full implementation over multiple months? Be transparent that the reduced scope means reduced coverage and make sure they understand what they are accepting. Never silently reduce quality to meet a budget — always document the scope reduction and its implications.