Your agency, our engineering team. The client never knows we exist.

We work inside your workspace under your naming conventions, and where you want it, on your email domain. Client-facing documents carry your branding only. If a client call needs an engineer, they join as part of your team or we brief your PM instead, your call, agreed before kickoff.

A non-solicitation clause in the same document as the NDA, running both directions and surviving the end of the engagement. It is enforceable, and it is the reason we do not publish client work without written permission.

Two things. Internally: AI-assisted code generation under senior review, automated test authoring, migration and refactor tooling, and spec-to-scaffold on new services, which is what compresses a proof of concept into two weeks. In the product: retrieval-grounded assistants, document extraction, computer vision, forecasting and agentic workflows, built as real features your client can sell. We will show you which parts of an estimate AI actually changed.

You do, or your client does, whichever your contract with them specifies. Full IP assignment on final payment, including repositories, infrastructure definitions and documentation. We retain no licence and no reuse right over anything project-specific.

We recommend it. A paid pilot (one module, one integration, one prototype) is the cheapest way for you to see how we estimate, communicate and ship before you put a large brief at risk.

You get told early. Weekly demo builds exist so that a slipping timeline is visible in week two, not week nine. Where we have misestimated, we say so and absorb it rather than reopening the price with your client already committed.

We are in Dhaka, GMT+6. Against a 09:00–18:00 day here: the UAE overlaps seven hours, the rest of the Gulf six, Central Europe four to five, the UK three to four, and eastern Australia three to four in your afternoon. US Eastern overlaps zero hours on standard schedules, so for North American partners we run a shifted 14:00–22:00 shift that puts 09:00–12:00 Eastern inside our day, with US Pacific handled by one fixed daily call and an async process. Whichever window applies to you goes in the engagement document, so nobody is guessing in week three.

A GDPR Article 28 processing agreement, Standard Contractual Clauses for the transfer (Bangladesh has no adequacy decision, so SCCs are the mechanism) and a named sub-processor list you can hand to their DPO. Where the requirement is that data does not leave the EU, we deploy into an EU region and scope engineer access accordingly. Same pattern for a Gulf client who needs in-region hosting.

We do, in the sectors on this site. We will tell you upfront if a brief you send overlaps with something we already run directly, and we will decline rather than create a conflict.