01
Something that should exist
A gap nobody has filled, a problem worth solving, or an idea you think would help. It doesn't have to be about a plugin that already exists.
What we build
The thing you keep working around.
Everything we build starts as a problem someone kept working around. The first plugins are in development now.
Hit something that genuinely needs solving? Send it. If it holds up, we'll try to build it — no promises, but a straight answer either way.
02
A workflow eating your week
The export, the re-upload, the copy between two screens. Repetitive work a computer should have quietly done for you.
03
Something that half-works
A plugin you rely on that's slow, abandoned, or fights another one. Sometimes the fix is a patch, not a replacement.
How it works
From a message to a plugin.
Four steps, and you can stop at any of them. Describing a problem costs you one message and commits you to nothing.
01
You report it
In your own words, with the messy details left in. What you tried, how often it bites, why the obvious fix didn't work.
02
We validate it
Our team looks at whether it's a real problem or a one-off workaround, and whether a plugin is even the right answer.
03
We try to build it
If it holds up, we take it on. Not everything does, and we'd rather say so than start something we can't finish properly.
04
It goes public
Once it's solid we submit it to the WordPress plugin repository, so anyone with the same problem can find it and install it the usual way.
Where it ends up
What we build goes to wordpress.org.
Not a private tool locked to whoever asked for it. If a problem is worth solving once, it's worth solving for everyone who has it — and the repository is where WordPress users actually look.
01
In the repository
Submitted to wordpress.org like any other plugin, so you install it from your own dashboard rather than from us. Nothing to sign up for before it works.
02
Looked after
We intend to maintain what we publish. "Last updated three years ago" is one of the six frictions on our own homepage — repeating it would be a poor look.
03
Not dependent on us
Public code in a public repository. If we ever stopped, what you're relying on is still there and somebody else can pick it up.
Where we fit
What we're built for.
Where we're strongest, so you can tell at a glance whether this is one for us. If your problem sits at the edge of it, send it anyway.
As deep as the problem needs
We go deep rather than wide. A one-line fix or a full plugin, whichever actually solves it. If you need a whole site designed and built, an agency will serve you better — but when it hinges on one stubborn piece of functionality, that part is ours.
Behaviour, not appearance
Our craft is making a tool work the way you'd expect: the logic, the defaults, the edge cases nobody thought about. Making a site look a particular way is a different craft, and we'd rather point you at someone excellent at it.
The version that fixes what's wrong
The most useful thing you can tell us is what your current plugin gets wrong for you. That's a real problem with a real answer — and a far better brief than a straight copy of something that already exists.
Built to still be here in two years
We take on what we can keep maintaining, which makes for a shorter list than we'd like. It's also why nothing we publish should turn into the abandoned dependency you're stuck with.
So — what's in your way?
One message, as detailed or as rough as you like. You'll hear back from a person, and you'll get a straight answer about whether we can help.