Bring a defined client requirement. We can discuss specialist delivery, implementation support or a technical assessment, with responsibilities and communication agreed upfront.
Agencies and consultancies
You need specialist delivery capacity without handing over the client relationship.
Potential work. Defined implementation, integration, assessment or surge delivery under clear white-label or co-delivery terms.
What you retain
Client relationship, commercial ownership of the engagement with your client, and the communication identity you choose.
What the engagement must define
Who speaks to the client, and under whose name.
Scope, review, acceptance and escalation paths.
Confidentiality and non-solicitation terms as agreed.
Software and platform businesses
A customer needs implementation, migration or integration support tied to your product.
Potential work. Scoped delivery against a customer requirement, with product boundaries respected.
What you retain
Product roadmap, customer commercial relationship and product support obligations unless otherwise agreed.
What the engagement must define
Customer-facing communication and escalation.
Environment access and change authority.
Handover back to your support model.
Investors and corporate-development teams
You need a clearer technical picture before a transaction, integration or investment decision.
Potential work. Technical due diligence, integration assessment, or reviews of cost and operating risk within an agreed boundary.
What you retain
Investment thesis, deal process and decisions that follow from the findings.
What the engagement must define
Scope, access and confidentiality for diligence materials.
Who receives findings and in what form.
What is out of scope (legal opinions, valuation, etc.).
Working agreements we settle early
Client communication
Who speaks to whom, and under which identity.
Delivery responsibility
Scope, review, acceptance and escalation.
Commercial arrangements
Fees, billing, changes and any agreed referral terms — set case by case. We do not publish a standing referral-fee schedule.
Handover and continuity
Documentation, access and ongoing responsibilities after delivery.
How a partner engagement typically runs
Enquiry
Share the client need, constraints, timeline and whether delivery should be white-label or named.
Scope
Agree deliverables, access, communication rules, fees and change control in writing.
Delivery
Execute against the agreed scope with the review cadence you both accept.
Handover
Transfer documentation, access and residual responsibilities through the channel you agreed.
Examples of work we take on
Example engagement — illustrative. Typical scopes of work, not named client case studies.
White-label delivery in a specialism you do not staff
delivery under your brand, in your process, with client relationship and confidentiality terms written down.
Implementation capacity for an ISV's customers
a defined implementation or migration scope for your customer, with partner rates agreed.
Technical due diligence for an investor
a fixed-fee assessment written for an investment committee.
Post-merger estate and integration assessment
the combined estate mapped with integration effort and cost quantified.
Portfolio-wide cost review
a consistent cost and estate assessment across portfolio companies, comparable between them.
Start with clarity.
Discuss a defined delivery scope for your clients.
We can explore specialist delivery, implementation support or a technical assessment while you keep the client relationship.
