Custom theme development
Your designs built as a maintainable custom theme — no page-builder debt for the next developer to unpick.
You keep the client relationship. We build the WordPress.
HOW MUCH Labs works as a subcontractor for design studios, marketing agencies and web bureaus who need custom WordPress development, plugins and API integrations without hiring in-house.
Everything ships under your name. Your client never has to know we exist.
Most agencies can design a site well before they can build the awkward half of it: a custom plugin, a CRM integration, a migration, a performance problem that shows up two weeks before launch.
Hiring a developer for that is a permanent cost for occasional work. Passing the whole project to another agency means losing the client.
Subcontracting keeps the project — and the margin — with you.
We work to your brief, in your process, at whatever depth you need: a two-day fix, a full custom theme, or the technical half of a long build while you handle everything the client sees.
Built with both available approaches — direct database synchronization and the Zabun REST API. If a real-estate client lands on your desk, the integration is not new territory.
See the WordPress–Zabun integration work →Whole builds or single problems. Both are normal.
Your designs built as a maintainable custom theme — no page-builder debt for the next developer to unpick.
Functionality that does not exist off the shelf, written as a plugin your client owns rather than a pile of snippets.
WordPress connected to the systems the business actually runs on — CRMs, ERPs, booking and property platforms.
Sites that pass on real hardware, not just in a lab. Useful when a client is unhappy and the launch already happened.
Moving a site off a fragile stack, or rebuilding it properly while keeping URLs, SEO and content intact.
Updates, monitoring and fixes behind your support offer, so your client sees your name on the SLA.
We do not compete for your clients' design, strategy, content or advertising work. Development is the whole offer.
Designs, requirements, or just the problem. We read it properly and come back with questions — usually the ones that would have surfaced halfway through the build.
A fixed scope, price and delivery date, written in language you can forward to your client with our name removed. Anything we consider risky or underspecified is named here, not discovered later.
Your client signs with you. You mark up however you like. Our agreement is with your agency only, and we invoice your agency only.
One named developer, progress visible on a staging site, updates in whichever channel you prefer — your Slack, email, or your project tool as a guest.
Full source, repository access and documentation transfer to you. If you want us on standby for launch week or ongoing maintenance, we are; if not, you are not tied to us.
We do not email, call or invoice your client. You are the only point of contact unless you explicitly bring us in.
Documentation, staging links, commit messages and handover material carry your naming — not ours.
We will sign your non-disclosure and non-solicitation terms before you share client information. We also offer ours if you would rather start from a template.
Full source and IP hand over on final payment. Nothing is licensed back to us and nothing phones home.
We publish nothing about the project — no case study, no screenshot, no client name — without written approval from you.
Some agencies prefer to introduce us openly as their development partner. That is available on request, but invisible is the default.
Most partners start with a fixed-scope project and move to reserved capacity once the work is steady.
You send the brief and designs. We return a written scope with a fixed price and delivery date before anything is built.
You quote your client whatever you want on top. Our number stays stable so your margin is predictable.
Best for a defined build: a custom theme, a plugin, a migration, one integration.
You book a set number of development days each month and use them across whichever client projects need them.
Useful when work arrives unpredictably but constantly, or when you need someone on call for launches and maintenance.
Unused urgency is the point: capacity is held for you rather than quoted from scratch each time.
Not unless you decide to tell them. We work under your brand, in your channels, with your naming. We do not contact your client, publish the project, or list them as our own reference without your written approval.
You do, on final payment. We hand over full source, documentation and repository access so you are never dependent on us to keep the site running or to hand it to another developer later.
Yes, as part of your team if you want a technical voice in the room — introduced however you prefer. Many partners keep us entirely off client calls instead; both work.
From yours. Figma, XD, a PDF or an existing site to match — we build to it and flag anything that will fight WordPress before we start rather than after.
Fixed-scope projects are quoted per project after we read the brief, so you know your cost before you quote your client. Reserved capacity is a monthly rate for a set number of development days. No hourly surprises either way.
Depends on current capacity. Small fixes can usually slot in within a week; a full build is scheduled. Tell us your launch date early and we will be honest about whether it is realistic.
You get one named developer, a written scope, and progress you can see on a staging site throughout. If something is going off-track, you hear it from us before your client hears it from you.
Send the project you are weighing up — or just the shape of the work you keep having to decline. We will tell you honestly whether we are the right fit.
We are happy to sign your NDA before you share client details.