Tag: Subscription Tiers

A service guarantee sounds simple until it becomes a product matrix.

Does the service include support?

Yes.

How fast?

That depends what you bought.

GitHub’s support structure makes the fragmentation unusually visible because the company publishes the response promises side by side.

Support became another upgrade path

In 2018, GitHub announced an expanded Premium Support program for Business Cloud and Enterprise customers. GitHub described the offering as a response to teams that needed around-the-clock care beyond its standard support. The new Premium and Premium Plus plans included 24/7 web and phone support, priority ticket handling, and guaranteed initial response times of 30 minutes for urgent requests and four hours for high-priority requests. Premium Plus added a named technical support account manager and other services. See GitHub’s 2018 Premium Support announcement.

The modern structure is even clearer.

GitHub Enterprise includes support, but GitHub’s current comparison lists the included Enterprise support level as 24/5 with an initial response of under eight hours for urgent and high-priority cases. Premium and Premium Plus provide 24/7 coverage and formal service-level agreements. Premium guarantees a 30-minute initial response for urgent tickets and four hours for high-priority tickets. Premium Plus adds a named Customer Reliability Engineer, incident management, technical advisory time, and faster normal-priority handling. See GitHub’s current Premium Support comparison.

Same platform.

Different promises about what happens when it breaks.

A response guarantee is not a resolution guarantee

GitHub is careful about an important distinction: its SLA covers the initial response, not the time required to solve the problem.

That is reasonable. A broken repository permission can be fixed quickly. A deep infrastructure bug may require engineering work regardless of how much the customer pays.

But the tier still changes the customer’s position during an incident.

One organization gets shared support during defined hours. Another receives 24/7 priority handling. Another has named personnel who already know the account and can coordinate an incident.

The service itself may have the same outage. The path through the outage is different because support has been packaged separately.

The guarantee becomes part of the upsell

There is nothing inherently dishonest about charging more for expensive human support. Dedicated engineers and 24-hour staffing cost money.

The Dead Internet Theory angle appears when a formerly straightforward expectation—I pay for the business service, therefore serious problems get serious support—splits into increasingly specific commercial tiers.

The customer is no longer buying only software capacity or features. The customer is buying a place in the support queue, an escalation path, and a promised response clock.

That changes how the cheapest paid tier should be evaluated.

The important question is not whether the plan technically includes support.

It is what support still means at that tier once faster response, stronger escalation, incident coordination, and dedicated expertise have all become separate things that can be sold above it.

A feature does not have to disappear to be removed from your plan.

It can simply move one column to the right on the pricing table.

Evernote has repeatedly adjusted the boundary between its free and paid tiers. In late 2023, the company announced that Free accounts would be limited to 50 notes and one notebook for new creation. Existing users above those limits could still view, edit, export, share, and delete their existing material, but creating more required getting back under the limit or subscribing.

In 2024, Evernote described “virtually unlimited note and notebook creation” as a paid benefit while also limiting Free accounts to one connected device at a time.

Evernote documents the changes in its 2023 Free account limits announcement and its 2024 device-limit update.

The feature being sold may be ordinary use

There is nothing exotic about creating a 51st note.

That is what makes tier changes interesting.

Subscription software often begins by separating advanced features from basic ones: collaboration controls, automation, administration, large uploads, analytics. Those boundaries are easy for users to understand.

But a company can later redraw the line around behavior that had previously been normal everyday use.

Once that happens, the paid tier is not only selling something new. It may also be restoring freedom the user remembers having before.

Existing data makes the decision asymmetric

Evernote handled the 2023 change more gently than simply locking old notes. Users above the new Free limits retained access to their existing content and could export it.

That matters.

Still, a person with hundreds or thousands of notes has a different decision from a new user evaluating the Free plan today.

The new user can walk away with almost nothing invested.

The established user may have years of clipped pages, scans, task lists, tags, notebooks, links, and personal organization built around the service.

The subscription price is therefore compared not only with competing software, but with the inconvenience of migration.

A paid tier can also fund genuine improvement

Evernote argued that subscriptions supported infrastructure work, real-time editing, AI features, stability improvements, security work, and faster synchronization.

That is a legitimate part of the comparison. Software has continuing development and hosting costs. A free tier does not create a permanent entitlement to every capability it once included.

The useful question is more precise: what additional value is being sold, and what old capability has been moved behind payment?

Those are not the same thing.

If a higher tier adds substantial new functionality, the upgrade is easy to describe as a new product.

If the main practical effect is that an established user must pay to keep doing what the old tier already allowed, the economics feel different.

Nothing vanished from the software.

The line moved around the user.