Custom developmentfor the parts plugins can't do.
Plugins, web apps and connectors built for the part that's specific to your business, and written so the next developer can follow it.
What we build
Custom work, documented as it's written, so it still makes sense to whoever opens it next.
Custom plugins
New features for WordPress with a clean admin screen and code the next developer can read.
Web apps
Tools your staff or customers use in the browser: booking, scheduling, portals, dashboards.
Connectors and APIs
CRMs, payment gateways, email platforms and donation tools, connected to your site and tested.
Custom themes
Built from a lean starting point, with only the features your site actually uses.
Speed and database work
Query tuning, caching and cleanup for sites that have outgrown their original setup.
Code review and repair
An audit of a site you inherited, then steady improvements without starting over.
One site, talking to everything else
Connectors pass information between your website and the tools you already use, so nobody has to type it twice.
- Heart Warrior CPRA custom plugin for class scheduling and sign-ups.
- Our own fleet toolsThe system we use to watch over about fifty client sites from one place.
- Lay DominicansCustom plugins across a family of related sites.
Building on WordPress since 2007
We've built on WordPress since before Gutenberg and before Elementor. We know the current tools, and we remember why the old ones changed, which helps when something breaks after an update.
Our custom code follows WordPress's own coding standards, it's commented, and it avoids clever shortcuts that stop working after the next major release.
Development is priced by scope. Your proposal has one number in it, agreed before any work starts.
Start a projectWhere we spend most of our time
- Custom post types and fields
- Custom Elementor widgets
- Members-only content
- REST API endpoints
- Integrations with outside services
- Staging and safe deployment
- Version control
- Replacing abandoned plugins
- Core Web Vitals and speed work
- Moving sites between hosts
David handled all the scary backend stuff I didn't have the time or skill to deal with, two site migrations, cool as a cucumber, and his monthly health reports kept me connected to it all.
How development work runs
We write down what we'll build, and why, before any code is written.
- 01
Audit
We review your current site, its code and your goals before proposing anything.
- 02
Plan
We write down the approach and the price, and you approve both before we start.
- 03
Build
We develop on a staging copy with regular previews, so you see progress as it happens.
- 04
Handoff
Documented code and a walkthrough, so your team knows what was built and why.
Questions people ask
We already have a developer. Can you work with them?
Yes. We often work alongside in-house developers and other agencies, either on one specific piece or on the parts nobody else wants to own.
Can you take over a site you didn't build?
Yes. We start with a technical audit so we both know what we're taking on. If we find something serious, you'll hear about it before any work starts.
Can you connect our site to a tool we already use?
Usually, yes. If the tool has an API or an export, we can connect it. We'll tell you during the audit if it doesn't, and what the options are.
What does development cost?
Projects are priced by scope, so your proposal has a fixed number. Ongoing support runs through a Care Plan, or $125 an hour for one-off requests.
Will custom work survive WordPress updates?
We build on WordPress's documented APIs and test major releases on staging before they reach your live site.