01
A plugin that should exist
You've searched the repository twice and found six things that almost do it. Tell us what the missing one looks like.
What we build
The thing you keep working around.
Small, focused WordPress plugins that do one job properly. We're building the first of them now — and the rest of the list comes from people telling us what's actually in their way.
If you need something specific, describe it. We'll tell you honestly whether it's something we can build well — and if it isn't, we'll say so and point you somewhere better if we can.
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 describe 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 scope it back
We look for the smallest thing that would genuinely solve it, and tell you what we'd build — or that we're the wrong people for it.
03
We build it
Narrow in scope, clear in purpose, tested and documented. You see it working before anybody else does.
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.
Nothing is published there yet.The first submissions happen when the first plugins are ready — so this is a commitment written down before there's anything to point at, which is the only time writing it down means much. Telling a stranger about your workflow is a small act of trust; the least we can do is make sure what comes out of it belongs to everybody, rather than becoming something locked away behind us.
Being straight with you
Where we're less useful.
Not a closed door — just an honest read on where our help is worth having and where it isn't. If your problem sits near one of these, ask anyway and we'll tell you what we think.
Whole website builds
We're set up for tools rather than entire sites, and someone who does that full-time will serve you better. If it comes down to one stubborn piece of functionality, though, that part is ours.
Theme and design work
Making a site look a particular way is a different craft from making a tool behave properly. The second one is where we're strong, and we'd rather point you at someone good than do a passable job of the first.
"Just like that one, but mine"
A straight copy of an existing plugin rarely helps anybody. Tell us what that one gets wrong for you instead — that's usually the more interesting problem, and the one worth building.
Anything we couldn't keep up
If we can't picture ourselves still looking after it in two years, building it would be doing you a quiet disservice. We'd rather say that at the start than leave you with something abandoned.
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.