What we don't do
The engagements we decline, and why refusing them is part of the service.
Every agency has work it won’t take. Ours is listed here, in writing, so you don’t have to discover it on a call.
Engagements we decline
- Tenders decided in advance. Bidding against three other agencies on a budget that was fixed before anyone read the requirements. Nothing we could write in a bid changes that, so we don’t submit one.
- White-label subcontracting. The whole point of hiring us is talking to the people doing the work. Building things another agency puts its name on removes exactly that.
- Marketing-stack work. Pixels, ad platforms, GA conversion tuning, consent banners. It is important work, but it is outside our scope, and we can refer you to specialists.
- Rewrites without a reason. “The new framework is out” is not a reason. If your store is fast and maintainable, the initial technical audit will say exactly that, and the engagement ends there.
- Retainers without scope. A monthly invoice for unspecified availability creates friction on both sides. Our retainers have a scope agreed in writing, named responsibilities, and one month’s notice on either side.
- Work we could not defend a year later. Dark patterns in checkouts, fake-urgency timers, consent walls designed to exhaust. We decline this work even where it would increase conversion.
Why declining work is part of the service
Every one of these is an engagement someone was willing to pay for. Declining them is what keeps our recommendations independent of what we would prefer to sell you.
How we work, and the contract before you sign
On every engagement we keep to weekly written check-ins, work in your repo from day one, and go/no-go cutover checklists. We deploy so that a release can be rolled back. You get the contract, exit terms included, in writing before you sign.