We work two ways. As the engineering half of agencies and studios who have the client but not the build. And as the long-term technology side of businesses that run on software but do not employ engineers.
Both come down to the same thing: a partnership is a set of constraints we accept that a supplier would not. The rest of this page is those constraints, written plainly enough to hold us to.
An agency and a business are not worried about the same thing, so it would be dishonest to sell them the same paragraph.
Design studios who win a project that turns out to need a real backend. Marketing agencies whose client asks for a platform, not a campaign. Dev shops with more signed work than engineers.
The thing actually stopping you is not price. It is that handing a client to another firm feels like handing over the relationship.
Not during the build, not after it ships, not in two years. Written into the agreement as a non-solicit that runs both during and beyond the engagement. Your client relationship is the asset you are protecting — we know that is the whole question.
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. If you would rather be open about who builds it, that is your call to make, not ours.
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.
No account manager relaying requirements badly. You get direct access to the person writing the code, because a second layer of translation is where agency subcontracting usually breaks.
The portal your dealers order through, the system your staff live in all day, the platform your revenue moves across. It exists, it matters, and nobody on your payroll owns it.
Hiring a team is premature. A project-by-project vendor forgets your system between jobs. The fear is ending up dependent on whoever happens to hold the passwords.
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.
A partnership 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.
The point of a technology partner is that somebody other than you is carrying the architecture in their head — what depends on what, what will break at scale, what needs replacing before it fails. That is the job.
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 just a supplier with better manners.
Most partnerships settle into one of these. If yours does not, say so on the call and we will scope something that fits rather than force it into a bucket.
Design studios, brand and marketing agencies, and dev shops running at capacity.
Per project, fixed scope and fixed price. You hold the client relationship and the margin; we hold delivery.
Businesses with real operational software and no in-house engineering team.
Monthly retainer for a defined block of engineering capacity. Maintenance-only plans start at ₹10,000/mo; genuine partnership engagements are scoped higher.
Consultants and operators who keep meeting businesses that need a system built.
You make the introduction, we take it from there. Referral terms agreed per introduction and in writing before anything starts — we would rather set the number with you than publish one that turns out to be wrong for the deal.
Founders with domain expertise and a product that needs an engineering half.
Reduced fee against equity or revenue share. We are open to this and will discuss it honestly, but the bar is high and we take on very few. Expect us to say no more often than yes.
Anyone can publish a page of promises. These are the things we turn down revenue to avoid — which is the only version of a commitment that costs something.
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.
Nobody should sign a long agreement with a studio they have not watched work. So we do not ask anyone to.
30 minutes on what you build, where you keep running out of engineering, and whether our work is the right shape for your clients.
Every partnership we would want starts with one contained piece of work. You find out how we communicate under pressure before anything larger depends on it.
Non-solicit, white-label conditions, IP, response times and rates — agreed once, then reused for every project after it.
Once the terms exist, new work starts in days rather than weeks, because the negotiation already happened.
If you are an agency, that is usually the project that needed a backend. If you are a business, it is the system nobody has owned since it launched. Either way, start with the thing you are stuck on.
