2018
Three engineers, one apartment
Zeeri Labs starts in a two-room flat in Putali Line with a single client and a borrowed router.
A studio that behaves like a small company, on purpose
We stayed at twenty-five people because that's the largest size where everyone still knows what everyone else is shipping. Growth beyond that has to earn its way in.
At a glance
- Founded
- 2018
- People
- 25
- Teams
- 6
- Office
- Dharan, NP
- Local time
01 Story
Built by engineers who kept inheriting other people's messes
Zeeri Labs began in 2018 because three of us kept being hired to fix software that had been built quickly and cheaply, and kept concluding the problem wasn't the code — it was that nobody had been around long enough to care about year two.
So we built the studio around the opposite bet: fewer clients, longer relationships, and engineers who stay on a project past the launch party. It's a slower way to grow a company and a considerably better way to build software.
Eight years later, roughly two-thirds of our work each year comes from clients we already had. That number is the one we actually watch.
02 Timeline
How the studio got here
2019
First team of ten
The studio moves into its current office in Dharan. Design joins engineering as a standing discipline.
2021
Work crosses borders
First long engagements in Australia and the UK. We learn to run a studio across four time zones.
2023
Care retainers begin
After watching too many products decay a year post-launch, maintenance becomes a first-class offer.
2026
Twenty-five people
Six delivery teams, an apprenticeship programme, and roughly 120 products in production.
03 Principles
Five things we actually argue about
Not values on a wall. These are the positions that come up in project reviews, and the ones a new hire hears in their first month.
01
We say the inconvenient thing early
A schedule risk raised in week two is a conversation. The same risk in week ten is a crisis. We'd rather have the awkward call.
02
The codebase is a handover document
Everything we write assumes someone else will maintain it — often your own team. Naming, structure and tests all serve that reader.
03
Boring where it counts
New technology needs to earn its place against the cost of nobody else on the team knowing it. Sometimes it does. Usually it doesn't.
04
Seniors stay on the project
The people in your kickoff are the people in your code review. No quiet substitution once the contract is signed.
05
Ship small, ship often
Big-bang launches hide problems until they're expensive. We'd rather put something in front of real users in week six.
04 Culture
What a week here looks like
Nothing exotic. Predictable hours, real code review, and enough quiet to think.
- Sunday to Friday, 09:30 to 18:00. Overtime is a planning failure, not a badge.
- Friday afternoons are unbooked — for learning, internal tools, or finishing the thing that's been nagging you.
- Every change is reviewed by a person, including the founders' changes.
- One office, hybrid by arrangement. Most people are in three or four days a week.
- Momo on the last Friday of the month, which has survived every attempt to make it a formal programme.
Come and see the place.
Clients in eastern Nepal are welcome to visit the office before signing anything. Everyone else gets a video call and an honest tour.
- Address
- Dharan, Nepal
- Careers
- 6 roles open
- Team
- Meet everyone