Your client never needs to know we exist

Staying invisible sounds like a policy. It is mostly a checklist, and the items on it are unglamorous. Here is what we actually do, partly so you can hold us to it and partly so you can ask the same questions of anyone else you are considering.

Before anything starts

The NDA is signed before the kickoff call, not attached to the first invoice. It covers your client's identity, the work itself, and the fact that the engagement exists at all. We do not reference the project in a pitch, a case study, a portfolio or a conference talk — not after launch, not after the engagement ends, not with the details filed off.

This costs us something real. A delivery bench that cannot show its work has to win business on referral and reputation instead. We think that is a fair price for being trusted with other people's client relationships.

During the build

The operational details are where invisibility is won or lost:

• Staging runs on your domain or a neutral one, never ours
• Repositories live in your organisation, with our access granted and later revoked
• Commits carry the agreed author identity, so the history reads as your team's
• Design files are created in your workspace rather than shared out of ours
• Documentation carries your branding, or none at all

The commit history is the one that surprises people. A client with repository access can read it, and a year of commits from an unfamiliar organisation is a conversation nobody planned for. It takes thirty seconds to configure correctly at the start and is tedious to rewrite later.

The no-contact rule

We do not contact your client. Not for feedback, not for a testimonial, not for a reference, not after the work ends. If your client somehow reaches us directly, we tell you and we do not reply.

The relationship is the thing you are protecting. Everything else on this page is just the mechanics of protecting it.

This has a cost for you, which we should be straight about: you are the only channel. Feedback comes through you, clarifications come through you, and when a client changes their mind on a Friday afternoon, you are the one who hears it first. A partner who never speaks to your client cannot absorb that for you.

At handoff

Final delivery contains source files, code, documentation and credentials — and no trace of us. No readme crediting a third party, no comment block with a company name, no attribution in the footer, no analytics or error-reporting account pointing somewhere unexpected.

We also revoke our own access once you confirm you have everything. Lingering access to a client system you no longer need is a liability for both of us, and the longer it sits the more likely it is that nobody remembers it exists.

What to ask any delivery partner

If you are evaluating partners, these five questions separate a considered arrangement from a hopeful one: Whose domain serves staging? What identity is on the commits? Will this appear in your portfolio, ever? What happens if my client emails you directly? And who revokes access at the end, and when?

Any partner who has thought about this will answer all five without hesitating. Any partner who has not will tell you it has never come up — which is true right up until the moment it does.