Becoming an Elite Author Was the Easy Part

The Elite badge arrived on a Tuesday. The next morning I had the same inbox and the same to-do list. I made coffee, opened my support queue and answered a buyer in Ohio who couldn’t get her contact form to send. There was no ceremony and no sudden change in how my days felt. Badges are a snapshot. Reputation is a habit. It took me a while to understand that reaching a milestone and staying worthy of it are two completely different jobs, and that the second one is much harder. Becoming an Elite author was the easy part. Staying one means shipping every month.

What the badge really measures

A milestone badge tells the world that your themes have sold well over time. It is a nice moment, and I won’t pretend I didn’t smile when I saw it. But a badge measures the past. It doesn’t tell a buyer whether your theme works with the latest version of WordPress, whether your support is still fast or whether you will still be around next year.

Buyers are smart. They look at the last update date before they look at your badges. They read the most recent comments, not the oldest ones. They check whether you answered the question someone asked last week. In other words, they are measuring your habits, not your history. That is the reputation that keeps a theme selling, and it has to be earned again every month.

A monthly rhythm

One update per theme per month, even if it is small. Buyers notice a theme that is alive. This is the single most important habit I have built, and it has outlasted every other productivity system I have tried.

Not every update is exciting. Some months it is a bug fix and a compatibility check. Some months it is a new header preset or a better mobile menu. Occasionally it is a major release that took weeks of work. The size doesn’t matter as much as the rhythm. A changelog with steady entries tells buyers that someone is paying attention, testing against new software and fixing problems before they spread.

How I plan each month

1. In the first week, I review support tickets and comments from the previous month.
2. I pick one improvement per theme that would help the most buyers.
3. In the second and third weeks, I build and test those changes.
4. In the fourth week, I update the documentation, write the changelog and submit the updates.
5. On the last day, I write a short note to myself about what to tackle next month.

Keeping the scope small is what makes the rhythm sustainable. If a feature is too big for one month, I break it into pieces. The first piece ships this month, the next piece ships next month. Buyers see progress, and I never disappear for half a year working on something huge.

The rhythm also protects me from a quiet trap that catches many authors after a milestone. When sales are strong, it is tempting to coast for a while and enjoy the results. A few months pass, a new version of WordPress arrives, a popular plugin changes how it works, and suddenly the theme has small problems that nobody fixed. Buyers start leaving comments asking whether the theme is still supported. Reviews soften. By the time the author returns, it takes months of work to rebuild trust that a steady monthly update would have kept intact. I have watched talented authors fall into this, and I have felt the pull myself. The calendar keeps me honest, even in the months when I would rather take a break.

When I do take a vacation, I prepare the update ahead of time and schedule it, so the rhythm continues while I am away.

Ship something every month and the badges take care of themselves.

Cole Bennett, theme author

Say no more often

Not every feature request belongs in the theme. Some belong in a child theme tutorial. This was the hardest lesson for me, because I genuinely want to help every buyer who asks for something.

In my early years, I said yes to almost everything. A buyer wanted a special layout for one page, so I added an option. Another wanted a unique footer style, so I added another. Over time, the settings panel became a maze. New buyers felt overwhelmed, the code became harder to maintain and every update risked breaking some rarely used option. Saying yes to everyone made the theme worse for everyone.

Now I ask a simple question before adding anything: would at least one in ten buyers use this? If the answer is yes, it goes on the roadmap. If not, I write a short tutorial showing how to do it with a child theme or a small snippet, and I send that to the buyer instead. They still get their solution, and the theme stays clean for the next person.

Requests that usually become tutorials

• Custom layouts for a single, unusual page
• Integrations with niche services only a few buyers use
• Very specific styling that differs from the theme’s design language
• Features better handled by a dedicated plugin

Protecting the work that matters

After the badge, I noticed new kinds of requests arriving. Invitations to speak at events, offers to build custom sites, partnership pitches and plenty of well-meaning advice. Some of those were wonderful. But each one took time away from the monthly rhythm, and the rhythm is what earned the badge in the first place.

So I set a few boundaries. I take on one outside project per quarter at most. I keep my support hours fixed, no matter how busy the month gets. And I block two full afternoons a week for building, with notifications off. None of this is complicated, but it is easy to let slip when exciting opportunities show up. The badge made me more visible. Staying focused kept me worthy of it.

What I track instead of badges

I don’t check sales charts every day anymore. Instead, I keep a simple monthly scorecard with a few numbers that reflect the health of my themes and my reputation:

• Average first reply time in support
• Number of tickets that turned into documentation
• Days since each theme’s last update
• Number of bugs reported versus bugs fixed
• The tone of recent reviews and comments

When those numbers look good, sales tend to follow. When one slips, I know where to focus next month. It is a much calmer way to run a business than refreshing a dashboard and hoping.

Key takeaway: Milestones are proof of past work. Steady monthly updates, honest boundaries and the discipline to say no are what keep a reputation strong.

To anyone chasing the badge

If you are working toward your own milestone, I hope you reach it and celebrate properly. Take your family to dinner and enjoy the moment. Then, the next morning, open your inbox and answer the first ticket as carefully as you did when you had eleven sales. Plan one small update for each theme this month. Write one tutorial instead of adding one option. The badge is a lovely snapshot, but your buyers are watching the habit, and the habit is what lasts.