01
Capacity on a won account
You have signed the work and the team is not free. We add engineers who match your stack and your standards, without you carrying the hire.
Agencies, consultancies and outsourcing firms
Your delivery arm. Invisible when that is the point.
A large part of our work is delivered under someone else's brand. We are used to being the engineering behind another firm's promise, working in their tooling, to their standards, with no presence in front of their client.
Why partners call us
Three reasons, and they are all about a client you already have.
Partner work is not a side line here. It is how a large share of our delivery reaches an end client.
02
A capability you do not staff
Salesforce, AI engineering, mobile or integration work that sits outside your bench. You keep the account and the margin rather than referring it away.
03
A build under your brand
The whole delivery, run as part of your firm. Your name on the work, your relationship with the client, our engineers behind it.
Under your brand
Your name on the work. Your relationship with the client.
White-label delivery only works if the boundary is decided before anyone starts. We agree it in writing, then hold it.
How the team is represented
Engineers work under your account structure, in your tooling, with your naming. Where you want it, they operate from addresses on your domain and appear in your client channels as part of your team.
- Your repositories, tracker, chat and documentation
- Your templates for estimates, reports and release notes
- Standups and reviews inside your cadence, not ours
- Your definition of done, your review gates
How we stay invisible
When the account calls for it, there is no visible Insteller. We are briefed on what the client has been told, and we do not contradict it.
- No client-facing presence unless you introduce us
- No approach to your client, during the engagement or after it
- No use of your name, your logo or the work in our own material
- Engineers briefed on the boundary before they start
Confidentiality and the paperwork
Confidentiality and intellectual property assignment are signed before anyone is introduced, and our terms sit behind yours rather than beside them.
- Back-to-back terms with your client contract where required
- Non-solicitation of your clients and your staff
- All work product assigns through you to your client
- Access granted and revoked by you, never shared onward
Security posture
Access is the least needed to do the work. Engineers are employees, named to you, on managed machines.
- No undisclosed subcontracting to a third party
- Client data kept in your environments where possible
- Named engineers, disclosed and approved before access
- Offboarding on the day a person leaves the engagement
Representation
How we appear, decided by you.
Three arrangements. Pick one per account, not one for the partnership, and change it when an account changes.
| Dimension | Under your brand | Named alongside you | Direct to your client |
|---|---|---|---|
| Who the client sees | Your team, entirely | Your team, with a named delivery partner | Both firms, with you leading |
| Email and accounts | Your domain and your tooling | Your tooling, our identity disclosed | Either, as you set it up |
| Client meetings | You attend, we brief you | We attend when you ask | We attend as part of the team |
| Documents and reporting | Your templates, your logo | Your templates, contributions credited | Joint format, agreed once |
| Our marketing rights | None. The engagement is not referenced | None without your written approval | By written approval only |
| Typical use | Agencies and consultancies | Systems integrators and delivery firms | Long partnerships with shared accounts |
Before the deal is won
We help you win it, then we build it.
Most suppliers appear after the contract is signed. The useful work happens before that, when you are sizing something you have not sold yet.
01
Before you quote
Effort estimates, a solution outline and the architecture options behind them, sized by the engineers who would do the work rather than by a sales desk.
02
Inside your proposal
Anonymised profiles, methodology sections and delivery plans you can put your own cover on. Written for your document, not lifted from ours.
03
On the client call
A technical lead on the call under your brand when a buyer wants to interrogate the approach. Briefed beforehand on what has been said and by whom.
04
Before you commit a date
A bench check against the roles and the start date you are about to promise, so the date in your proposal is one we can actually hold.
Pre-sales support is part of the partnership rather than a separate engagement. We expect to estimate work that does not close.
Adding capacity
From a call to engineers delivering, in about two weeks.
The partnership paperwork is done once. After that, each new requirement starts at the proposal step.
01
Partner intake
One call to understand your delivery model, your stack, your tooling and how you want us represented to your clients.
02
Paperwork once
Confidentiality, non-solicitation and a master agreement signed at the partnership level, so the next engagement does not restart legal.
03
Named proposal
For each requirement, the engineers by name and seniority, their availability and a start date you can put in front of your client.
04
Team working
A bench-ready role starts within a week of agreed scope. A recruited role takes three to six weeks.
Working in your day
We deliver from Galle at GMT +5:30. That is a full working-day overlap with Australia, Asia and the Middle East, and a working morning with Europe and the United Kingdom. Overlap hours are agreed in writing, with an escalation path outside them, so your client never waits on a timezone.
Proof
Delivery you could have put your name on.
Selected engagements. We describe the work, not the client, which is the same discipline we apply to yours.
Business-as-usual ownership of a CPQ-centred Salesforce estate at a specialty manufacturer
Ongoing ownership of a production Salesforce environment built around CPQ, covering configuration and custom features, ERP and shipping integrations, a customer community and day-to-day org support, held by one team.
Read the case studyFull-stack campaign platform built for a United States marketing company, with advertisement generation engines built in house
A campaign platform that runs United States marketing campaigns from one portal and generates image and video advertisements through engines we built and own.
Read the case studyMRP system built for a manufacturer operating under FDA compliance requirements
An MRP system in use at a company operating under FDA compliance requirements, covering product lifecycles, orders, workstations and audit trails.
Read the case studyNext step
Send us the requirement you are quoting.
Tell us the stack, the roles and the date you need to promise. You will get availability, named engineers and an estimate you can put in your own proposal.