·Partners
Partnership is what we give up.
Every vendor calls itself a partner, so the word proves nothing. What proves something is the list of things we sign away — so that is what this page is.
·For agencies & studios
Your client stays your client.
The only question that matters when you subcontract is whether the people you bring in will still be strangers to your client in two years. Four commitments, all of them in the agreement.
We will not approach your client
Not during the build, not after it ships, not in two years. Written into the agreement as a non-solicit that runs during and beyond the engagement. Your client relationship is the asset you are protecting — we know that is the whole question.
We appear as your team, or not at all
White-label by default. Your brand on the work, your name in the client's inbox, our engineers on your calls if you want them there. Being open about who builds it is your call to make, not ours.
Your date is the date
You have already promised something to your client. We scope against that promise and fix it in writing, so the commitment you made is the commitment we are held to.
You talk to the engineer
No account manager relaying requirements badly. Direct access to the person writing the code — a second layer of translation is where agency subcontracting usually breaks.
·For businesses
You never become dependent on us.
The fear here is the opposite one — that a partner becomes a permanent cost you cannot leave. Every commitment below is designed so that leaving stays easy.
You own everything, continuously
Source, IP, infrastructure and documentation are yours from week one, not handed over at the end. Repository and deploy access sit with you throughout. Leaving is always possible, which is the only thing that makes staying a decision rather than a trap.
Retained capacity, not a subscription
A retainer buys a defined amount of engineering time each month. If a month is quiet we tell you, and we bank it or bill less. We are not interested in charging you for a slow month and hoping you do not notice.
We hold the technical picture
The point of a technology partner is that somebody other than you is carrying the design of the thing — what depends on what, what breaks at scale, what the next change will actually cost. That is the job.
We will tell you to stop
When a feature is not worth building, when an existing tool solves it more cheaply, when the honest answer is that you do not need us this quarter — you will hear it. A partner who only ever agrees is a supplier with better manners.
·What we will not do
The refusals.
Commitments are easy to write. Refusals cost something, which is why they are the part worth reading.
We will not
- Take on work we cannot staff. If we are full, you get a date, not a maybe.
- Put a junior on senior work and invoice it as senior work.
- Quote a number before we understand the constraint that makes the job hard.
- Recommend a custom build when an off-the-shelf tool genuinely solves it.
- Hold your repository, your domain or your infrastructure as leverage.
- Contact your client behind you, in any form, ever.
·Shapes
Four ways this runs.
White-label engineering
Per project, fixed scope and fixed price. You hold the client relationship and the margin; we hold delivery.
Embedded technology partner
Monthly retainer for a defined block of engineering capacity, scoped to a real roadmap. We do not sell standby maintenance on a system that is already stable.
Referral partnership
You make the introduction, we take it from there. Terms agreed per introduction and in writing before anything starts.
Product partnership
Reduced fee against equity or revenue share. We will discuss it honestly, but the bar is high and we take very few. Expect us to say no more often than yes.
A conversation, not a pitch
Thirty minutes on what you build, where you keep running out of engineering, and whether our work is the right shape for your clients.
A small first project
Every partnership worth having starts with one contained piece of work. You find out how we communicate under pressure before anything larger depends on it.
Terms in writing
Non-solicit, white-label conditions, IP, response times and rates — agreed once, then reused for every project after.
A standing lane
Once the terms exist, new work starts in days rather than weeks, because the negotiation already happened.
- Based in
- Dehradun, India
- Working across
- 8 countries
- Building since
- 2023
- Reply
- One business day
Send the first project.
Not a partnership proposal — one contained piece of work. That is how every arrangement here has actually started, and it tells both of us more than a call ever will.