A Clientexec license bought in 2006 with one year of updates included has, on the company’s own account, been able to take every upgrade since. That ends at version 7.2.1.

Clientexec is billing and client management software that hosting companies run themselves to invoice their customers. Owners of an Owned License whose update period has lapsed will need a $50 extension before they can upgrade, and licenses sold with lifetime updates are unaffected.

The awkward part is what happens to anyone who tries without one. According to the email, the installation will fail to complete the upgrade, and the remedy is to restore from backup or re-upload the files of the previous version.

A thread on WebHostingTalk filled in what the email did not. A representative posting under the company’s own account spent an evening answering, explained why the failure looks like that, and apologized for how the email had been worded.

Key facts

  • What changes: the one-year update window included with Owned Licenses starts being enforced at version 7.2.1. The company says license terms themselves are not changing.
  • Cost to resume upgrades: a 1 Year Updates Extension, given in the email as $50, bought through the customer account rather than listed on the public pricing page.
  • The failure mode: attempting 7.2.1 without an active extension leaves the upgrade incomplete, with restore from backup or re-uploading the previous version as the way out.
  • Why it fails rather than refuses: the company says its auto-upgrade system was never built to check update entitlement, and the check arrives inside 7.2.1 itself.
  • Unaffected: licenses sold with lifetime updates, according to the company.
  • Context: Owned License sales were discontinued in December 2025, alongside what the company described as its first price increase for existing clients in a 23-year history.

One Year of Updates, Twenty Years of Not Checking

The Owned License was Clientexec’s perpetual option: pay once, run it indefinitely. What that license included, and what customers experienced, drifted apart.

The email puts it plainly. An Owned License came with one year of software updates, and “Historically, we haven’t strictly enforced this update period, which has allowed customers with expired update access to continue upgrading to newer versions of Clientexec.”

That is the tension. The company’s position is that nothing in the written terms is being altered, and it said so repeatedly: “we are not changing the terms or conditions of any existing licenses”, and separately that it is “beginning to enforce the update eligibility requirements that already applied to licenses when they were originally sold”. But two decades of not checking builds an expectation of its own, and when the checking starts, customers experience a change even where the contract has none.

The $50 figure also appears in Clientexec’s public documentation, which gives it as the annual price for updates and support on an Owned License and says that without paying it a customer can carry on using the version covered by the original license and pay “when you wish to upgrade to a newer version”. That page carries an update date of 20 August, the same day the email went out, and we found no archived copy of it, so it does not establish how long the figure has been published.

There is prior context on the record. In December 2025, Clientexec raised leased pricing in what that announcement described as the first increase for existing clients in a 23-year history, taking the branded leased plan from $12.95 to $16.95 a month and the unbranded from $14.95 to $19.95, with existing customers moving across on 1 February 2026. The same post said the company had “made the decision to discontinue owned license sales effective immediately”, while adding that support and updates for owned licenses “will continue to be available and can be renewed as normal”. Those are two dated facts eight months apart. Neither the December announcement nor the thread presents them as a single plan.

The Hosting Price Squeeze, Part 1: Why Your Costs Keep Climbing

Why the Upgrade Fails Instead of Refusing

The most specific criticism in the thread was not the fee but the way that first blocked upgrade would fail. A blocked upgrade, the argument ran, should be blocked rather than attempted and abandoned. One long-standing participant argued for warnings or a withheld download instead, saying that “Users won’t be happy with the ‘it failed, revert versions’ approach”.

The company gave a specific reason. Its representative agreed that “preventing the upgrade in the first place is a much better experience”, and explained that the auto-upgrade system “was never built to check whether a particular version was covered by a license’s updates period”. The eligibility check therefore has to arrive as part of 7.2.1. From that release onward, the company says, the upgrade process will check and “clearly tell you that your license isn’t eligible before allowing the upgrade to proceed”.

That makes 7.2.1 the awkward transition, because it is the release that installs the checking. The company also said this is why it wrote to customers ahead of the release rather than shipping it and “catching people by surprise”.

A hosting operator in the thread reached the same diagnosis independently, reading the rollback as being “about the mechanism to check this being built into the new version, not the version people are updating from”, and suggested an intermediate release that adds the check without moving the base install, or simply granting everyone one more update. The company did not indicate in the thread that it would adopt either suggestion.

The Fee Drew Less Objection Than the WHMCS Comparison

Reaction in the thread was not one-sided. Several said the fee itself was fair. One said $50 a year “doesn’t sound at all unreasonable” given that the license had included one year of updates; another accepted it provided the term was stated at purchase; a third read the notice as a term that “was stated but not enforced as stated” now being corrected. A fourth described expired licenses being able to update as “a bit broken” in the first place.

Within the first few replies, several participants were comparing it to WHMCS. Their recollection, and it is their recollection rather than anything we have checked, was of renewal costs doubling and owned licenses disappearing afterward. One described the sequence as removing the support product that made owned licenses upgradeable, leaving the license itself untouched “though eventually unusable”.

The company rejected the parallel. Its representative called it “quite an unfair comparison”, said that in the company’s twenty-year history it had “never changed the terms of an existing license”, and objected to being measured against “a VC backed competitor”. The representative added that nothing beyond the enforcement change was “being planned or implied”.

The Renewal Multiplier Index: What Hosting Costs After the Intro Price

What Owners Should Check Before 7.2.1

Licenses sold with lifetime updates are unaffected, according to the company, and its representative accepted that the email should have said so: “In hindsight, we should have specifically mentioned lifetime-update licenses and made it clearer that those licenses are unaffected. I apologize for the confusion that caused.”

The practical steps are short. Owners of a perpetual license should establish which kind they hold, because the company draws a hard line between licenses sold with a limited update period and those sold with lifetime updates, and says only the first group is affected. The email’s own instruction is not to attempt the 7.2.1 upgrade until update access is confirmed as active, and to take a full backup of files and database first.

An Owned License does not stop working when its update access lapses. According to the company, it “will continue to work on the versions it is entitled to use”, and renewing updates is required only to move to a version released outside that window. For a billing system that is a meaningful distinction: staying put remains permitted, moving forward is what now carries a charge.

As of 24 August, Clientexec had not announced 7.2.1 on its blog, where version 7.2 was published on 6 August. Nothing forces a decision before then, and the company’s documentation says the fee can be paid when an upgrade is actually wanted. What 7.2.1 changes for affected owners is that continued access to new versions carries the $50 charge, and the alternative is staying on a version the license is entitled to use.

About the Data

The December 2025 pricing announcement, the 7.2 release date and the public pricing page were read directly from Clientexec’s own site on 24 August. The email text, the company’s four replies and the operators’ reactions come from a WebHostingTalk thread dated 20 and 21 August, which returns an error to automated requests and was read from dated screenshots supplied to us. The $50 figure appears in the email and in Clientexec’s documentation, though not on its main pricing page, which lists leased plans only.