The Pricing Page That Almost Disappeared the Night Before Launch

Written on
The Pricing Page That Almost Disappeared the Night Before Launch

A SaaS startup’s designer spent three weeks redesigning the company’s pricing page. The night before launch, IT removed a former contractor’s account from the team’s design tool as part of routine cleanup.

That contractor had created the project file years earlier. When the account went, so did ownership of the file holding the new pricing page, the company’s full icon set, and most of its marketing illustrations. Recovery took two days of support tickets and a lot of nervous waiting. The launch slipped a week.

What Visitors Want From a Pricing Page

What Visitors Want From a Pricing Page

People arrive at a pricing page with one question: which plan am I, and what will it cost me? Everything on the page either helps answer that quickly or gets in the way.

Most pages fail by hiding the number. Plans labeled with clever names, a “contact sales” button on everything above the starter tier, and a feature table with 60 rows. A buyer comparing three tools in three browser tabs usually closes the one that makes them work hardest.

Show prices for every plan you can. Name plans by who they serve, such as a solo freelancer, a growing team, or an organization with compliance needs. Keep “contact sales” for the plan that genuinely requires a conversation.

Showing Usage-Based Pricing Without Scaring People

Pricing tied to consumption, such as API calls, messages sent, or records processed, makes sense for many products. It’s also harder to present, because buyers can’t see their bill in advance.

The startup’s first draft listed a per-unit rate and nothing else. In testing, visitors couldn’t estimate what they’d pay, and several assumed the worst.

The redesign added three things. A simple slider where visitors could pick their expected volume and see a monthly estimate. Two or three worked examples, like “a five-person support team sending 8,000 messages a month pays about $140.” And a plain note about spending limits and alerts, so nobody feared a surprise invoice.

Usage-based pricing also needs a unit customers understand. “Credits” mean nothing to a first-time visitor until you explain what a credit buys.

Small Details That Shift Decisions

Small Details That Shift Decisions

A monthly or annual toggle should default to whichever option you want most buyers to choose, with the savings shown in dollars, not just a percentage. Highlight one plan as the usual choice. Collapse the full feature table behind a “compare all features” link, keeping the top six or seven differences visible.

Then test. Five people unfamiliar with the product, each asked to pick a plan and estimate their cost out loud, will expose problems no internal review catches.

Where Design Assets Actually Live

The near loss exposed something most startups never examine. Design work sits in more places than anyone tracks: files in a cloud design tool, source illustrations on a designer’s laptop, exported icons in the code repository, brand fonts bought on someone’s personal card, and a logo whose original file nobody can find.

Each location carries its own risk. Files owned by individual accounts vanish when those accounts do. Version history may only go back a limited time on lower-tier plans. Font licenses tied to personal emails create legal trouble when the person leaves.

Audit Design Like Any Other System

Audit Design Like Any Other System

Engineering teams run recovery tests on databases. Design assets deserve the same treatment, and a disaster recovery audit checklist adapted for design catches most of the gaps.

Start with ownership. Every design file should belong to a company account or shared team space, not an individual. Offboarding steps for designers and contractors should include transferring files before removing access, in that order. Export source files and the full design system to company-controlled storage on a regular schedule, monthly at minimum. Keep font and stock image licenses in one shared folder, with purchase records.

The final item on any disaster recovery audit checklist is a real test. Could a new designer rebuild the pricing page from backups alone, in a single day? If the answer involves tracking down a former contractor, the backups aren’t finished.

Two Days of Waiting

The startup now backs up its design files every month and checks file ownership whenever someone leaves. The new pricing page launched a week late and raised trial signups by about a fifth. Its designer still keeps a copy of that file in three places.

Until next time, Be creative! - Pix'sTory

Easy-to-Use
Photo & Animation Maker

Register - It's free
Have an account? Login