Polestar Solutions

Field Notes

Google Cloud commits: the third bidder you should price anyway

You may never leave AWS or Azure, but pricing a credible Google Cloud commit changes your renewal anyway. How a third bidder you have actually costed moves your incumbent, without a migration.

Key points

  • On a $3M a year cloud commitment, an incumbent pricing against a credible costed competitor instead of a captive customer only has to move 4% for the model to be worth $120,000 a year, without a single workload changing homes.

A priced alternative beats a vague threat

Every buyer knows to say "we are looking at Google Cloud." Every account team knows it means nothing, because it is a vague threat with no economics behind it. What has weight is a specific, credible number: at your actual usage, a Google Cloud commitment at their published rates and realistic discounting would cost this, versus your incumbent's renewal at that. The difference between the two is the gap your incumbent has to justify, and it is a very different thing to defend a price against a modeled competitor than against a customer's general unhappiness.

Pricing the alternative properly means running your real workload through it, not gesturing at a competitor's marketing. Take your actual run rate and cost profile and model what the equivalent commitment on Google Cloud would look like, including their committed-use discounting, so the alternative is grounded in your usage rather than a headline rate. A modeled third bidder built from your own numbers is a document you can put on the table, and a document is leverage in a way a threat never is.

app.isvcosell.com/tooling/cloud-cost

The third bidder, costed from your own workload: a Google Cloud commit modeled at your real usage, not a competitor's headline rate.

THE SAME JOB, TWICE

TODAY, BY HAND

A cloud analyst pulls the incumbent renewal quote and the last twelve months of AWS or Azure billing exports into a spreadsheet.

They try to rebuild the estate on Google Cloud from published rate cards, guessing at committed-use discounting they have never negotiated.

The model stalls on workload mapping, so the alternative gets summarized as a slide that says we are evaluating Google Cloud.

On the renewal call the account team hears the vague threat, recognizes it as one, and prices the renewal against your reluctance.

Two to three weeks of modeling, usually abandoned halfway

WITH ISVCOSELL

Open the cloud cost tool and load your real run rate and cost profile, the actual usage the incumbent bills you for.

Model the equivalent Google Cloud commitment at published rates and realistic committed-use discounting, so the alternative is a number, not a gesture.

Set the incumbent renewal against the modeled commit side by side and identify the movable slice, the specific project or workload that could actually go.

Bring the workload-level model to the table as a document the account team has to price against.

An afternoon to a costed third bidder

What changes: weeks of half-finished rate-card modeling become an afternoon, and the renewal changes character. On a $3M a year cloud commitment, an incumbent pricing against a credible costed competitor instead of a captive customer only has to move 4% for the model to be worth $120,000 a year, without a single workload changing homes.

PART TWO

What the third bidder actually does to the deal

The value of a priced third bidder is not that you will act on it, it is what its existence does to the incumbent's calculus. An account team pricing a renewal against a customer with no alternative optimizes for margin; the same team pricing against a customer holding a credible, costed competitor optimizes for retention, and those produce different numbers. You do not have to threaten to leave. You have to make it clear, with numbers, that leaving has been costed and is not absurd, and the incumbent adjusts because they now have to.

This works precisely because the incumbent cannot be sure you are bluffing when the alternative is real and specific. A vague mention is easy to dismiss; a workload-level model of a Google Cloud commit, with a real number attached, forces the account team to consider that this customer has done the work and might actually move a portion of spend, or the next project, or the growth. The uncertainty you introduce is the leverage. The third bidder does not have to win the deal; it has to be credible enough that the incumbent negotiates as if it might.

"Your incumbent prices your renewal against your alternatives. If your only alternative is a vague threat, they price against nothing. A costed third bidder is the number that moves them."

PART THREE

Where a partial move is genuinely credible

The third bidder is most powerful where it is most believable, and cloud gives you natural places to make it real without a wholesale migration. A specific new project, a particular data or AI workload where Google Cloud has genuine strengths, a discrete environment that could run anywhere, each is a credible candidate for a partial move, and a partial move is a far more plausible threat than a full one. Pricing the third bidder for a specific, movable slice of your estate makes the alternative concrete rather than hypothetical, and concrete is what the incumbent respects.

This also protects you from the bluff being called. If you anchor your leverage on a full migration you have no intention of doing, a sharp account team may test it, and a bluff exposed is worse than none. Anchoring it on a genuinely movable workload means the threat is one you could actually execute, which makes it both more credible and safer to hold. The point of the third bidder is a stronger renewal on the estate you are keeping, and the way to get it is an alternative real enough that you would not be embarrassed to be held to it.

app.isvcosell.com/tooling/cloud-cost

The incumbent renewal against the modeled Google Cloud commit, with a movable workload as the credible, executable partial-move threat.

THE THIRD BIDDER

Pricing an alternative you may never take

1 Model from your workload. Cost a Google Cloud commit at your real run rate and their committed-use discounting, so the alternative is a number, not a gesture.

2 Make it specific. A workload-level model the incumbent has to price against beats "we are looking at Google," which they know means nothing.

3 Anchor on a movable slice. Point the threat at a genuinely portable project or workload, so the alternative is credible and safe to be held to.

4 Use it to keep, not leave. The third bidder wins you a stronger renewal on the estate you are keeping. It does not have to win the deal, only be credible.

THE HONEST LIMIT

A lever, not a bluff to overplay

A third bidder is leverage, and leverage overplayed becomes a liability. If you brandish a Google Cloud model you have not really thought through, a competent account team will find the holes, and a credible alternative that collapses under one question does more harm than staying quiet. The model has to be honest about migration reality and real about which workloads could actually move, or it is a bluff dressed up as analysis.

What pricing the third bidder removes is the worst position in a cloud renewal, which is having no alternative at all and negotiating on hope. You may have every intention of staying with your incumbent, and that is fine; the point is to stay on terms shaped by a real alternative rather than by your own captivity. A costed third bidder, held with discipline and anchored on something you could actually do, is how a locked-in customer negotiates like one who has a choice, because on paper, they do.

MA

About the author

Morten Andersen, Cofounder, ISVCOSELL

Morten brings two decades of enterprise and software procurement, with stints across Oracle, IBM, SAP, and Salesforce shaping how he reads a deal. He has led sourcing through hundreds of renewals, from mid market order forms to nine figure global agreements, and learned that the buyers who win are the ones who walk in knowing the market. He built ISVCOSELL to make that pattern recognition repeatable.

More posts by Morten Connect on LinkedIn →

See it in the product

How benchmarking works → Browse the use cases → Every feature → Calculate your time saved →

FREE TRIAL · FULL PLATFORM · NO CARD REQUIRED

Price the third bidder before your cloud renewal.

The free trial opens the benchmarking database, 1,483 vendors deep, plus the negotiation guides, playbooks, and talking points for your own renewals. No card needed, a corporate email is all it takes.

Start your free trial → Or decode a contract free, no account

Free for 30 days, no card needed. Your data stays isolated at the database, and you can export or delete it any time.

Watch it in action

The cloud commit grows again What discount should we expect? ISVCOSELL: the three minute demo

Browse the full demo library →

THE ISVCOSELL AI BRIEF · WEEKLY

The week in enterprise software buying, in one email.

What shipped on the platform, and the pricing and licensing moves worth knowing before your next renewal. One email a week, to your work address. Unsubscribe any time.

Subscribe

More in Field Notes

1,483 vendors, one method: how the benchmark library is built

A benchmark is only as good as the deals behind it and the honesty of how it is compared. How the library is built from modelled deal cohorts, normalized, placed in the right peer cohort, and graded by confidence.

Read

300 vendors, 52 weeks, one team: the renewal calendar problem

The average enterprise runs 300+ software vendors and every one of them renews. Why notice windows are where budgets quietly die, and how a renewal desk with AI agents turns the calendar from a threat into leverage.

Read

A calmer desk, and Main Apps where the work starts

The platform now wears the desktop look: warm paper, one interactive colour, and Main Apps folded into Home so your instruments live where you start.

Read

A live analyst in your ear: inside the call copilot

The vendor call is where prepared positions meet improvisation, and the rep does this every day. The live call copilot runs a whisper rail beside the conversation: live transcript, grounded prompts, and the exact fact you need at the moment the claim is made.

Read

Adobe ETLA vs VIP: seat reclaim, right-profiling, and the walk away

An Adobe ETLA renewal is decided before you discuss price, by how many seats sit idle and how many are over-profiled. How to reclaim the waste, right-profile the rest, and build the VIP walk away Adobe respects.

Read

Agent to agent: how the Agent Negotiation Protocol works

When a buyer's AI agent negotiates with a vendor's AI agent, someone has to keep the record straight. How the open Agent Negotiation Protocol handles identity, mandate, and a ledger neither side can rewrite.

Read

Want help putting this into practice?

Contact us to discuss your project.

Get in Touch