Founder-led engineering/Explicit acceptance criteria

Custom software,
engineered in Kathmandu.
Shipped in two-week sprints.

A founder-led studio that designs and builds custom software, from business platforms and SaaS products to billing systems and data pipelines, for startups, agencies and growing businesses in the US, UK, Europe and Australia. Fixed-fee sprints, you work directly with the engineer building it, and you own all the code.

14 days
Per agreed sprint
Direct
Engineer access
Full
Project handover
zariya-sh • engineering sandbox
Local demonstration

Explore our approach. Ledger operations run locally; ping measures an HTTP request to this website, not production infrastructure.

// Type help or choose a command. No live cluster or client data is accessed.

5.0★Rated on Clutch
1 verified review
Fixed-fee sprints
Scope agreed before we start
You own the code
Repo, infra and docs handed over
Registered company
Zariya Labs Pvt. Ltd., Kathmandu
What we build

Custom software, designed around how you work

Off-the-shelf tools stop fitting. We design and build the software your business actually needs, from first sketch to a system you own.

Business platforms & internal tools

Portals, dashboards, back-office and workflow software that replaces spreadsheets and manual work.

Web app · Auth · Roles · Reports

SaaS & product MVPs

Take an idea to a working, deployable product in a sprint, built so you can keep extending it.

Next.js · NestJS · PostgreSQL

Mobile apps

Cross-platform Android and iOS apps that keep working with poor connectivity, backed by a clean API.

Flutter · Dart · Firebase

Billing, payments & ledgers

Invoicing, subscriptions and double-entry ledgers that stay correct under retries and concurrency.

TypeScript · PostgreSQL · Idempotency

Data pipelines & dashboards

Ingest, clean and publish data from files, APIs or satellites into something your team can use.

Python · PostGIS · Dashboards

Cloud & DevOps

Deployments, CI/CD, monitoring and secure infrastructure that you own and can hand to any engineer.

Cloudflare · Docker · CI/CD

Not sure what you need? Describe the problem and we will propose a scoped first sprint.

Predictable Engineering Cadence

Two-Week Sprint Operating Model

We eliminate ambiguity with a compressed, high-velocity engineering cycle. Each sprint has a bounded scope, agreed acceptance criteria and a Day-14 handover. Larger systems require multiple sprints.

01
DAY 1 – 2

Architecture & Scope Spec

Deep requirements dissection, interface contract definitions, database schemas, and edge network topology. We lock invariants before any code is committed.

  • ✓OpenAPI / Protobuf contracts defined
  • ✓State machine & ACID boundary audit
  • ✓Threat modeling & access-control mapping
  • ✓Explicit scope and acceptance signoff
Deliverable:Technical Architecture Doc (TAD)
02
DAY 3 – 12

Rapid Implementation & Daily Demos

Focused engineering in TypeScript, Python, Flutter and modern frameworks. Trunk-based development paired with live preview URLs and regular recorded demos.

  • ✓Continuous ephemeral preview branch deploys
  • ✓Regular async demos & release changelog
  • ✓Zero blocker escalation protocol
  • ✓Reproducible build pipeline
Deliverable:Working Production Candidate
03
DAY 13 – 14

Automated Test Suites & Handover

Rigorous chaos testing, P99 latency load verification, complete runbook documentation, CI/CD access transfer and secret rotation, and production cutover support.

  • ✓k6 & wrk benchmark load test reports
  • ✓Unit + integration tests for agreed acceptance criteria
  • ✓Docker Compose / infrastructure scripts
  • ✓100% IP & repository transfer to client
Deliverable:Production Release & Full IP Transfer
</>

Direct Access to the Engineer Building It

No account managers or middlemen. You work directly with the engineer who writes the production code.

Fixed-Fee SprintsAgreed Acceptance Criteria
Working with a Kathmandu team

Why work with Zariya Labs from Kathmandu

Outsourcing succeeds on how the work is run, not on where the desk is. Here is how we make a 5h45m offset from GMT an advantage.

Founder-led, no middlemen

You talk directly to the engineer building your product. No account-manager layer, so nothing gets lost in relay.

Cost that makes sense

Kathmandu engineering costs a fraction of US or Western Europe rates, and fixed-fee sprints keep the total known before work starts.

Async by default

Written updates, recorded demos and preview links mean progress never depends on a shared meeting hour.

You own everything

Repository, infrastructure code, tests and documentation transfer to you at the end of each sprint.

Your timezone and ours

Nepal Standard Time is UTC+05:45, all year. We are available around the clock, so a 09:00-17:00 day in your region is covered:

Working-hour overlap between Kathmandu and client regions
Your regionOverlapWhat that means
UK / IrelandFull working day coveredSame-day answers to most questions
Central EuropeFull working day coveredMorning calls, async in between
Australia (Sydney)Full working day coveredCalls in your afternoon, our morning
US East / WestFull working day coveredWork is ready when your day starts

Need a specific call window? Tell us in the brief, at contact@zariyalabs.com.np.

Low-risk ways to start

How we work with you

Start with one sprint. If it delivers, keep going. If it does not, you still own the code.

Best first step

Fixed-fee sprint

A bounded piece of work delivered in 14 days with agreed acceptance criteria.

  • Scope and acceptance signed off before day 1
  • Daily written progress, recorded demo each week
  • Full repository, infra code and runbook handover on day 14
  • Larger systems run as consecutive sprints
Ongoing product work

Extended team

Added capacity that works as an extension of your team, after a successful first sprint.

  • Engineers who already know your codebase, scaled to your needs
  • Works in your repo, tracker and chat
  • Monthly scope review, no long lock-in
  • Same handover and ownership terms
Our work

Things we have built, in the open

Products and platforms we designed and built ourselves. The source is public, so you can read the code before you hire us.

Mobile app

KrishiSource

An open-source, offline-first Flutter app that gives Nepali farmers live wholesale vegetable and fruit prices, with English and Nepali search and a scheduled price scraper behind it.

Flutter · Dart · Riverpod · Isar · Python · Flask

View the source on GitHub (KrishiSource, opens in new tab) ↗
Accounting / AI agents

AgentLedger

A hackathon project: AI agents parse invoices, redact personal data and post balanced double-entry journal entries, with low-confidence cases routed to a human review queue.

TypeScript · Node · MCP · PostgreSQL · Google Cloud Run

View the source on GitHub (AgentLedger, opens in new tab) ↗

These are our own projects, not client engagements. Client work is shared with permission; ask us for a walkthrough or a reference.

The person you work with

Meet the founder

Bikram Bahadur Basnet

Bikram is a software engineer and the founder of Zariya Labs. He holds a Bachelor of Information Technology from Victoria University in Melbourne and has worked as a freelance software engineer since January 2026. In July 2026 he incorporated Zariya Labs Pvt. Ltd. in Kathmandu to run that work as a studio.

He is your direct point of contact and the engineer behind the production code. The projects listed under Our work, including the open-source source code, are his, so you can read how he builds before you hire the studio.

Role
Founder & Managing Engineer
Based in
Kathmandu, Nepal
Education
Bachelor of Information Technology, Victoria University, Melbourne
Company
Zariya Labs Pvt. Ltd., incorporated 29 July 2026 (Reg. No. 397624/83/84)
Sprint Scoping Tool

Sprint Scope Builder

Configure your engineering domain, workload context, and delivery cadence. We formalize technical milestones, test suites, and deliverables before sprint day 1.

Engineering domain
Workload context
Delivery cadence
Proposed Sprint Scope
Fixed-scope • 14-day cycle
14-Day Delivery Milestones
Days 1–2
Architecture & Schemas
Days 3–12
Build & Daily Demos
Days 13–14
Benchmarks & IP Transfer

Reference topology

TypeScript/Node + PostgreSQL transactions, durable idempotency keys and an outbox

Validation plan

Measure the existing workload and agree a regression benchmark.

Proposed delivery

Transactional kernel, reconciliation invariants and replay tests. One bounded implementation with tests, documentation and Day-14 handover.

Architectural Doctrine

The Engineering Manifesto

Four non-negotiable engineering principles that dictate how we architect systems, write code, and deliver value without agency friction.

// TENET 01DATA INTEGRITY

Explicit Ledger Transactions

Object-Relational Mapping libraries hide N+1 queries, obscure database deadlocks, and introduce ambiguous transaction boundaries. In financial ledgers, audit systems, and billing pipelines, we write explicit SQL transactions with balanced postings, durable idempotency keys and serialization retries. Your balances are calculated, never updated in place.

• Serializable Isolation|• Reconciliation tests
// TENET 02INFRASTRUCTURE PHILOSOPHY

Boring Tech at Core, Edge at Perimeter

We do not adopt experimental databases for mission-critical core state. At the persistence layer, we rely on battle-tested PostgreSQL. At the perimeter, we use Cloudflare for fast, cached delivery. Reliability in the engine room; speed at the edge.

• Predictable Resource Bounds|• Regional measurements
// TENET 03OPERATIONAL CADENCE

Async-First Delivery

We keep status updates asynchronous and use technical calls when decisions need discussion. We write production software. Every commit triggers automated trunk-based CI tests, ephemeral preview environments, and concise recorded walkthroughs. You talk directly with the engineer writing the code.

• Recorded Demos|• Direct Engineer Access
// TENET 04OWNERSHIP TRANSFER

Day-14 Complete IP & Infra Handover

Zero proprietary platform lock-in. On the final day of every sprint, 100% of the Git repository, Docker orchestration files, infrastructure scripts, and automated test suites are formally transferred to your organization. You receive runbooks, deployment scripts and ownership of commissioned code. Third-party dependencies retain their licenses; support and rollout responsibilities are agreed in the scope.

• 100% Client Code Ownership|• Zero Vendor Lock-in

Questions buyers ask first

Who owns the code and infrastructure?

You do. Commissioned code, infrastructure definitions, tests and documentation are transferred to your organisation at handover. Third-party dependencies keep their own licences. We sign an NDA and IP assignment before work begins if you want one.

How do we communicate across the timezone gap?

Written daily updates, recorded demos and preview links for progress, plus scheduled calls in a window that suits you for decisions. See the table above.

What does a first engagement look like?

A short scoping conversation, a written scope with acceptance criteria, then a 14-day fixed-fee sprint that ends in a working, handed-over deliverable.

How is pricing decided?

Sprints are fixed-fee against an agreed scope, so the total is known before work starts. Scope and fees are agreed before implementation.

Is my data safe?

Share the minimum. Access is granted per project and revoked at handover. Please do not send passwords or confidential datasets in the brief form; we set up access properly once we start.

What if the sprint does not go well?

Acceptance criteria are agreed up front, so it is clear what was delivered. You keep everything produced to that point.

Discuss your first sprint

Tell us what needs to work, what exists today, and how you will judge success. Scope and fees are agreed before implementation.

Avoid passwords and confidential datasets. Your draft stays in this browser until you copy, download, or open it in your email app.

Open email app

Direct contact: contact@zariyalabs.com.np · Printable capabilities

Find a section

↑ ↓ navigate · Enter select · Escape close