Skip to content
Notifications
Clear all

Is there a standard markup for cloud infrastructure through a reseller?

4 Posts
4 Users
0 Reactions
18 Views
(@isabelr)
Estimable Member
Joined: 3 months ago
Posts: 59
Topic starter   [#12482]

Alright, let's cut through the vendor fog. I've been reviewing three different quotes for the same hypothetical GCP/AWS setup—same compute, same storage, same support tier—and the prices from their "premier partners" are all over the map. One was nearly 40% higher than the lowest.

This got me wondering: is there actually a standard, understood markup when you go through a reseller, or is it just a free-for-all? I'm not talking about the CSP's own list price, I mean the layer added by the middleman.

My cynical side assumes they look at your company's revenue and your compliance headaches (GDPR, SOC2, etc.) and price accordingly. The more desperate you look for a bundled "solution," the higher the margin. But I've heard whispers of a typical 10-15% range for just straight infrastructure, with the reseller making their cut from the CSP rebates on the back end.

Anyone willing to share anonymized data points? Not looking for exact figures, but the *delta* you've seen between a direct quote and a reseller quote. Especially if you've managed to peel back the licensing and support to see the raw infra cost.

Or is this a fool's errand, and the only rule is that there are no rules? —IR


Trust but verify – especially the audit log.


   
Quote
(@consultant_carl)
Honorable Member
Joined: 6 months ago
Posts: 412
 

Your cynical side isn't far off, honestly. The "standard" markup is a myth, in my experience. It's a free-for-all dressed up in partner-tier slide decks.

The 40% spread you're seeing is the real answer. That delta isn't just about compliance headaches or your revenue, though. It's often about what else is bundled into the deal. One quote might be padding margin to cover perceived pre-sales engineering or future "strategic guidance" they assume you'll need. The lowest quote might be a loss-leader to get your footprint on their books for those back-end rebates you mentioned, banking on your environment scaling later.

I've had clients get identical AWS Enterprise Support quotes from two partners with a 22% difference. When we pressed, the higher one included a vague "managed services runway" that wasn't in the spec. Peeling that back, the raw infra markup was around 8%. So the rule is: you have to force the breakdown. If they won't isolate the pure CSP list price plus their explicit markup for reselling, walk. They're hiding something.


Implementation is 80% process, 20% tool.


   
ReplyQuote
(@danielr23)
Reputable Member
Joined: 3 months ago
Posts: 359
 

> force the breakdown

This is the only method that works. We codified it into procurement. Any quote without a line-item separation of CSP list price and partner add-on fee is rejected automatically.

The 8% figure you found for raw infra is consistent with what I've seen for large, committed spend with no attached professional services. That number can go negative, however, if the partner is chasing a volume-based rebate from the CSP. That's when the loss-leader behavior starts.


Trust, but verify


   
ReplyQuote
(@chrisp)
Honorable Member
Joined: 3 months ago
Posts: 462
 

Exactly. That "managed services runway" is the classic catch-all for padding. I've seen it disguised as "onboarding," "environmental validation," or even "vendor liaison fees."

The 8% figure for pure infra rings true in competitive bids, but only after you've stripped out those bundled assumptions. Sometimes the markup isn't even a percentage, it's a flat monthly "management fee" that gets buried.

Forcing the breakdown is key. If they can't or won't, it usually means their value prop is too fuzzy to justify the cost.


✌️


   
ReplyQuote