Proven Technical Execution
Case studies documenting real problems, the architectural decisions we made, and what actually happened. Not portfolio screenshots — engineering outcomes.
The Planning Bord
Comprehensive ERP System
3hrs → 0
Manual reconciliation time
4 → 1
Systems staff must learn
2 without rebuild
Modules added post-launch
The Problem
The client was managing inventory, project tracking, HR, and finance across four separate tools with no shared data. Staff were manually reconciling records between systems every Friday — a process that took 3 hours and still produced mismatches. Each new team member needed to be onboarded to four separate tools.
The Architecture Decision
We built a single modular platform where each function (inventory, HR, projects, finance) operates as a discrete module with clean data boundaries. Modules share a common data layer so inventory changes immediately reflect in finance reporting. The modular design meant the client's specific workflow automations could be added without touching unrelated modules.
The Outcome
Reduced the Friday reconciliation process from 3 hours to automated — zero manual effort. New staff onboarding dropped from multi-tool setup to one system. The client has since added two new modules (client portal, automated billing) without any rebuild of the existing platform.
Additional Work
Anonymised summaries of enterprise work. Full details available after NDA signing.
Healthcare / Nepal
Healthcare Platform — Compliance Module Swap
Six months into a build, national compliance requirements changed. The entire billing and data-handling approach needed to change.
Because the system was modular from day one, the compliance-affected modules were replaced without touching anything else. No rebuild, no deadline crisis.
"We swapped out the affected modules without touching anything else. No rebuild, no deadline crisis." — CTO
Education / Nepal
School ERP — Government Board Integration
A school group needed their internal student records to generate reports in the exact format required by two different exam boards, which changed requirements annually.
Built a reporting module that is maintained independently of student records. Board format changes are handled as module updates, not system changes.
Retail / Nepal
Retail POS — Multi-branch Inventory
A retailer with four branches was running separate POS systems with no shared inventory view. Staff were calling between branches to check stock.
Unified inventory module connected to all four branch POS systems. Real-time stock view across all locations. Built in 8 weeks on a fixed-fee pilot.
Dedicated Product Team
Most Nepal IT firms sell project-based work. We also offer a dedicated team model: 2–3 engineers embedded in your product long-term, operating as an extension of your own team. Monthly retainer, no re-scoping overhead, no handoff risk.
Best suited for startups and scale-ups that have a working product and need reliable ongoing engineering capacity without the cost and overhead of hiring locally.
Engagement type
Monthly retainer
Minimum term
3 months
Team size
2–4 engineers
Onboarding
2 weeks