Forem: DNSK WORK

I Was Wrong About Being Wrong About Social Media

Tanya Donska — Mon, 29 Sep 2025 15:03:58 +0000

I told myself I was making a principled stand. Really, I was just scared of being visible.

I spent two years not posting on social media while telling everyone – and myself – that it was because I had integrity.

"I don't want to play those games," I'd say when someone suggested building a presence. "The growth hacks, the fake engagement, the constant posting – it's all manipulation."

I sounded so principled. So above it all.

What I actually meant was: "I'm terrified people will see my work and think it's mediocre."

The manipulation tactics were a convenient excuse. Growth hacking felt gross, so I used that grossness to justify staying invisible. If the only way to succeed on social media was through tactics that felt wrong, then I could avoid the whole thing without admitting I was just scared.

Except the tactics weren't the only way. I was using my legitimate discomfort with marketing manipulation to hide from a much less impressive fear: what if I put myself out there and nobody cared?

Then something shifted in how platforms work, and I accidentally discovered that my fear had been masking something useful all along.

The Excuse That Let Me Hide

Every time someone suggested I should post my work, I had a ready list of reasons why social media was fundamentally broken:

"They want you to post 3 times daily. I don't have time to create that much content."

"You need to follow/unfollow hundreds of accounts to game the algorithm. That's just spam."

"Everyone's buying engagement to look legitimate. The whole thing is fake."

"Real work doesn't get noticed – only viral tricks and clickbait."

All of this was true in 2022-2023. The advice floating around genuinely was terrible, and the tactics genuinely were manipulative.

But here's what I wasn't admitting: even if all that manipulation worked, I probably still wouldn't have done it. Because the manipulation wasn't actually why I was avoiding social media.

I was avoiding it because showing your work publicly is uncomfortable. Because explaining your thinking makes you vulnerable to disagreement. Because having opinions in public means people might think those opinions are wrong or basic or obvious.

The growth hacking stuff was real, and it really was gross. But I was using it as a shield against facing a much simpler truth: I didn't want to be visible because visibility is scary.

What Actually Got Me to Try

I didn't overcome my fear through some moment of courage or personal growth. I just got annoyed.

A client kept asking where they could see more of my work. I'd send portfolio PDFs, and they'd respond with "do you have a blog or something?"

After the third time explaining that no, I don't maintain a blog because the ROI on content marketing is questionable, I realized I sounded like I was making excuses for not having any public presence at all.

So I wrote something about SaaS pricing pages on HackerNoon. Not because I'd overcome my resistance to social media, but because it seemed less embarrassing than admitting I was scared of it.

The piece was just me breaking down why pricing pages consistently confuse users. The kind of analysis I'd normally put in a client presentation. Nothing fancy, nothing viral-optimized, just showing the design thinking.

It got 2,407 reads. Over 6 days of total reading time. People I'd never met mentioned it across the web.

And I spent the entire time it was happening feeling like I might throw up.

The Fear Behind the Fear

Here's what I learned watching that post get traction while simultaneously wanting to delete it and hide:

The fear of social media manipulation tactics wasn't protecting me from anything. It was just giving me a socially acceptable reason to avoid something uncomfortable.

Because even after platforms changed and growth hacks stopped working, I still felt that same resistance. The tactics weren't the problem – the vulnerability was.

Every time someone engaged with the post, I had this split reaction: "Oh good, people found it useful" mixed with "Oh god, now they have opinions about my thinking."

Someone would leave a thoughtful comment agreeing with my analysis, and I'd feel validated. Someone would disagree or point out something I'd missed, and I'd feel exposed. Both reactions were about the same thing: being visible means being evaluate-able.

The growth hacks and manipulation gave me something external to reject. Something that let me feel principled instead of scared.

But what I was actually rejecting was the discomfort of having a public professional identity.

What Changed (And It Wasn't Just the Algorithms)

While I was busy avoiding social media, platforms did actually shift in ways that validated some of my original instincts.

Trust in social media dropped to 42% globally. Instagram removed hashtag following entirely. YouTube started demonetizing mass-produced generic content. All those manipulation tactics that felt wrong? Platforms killed them because they were destroying user trust and ad revenue.

The algorithms changed to reward exactly the things I was naturally good at: clear visual hierarchy, authentic voice, user-focused thinking. Design skills instead of marketing tactics.

So in a way, I was right that the old approach was broken. But I was wrong about why I was avoiding it.

I thought I was making a principled stand against manipulation. Really, I was just scared of being judged. The manipulation gave me something concrete to point at, something that made my avoidance seem thoughtful instead of fearful.

What Actually Works Now (And I Hate That It's This Simple)

The content that performs best now is exactly what I could have been doing all along if I hadn't been so busy making excuses:

Just share your work and explain your thinking.

That's it. That's the whole strategy.

User-generated content – the kind that looks like a human made it – gets 4x higher click-through rates than polished marketing. Authenticity beats polish. Quality beats quantity.

The post that got traction wasn't fancy. I didn't optimize it for virality. I didn't use any growth hacks. I just explained a design pattern that doesn't work and why teams keep using it anyway.

Turns out when you remove the manipulation tactics I was using as an excuse, what's left is: do you have something useful to say, and can you say it clearly?

Those are design problems, not marketing problems. Visual hierarchy, clear communication, understanding user needs – this is what I already do professionally.

The only thing stopping me was the discomfort of doing it publicly.

The Part Where I'm Still Uncomfortable

I'm writing this post and still feeling that same resistance. Part of me wants to not publish it because admitting I was hiding behind excuses is embarrassing.

I told myself for two years that I was too principled for social media. That I had integrity. That I was better than the growth hackers and engagement farmers.

Really, I was just scared that people would see my work and think "that's obvious" or "that's wrong" or "why should I care what this person thinks?"

The discomfort hasn't gone away. I still hesitate before posting. I still check engagement with that mixture of hope and dread. I still have moments where I think "maybe I should just delete everything and go back to being invisible."

But I've gotten better at recognizing that discomfort for what it is: not a sign that something's wrong with social media, but a sign that visibility requires courage I didn't want to admit I lacked.

What I Wish I'd Understood Sooner

The growth hacks and manipulation tactics were real problems. Platforms rewarding fake engagement and viral tricks genuinely did make social media feel like a scam.

But using that as a reason to avoid the entire space was like refusing to learn design because some designers use dark patterns.

The tools aren't the problem. How they're used is the problem. And now that platforms have shifted to reward authenticity over manipulation, the excuse is gone.

What's left is just the scary part: putting your work and thinking out there for evaluation.

Turns out design skills translate perfectly to content when you stop trying to "do content" and just share what you know. Visual hierarchy matters more than growth hacks. Clear communication beats clickbait. Understanding what users need beats pushing what brands want to say.

I already had these skills. I just didn't want to use them publicly because public means vulnerable.

The Actually Useful Takeaway

If you've been avoiding social media because the tactics feel wrong, you might be right about the tactics but wrong about why you're really avoiding it.

Ask yourself: if all the growth hacks disappeared tomorrow and platforms rewarded exactly the kind of quality work you already do – would you suddenly feel comfortable posting?

If the answer is no, then the tactics aren't your real blocker. The discomfort of visibility is.

And that's fine. Visibility is uncomfortable. Having opinions in public is scary. Being evaluate-able by strangers is vulnerable.

But if you wait until those feelings go away, you'll wait forever. The discomfort is part of it.

The good news is that platforms now reward exactly what designers are naturally good at: clear visual hierarchy, authentic communication, user-focused thinking. You don't need to learn marketing or growth hacking or any of the manipulation tactics that felt wrong.

You just need to share your work and explain your thinking. That's the same thing you do professionally – just in public instead of in client presentations.

The hard part isn't the content. It's accepting that being visible means being vulnerable, and that's okay.

A Note on the Research

The data and trends in this piece come from research I did with Alex Halchenko on how social media algorithms have shifted to reward design thinking over traditional marketing tactics. We spent months tracking platform changes, analyzing engagement patterns, and talking to designers about what was actually working versus what marketing gurus were still selling.

If you want the full breakdown with all the platform-specific numbers and uncomfortable projections about where this is heading, Alex published the complete research here: Social Media Marketing Essentials: Why Designers Are Winning in 2026.

You can find more of my work and thinking about design at DNSK.WORK.

How I Watched the UX Skills Hustle Eat My Friends Alive (And Almost Got Me Too)

Tanya Donska — Mon, 22 Sep 2025 12:30:07 +0000

A love letter to every designer drowning in courses while their dreams collect dust

Last Tuesday, my friend Sarah called me crying.

Not the dramatic, something-terrible-happened kind of crying. The quiet, exhausted kind that comes from spending nine months preparing for a career that keeps moving further away the harder you chase it.

"I just finished another $300 course," she said. "The instructor mentioned three new tools I've never heard of. I feel like I'm running backward."

Sarah has 47 certificates. A Notion database with 200+ bookmarked "must-learn" resources. She can tell you the difference between atomic design and material design in her sleep. She's memorized every UX law from Fitts to Miller.

She's also never designed anything that a real human being has actually used.

And honestly? That used to be me.

My Own Descent into Course Hell

Ten years ago, I was Sarah. Different name, same spreadsheet of skills I "needed" before I could call myself a real designer.

My morning routine was pathological: Wake up, check what new course dropped on which platform, panic about not knowing [insert trendy methodology], add it to cart, feel temporarily better about my future.

I had this fantasy that one day I'd cross some invisible finish line. I'd know enough. The anxiety would stop. Companies would somehow sense my completion percentage and throw offers at me.

Spoiler alert: There is no finish line. There's just more track.

The course creators know this. Hell, they're banking on it.

The Day I Realized It Was All Bullshit

I was on course number 23 (yes, I kept count) when the instructor said something that made me want to throw my laptop across the room:

"Now that you understand the theory, you'll want to take my advanced course where we put it into practice."

Practice. In another course. For another $199.

That's when it hit me: I was paying someone to teach me how to prepare to potentially maybe one day do the thing I claimed I wanted to do.

It was like taking swimming lessons in a parking lot. Sure, you're learning the motions, but you're never getting wet.

Let's Talk About What Nobody Wants to Admit

The online education complex has weaponized our imposter syndrome. They've turned "continuous learning" from a healthy professional habit into a full-blown anxiety disorder.

Every morning, my LinkedIn feed assaults me with the same message dressed in different clothes:

"The skill that's replacing UX research in 2024!"
"Why designers who don't know [X] will be unemployed by December"
"I made $500k after learning this ONE weird Figma trick"

It's exhausting. It's manipulative. And it's working.

We've created an entire generation of designers who are professional students. They're so busy learning how to design that they never actually... design anything.

The Real Talk Nobody's Having

Here's what actually happens when you get a design job:

Nobody cares about your certificates. I mean it. Nobody.

Your manager won't ask if you completed the Advanced Prototyping Masterclass. They'll ask if you can fix the checkout flow that's hemorrhaging customers.

Your team won't quiz you on design thinking frameworks. They'll need you to explain why the engineering team should spend three sprints rebuilding something that "already works."

Users definitely won't care about your course completions. They just want the damn app to let them reset their password without wanting to punch their screen.

What Working Designers Actually Do All Day

After I finally stopped taking courses and started taking jobs (messy, unglamorous, real jobs), I discovered what designers actually need to know:

How to argue without being an asshole. Because you'll spend more time defending your design decisions than making them. And if you can't explain why the button should be blue without sounding like a pretentious design blog, you've already lost.

How to ship something you hate. Your beautiful, user-tested, pixel-perfect design will get butchered by legal requirements, technical constraints, and that one executive who insists everything needs more "pop." Learning to find small wins in compromised solutions is a survival skill.

How to translate feelings into features. Not in some woo-woo way. I mean literally sitting with users who are frustrated to the point of tears and figuring out which specific interaction is making them want to throw their phone. Then fixing it with the three days and zero budget you've been given.

How to care less (strategically). You can't die on every hill. Learning which battles matter and which ones are just your ego talking will save your sanity and your career.

None of this comes from courses. It comes from doing the work, badly, repeatedly, until you get less bad at it.

The Portfolio Piece That Changed Everything

Want to know the project that finally got me hired? It wasn't some pristine case study with perfect process documentation.

It was a janky Chrome extension I built to fix my uncles's most-hated website.

My uncle, who types with two fingers and thinks "the cloud" is suspicious, couldn't figure out how to pay his water bill online. The city's website was a masterpiece of bureaucratic user hostility.

So I spent a weekend hacking together something that just... fixed it. Auto-filled the confusing forms. Highlighted the actually important information. Added a big, impossible-to-miss "PAY BILL" button.

It was ugly. It broke half the time. It only worked for one specific website in one specific city.

It also solved a real problem for a real person who was really pissed off.

That messy little project taught me more about design than two years of courses combined. It also gave me the best interview story I've ever had. Turns out, hiring managers love hearing about times you solved actual problems for actual humans.

The Uncomfortable Truth About Design Skills

Most of us already know enough to start. We just don't want to admit it because starting is terrifying.

Courses feel safe. There's a syllabus, a progress bar, a certificate at the end. You can't really fail at watching videos and completing exercises.

Real projects? Those can fail spectacularly. You might design something nobody uses. You might not know how to handle client feedback. You might realize you're not as good as you thought you were.

But here's the thing: You learn more from one failed real project than from ten successful course completions.

What Sarah Did Next

Remember Sarah from the beginning? I convinced her to try an experiment: One month, no courses. Instead, she had to ship one thing per week. Anything. Didn't matter how small or silly.

Week 1: She redesigned her apartment building's catastrophically bad laundry room sign-up sheet. Printed it. Hung it up. People actually used it.

Week 2: Made a simple website for her cousin's dog-walking business. It had five pages and one contact form. Her cousin cried with happiness.

Week 3: Created a Chrome extension that blocked course platform websites between 9 AM and 5 PM. (I'm not joking. She actually did this.)

Week 4: Redesigned the donation flow for a local animal shelter's website. Sent it to them unsolicited. They implemented two of her suggestions.

Four weeks. Four real things in the world. Zero certificates earned.

She got her first design interview the next month. They spent the entire time talking about the laundry room sign.

So What Now?

If you're sitting on twenty tabs of course landing pages right now, here's my advice:

Close them. All of them.

Pick the ugliest, most broken thing you interact with regularly. Could be an app, a website, a paper form at your dentist's office. Doesn't matter.

Fix it. Or try to. You'll probably make it worse at first. That's fine.

The point isn't to create something perfect. It's to create something. To move from learning about design to doing design. To stop preparing for a career and start having one, even if it's messy and small and starts with redesigning your building's laundry sign-up sheet.

The Plot Twist

Here's what the course sellers won't tell you: Every working designer still feels like they don't know enough. We all google basic stuff daily. We all have imposter syndrome. We all look at job postings and think "I only know 60% of this."

The difference between working designers and eternal students isn't knowledge. It's the willingness to jump in at 60% and figure out the rest as we go.

Your incomplete knowledge is enough to help someone with something. Today. Right now. Without taking another course.

Final Thought (Or Whatever)

The design education industry thrives on making you feel perpetually unprepared. They profit from your insecurity. They've turned professional development into a subscription service where the bill never stops coming and the product never quite delivers what you need.

But you don't need their permission to start designing. You don't need their certificates to solve problems. You don't need to know everything to know enough.

You just need to stop learning and start doing.

Even if it's messy. Even if it's small. Even if it's just making a better sign for your apartment's laundry room.

That's where real design careers begin. Not in course catalogs or certificate frames, but in the messy, imperfect act of trying to make something slightly less frustrating for another human being.

Sarah gets that now. She's stopped collecting certificates and started collecting problems to solve.

Her course completion rate has plummeted. Her design skills have never been stronger.

Funny how that works.

P.S. - If you're reading this while procrastinating on another course purchase, consider this your sign to close that tab and go fix something broken instead. The worst that happens is you'll have tried. That already puts you ahead of everyone still watching introduction videos.

Stop Teaching Users To Ignore You: Rethinking “Maybe later”

Tanya Donska — Tue, 16 Sep 2025 14:19:40 +0000

Last Tuesday I watched a new user bounce around a freshly minted dashboard. Up pops the friendly onboarding modal: "Welcome! Let us show you around." Two buttons: "Get started" and "Maybe later".

They hit "Maybe later" without reading the headline. Three minutes of guesswork. Five minutes later, the tab is closed.

This person wanted to succeed - they had just paid. But our first decision taught them to choose ignorance over guidance.

Designers, this one is on us.

Politeness theatre vs product outcomes

"Maybe later" looks considerate. We tell ourselves we are giving control and avoiding coercion.

I have shipped that modal too. It feels humane in a Figma frame. In the wild, it mostly operates as an opt-out from learning.

On one product we tracked, users who tapped "Maybe later" during onboarding had 73% higher churn. Not because they were less motivated - they had literally just signed up - but because we gave them permission to remain confused at the exact moment confusion is most expensive.

What reads as politeness in UI often converts into avoidable support tickets, abandoned features and lower LTV.

What the button communicates (whether you intend it or not)

When you place "Maybe later" next to essential guidance, you encode three messages into the interface:

This isn't urgent. If it really mattered, it would not be so easy to skip. Priority is telegraphed by friction.
Decide before you understand. You are asking users to make a meta-decision while they are cognitively cold. Faced with uncertainty, people default to the lowest-effort option: dismiss.
Success can wait. Every skipped explainer becomes a trap they will fall into later, when there is no supportive context on screen.

That is decision architecture, not just microcopy.

The moment the penny dropped

During a collaboration test, a tooltip explained shared cursors with "Got it" and "Maybe later". The participant dismissed instantly - not from disinterest, but because she was mid-task.

Ten minutes on, she tried to collaborate, could not see her teammate's cursor, and concluded the feature was broken. We had taught her to defer learning until failure, then left her to carry the cost.

We did not need more tutorial content. We needed a different delivery mechanism.

Design for learning-in-flow

The best products do not force a choice between learning and doing. They entwine them. Patterns that consistently outperform the modal-plus-skip pattern:

1) Contextual, just-in-time cues

Trigger lightweight guidance at the moment of intent, not on page load. A micro-hint that appears when a user opens the sharing panel lands better than a blanket tour on first visit. Keep copy atomic - one job per hint.

Design notes

Anchor hints to the control or surface being explained.
Prefer inline affordances and empty-state helpers over centre-screen overlays.
Set decay rules so hints do not reappear once demonstrated success is observed.

2) Outcome-framed microcopy

Users do not care about features - they care about not being stuck next week.

Instead of: "Use tags to organise tasks."

Try: "Tag now to find this in seconds next week."

Swap nouns for verbs, and verbs for outcomes. If the user cannot answer "what do I get for doing this now?", your copy is probably UI-centric rather than user-centric.

3) Progressive disclosure by default

Expose the minimum surface to get started, then reveal depth on demand. Allow users to master a narrow path, then progressively layer in capability. Progressive disclosure is not dumbing down - it is sequencing complexity in a way brains can absorb.

4) Guardrails over gates

If skipping truly risks error, add a light guardrail rather than a hard block.

Pattern: soft confirmation

"This step prevents common mistakes with invoices. Skip anyway?"

You are not coercing - you are calibrating the cost of the decision.

5) Durable return paths

If users are not ready now, they must know where help lives later. Bake a visible Learn surface into the product chrome: a help icon with contextual articles, a searchable command palette that surfaces how-to actions, or a checklist that sits in the sidebar rather than in a modal.

6) Demonstrations beat descriptions

When possible, show the behaviour. Micro-animations, ghost states and interactive "try it" sandboxes often out-teach paragraphs. If a control supports drag, hint with a tiny nudge. If collaboration has presence, pulse the avatar once.

Patterns and when to use them

First-run checklists
Replace the tour with a 3–5 item checklist aligned to activation moments. Each item deep-links to the task and auto-ticks on success. The list lives in the UI until completion, then retires quietly to Help.
Inline empty states
When a surface is empty, the most valuable content is an action that fills it. "Create your first rule" with a one-line benefit and a primary button beats a paragraph about rules.
Embedded coach marks
Small, anchored notes that appear after an intentional hover or focus, not on page load. Always provide an obvious way to bring them back.
Command palette education
Treat the palette as a learning surface. Surface verbs like "invite teammate" or "set up billing" with one-line benefits and result previews.
Checklists with consequences
If a skipped step will degrade the experience, reflect that status in-line: "Billing not set - usage capped at 5 exports" with a direct fix action.

What to instrument

If you are removing "Maybe later", measure the right things so design debates move from taste to telemetry:

Activation events: proportion of new users who reach the first meaningful outcome.
Time-to-value: median time to complete the core task once.
Guided action completion rate: how often a just-in-time hint leads to a successful action within the same session.
Help return paths: % of users who reopen guidance from the chrome and succeed on the next attempt.
Feature false-negative rate: sessions where users try a capability, fail, and do not return within 7 days.
Rage-click or backtrack signals: reductions here indicate guidance is doing real work.

A simple decision rubric for designers

Keep a skip only if all three are true:

The step is genuinely optional for immediate success.
The cost of skipping is legible to the user at the moment of choice.
There is a durable, obvious path to return later that does not require hunting through docs.

If any of these fail, do not offer a "Maybe later". Use contextual guidance, a checklist or a soft confirmation instead.

The real choice

Do you want users to succeed now, or do you want them to feel they controlled their confusion? Those are not the same. Optimising for the feeling of control at the expense of actual success hurts everyone.

Users do not want more choices. They want better outcomes. They want to feel capable using your product without friction.

"Maybe later" optimises for politeness over effectiveness. There is nothing polite about letting people fail when you could have helped them succeed.

The products that feel effortless do not offer escape hatches from learning. They make learning feel effortless too.

This is the kind of problem we obsess over at DNSK WORK. Small interface decisions shape how people learn your product, and the difference between good and great often hides in those seams.

https://dnsk.work/

Why SaaS Pricing Pages Fail

Tanya Donska — Thu, 04 Sep 2025 13:39:13 +0000

I’ve made pricing pages I was quietly proud of. Clean grids. Calm colours. A monthly/annual toggle that felt clever until it pushed the CTA just enough to break the fold on Safari. In screenshots, they looked convincing.

In practice, they behaved like polite doormen who never actually opened the door.

The first time a pricing page embarrassed me

We launched a tidy redesign on a Tuesday. By Friday, conversions were flat, support kept fielding “what’s included again?”, and sales were spending the first ten minutes of every call just explaining tiers. No one said the page was ugly. They said it was unclear. Which is worse. An ugly page that’s clear will still sell. A pretty page that whispers will not.

I opened the file and realised I’d built a catalogue, not a decision. Thirty rows of micro‑differences. Tooltips everywhere. Three primary CTAs because I couldn’t choose which conversation to have. It wasn’t a pricing page; it was my indecision with rounded corners.

What a pricing page quietly says (about you and me)

We pretend it’s about money. It’s about confidence.

Tooltips on every other line say: we don’t trust our words.
Every plan including everything says: we’re afraid to choose.
Starter/Pro/Enterprise cloned from the neighbour says: we hope imitation reduces risk.

Buyers read all of that, even if they don’t say it aloud.

Three mistakes I won’t repeat

1) Feature bingo
I once shipped a table with so many rows you needed a packed lunch to reach the footer. Buyers didn’t compare; they postponed. If you need binoculars to tell plans apart, you’re not selling—you’re daring people to open a spreadsheet.

2) CTA soup
Book demo. Try free. Talk to sales. Compare plans. All above the fold. That isn’t helpful; it’s a hostage situation. A pricing page needs one clear next step. Two at a push. Everything else belongs lower down or in a footer.

3) The week‑one ambush
Listing a feature on the table and then locking it behind “upgrade to unlock” two days later. Yes, short‑term ARPU ticked up. Trust fell through the floor. People remember the wall more than the upgrade.

What I aim for now

Tiers by outcome, not headcount
For launching. For growing. For scaling teams. Speak to the job that changes when they buy—not their job titles.

One safe recommendation
Highlight a default with “Best for most teams”. It’s not hand‑holding; it’s a shortcut past decision fatigue.

Three value stories, not thirty rows
Group features by Collaboration / Automation / Insight. If a line doesn’t fit a story, it’s either not core or it needs clearer language.

Transparent logic
If you’re usage‑based, show the maths with two simple examples. If you’re tiered, state what actually changes and why. No riddles. No asterisks pretending to be clarity.

No surprise maths
Let people estimate the bill without handing over an email. Radical, yes. Also respectful.

A tiny chooser
“Not sure? Answer three questions.” It’s not cute; it’s humane.

One primary action
Start free or Talk to sales. Pick. The other can be secondary. Two primaries is cowardice dressed as choice.

A short story with numbers (and sleep)

We helped a team whose page looked handsome and converted like soup. We didn’t reskin. We reframed: rebuilt tiers around real journeys in the data; rewrote features in human; added a tiny chooser; moved limits into a plain “What’s included, exactly” panel with actual numbers; removed the “included*” bait entirely. Six weeks later: conversions up 22%, support tickets down, the founder texting that they were finally sleeping. I’ll take boring improvements over shiny experiments most days.

If I had your page for a week

Day 1 — Rename the tiers
Outcomes and who it’s for in one line each. No poetry.

Day 2 — Cull the noise
Three clusters max. Anything with asterisks goes into a readable Limits panel.

Day 3 — Pick a default
Mark it as “Best for most teams”. Stand by it.

Day 4 — Reduce CTAs
One primary, one secondary. Everything else moves south.

Day 5 — Show the bill
Two worked examples. No calculator required.

Day 6 — Add the chooser
Three questions; one suggestion. It should feel like help, not a quiz.

Day 7 — Instrument and listen
Track plan clicks, time on page, chooser completion, and the “I thought this included…” tickets. Fix what those reveal first.

Copy I actually ship

Plan label — For growing teams
Why — Ship faster, keep control.
Cluster — Automation
Line — Remove handoffs, not oversight.
Limits — What’s included, exactly
Items — Requests/month, seats included, data retention. (Numbers, not vibes.)
Helper — Not sure? Answer 3 questions → we’ll suggest a plan.

One smile per page, maximum. Pricing is a commitment, not stand‑up.

Quick tests I like

30‑second test — Can someone explain their total cost aloud in thirty seconds? If not, fix the page, not the prospect.
Blindfold test — Hide logos. If your page is indistinguishable from competitors’, you don’t have pricing, you have camouflage.
Regret test — Pull last month’s “I thought this included…” tickets. If you hear the same line twice, the table owes an answer.

Founder note (with love)

If your pricing page hasn’t moved in a year, it’s leaking—money, confidence, and time you’re spending on calls a clear table should close. The fix isn’t a rebrand. It’s an hour a day for a week.

Choose outcomes. Pick a default. Tell the truth about limits. Cut the extra buttons. Show the bill. Then stop fiddling and watch the numbers. If it sells, keep it. If it confuses, don’t defend it—rewrite it.

The pricing page is where trust does the paperwork. Make it earn its keep.