Executive Summary
When an MSP client asks for a project to be delivered faster, at the same quality and for less money, the pressure often lands on the MSP’s team and margin. The Iron Triangle gives you a simple way to explain why speed, price and quality are connected – and why changing one affects the others.
- If speed and quality are fixed, the price usually has to rise.
- If price and quality are fixed, the delivery date usually has to move.
- If speed and price are fixed, scope or quality must change.
- The best response to pricing pressure is not an immediate discount. It is a question: Which two matter most?
What Is the Iron Triangle in MSP Sales?
Have you ever had a potential customer say something like this?
“We need this project completed urgently. It has to be done properly. And we need you to sharpen your pencil on the price.”
In other words, they want it fast, they want it good and they want it cheap.
Customers, eh?
The problem is that those three things rarely go together. This is where the Iron Triangle can help.
The classic project-management triangle is normally expressed as time, cost and scope, with quality affected by the balance between them. Microsoft describes the same principle simply: a project’s budget, schedule or scope cannot change without affecting at least one of the other two. For a client conversation, I translate those constraints into three words that are easier to discuss: speed, price and quality.
Why Can't MSP Clients Have Speed, Low Price and High Quality?
The Iron Triangle does not mean that an MSP cannot deliver excellent work quickly or cost-effectively. It means that every promise uses resources. Engineers have limited capacity. Security controls need testing. Migrations need planning. Third-party suppliers have lead times. Other clients already have commitments in the diary.
If the customer changes one constraint, something else usually needs to move to keep the project safe and commercially viable.
Client prioritises | What must move | MSP implication | Useful response |
Speed + quality | Price | Extra or specialist resource may be required | We can accelerate this, but the investment will increase. |
Price + quality | Time | Work must fit normal capacity and sequencing | We can protect the standard and budget with a longer delivery window. |
Speed + price | Scope or quality | Deliverables must be reduced or risk rises | We can meet the date and budget if we agree what moves to phase two. |
How Does the Iron Triangle Protect MSP Margin?
Many MSPs do not lose margin because they priced the original project badly. They lose it after the proposal, one small concession at a time.
- The prospect asks for a lower price, so the MSP reduces it.
- The customer then asks for an earlier delivery date, so the MSP agrees.
- The scope and quality expectations remain exactly the same.
The MSP absorbs the difference. Engineers work longer hours. Other projects are delayed. Senior technical people are pulled into delivery. Margin disappears and the team becomes frustrated.
The commercial problem is not simply that the customer asked. It is that nobody explained the trade-off.
I have seen this repeatedly when working with MSP founders and sales teams. They want to be helpful, so they say yes before calculating what that promise will do to engineering capacity, delivery risk and profitability. The Iron Triangle gives them a neutral framework. It turns an emotional negotiation into a practical business decision.
How Should an MSP Use the Iron Triangle in a Sales Conversation?
1. Confirm the pressure
Start by clarifying the request: “You have asked us to bring the project forward while keeping the same outcome and reducing the cost. Have I understood that correctly?”
This prevents you from reacting to an assumption. Sometimes the apparent deadline is only a preference. Sometimes the price objection is really a request for reassurance.
2. Ask which two matter most
Use questions such as:
- Is keeping the project within a particular budget the main priority?
- Is there a deadline that absolutely cannot move?
- Is achieving the full outcome at the required standard the most important factor?
- Of speed, price and quality, which two matter most to you?
These questions help the prospect rank their priorities instead of treating every preference as non-negotiable.
3. Explain the consequence of their choice
If speed and quality matter most, you might say:
“We can deliver this quickly and to the standard you need, but we will need to bring in additional resources and reschedule other work. That means the investment will be higher. How would that work for you?”
If price and quality matter most:
“We can deliver within that budget and maintain the standard you need, but we will need a longer delivery window. How comfortable would you feel about this taking an additional three weeks?”
If speed and price matter most, do not casually agree to lower quality. In an MSP environment, particularly around cybersecurity, backup or compliance, poor quality can create unacceptable risk. Reduce or phase the scope instead:
“We can meet the date and budget if we prioritise the critical controls now and move the lower-priority items into phase two. Which outcomes must be live on day one?”
4. Record the agreed trade-off
Once the prospect chooses, document the consequence in the proposal, statement of work or change request. Confirm the deadline, budget, scope, responsibilities, assumptions and what is explicitly excluded. A good sales conversation protects the relationship; clear documentation protects delivery.
Why Shouldn't MSPs Discount Before Understanding the Priority?
When pricing pressure appears, too many MSPs immediately assume the prospect wants a discount. But price may not be the deciding factor.
- Their current IT support contract may be ending on a fixed date.
- They may be opening a new office and need the network live before staff arrive.
- Their insurer may have given them 30 days to implement new security controls.
- A compliance deadline may create a financial or operational consequence if they miss it.
If the deadline matters more than the price, reducing your fee makes no commercial sense. The customer may be willing to pay more if you can confidently deliver the right outcome on time.
But you will only discover that if you ask.
Do not negotiate against yourself before you understand what the prospect really cares about. This is closely connected to the value conversation: when a buyer cannot see the commercial outcome, price becomes the easiest thing to challenge.
Three MSP Examples of the Iron Triangle in Practice
Example 1: A Microsoft 365 migration must happen sooner
A prospect wants 120 users migrated before their existing agreement renews. The proposed date is six weeks away, but they ask you to complete it in three.
The right response is not to squeeze six weeks of work into three for the same fee. Explore whether the deadline is fixed, identify the work required to accelerate testing and user support, and price the extra resource. If budget cannot move, phase the migration or revisit the deadline.
Example 2: Cybersecurity controls are needed on a fixed budget
A business must improve its security position but cannot fund the full roadmap this quarter. Quality cannot be compromised because weak implementation leaves both the customer and MSP exposed.
Prioritise the highest-risk controls, agree what will be delivered now and schedule the remaining work. Here, price and quality are protected by moving time and scope.
Example 3: A new office needs to open on Monday
The opening date cannot move, but equipment delivery and third-party connectivity are at risk. The customer still expects the full environment to be ready.
Use the triangle to separate the essential day-one outcome from the ideal end state. A temporary connectivity solution or phased deployment may protect the deadline, while the permanent solution follows. The customer sees the choice and owns the decision.
What Mistakes Do MSPs Make When Using the Iron Triangle?
Using it as an ultimatum. The framework should open a conversation, not shut one down. Ask questions and let the prospect establish the priority.
Treating quality as casually negotiable. For security, compliance and resilience work, quality may have a minimum safe standard. In those cases, change scope, timing or cost instead.
Ignoring scope. The client-facing shorthand is speed, price and quality, but many project-management sources use time, cost and scope. If the budget and deadline are fixed, reducing or phasing scope is often safer than lowering quality.
Failing to quantify urgency. A date is not automatically a business deadline. Ask what happens if the project is delivered one week later.
Agreeing verbally and documenting nothing. The proposal and statement of work must reflect the chosen trade-off, or the delivery team will inherit conflicting expectations.
A Simple Iron Triangle Checklist for MSP Proposals
- What business outcome is the customer trying to achieve?
- Which date is fixed, and why?
- Which budget limit is genuine, and who set it?
- What quality or security standards cannot be reduced?
- Which deliverables are essential on day one?
- What can be phased, removed or rescheduled?
- What additional resource is needed to accelerate delivery?
- Has the agreed trade-off been documented and approved?
Frequently Asked Questions
What is the Iron Triangle?
The Iron Triangle is a project-management model showing that time, cost and scope are interdependent. In a simple client conversation, MSPs can express these as speed, price and quality. A change to one factor usually requires movement in at least one other factor.
What does 'fast, cheap or good - choose two' mean?
It means a customer can normally prioritise two outcomes without expecting the third to remain unchanged. Fast and good usually costs more. Good and cheap usually takes longer. Fast and cheap usually requires a smaller scope or creates quality risk.
Should an MSP ever compromise on quality?
Not below a safe, compliant or professionally acceptable standard. For cybersecurity, backup, resilience and regulated work, the better option is usually to reduce scope, phase delivery, extend time or increase budget.
How can the Iron Triangle help with price objections?
It shifts the conversation away from a blanket discount and towards priorities. Once you know whether the buyer values deadline, budget or outcome most, you can propose a commercially sensible trade-off.
When should an MSP discuss the Iron Triangle?
Use it during discovery, proposal review, project scoping and any change request that affects the deadline, budget, scope or delivery standard. The earlier the trade-offs are discussed, the less pressure lands on the delivery team.
What should an MSP do if the client insists on all three?
Explain the resources and risks clearly, offer structured options and be prepared to walk away if the request cannot be delivered safely or profitably. An impossible promise is not good customer service.
The Real Job Is to Explain the Choices
Most sensible prospects understand that they cannot have the lowest price, the highest quality and immediate delivery. They simply need someone to explain the choices clearly.
That is what the Iron Triangle allows you to do.
- It protects your margin without making you defensive.
- It helps the customer understand why your proposal costs what it does.
- It gives your delivery team realistic expectations.
- It turns an uncomfortable negotiation into a practical business discussion.
The next time a prospect wants everything faster, better and cheaper, do not immediately agree. Draw the triangle, explain speed, price and quality, and ask: Which two matter most to you?
Their answer may completely change the conversation.
