Partner with us

The problem this solves

A client asks for something outside what you do. Turning it down sends them looking elsewhere, and the firm they find will be glad to take the rest of the account too. Building the capability yourself means hiring for a skill you may need once.

The third option is a partner who delivers under terms you set — visible or invisible to the client, as you prefer — and who has no interest in competing for your account. That is what this is.

How partnerships work here

Four arrangements, and most partners end up using more than one. None of them requires an exclusivity agreement or a minimum commitment.

Referral

You introduce the client and step back. We contract directly, you take a referral fee on the engagement, and you stay informed without carrying delivery risk. Best when the work is well outside your field and the client is comfortable with a direct relationship.

White-label delivery

We build it; your client sees your brand throughout. You remain the single point of contact, we work to your process and your reporting cadence, and our engineers appear under your account where that matters. This is the most common arrangement and the one that needs the clearest agreement up front — particularly around who holds the client relationship after launch.

Team extension

Named engineers join your team, use your tooling and attend your standups. Not a resourcing pool: you interview them, you keep them, and if someone is not working out we replace them rather than rotating people through. Useful when you have the architecture and the shortfall is capacity.

Product partnership

We build and run Medixar for healthcare and Workdome for CRM, HR and finance. If either fits a client of yours, there is a reseller and implementation arrangement — you handle the client and the configuration, we handle the platform.

What you can put in front of a client

Everything on our services and technologies pages is available through a partnership. In practice partners most often bring us:

Custom software and platform builds

Enterprise systems, integrations and the long-running platforms that are too involved to hand to a freelancer. Forty-one are written up in our case studies, with the stack and the deliverables on each.

AI and decision engines

Language models in a product, document and language understanding, and business rules engines that analysts configure without a deployment. What we have actually shipped, and what we decline to build.

Cloud services and management

Migration to and management of AWS, Azure and Google Cloud, including architecture design, deployment and ongoing operation.

Network monitoring and management

Continuous monitoring of network infrastructure: bandwidth management, firewall configuration, security audits and real-time performance analytics.

Cybersecurity

Vulnerability assessments, intrusion detection and prevention, endpoint protection and managed security services.

Data engineering and analytics

Ingestion, ELT, governance and visualisation — the pipeline work that has to exist before a dashboard means anything.

IT consulting and strategy

Assessments, technology roadmaps and the architecture decisions that are expensive to reverse.

What we expect, and what we commit to

Non-compete

We do not approach your client for work you could have done

Attribution

Yours by default; we name a partner only with written agreement

First response

Within one working day, with who would do the work

Commitment

None. No exclusivity, no minimum volume, no retainer

The one thing we ask is an honest brief. Most partnerships that go wrong do so because the scope a partner was given was already optimistic before it reached us, and nobody wanted to be the one to say so.

Start a partnership

Tell us what your client needs and which arrangement you have in mind — or ask, if you are not sure which fits. Email [email protected] or use the contact form, and we will come back within one working day.