About — E. Deal Nepal

About the studio

A small team that stays with the work.

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.

How we got here

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.

What we value

2017

Understand before building

We begin with the problem, users, existing systems, and constraints before recommending a solution.

02

Make change safe

We favour readable code, documented decisions, migrations, tests, and operational practices that support future change.

03

Keep ownership clear

The people who make technical decisions stay close to the work, documentation, and handover.

04

Prefer small releases

Frequent, reviewable delivery helps surface uncertainty while it is still possible to change direction.

05

Stay accountable

We communicate constraints early and keep the delivery record clear for the people who own the product.

How we work

Estimates we stand behind

If we scoped it wrong, that is our cost to absorb, not a change request. It keeps us honest at the start.

Write it down

Decisions live in the repository, not in someone's memory. Every project ends with a handover document.

Small releases

Shipping weekly beats a launch date. It also means problems surface while they are still cheap.

Say no early

We turn down work we are not the right team for, and we say so in the first call rather than the third.

The team

Replace the placeholder portraits and names below with your own team. Roles are grouped by practice.

Portrait

[Team member name]

Principal engineer · Platform

Portrait

[Team member name]

Engineering lead · Product

Portrait

[Team member name]

Product designer

Portrait

[Team member name]

Data engineer

Want to know if we fit your project?

Send us the problem in a paragraph. We will reply with what we would do and who would do it.

Contact us →