Google Ads measurement
Accept and this site loads Google’s advertising tag, so a paid-search click can be matched to an enquiry. Reject and it never loads. There is no Google Analytics, Meta or LinkedIn pixel here either way, and the enquiry form’s two cookies are set regardless. Every cookie is named in the cookie policy.
You currently accept it.
You currently reject it, and it has not loaded.
You sell the site; your client only ever talks to you. We write the theme, plugins, WooCommerce logic and integrations — inside your own tooling: accounts you created, a repository you own, staging on your domain. Nothing carries our name.
A white-label development partner builds under another agency's brand. For white-label WordPress and WooCommerce development that means our engineers work inside your repository, your ticket system and your staging domain, carrying no reference to us. Your client sees one supplier: you. We never contact them, during the project or after.
Most white-label promises stop at "we won't tell anyone". A subcontractor's name rarely escapes through a person — it escapes through a staging subdomain, a plugin header or a commit email. Here is every surface, including the one we can't close alone.
Your template, logo and pricing. We never publish suggested resale rates — that would put a floor under your pricing.
Your GitHub, GitLab or Bitbucket organisation from the first commit. Never "transferred later" — a transfer leaves a history.
READMEs, runbooks and licence register in your template, written to forward to your client unedited.
A subdomain on your domain or your client's — never a URL anyone could search and find us behind.
Your Jira, Linear, ClickUp or Basecamp, on accounts you create and revoke. No parallel board to glimpse in a screen share.
Alerts reach your Slack from your CI, under your app name. A bot called "canopus-ci" undoes the other seven rules in one message.
The Author and Plugin URI fields in every plugin and theme name your agency — WordPress prints them in the admin plugin list.
Commit emails on a repository we don't control. Issue us accounts on your domain and it closes; otherwise it stays a stated risk.
Every rule is configuration you can inspect on a call before signing. Comparing partners? Ask rule 07: whose name goes in the plugin header? It's the leak that survives longest — in your client's WordPress admin for the life of the site.
Most agencies arrive because a WordPress project outgrew plugins or a store outgrew its theme. The rest exists because those projects keep needing an API behind them.
Builds where the design can't be bought and the logic can't be plugged in. Business logic lives in a plugin, never the theme, so a redesign can't delete the integrations.
Stores that outgrew what plugins can express: tiered B2B pricing, quote-to-order approval, subscriptions, ERP-reconciled stock — built on High-Performance Order Storage.
The project you were going to decline: a client portal, a booking engine, a Next.js front end reading from WordPress. Same invisibility rules, different stack.
When the pipeline is steady. A named engineer works only on your accounts and attends your standups.
Every step produces an artefact you can forward to your client without editing it first. That's the test we design the process against.
Signed before you send anything. We scope from the requirement, not the logo, and give you a straight yes or no on whether we should take the job.
Ranges with each assumption printed beside them, plus a list of what we weren't told. You re-price and send your own. A firm number needs a written scope — a forwarded email gets a range, and we'll say so.
Accounts in your repository, tickets and Slack. Commit identities, plugin headers and staging domains set before the first push — a corrected history is still a history.
On your domain, so you forward the link with no caveat. A slip shows a fortnight in, not a week before launch, and reaches you in writing the day we see it.
Runbook, licence register and editing notes in your template. Credentials transferred, our access removed, and recorded walkthroughs your client's staff can watch without meeting us.
A 30-day defect warranty at no cost on what we built: you raise the ticket, we fix it, you report it fixed. Ongoing updates and monitoring run as a retainer you resell, endable on 30 days' notice.
Agency–subcontractor relationships fail in the same five ways. Promises are cheap, so these are clauses.
We never contact your client independently — not for a testimonial, a case study or follow-on work, and not after the partnership ends. If they approach us, we tell you and decline.
You are the client — scope changes reach us as change requests from you. We don't negotiate with your customer or comment on your pricing.
Bad news reaches you first, always — a date at risk reaches you before anyone else, blunt internal version included. You should never be surprised alongside your client.
IP assigns to you on payment, with onward assignment rights — to your client, on your terms. We retain nothing and licence nothing back.
Either side can stop on 30 days' notice — with a full handover of documentation, credentials and known issues. A partnership that's painful to leave isn't one.
If a brief needs something we don't run in production — Salesforce or SAP configuration, say — we tell you before you quote it. For your client's security questionnaire, see what we hold and what we don't.
The shape you pick decides who absorbs an overrun — worth choosing deliberately.
Against a written scope with acceptance criteria. Suits a defined build you've already sold, with a number you can mark up.
A named engineer reserved to your agency, allocated across your clients. It prices better for steady volume and removes the availability question.
Cheaper per unit of work, because you absorb the variance. Right for discovery or a backlog that isn't written yet.
Three are the fears agency owners name on the first call. The fourth nobody asks about until it happens.
It rarely leaks through a person — it leaks through a staging subdomain, a plugin header, a commit email or a PDF author field.
How we handle it: seven of the eight surfaces are configured at kickoff. The eighth, commit authorship, we flag before you sign — your decision, not our omission.
The real limit of white label: it works on defined scopes and badly on discovery, where the requirement arrives two conversations removed.
How we handle it: no fixed fee on discovery-heavy work. We quote a paid discovery, run through you, and hand back a specification you can price.
You promised a date built on our estimate. When it moves, your client hears it from you, and the damage lands on your side.
How we handle it: two-week increments, each ending on a staging URL you can open, so a slip surfaces early — in writing, the day we see it.
Your client meets our engineer, likes them, and starts asking questions directly. Six months later they wonder what your margin is for.
How we handle it: direct approaches go back to you, and we tell you it happened. Every engineer is briefed on that before repository access.
Yours. The Author, Author URI and Plugin URI fields in every plugin and theme name your agency, set before the first commit. It matters more than most of the NDA: WordPress prints them in the admin plugin list, in front of your client for the life of the site. Ask any partner this — it shows fast whether they've done it before.
Your client does, in their own name, with a licence register listing every renewal date. We won't put an ACF Pro key or WooCommerce extension on our account — that dependency breaks when the partnership ends. Agency-level licences work too, if decided at kickoff rather than discovered at renewal.
A marketing site runs four to seven weeks once content is ready; a content-heavy build eight to fourteen; a WooCommerce store six to sixteen, depending on catalogue and integrations; anything behind a login twelve or more. The usual delay is content and third-party access, not code, so we set a content deadline in week one.
Yes — often your developer on templates and ours on the plugin and integration layer. It works when the boundary is drawn at kickoff and enforced in code review: who owns which directories and whose conventions win. It fails when both sides edit the same functions file, so we draw that line before starting.
You decide. By default you're the only voice and clarifications round-trip through you. Some partners put us on calls as their named technical lead, under their branding — fine if agreed in advance. What never happens is us contacting your client independently, during or after the partnership. That part is contractual.
Never. A 30-day defect warranty at no cost covers bugs in what we built: you raise the ticket, we fix it, you tell your client. Beyond that, updates, backups and security patching run as a retainer you resell at your own margin — the AMC shape under dedicated teams and support, endable on 30 days' notice.
You do — the code lives in your repository from the first commit. IP assigns to you on payment for the milestone in which it was written, with the right to assign onward to your client. We retain nothing and licence nothing back. The same position applies across every engagement model we offer.
Two to four weeks from first call to first commit, covering NDA, agreement, accounts and conventions; later work usually starts within a week. Make the first project contained, before a flagship account is on the line.
Thirty minutes with an engineer, not a salesperson. Bring the scope you're about to quote, or the late project you need off your team — you'll leave with a range and its assumptions.