The Objections Are the Deal: Startup Sales Lessons

At GTM Academy in San Francisco, our cofounder Sudheesh Nair sat down with Nishkarsh, founder of HydraDB, and worked through the questions a buyer actually asks. Not the pitch. The pushback.

The two of them are at different points on the same curve. Sudheesh was president of Nutanix, then CEO of ThoughtSpot for six years. HydraDB is months old. As Nishkarsh put it, "if it's like a graduation curve so these just kind of like the top of the curve right now I'm somewhere in the middle." The answers below are better for that gap, not worse.

Most of it came back to money. Four of the objections below are the price question in different clothes. Two more are what is left once price is agreed. One rule ran under all of them, from Sudheesh: "never answer a question that they didn't ask."

So what does it cost?

Answer with a range, not a number. You cannot dodge the question. Nobody takes a meeting without knowing whether the answer is ten dollars or ten million. But a single number, given early, is a number you will negotiate against yourself. Nishkarsh described the spiral: you walk in with two million in your head, someone says a hundred thousand, and by the end of the exchange you are discounting seventy.

His fix is to know what you are pricing for. "Am I de-risking technology? Am I de-risking product?" he asked, with go to market as the third. HydraDB's first customer paid one dollar for a workflow that cost five to run. "We were losing $4 in every single workflow they ran," he said, and took it, because what he was de-risking at that point was the technology.

Sudheesh splits the room into what he calls "flounders and founders." The flounder says nothing, or says it depends.

The answer that gets you to a second meeting is a range: "we have customers in the range of, I don't know, $17 to $7 million."

The range can be absurd. That is not the point. "When you give that range, customers will actually now say, okay, now I want to know where will I fall? And that means your discovery calls will start."

Then stop talking. Nishkarsh: "Don't, just don't say anything and let the person in front of you come back to you."

Someone in the room asked how you say five million with a straight face. Sudheesh's answer was that you do not, not yet. "First few customers, you are buying them. They are not buying your product."

Why are you more expensive than them?

The name is bait. Sudheesh's point is that the question is a test of temperament. "Most vendors are not comfortable hearing their competitors name," he said, and buyers who negotiate for a living know it. There are two reflexes, and both lose: cut the price, or attack the competitor.

What works instead is to "compare outcomes, not what you're actually seeing in terms of the line items." He recommends rehearsal, seriously. "You need to be in front of a mirror. You take your competitor that you hate the most." Say the name until it stops doing anything to you.

Then you can ask the useful question: if you like them, why are you not already with them?

Nishkarsh, whose product is meant to be the cheap option, gets the same question from the other direction. His way out is expertise. One prospect kept raising a competitor's free VPC peering. He changed the conversation by asking whether they had thought about rotating their ELB addresses. They had not. "We'd rather act as your knowledge partners," he said, than be the cheapest line item.

Sudheesh added the diagnostic: "if there is a big price delta chances are something is off." Different scope, different capability, or you have mispositioned yourself. That is an investigation, not a discount.

Just give me your best price.

Separate the bill. The product number can flex. The expertise cannot, because it is arithmetic. Two engineers across time zones cost what two engineers cost: "One engineer is going to cost you $200,000. Two engineers are simply going to cost you $400,000." He holds that line and says so out loud.

"Quality does not come with discounts."

Sudheesh's rule came from a negotiation course years ago and he still repeats it: "no unilateral concessions." If the price moves, something moves back. A video testimonial. A speaking slot. Something you wanted anyway, now bought rather than given.

The harder discipline is walking. Nishkarsh quoted a seed-stage company five thousand dollars a month and was told they would not pay it. He let them go, because they sat slightly outside the profile he had defined. He was, in his word, terrified. They came back three months later.

"Try walking away once or twice, and that changes your perception completely."

We don't have the budget.

Usually that means no new money, not no money. Nishkarsh stopped fighting for budget already committed. Instead of offering to replace a working stack, he looks for a greenfield use case, which has no incumbent line item to be compared against. When one prospect stalled, he handed over the evaluation itself: run it, and "if it's working out for you you will never hear from us." Their engineers ran it. It did not work. They came back.

Sudheesh's version is that the cost of standing still has to be made concrete, and then you have to help them pay for it. "It is not enough to explain why they should buy us. It is on us to tell them where to find the money." In most companies, he said, "there is no new money you are actually doing something called share shifting."

Which means you need an answer to the question the buyer cannot ask on your behalf: what should I stop buying so I can buy your product.

Two more, once the price stops being the argument.

You're too small. Who else is using this?

Being small is the argument, not the problem. An attendee framed it as power dynamics stacked against the startup. Sudheesh disagreed with the premise. They took the meeting. Something is wrong that nobody else has fixed. "You are the doctor," he said.

Competing against Microsoft at a large retailer with no reference customers, he told the buyer the truth: you will be among our first ten customers. Then he made the size differential the case. "Microsoft can afford to lose this account and they will still be fine." Against that, "if I lose you, my chances of me closing my next round, making the payment, all of those things that happen".

So "who do you think is going to work hardest for your deal?" And after signature, "who's going to be on your WhatsApp?"

That buyer is still on his, two companies later.

Nishkarsh gets the policy version. One company would not work with vendors under three years old. "I said, by the time you work with us, we will be three years old." His GTM lead broke another stall by offering to skip the POC and go straight to production. The room went quiet, then agreed to the POC and signed. Some requirements are immovable, though, and you qualify out: "you literally cannot backdate your startup's age, or at least you shouldn't."

Security and legal will take months.

Procurement cannot win your deal, but it can delay it to death. Sudheesh gave three moves, scoped to companies of a few thousand people or fewer. Coach the champion before they need it:

“you have to manifest their future for them"

Meaning walk them through what procurement and security will say, and what they will answer. Refuse the queue, because "customers love running sequentially", NDA then pilot then the security questionnaire, when most of it can run at once. And treat procurement as a buyer rather than an obstacle. They are measured on something, and it is not always price. "Procurement teams want to be on stage telling stories video case studies." Give them one.

One attendee added a procurement FAQ: year on year increase, true ups, true downs, infosec, written once and sent right after the demo, so the champion can run it internally.

On legal, Sudheesh was short. Work on their paper. "You should ask for their mutual NDA and sign it." Concede what a founder can concede and do not let lawyers run the company. What you never trade is the product itself: "build good product sell with high integrity do not mess with security privacy and compliance."

The objections are the deal.

Sudheesh closed on the thing the whole session had been circling.

"The objections are the deal. You know, you are not getting the deal without objection. If you don't get objection, that means the deal is not there."