Pricing

The seats you decide not to buy

17 November 2026 · 12 min read

There is a decision every consultancy using per-user software makes, usually in about four seconds, usually without discussing it. Someone new starts, and somebody works out whether they really need their own login. The answer is often no. That four-second decision, repeated for two years, is why your records cannot tell you who did what.

This is not an argument that per-seat pricing is dishonest. It is a perfectly reasonable model and it works well in plenty of industries. It is an argument that it fits a consultancy badly, that the misfit shows up in your data rather than on your invoice, and that since April 2026 the damage has a name and a cost.

Why vendors price per seat

Give them their due: the logic is sound. A firm with forty staff gets more value from a CRM than a firm with four, so charging the larger firm more is fair. It is easy to understand, it scales revenue with customer success, and it gives a salesperson something to negotiate. Most business software is sold this way because most business software is bought by a company with an HR system, a fixed headcount, and a manager who can requisition a seat without thinking about it.

A consultancy is not that company. Its headcount is lumpy, seasonal, part-time, and extends beyond its payroll. And the pricing model that works fine for a software firm with forty engineers produces, in a consultancy, a quiet and continuous incentive to leave people out of the system.

The six people who do not get a login

Count how many of these you recognise.

The front desk

Someone answers the phone and greets walk-ins. Walk-ins are often your highest-intent enquiries — a student who physically came to your office is more serious than one who clicked an ad. Under seat pricing the receptionist rarely gets an account, because they are "not a counsellor." So walk-ins get written in a notebook and typed up later by somebody else, or not typed up at all, and the single best lead source in the building has the worst data in the building.

The junior who started in August

A new counsellor joins mid-season on a three-month trial. Adding a seat means a conversation with the vendor, a prorated charge, and a commitment you are not ready to make about someone who might not stay. So for the first few months they work out of a senior's account, or out of their own WhatsApp. By the time they are permanent, three months of their work is attributed to someone else or to nobody.

The accounts person

They need to see invoices and payments and nothing else. Paying a full counsellor seat for someone who will look at one screen feels absurd, so they do not get one. The finance data moves into a spreadsheet instead, and from that moment your books and your case records are two systems that disagree.

The branch that is two days a week

A second office, one person, part-time. A full-price seat for a two-day-a-week operation is hard to justify, so the branch reports in by WhatsApp and someone at head office enters it. The entries are a day late and they are a summary, not a record.

The owner's second login

This one is almost funny. The owner has an account. The owner's spouse or brother, who genuinely runs half the business, uses it. Two people, one identity, and an activity log that is now fiction for the most senior decisions in the firm.

The sub-agents

This is the expensive one. You work with four or five sub-agent offices who send you students. Giving them portal seats at per-user rates is a real cost against a referral relationship with uncertain volume, so you do not. They email you documents. Somebody downloads the attachments, renames them, and uploads them into the case. Nobody can say afterwards who checked what, or when, or whether the sub-agent was ever told the student's financial evidence was out of date.

Every one of those six decisions is individually sensible. Together they produce a record that cannot answer the question you will eventually be asked.

What those decisions do to your data

Shared logins destroy attribution

Attribution is not an HR nicety. It is the answer to "who advised this student, and what did they tell her." When three people use one account, every activity log entry is a guess. You cannot run a conversion rate by counsellor, you cannot investigate a complaint, and you cannot evidence oversight of anybody — because as far as the system is concerned, one person did all of it.

It also removes the only real deterrent in a records system. People are careful when their name is on the entry. When the entry says "admin", they are not being careless; they are being anonymous, which is different and worse.

Shadow systems appear wherever a seat was not bought

Every person you left out does their work somewhere. The front desk has a notebook, the branch has a WhatsApp group, accounts has a spreadsheet, the sub-agents have email. Those are not gaps in your system, they are competing systems, and each one has data your CRM does not.

The cost is not the duplication. It is that reconciling them is a person's job that nobody has been given, so it does not happen until something goes wrong, at which point it is archaeology.

The record thins out exactly where the risk is

Notice where the missing seats cluster: first contact, sub-agent oversight, and money. Those are the three areas a university partner will ask about, and they are the three areas seat pricing systematically pushes out of the system.

Why this stopped being just an annoyance

Since April 2026, UK sponsors have been required to evidence how they oversee their education agents. They do not have a magic view into your office, so that requirement lands on you as a request: show us what you do.

What they ask for, in practice, is who advised the student and what they were told, which documents were checked and when, the signed fee agreement and what was invoiced against it, how sub-agents were supervised, and what happened to the cases that were refused or withdrawn.

Read that list against the six missing seats. The walk-in has no first-contact record. The junior's three months are attributed to a senior who was not there. The invoice lives in a spreadsheet. The sub-agent oversight is an email thread on somebody's phone. You can still answer — by spending two weeks reconstructing it, which is what most firms do, and which produces a document that is an argument rather than a record.

This matters more in Pakistan than almost anywhere. Refusal rates for Pakistani applicants ran between 18 and 19 per cent in recent periods and withdrawals above forty per cent in some cohorts, several universities have suspended Pakistani recruitment outright, and partners are applying refusal thresholds as low as five per cent. The agents who keep their partnerships will be the ones who can produce a record on request. Being unable to is not a filing problem; it is a loss of the partnership.

The seasonality nobody prices for

A consultancy's staffing is not a line, it is a wave. Intake seasons bring temporary counsellors, interns, and relatives drafted in for six weeks. Between seasons the office is half empty.

Per-seat pricing handles that badly in both directions. Adding six seats for eight weeks means six prorated charges and six conversations with a vendor, so most firms do not bother and the temporary staff work out of permanent accounts. Then the season ends and the seats you did add are still billing, because removing a seat usually requires a support ticket and, on an annual plan, often cannot be done until renewal.

The result is a firm that is under-licensed exactly when volume is highest and over-licensed exactly when it is lowest. The invoice is wrong all year in alternating directions, and the records are thinnest during the period that generates most of the revenue.

The intern who did real work

The specific case worth naming: an intern spends ten weeks handling first-response on enquiries, which is genuinely useful and genuinely leaves a trail. Under a seat model they almost never get an identity. When a complaint arrives four months later about something said during that period, there is no record of who said it — the entries are under whoever's login they borrowed, and that person honestly does not remember.

You are then in the position of answering a university partner with "we believe a member of our team advised her, but we cannot confirm who." That is a worse answer than almost any mistake you could have made.

The cap version of the same problem

Flat pricing with caps has a cousin of this problem, and it should be named, because it is easy to treat "flat" as automatically better.

Relently publishes its tiers openly — Rs. 7,500 for 3 staff and 300 active students, Rs. 15,000 for 10 staff and 1,500, Rs. 35,000 for unlimited staff and students with 40 sub-agent seats, and Rs. 55,000 once sub-agent seats reach 41 to 65. That transparency is genuinely better than a vendor who will not tell you the price at all.

But a staff cap is a seat count with a different shape. Your fourth hire doubles the bill from Rs. 7,500 to Rs. 15,000, so the same four-second conversation happens, just less often and with more at stake.

The student cap has its own version. Relently defines active students as "files that aren't Enrolled or Closed" — your live pipeline. That number peaks in intake season, which is the worst possible moment to be choosing between an upgrade and closing files you are still working on. A file closed early to stay under a cap is a record that stops before the story does.

What flat pricing actually changes

Casly is $20 a month, flat, not per user, with no staff cap, no active-student cap and no branch limit. The point is not that it is a smaller number. It is that it removes the four-second conversation entirely.

When seats are free, the receptionist gets an account and walk-ins are logged at the desk by the person who met them. The August junior gets their own identity on day one, so their three trial months are their own work. The accounts person gets a login limited to what they need. The two-day branch enters its own cases. The owner and the co-owner have separate identities, so the activity log for the firm's biggest decisions is true. And the sub-agents get portal seats, which means documents arrive through a channel that records who sent what and when, instead of an email somebody has to transcribe.

None of that is a feature. It is the same features, used by everyone who should be using them, because nothing in the price is arguing against it.

The permissions point

Free seats only work if a seat can be narrow. Giving the front desk an account is a bad idea if that account can see company revenue. In Casly, company-wide financial aggregates are restricted to the CEO role, invoice visibility is gated separately, a counsellor sees only the balances of clients assigned to them, exports and printing are gated and logged, and no client-facing page shows money at all. The front desk gets an identity and the ability to log an enquiry, not the books.

The honest counter-argument

Flat pricing is not free of trade-offs and pretending otherwise would be the same marketing this post is complaining about.

A flat price means a four-person firm and a forty-person firm pay the same, which is worse value for the four-person firm than a well-designed per-seat plan would be. A vendor charging one flat rate has less revenue to spend on hand-holding, so you should expect self-service rather than a dedicated onboarding manager — if you want someone to sit with your team for a week, a vendor with a $500 setup service is selling you something real and this one is not. And a single low price is only sustainable if the product is genuinely multi-tenant and cheap to run; it is fair to ask any vendor charging it how that works.

There is also a legitimate version of the seat argument: a cost per person makes a firm think about whether each person needs access, and there are organisations where that discipline is healthy. In a twelve-person consultancy where the problem is that nobody is in the system rather than that too many people are, it is not.

The seven questions to ask about seats

If you are staying on a per-seat product — which may well be the right call — these are worth asking before you sign, because the answers vary far more than you would expect.

  1. What counts as a user? Some vendors count anyone who logs in. Some count only staff and give portal access away. Relently's page states its own definition plainly: staff seats count admins, managers and agents. Get yours in writing.
  2. Do sub-agents consume seats? This single answer can double or halve your bill. Ask specifically about portal access for people outside your company.
  3. Do clients and parents consume seats? They should not, and most vendors do not charge for them, but confirm it.
  4. Can I buy a cheaper, narrower seat? A read-only or finance-only account at a lower rate solves most of the problem. Many vendors have one and do not advertise it.
  5. How quickly can I add and remove seats, and who has to do it? If removing a seat needs a support ticket and a renewal date, your seasonal staffing will cost you all year.
  6. What happens to a departed counsellor's records? When the seat is removed, does their history stay attributed to them, or does it become orphaned? If it becomes orphaned, every staff departure erases part of your audit trail.
  7. Is the seat price locked, and for how long? Per-seat pricing scales with your growth, which means the vendor's revenue from you grows automatically. Ask what else can change on top of that.

Question six is the one people skip and it is the most important. A consultancy loses counsellors — it is a high-turnover role in most firms — and if your system's history depends on an active seat, then the oversight evidence for every student that counsellor touched walks out with them. Ask to see what a deactivated user's old entries look like. Make them show you, in the trial.

Count your real number before you buy anything

Do this before you look at a single pricing page. Write down every person who touches a student file in any way over a normal month. Include the receptionist, the part-timer, the accounts person, the owner's relative, the intern, and every sub-agent office. Not the payroll — everyone who touches a file.

That number is your real seat requirement. Most firms find it is between two and three times their headcount once sub-agents are counted.

Now take that number to every vendor and ask what it costs. Not your counsellor count. The real one. Then ask the question that follows from it: of those people, which ones would you quietly not add if each one had a price — and what would your records look like in two years without them?

That is the comparison. The monthly figure is just where it shows up.

One last thing worth saying plainly, because it is easy to read all of the above as an argument that you are being cheap. You are not. Every firm that shares a login is making a rational decision with the information in front of it: the cost of the seat is visible, immediate and on an invoice, and the cost of the missing record is invisible, deferred, and lands eighteen months later in a form nobody connects back to the decision. That asymmetry is the whole problem. Nobody chooses a worse audit trail; they choose a smaller bill, and the audit trail is what the smaller bill was made of.

The fix is not more discipline. It is removing the question, so that the default is an account for everyone who touches a file and nobody has to weigh a record against a line item at four seconds' notice.

Common questions

Why is per-user pricing a bad fit for an education consultancy?

Because a consultancy’s headcount is lumpy, seasonal and extends past its payroll. Under seat pricing the receptionist, the trial-period junior, the accounts person, the part-time branch and the sub-agents routinely do not get accounts, so walk-ins, first contact, money and sub-agent oversight move into notebooks, spreadsheets and email. Those are exactly the areas a university partner asks about.

Does Casly charge per user?

No. Casly is $20 per month flat, with no staff seat count, no active-student cap, no branch limit and no setup fee. The point is to remove the decision about who is worth a login.

Do sub-agents need paid seats?

It depends on the vendor, and this single answer can double or halve your bill, so ask it explicitly. Relently includes 40 sub-agent portal seats on its Rs. 35,000 Enterprise tier and moves the whole plan to Rs. 55,000 per month at 41 to 65 seats. Casly does not count seats at all.

What happens to a counsellor’s records when they leave?

Ask every vendor this during the trial and make them show you. If a deactivated user’s history becomes orphaned rather than staying attributed to them, every staff departure erases part of your audit trail — and counsellor turnover is high in this industry.

Is flat pricing always better than per-seat?

No. A flat price means a four-person firm pays what a forty-person firm pays, which is worse value for the small firm than a well-designed per-seat plan. A single low price also funds less hand-holding, so expect self-service rather than a dedicated onboarding manager. The argument here is about fit, not superiority.

Give everyone who touches a file a login

Flat pricing, no seat count, with permissions narrow enough to make that safe.

Start free
READ NEXT
Casly

Enterprise-grade CRM engineering, purpose-built for education and immigration consultants.

PRODUCT Features Pricing app.casly.app
COMPANY Blog Help center
LEGAL Privacy Terms
© 2026 Casly · Registered in England and Wales, company no. 13922535