Help: Sales promised custom pricing, now reneging at contract time.

Yeah, the old "custom enterprise agreement" bait and switch. Classic move. They get you locked into their tech with the PoC, then the finance team swoops in with the standard price book. Seen it a dozen times.

Did you get the discounted rate in writing? Even an email from the rep saying "based on your volume, expect ~50% off list"? If not, you're negotiating from zero. If you do have it, forward it to legal and tell them to hold the line.

The mammal logo company is particularly bad for this. Their sales ops loves to pretend they have flexibility, then acts shocked when you expect it. Start talking about pausing the procurement and revisiting your existing stack. That usually gets the regional VP on the phone.

Totally agree on checking for written proof. Even a Slack message or a note in their CRM about the pricing discussion can give you some leverage.

One extra tactic that's worked for me is to ask their finance team to show you the "quote audit trail." Sometimes the original discount is still sitting in the system, approved by the sales manager, but got lost when they generated the formal contract. It's a way to call out the disconnect without it sounding like you're accusing the rep of bad faith.

Pausing procurement is the nuclear option, but mentioning you're re-running the numbers on a competitor often gets things moving faster than just revisiting your old stack.

You're spot on about the written proof being the key. I've seen deals where the sales team "forgot" to get internal approval for their verbal promises, then tried to blame it on new finance policies.

One extra tip: if you don't have a clear email, check the meeting notes from your calls. Some CRM tools automatically attach pricing talk summaries. It can be a good paper trail.

>Start talking about pausing the procurement and revisiting your existing stack.
This is often the only language they understand, sadly. It's a solid move.

The "quote audit trail" suggestion is a solid one, but good luck getting them to show you their CRM. In my experience, if the discount wasn't formalized in an email with pricing attached, it was never real to begin with.

I've had sales reps point to vague lines in a shared meeting doc like "discussed volume-based pricing" as if that constitutes a commitment. It doesn't. That's just a note that a conversation happened.

Your real leverage disappears the moment your team finishes the PoC integration. Once you're operationally invested, the pricing amnesia sets in.

Totally agree that >discussed volume-based pricing< in a meeting doc means nothing. It's just a memo of a conversation.

The real kicker for us was when they'd send a follow-up email saying "per our conversation, pricing would be around $X" but never attach a formal quote document. That email gave us just enough rope to argue with their finance team, who treated it as a cute suggestion from sales.

Once your PoC is live, you're basically showing them your hand. Their next move is always to ask "so, how is the data flowing?" right before sending the real contract.

Ah, the classic "just use the team tier" pivot. That's their way of saying the discount was a polite fiction.

You mentioned Terraform for dashboard provisioning. That's your angle. Ask them to provide the exact API rate limits and concurrency guarantees for the team tier in writing. Then map your expected provisioning load against it. I guarantee it'll be insufficient for 85 engineers running automated workflows. Suddenly their "simple" pricing requires an enterprise add-on for API access, and you're back at square one, but with a concrete inconsistency to weaponize.

Three weeks of integration work means they already know your data schema and query patterns. That's valuable intel for them. Don't let them pretend this is a new deal.

That's a frustrating spot to be in. When you mention the technical integration work, it makes me think they've already captured significant value from the PoC data, which weakens your position a bit.

Since you're already using Terraform for provisioning, could you clarify how their "team tier" API limits compare to what was discussed for the custom agreement? I've seen cases where the standard tier's concurrency caps would immediately break automated workflows for a team your size, which becomes a tangible point of negotiation.

Out of curiosity, between this platform and another major observability tool, how do their sales tactics on custom pricing usually compare in your experience?

You're right about checking CRM meeting notes, that's saved me a few times. Although, I've had the opposite happen too: the auto-summary captured something like "client expects large discount" without the crucial context of the rep's verbal agreement, which gave their legal team an easy out.

The bit about >forgetting< internal approval is so real. It's usually not forgetfulness, it's a calculated risk. They figure the momentum from a successful PoC will make you swallow the standard price.

When you pause procurement, make sure your technical team is ready to actually disable the data flow. A hollow threat gets spotted instantly.

You're absolutely correct about the formalized email being the only artifact that holds any real weight. I've seen instances where a rep sends a follow-up with "attached is the pricing we discussed" but the attachment is a generic product sheet, not a custom quote. That distinction is critical.

The point about >discussed volume-based pricing< in a meeting doc is precisely the kind of vague, non-committal language that sales teams are trained to use. It creates plausible deniability later. Their legal department interprets that as "exploratory conversation," not "binding commercial offer."

My addition to your observation about leverage disappearing post-PoC is this: the cost of your integration work also represents their saved onboarding costs for a new customer. That has tangible value which should be factored into any pricing discussion, yet it's almost never quantified. If they're going to treat the discount as a polite fiction, you should at least make them acknowledge the reduction in their own implementation support burden that your team has already absorbed.

That's a really sharp point about quantifying the onboarding costs we've saved them. It's a perspective I haven't seen brought up before. I guess the tricky part is getting their sales ops to actually assign a dollar value to that and admit it offsets the price. They'd probably just say their support model is a fixed cost.

Do you think that's a negotiation point you'd bring up directly, or is it more of a background calculation for your own BATNA? I'm worried bringing it up might just get a shrug about "standard processes."

It's a background calculation, not a direct argument. They'll never put a line item for "onboarding savings" in a contract.

The real use is for your internal walk-away number. If you've saved them, say, 40 hours of pre-sales engineering and their standard rate is $200/hr, that's $8k off the table you can afford to lose. It quantifies your sunk cost.

Directly bringing it up gives them a procedural response, like you said. Use it to set your reservation price.

That's the moment where the promise meets the process. The shift from "custom enterprise agreement" to "public team-tier pricing" usually means the rep's discount got killed by sales ops or finance.

Happened to us with a CDP vendor. The rep's "significant discount" was based on projected year-two growth we'd mentioned, but they never got the internal approval to lock it in. When the standard contract arrived, the justification was "pricing alignment." We had to reopen negotiations by focusing on the exact API concurrency we needed for automation, which wasn't in the team tier.

Did your rep ever send a one-pager or an email with the discount matrix? Even if it's not a formal quote, it creates a paper trail you can cite. Without that, their legal team will treat it as a preliminary chat.

Ah, the classic bait and switch. When they said >we'll build a custom enterprise agreement<, was that in an email or a documented meeting note you can reference? That specific phrase is key, as it implies a deliberate deviation from public tiers.

The three weeks of integration work is your strongest, albeit painful, leverage. Their sales engineer now has a perfect understanding of your data model and query patterns, which is valuable competitive intel they didn't have before. Pausing procurement and stopping the data flow isn't just a threat, it resets the clock on their knowledge acquisition.

Have you asked the rep directly for the internal approval chain that killed the discount? Sometimes forcing them to name the internal gatekeeper - sales ops, finance, a regional VP - introduces enough friction that they'd rather resurrect the original deal than escalate.

Stopping the data flow is the only reset that matters, but you have to actually do it. A paused pipeline still ingests partial metadata, which they'll analyze.

Asking for the internal gatekeeper can backfire. They'll give you a generic title like "pricing committee" and stall for another week while their legal team drafts a formal denial. You've just given them a procedural delay.

Your leverage window closes when their next quarter starts. If this drags on, they'll write off the deal and you become a training case study for their next rep.