About the studio
E. Deal Nepal is a small engineering studio focused on understanding the domain properly and building software a client's own team can carry forward.
The first years were maintenance and rescue work — inherited codebases, undocumented servers, features nobody could safely change. It taught us to value the parts of software that don't demo well: migrations, tests, runbooks, naming.
Today we work in three areas — product engineering, cloud platform work, and data tooling — with clients in Nepal, the Gulf, Australia and the UK. We keep the team deliberately small so that every project has a senior owner rather than a coordinator.
We are not trying to be the biggest studio in Chitwan. We are trying to be the one people call back.
We begin with the problem, users, existing systems, and constraints before recommending a solution.
We favour readable code, documented decisions, migrations, tests, and operational practices that support future change.
The people who make technical decisions stay close to the work, documentation, and handover.
Frequent, reviewable delivery helps surface uncertainty while it is still possible to change direction.
We communicate constraints early and keep the delivery record clear for the people who own the product.
If we scoped it wrong, that is our cost to absorb, not a change request. It keeps us honest at the start.
Decisions live in the repository, not in someone's memory. Every project ends with a handover document.
Shipping weekly beats a launch date. It also means problems surface while they are still cheap.
We turn down work we are not the right team for, and we say so in the first call rather than the third.
Replace the placeholder portraits and names below with your own team. Roles are grouped by practice.
Principal engineer · Platform
Engineering lead · Product
Product designer
Data engineer
Send us the problem in a paragraph. We will reply with what we would do and who would do it.