Account tiers: one-to-one, one-to-few, one-to-many

With forty accounts and one seller, "our best for everyone" ends up thin for everyone. Account tiers split limited time by what an account could be worth and how well it fits. Klasna for Teams uses three:

• One-to-one: a handful of accounts, each with its own plan. For Veloria: a committee map, a sample lesson built on a customs form, a pilot plan agreed with Pavlo.
• One-to-few: clusters of similar companies that share one message. For twelve IT firms whose staff talk to foreign clients: one case study, one webinar, follow-ups adapted to each company.
• One-to-many: programs for everyone who fits the profile: a monthly newsletter, a clear pricing page, a sample lesson anyone can book.

The deeper the tier, the more the work is tailored to one company and the more hours it costs. A disqualified account gets no tier at all: it may still read the newsletter, but it gets no selling time.

The one-to-one tier goes to accounts where a win would change the year and the fit is real. Veloria, Cobalt and Orchid could each buy hundreds of lessons a month, and each has a work need for English.

One-to-one is account-based marketing (ABM) at its most personal: research on the company, a committee map, content written for its situation, and a plan agreed with the buyer. For Veloria that means a sample lesson built on a real customs form, not a generic deck. Because each account takes many hours, the tier stays small.

Three kinds of account don't belong here. A famous chain that wants English only as a perk fails a disqualifier, however large it is. A well-fitting IT firm that is one of a dozen similar ones belongs in a cluster with its peers, where shared work serves them all. And a company that visited the pricing page twice has shown a signal for one-to-many follow-up, not earned a personal plan.

Segments are useful for scoring, but tiers are given to accounts. Two companies with the same industry label can be very different customers, so score the company in front of you.

Orchid is a retail chain, and Teams' old retail clients lost money: they bought English as a perk for store staff. Orchid's request is different. It comes from the head office, for buyers and import staff who deal with foreign suppliers every day. That is a work need, the strongest predictor in the profile, so Orchid can sit in one-to-one despite the label.

The check works both ways. If it turns out that Orchid really wants a perk for its stores, it drops a tier, just as the profile would predict. Tiering by label alone would make two mistakes at once: it would bury a promising account because of its industry, and it would protect a weak account because its industry looks good.

Below one-to-one, the work is shared. One-to-few groups similar companies into a cluster that shares one message: for IT services firms in Kyiv and Lviv whose staff talk to foreign clients, one case study from a current client, one webinar on English for client calls, and follow-ups adapted to each firm. Teams' six current clients already suggest the clusters: IT firms, design studios, a law and accounting practice. What worked for them is the content.

One-to-many covers every other company that fits the profile: a newsletter, a clear pricing page, a sample lesson anyone can book. It costs little per account, and it does a second job: it shows who is ready to talk. A company that books a sample lesson or a call has raised its hand.

That's why the lowest tier is not a dumping ground. It's how Teams stays visible to dozens of fitting companies without spending selling hours on them, and how it finds the next accounts worth moving up.

Tiers are a plan for now, not a permanent label. Accounts change, and the tiers should follow what buyers do, by a rule written in advance, not by mood.

Teams' rules: a one-to-many company moves up when it books a call and passes the disqualifiers. A one-to-one account drops when its budget owner says "not this year". Written rules keep the tiers honest: nobody keeps a favourite account in one-to-one after it has gone quiet, and nobody ignores a small company that just asked for a proposal.

Sound practice, in short: keep one-to-one to a handful of accounts, because it's costly; group similar companies into clusters that share one case study and message; write down the move rules. Two common mistakes: putting every account above 500 employees in one-to-one, which tiers by size instead of fit and potential; and never moving an account once tiered "so the plan stays stable", which ignores exactly the signals the tiers exist to catch.

Tiers become real when they turn into hours. Teams' planning assumption is about 100 hours a month for account work: a working number, not a benchmark. The split: one-to-one gets 45 hours across three accounts, one-to-few 30 across three clusters, one-to-many 25.

Per account, the gap is large on purpose. Each one-to-one account gets 45 / 3 = 15 hours a month. A cluster of ten companies with 10 hours gets about one hour per company. Effort follows what an account could be worth: a win at Veloria could bring hundreds of lessons a month, while each IT firm in a cluster is smaller but served efficiently by shared work.

Writing the split down does two things. It shows whether the plan is realistic: if one-to-one needs 25 hours per account to be done properly, three accounts don't fit. And it makes every later change visible as a trade, because the total doesn't grow when someone adds an account.

Because the hours are fixed, adding an account to a deep tier always takes time from somewhere else. Leo wants a fourth one-to-one account at the same 15 hours each. Four accounts take 4 × 15 = 60 hours. With 100 hours in the month and one-to-many keeping its 25, one-to-few is left with 100 − 60 − 25 = 15 hours: half of what the clusters had.

So the fourth big account is paid for by the clusters of firms that already fit the profile best. That might still be the right call if the new account could change the year, but it should be made knowingly.

The practical move with Leo: show him the hours and ask which one-to-one account he'd drop, or which cluster he'd starve. A fixed budget of time turns a wish ("every big name in one-to-one") into a choice. Two errors to avoid in the arithmetic: assuming the clusters keep their 30 hours (the month doesn't stretch) or that they lose everything (one-to-many's 25 hours are protected in this plan).

Personal attention wins deals, so it is tempting to give it to more accounts. But with fixed hours, each extra one-to-one account takes time from clusters and programs and spreads the personal attention thinner. Past a handful, one-to-one stops being personal at all. Keep it to the few accounts that could change the year.

The tiers fit on one page: a short table with account or cluster, tier, why (potential and fit, such as "forty people need English for carriers and customs; a paid pilot is on the table; the budget path is being mapped"), what we'll do this quarter in things the buyer would notice ("send Pavlo a sample lesson built on a customs form" beats "research Veloria"), hours a month and the rule that moves it.

How it fits together: in this module the profile says who fits, the score ranks them, and the tiers decide how much time each gets. Next comes the module case: forty companies, two years of deals and one question: who is Teams' ideal customer?