Ankit Panchal

It all started with a simple freelance task in 2017.

A client needed a way to load a script on their WordPress site. No fancy features, no admin UI, just a small script injected into the header. I built a quick plugin that hooked into wp_head, zipped it, and sent it over.

That tiny job became my entry point into plugin development.

Up until that point, I had mostly worked on WordPress websites — custom themes, site builds, client requests. But building a plugin, however simple, felt different. It was focused, reusable, and had potential to scale far beyond one site.

The Shift From Projects to Products

After that freelance gig, I started exploring plugin ideas of my own. My first public release was a simple analytics tool, Advanced Page Visit Counter. I created it to track page views without relying on external scripts or Google Analytics. Lightweight, privacy-conscious, and easy to use.

I put it on the WordPress plugin repository without much expectation.

But slowly, installs grew. Support requests came in. Feature ideas started stacking up. I kept iterating.

Over the next few years, that plugin went on to cross 1 million downloads and serve thousands of websites. It was my first lesson in building something useful at scale and the effort that goes into maintaining it.

What Made It Work

Looking back, a few things helped that plugin take off:

• It solved a real problem in a simple way
• It didn’t try to do too much
• It was designed for WordPress users, not developers
• I responded to feedback early and often
• I kept improving it even when growth was slow

The plugin didn’t go viral. It just kept showing up, quietly and consistently.

Beyond One Plugin

Since then, I’ve released a few more plugins:

• Hide Admin Bar Based on User Roles — now active on over 30,000 sites
• Disable Block Editor FullScreen Mode — just 4 lines of code, but solves a real annoyance
• UltimaKit for WP — a modular toolkit to reduce plugin bloat
• NoteFlow — a Mac-style notes experience for WordPress
• Like Dislike for WP — simple, clean like/dislike buttons for posts

Each one started as a small idea, a personal itch or a recurring user request.

Some grew faster than others. Some are still growing. But all of them taught me something.

What I Learned

• You don’t need to build big to be useful
• Solve one problem well instead of solving many halfway
• Plugin success isn’t just about code, it’s about clarity, UX, and support
• WordPress is still full of unsolved problems
• Shipping something is better than planning everything

Still Just Getting Started

Today, I’m more excited than ever to build plugins. But I’m also focused on building in public, writing more, and sharing what I’ve learned, not just what I’ve shipped.

If you’re thinking about building your first plugin, start small. Solve one problem you personally face. Release it. Support it. Improve it.

You never know where it might take you.