Clients

Working as an agency's delivery partner

A large share of this work reaches the end client through an agency, and it is a deliberate specialism rather than filler between direct projects. Agencies win enterprise Drupal, WordPress or AI work on the strength of strategy and design, then need senior engineering behind it that will not embarrass them in front of a client.

That means working to your process and your tooling, in your repositories, reporting into your project manager. On client calls as a member of your team, or entirely invisible — your call, and it is not a decision you have to make once and live with. NDAs and non-solicitation terms are expected and signed as a matter of course; I have no interest in the relationship you have built.

Why there are no client logos here

Because most of this work is covered by confidentiality or subcontracting agreements that govern whether a client can be named at all, and a logo wall is worth precisely nothing unless every logo on it is real and permitted. Plenty of consultancies solve that by being vague about which logos represent actual paid engagements. I would rather solve it by not having the wall.

Named references are available on request at the point where they actually matter — alongside a proposal, when you are deciding — rather than published for traffic. What is public instead is the work itself: the case studies set out real architectures and the reasoning behind them, which is a better basis for judging whether I can solve your problem than a grid of logos.

How engagements are shaped

The real constraint is capacity, not budget. Senior work is not delegated to a bench, so a limited number of engagements run at once and an honest "not until next quarter" is a possible answer.

Where clients are

• United States & Canada — East-coast mornings; asynchronous handover to the West Coast.
• United Kingdom & Ireland — Four to six hours of shared working afternoon.
• Europe — GDPR data processing agreements and EU-region infrastructure as standard.
• Australia & New Zealand — Morning overlap, which suits a daily check-in rhythm.
• Middle East — Close to full working-day overlap.

Contracting, IP assignment, GDPR and data residency and invoicing currency are all settled in advance rather than negotiated on a first call — see working with clients.

Common questions

What kind of clients do you work with?

Five recurring types: SaaS and product companies adding AI or scaling an existing product; digital agencies needing senior delivery behind enterprise CMS or AI work, often white-label; enterprises with governed platforms and compliance obligations; funded startups building production infrastructure for the first time; and established businesses whose platform has been let go and needs rescuing. Sizes range from a two-person founding team to organisations with their own internal engineering department.

Do you work with agencies as a subcontractor?

Yes, and it is a substantial share of the work. That means delivering under your brand, to your process and tooling, reporting into your project manager, and either joining client calls as part of your team or staying entirely invisible — whichever you prefer. NDAs and non-solicitation terms are expected and signed as a matter of course.

Why are there no client logos on this page?

Because most of the work is covered by confidentiality or subcontracting agreements that govern whether a client can be named, and a logo wall is only worth anything if every logo on it is real and permitted. Named references are available on request at the point where they actually matter — usually alongside a proposal — rather than published for traffic.

What size of engagement do you take?

From a bounded architecture review that ends in a written recommendation, through scoped project delivery with a fixed outcome and date, to a retained block of senior time each month for platforms that need an ongoing owner. The constraint is capacity rather than budget: senior work is not delegated to a bench, so only a limited number of engagements run at once.

Which regions do you work across?

The United States and Canada, the United Kingdom and Ireland, Europe, Australia and New Zealand, and the Middle East, working from India. Timezone overlap, contracting and IP assignment, GDPR and data residency, and invoicing currency are set out in full at manouwer.com/working-with-clients/.