Three buying situations: first-time, renewal, switch

The same product can be bought in very different ways. A buying situation describes where the buyer stands: buying something for the first time, renewing what it already has, or switching from another provider. For a subscription-like service, watch a fourth case too: expansion, more people inside a current account.

The situation decides what the buyer compares you with, what they fear, how many people get involved, how long it takes and what proof they want. That's why one deck for every prospect fails: it answers the wrong question for at least two of them.

Klasna for Teams has all three this week. Veloria has never bought corporate English: a first-time purchase. A design studio in Lviv, a client for a year, renews in December: a renewal, plus an expansion if it adds its support team. Cobalt has used another school and is unhappy: a switch. The test is simple: is there a current provider, and is it you? Name the situation, then plan the move.

A company buying something for the first time doesn't know what good looks like. It can't judge quality or price yet and isn't sure who should be involved. Its real alternative is not another supplier: it is doing nothing.

That makes the committee bigger and slower. Before anyone compares offers, someone inside has to convince the budget owner that the money should be spent on this at all. At Veloria, Pavlo first has to persuade the finance director that English for dispatchers is worth paying for.

So the move has two parts. First, sell the problem before the product: help Pavlo describe what weak English costs Veloria with its EU partners. Second, help them buy: suggest who to involve, what to measure and how to start small. A first-time buyer values a guide more than a feature list.

What doesn't fit: a discount that expires at month's end (pressure on someone who can't judge value yet), a comparison with three other schools (an answer to a question nobody asked) or supplier registration forms (they come much later).

A renewing client already knows you, which makes the renewal look easy. It is also easy to lose through neglect. The client doesn't mainly compare you with other schools' prices; it compares you with its own past year: did people attend, did it help, were the invoices right? Its fear is paying again for something nobody uses.

So bring the evidence before they ask: attendance, progress, what learners say. For the Lviv studio, whose renewal falls in December, that means a short review of the year well ahead of the date, not an invoice that arrives on time and says nothing.

If doubts appear and nobody answers them, a quiet renewal can turn into a fresh decision. Then procurement asks other schools for quotes, and you are back in a competitive purchase against suppliers who have nothing to prove about the past year. The cheapest renewal is the one where the value was visible all year long.

An expansion adds people, teams or uses inside an account you already have. The Lviv studio wants to add its support team alongside the renewal. It feels like a formality because the company knows Klasna, but the new team doesn't.

Treat an expansion as a small first-time purchase inside a familiar account. The users are new: support agents with their own shifts and needs. The money may be new too: the support team's lessons may come from a different budget line than the design team's. And the person who approves that budget may not be the one who signed the original contract.

So ask the first-time questions again, briefly: who pays for the new people, who will use the lessons, and what they need to see to say yes. The account relationship makes it faster, since the contract, the security review and the invoicing already exist, but skipping these questions is how expansions stall for months after everyone said it was a good idea.

A company that complains about its current provider is not automatically ready to move. Switching has a cost of its own: a new contract, new schedules, learners halfway through a course, and someone inside who chose the old provider and may feel judged. The switching buyer's fear is going through all that and ending up no better off.

Cobalt is unhappy with its language school and still under contract. It will compare Klasna with that school line by line, so a general pitch won't do. Find out exactly what isn't working and show how Klasna would fix that one thing, not everything. Don't attack the other school: somebody at Cobalt picked it, and that person may be on the call.

The trap is reading dissatisfaction as a buying signal and rushing to a price. A buyer who sees only a new invoice and a disruptive move often decides that the devil it knows is cheaper. Your job is to make the gain specific and the move small.

Each buying situation has its own comparison, and the comparison tells you what to do:

• First-time purchase: compared with doing nothing; the buyer fears buying something it can't yet judge. Sell the problem, then guide the decision.
• Renewal: compared with its own past year; the buyer fears paying again for something nobody uses. Show evidence of use and value early.
• Switch: compared with the current provider; the buyer fears the cost of changing for no real gain. Fix the one thing that isn't working and make the move easy.
• Expansion: new people inside a current account; the question is who pays for them and whether they'll use it. Treat it as a small first purchase.

This is a quick diagnostic for any Klasna for Teams conversation. Before writing a proposal, ask what the buyer will hold it up against. If you can't say, you don't yet know the situation, and that is the first question for the next call.

For a switching buyer, the decision is as much about the move as about the product. Once you know what isn't working, lower the cost of changing with three practical moves:

• Time the start to the current contract. Cobalt's agreement with its school still runs; a start date that fits its end avoids paying twice.
• Plan for learners mid-course. Say how their level and progress carry over, so nobody starts again from zero.
• Offer proof before the full move. A small trial group with success criteria agreed up front lets Cobalt test the fix on its real problem.

Some moves feel strong and backfire. Listing the other school's weaknesses offends whoever chose it. Sending the "why companies should train staff in English" deck answers a first-time buyer's question; Cobalt already believes in training. A price that "only holds if you sign this week" is invented pressure on a buyer whose real worry is risk, and it signals exactly the kind of supplier they're trying to leave.

Getting the situation wrong means answering questions nobody asked. Send Cobalt a "why train staff in English" deck and it will think you didn't listen; treat the Lviv studio like a cold lead and it will wonder whether Klasna has forgotten it.

Situations also change mid-deal, so name the situation again whenever the facts move. A renewal with falling attendance and no answers can turn into a switch, with Klasna as the school someone wants to leave. Signs include a client asking other schools for quotes, a new person reviewing the contract, or questions about value that nobody replied to. When that happens, the client now compares Klasna with an alternative, so the switch logic applies in reverse: find out exactly what isn't working, fix that, and make staying easy.

How it fits together: the buying situation sets what the buyer compares you with and fears, and so it sets your move. Next lesson: how to lower each committee member's risk with proof, pilots and guarantees.