Basic, Standard, Premium: How to Draw the Scope Lines Between Freelance Tiers

There is plenty written about why three tiers work — anchoring, the Goldilocks effect, the middle option winning both comparisons. That part is settled and you can read it anywhere.

What almost nobody writes about is the part that actually breaks in practice: where the scope lines go. Tiers fail not because the prices were wrong but because Standard and Premium weren't distinguishable enough for a client to see, or because the boundary between them was never written down, so every Standard client asked for Premium work and got it.

The Rule: Tiers Differ by Deliverable, Not by Effort

The most common way tiers collapse is defining them by how much work you'll do. "Premium includes more in-depth research" is invisible to a buyer — they can't verify it, can't compare it, and can't tell what they're paying extra for. Clients default to the cheapest tier whenever the difference isn't legible.

Every tier boundary should be something a client could count or check. There are four levers that do this reliably:

↔ Scroll sideways to see all columns

Notice that only the first lever adds work proportionally. Turnaround and post-delivery support let you charge more without linearly increasing your hours — which is exactly what keeps the top tier profitable.

What Each Tier Is Actually For

Basic — the smallest version that still works

A client who buys only Basic should get something usable, not a teaser that forces an upgrade. Deliberately crippled entry tiers generate refund requests and bad reviews, and they don't convert to upgrades as often as people expect. Basic's job is to remove the "is this person any good" hesitation at low risk.

Standard — the one you actually want sold

Standard should be Basic plus the two or three things clients ask for most. If you already know what the common add-on requests are, that list is your Standard tier. This is the tier to design first and the one your pricing should be built around, because it's where most of the volume lands.

Premium — done-for-you, with a defined ceiling

Widest scope, fastest turnaround, most support. But "most" must still be a number. More on this below, because it's where the money leaks.

The Trap: Premium That Pays Worse Than Basic

Two rules prevent it. First, cap revisions at every tier, Premium included. Unlimited revisions at the top is the fastest way to invert your ladder, because the clients who buy Premium tend to be the ones with the most opinions and the most stakeholders. If you want Premium to feel generous, widen the revision window or speed up each round rather than uncapping the count.

Second, price the top tier on turnaround and support, not just volume. Rush delivery is worth real money to a client and costs you scheduling rather than scope. Our guide to pricing a freelance project covers the estimation side, and the hourly rate calculator gives you the floor to check each tier against.

Build Your Three Tiers

Enter what you want your middle tier to be. This spaces the other two, and — more importantly — checks each one against your hourly floor.

Writing the Boundary So It Holds

A tier table on your website is marketing. What stops scope drift is the same table restated as a scope of work, attached to the agreement, with exclusions written out. Our guide to writing a scope of work covers why exclusions matter as much as deliverables — with tiers, that's doubly true, because the excluded items are literally the next tier up.

That last sentence does most of the work. It converts an upgrade request from a negotiation into an already-priced menu item. Generate the full document with the scope of work generator, and if you're sending tiers as options to a prospect, the proposal generator handles the presentation.

When a Standard Client Asks for Premium Work

This will happen on nearly every project, and how you handle the first request decides the rest of the engagement.

The instinct is to absorb it — it's small, you don't want friction, and the relationship feels worth more than the item. But absorbing the first request teaches the client that the tier lines are decorative, and it guarantees a second one. The alternative isn't confrontation. It's naming the item and offering the choice:

Four things make this work: it says yes rather than no, it points at a boundary that already existed before the project started, it gives a specific price instead of "that'll cost extra," and it offers a face-saving exit. Most clients pick one and move on without any awkwardness at all.

If requests keep arriving despite this, the underlying issue is usually scope definition rather than the client — see the contract clauses worth redlining for the change-order language that backs it up.

When Tiers Are the Wrong Model

Tiers suit repeatable work where the deliverable is roughly the same shape each time: logo packages, websites of a known size, monthly content, recurring maintenance. They save scoping time and let buyers choose without a call.

They're a poor fit when:

• Discovery changes the shape of the job. If you can't know the deliverable until you've dug in, a tier is a guess you're contractually bound to.
• You're pricing on outcome value rather than deliverable count — a tier table anchors the conversation to units and away from results.
• The work is genuinely bespoke. Publishing tiers you constantly deviate from is worse than not publishing them.

A common resolution is running both: tiers for the standard offering, and custom quoting above the top tier. Saying "projects beyond Premium are quoted individually" costs nothing and keeps the ladder honest. For retainer arrangements the same logic applies with an extra wrinkle — see how to get freelance retainer clients, and note that unpaid retainers behave differently from unpaid projects if it comes to that.

Frequently Asked Questions

The prices are the easy part. Write down what each tier does and doesn't include, cap the revisions everywhere, and check that your best package isn't your worst-paid one — and the ladder holds on its own.