Aurumane is a small WordPress plugin studio. One developer, in Manila, building tools that solve specific problems on real production sites.
The studio exists because most WordPress plugins are built for the wrong audience. They’re optimized for the marketplace, not the maintainer. They aim to look complete on a feature list rather than to feel right at 11pm when something breaks. Aurumane goes the other direction. Every plugin starts with a real problem on a real site, and ships when it works the way a working developer would actually want to use it.
Who’s behind this
I’m Terrell Anderson, a self-taught Lead Web Developer with about six years of production WordPress experience. Most of that time has been spent building custom plugins, WooCommerce integrations, and HubSpot REST API work for biotech, healthcare, and scientific conference clients at a small marketing agency. I’ve shipped, debugged, and quietly rescued more sites than I can count, and I’ve spent enough hours inside other people’s plugin code to have strong opinions about how plugins should be built.
I work from Manila on UTC+8, eight hours ahead of most of my clients and most of the developers reading this. That offset means I tend to write code in the morning and answer email at night. It’s the rhythm I prefer.
Outside the studio I’m a parent, a fencer, a tabletop RPG nerd with too many character sheets, and a former seaweed harvester from coastal Maine. The work I do here pulls from all of it more than I expected when I started.
Why a small studio
Bigger plugin shops have to grow. They add tiers, agencies acquire them, founders move on, and three years later the plugin you bought is owned by a holding company you’ve never heard of. The plugin still works. Sort of. The roadmap is gone. The person who knew why it worked is gone.
A small studio doesn’t have that problem. It also doesn’t have venture capital, a full marketing team, or the bandwidth to ship a hundred features a year. What it has is one person who knows every line of code in every plugin, answers every support email, and can change direction overnight if the work calls for it.
That trade is the whole pitch. Fewer plugins. Slower releases. Better answers. A real person at the other end of every email.
How the work happens
Every Aurumane plugin starts as a real problem I hit on a real client site. If a client asks me to do something three times, that’s a candidate for a plugin. If a colleague describes the same pain on Twitter, that’s a candidate. If I find myself building the same thing twice with slight variations, that’s the strongest candidate.
From there the path is the same every time. I build a working internal version first, use it on real sites for at least a few weeks, then write the actual production version with cleaner code, real settings, and proper documentation. The free version goes on WordPress.org. The Pro version, if there is one, gets sold directly through Aurumane.
I don’t ship to a roadmap. I ship when the plugin is actually ready. Sometimes that means waiting an extra month to fix something that no one else would notice. That’s the work.
What’s next
Three small plugins shipped this year. Each one solves a single problem cleanly: login security, affiliate links, plugin portfolio tracking. The next stretch of work is on IntakeForge, a WordPress-native form and intake platform that’s currently in private testing with a handful of agencies. After that, a drag-and-drop email builder called QuillPost. Both will take time. Neither will ship until they’re right.
If you want to be told the day something new ships, send me a note and I’ll add you to the list. If you want to see what’s already out, the plugins are one click away.
Signed, Terrell. Manila, 2026.