OUR CORE PRACTICE · SINCE 2010
Most agencies can ship an MVP. We build the systems that are still running — still secure, still scaling, still compliant — five years after launch. Nepal Rastra Bank still runs the litigation system we built. DiNePa still runs the procurement SaaS. hundreds of projects shipped since October 2010, with 4.8★ across 25 verified Capterra reviews.
48-hour response · NDA on request · Your first call is with an engineer
THE PROBLEM
Custom software projects fail in three predictable ways. They fail at scope — agencies that win on price tend to under-spec discovery, and the resulting build hits architectural walls in month three because nobody mapped the real concurrency, integration, or compliance requirements. They fail at architecture — teams that learned web design and then started calling themselves “full-stack” ship MVPs that crumple the moment real users, real load, or real regulators show up.
And they fail at post-launch. The MVP gets shipped, the agency moves on, and 12 months later the codebase is unmaintainable, the deployment is fragile, and the original founders are quietly Googling for a new vendor to take it over. This is the single most common engagement we get inbound: “Our last team disappeared. Can you take it from here?”
We’ve spent 15 years specifically not being that team. We’re built around long-tenure clients — Nepal Rastra Bank has been with us five years post-launch, DiNePa is still on retainer years after go-live, and every client from our portfolio is still operational somewhere in the world. Custom software is a 5-year commitment, not a 5-month project. We engineer for the second year, not the demo.
OUR APPROACH
We map your business workflow, regulatory environment, integration surfaces, and target user load. We stress-test your assumptions: what does “real-time” actually mean for your users? How many concurrent sessions on peak day? What auditors will read these logs? Deliverable: a written technical spec, architecture sketch, fraud/security surface analysis, integration plan, and a fixed-price quote for the build phase. Discovery fee credited toward the build if you proceed.
We design for your specific load and lifecycle. Central bank legal workflow has nothing in common with a high-concurrency auction platform — both are “custom software,” but the architecture decisions are nearly opposite. We document data model, deployment topology, security model, audit trail design, and the integration plan for every external system. Deliverable: an architecture document the next team could pick up cold.
Two-week sprints. End-of-sprint demos on a live staging environment. You see real working software every two weeks — not a slide deck. We ship the data model first, the core workflow second, and the user interface third — because the order matters when you’re debugging real-world edge cases. Communication: dedicated Slack channel, weekly written status, video demo every sprint, and direct access to the engineering lead.
We don’t disappear after go-live. Every long-running client — Nepal Rastra Bank (5+ years), DiNePa (years of operational support) — remains on a retainer for feature work, performance tuning, security patches, and operator support. Deliverable: production deployment, monitoring/alerting setup, operator runbook, 90-day production warranty, and a clear handoff path if you ever decide to bring it in-house.
VERTICALS WE SHIP
The pattern beneath the verticals: transaction-heavy, workflow-critical, and accountable to someone — auditor, regulator, or user.
For: Regulated workflows where audit trails and access control are non-negotiable. Maker-checker patterns, immutable logs, role-based access, secure intranet deployment.
Reference deployment: Nepal Rastra Bank (litigation management system, 5+ years live, Laravel 9 + MySQL 8, bilingual English/Nepali Unicode).
For: Property listing platforms, MLS integrations, agent workflow, portfolio management. Large-catalog search, multi-photo media handling, lead-routing, CRM integration.
Reference deployments: My Saving Grace Realty (Philippines, 4,800+ active property listings), msg-homes, Exposure Realty, Property Bid.
For: Dispatch platforms, delivery tracking, driver/operator mobile apps, GPS routing, real-time order state. Operational software where minutes matter.
Reference deployments: RabbitDispatch (goods delivery), Local Service Booking App (Uber-for-services), TechRyde.
For: Sensor data ingestion, time-series storage, dashboards, alerting, consumption analytics. Real-time pipelines where reading lag breaks the product.
Reference deployment: Energyly (energy consumption monitoring + analytics platform with IoT integration).
For: Mission-critical systems — incident reporting, mass alerts, disaster management. Multi-channel push (SMS, email, push notifications), geofenced targeting, audit-grade delivery confirmation.
Reference deployments: Zippy Alert (incident reporting + mass notification), Alacer (disaster management + mass alert system).
For: Multi-party transactional systems — auctions, marketplaces, B2B procurement. High concurrency, fraud-resistant logic, multi-currency payment integration, operator panels.
Reference deployments: DiNePa (EU public-sector procurement SaaS), 6 auction formats across many platform deployments.
CASE STUDY DEEP-DIVE
Nepal Rastra Bank (NRB) is Nepal’s central bank — the institution that regulates the country’s commercial banks, manages monetary policy, and holds the foreign exchange reserves. Their IT Department engaged us to digitize the bank’s entire legal operations workflow. Before our system, NRB’s legal team was running on paper: physical case files moving between desks, manual approval cycles taking 7–10 days per case, and audit prep that required digging through filing cabinets ahead of every regulatory review. This was operational risk at a central-bank level.
An enterprise-grade Litigation Management System on PHP 8 + Laravel 9 + MySQL 8, deployed inside NRB’s isolated intranet for full data sovereignty. End-to-end case lifecycle tracking. Maker–Checker 4-Eye Principle enforced on every legal action — a creator submits, a checker approves, and nothing happens without both. Role-based access control with structured Creator / Checker / Admin permissions. Encrypted document management. Full bilingual English/Nepali Unicode with dual-date (BS/AD) display, because Nepali legal documents must render in Nepali script and dates often need both calendars. Immutable audit trail logging every system action for permanent regulatory transparency.
Case resolution dropped from 7–10 days to 2–3 days — a 70% reduction in resolution time by removing manual cycles and physical file movement. The system replaced manual audit preparation with 100% automated audit readiness via real-time reporting and immutable activity logs. Operational capacity expanded 5×: from 8 manual users on the paper system to 40+ digital users coordinating legal cases across the institution. The platform has been live in production for 5+ years, on continuous support with our team.
Central-bank-grade software is 30% engine, 70% the audit trail and the access model. Anyone can build a case-tracking app. The defensible work is the immutable event log, the maker-checker enforcement, the bilingual Unicode rendering in legal documents, and the deployment architecture that survives a security audit. We over-invested in those four from day one — and five years in, NRB is still running the system without a single rebuild. That’s the bar we set for every custom software engagement: still operational in year five.
TECH STACK
HOW WE ENGAGE
2–3 weeks · fixed fee
Best when you have a software concept but no spec. We map your workflow, regulatory environment, integration surfaces, and target load. Deliverable: a written technical spec, architecture sketch, and a fixed-price quote for the build phase. Fee is credited toward the build phase if you proceed.
3–6 months · fixed price
Best when you have a spec and need a fixed budget. We deliver production-ready software with operator admin, full integrations, monitoring, and a 90-day production warranty. Two-week sprints, end-of-sprint demos on staging, weekly written status. The engineer you meet in discovery is the engineer who ships your code.
Monthly · time-and-materials
Best post-launch — or if you inherited code from an agency that disappeared. We’ll audit the codebase, write a remediation plan, and either keep it running or rebuild the problem pieces. NRB and DiNePa have been on this model for years. Hours scale to your roadmap.
Standard contracts: MSA + SOW templates available on request before our first call. Mutual NDA on request, signed before discovery. Payment terms: 30% on signature, remainder milestone-based. Source code escrow on request for enterprise clients.
QUESTIONS
It’s the practice of architecting and building software for a specific business workflow, scale requirement, or regulatory environment — instead of bending an off-the-shelf product around your needs. Used when off-the-shelf tools genuinely don’t fit (regulated industries, unusual workflows, integration-heavy environments) or when the cost of customising off-the-shelf has exceeded the cost of building custom.
2–3 weeks discovery, then 3–6 months for mid-size systems. Enterprise systems with heavy regulatory or integration requirements can take 6–9 months. We give a fixed-price quote with a fixed timeline after discovery — not a wide range.
We quote firm numbers after a 30-minute discovery call where we understand your scope. Pricing model: fixed-fee discovery sprint, fixed-price MVP build, time-and-materials retainer post-launch. We’ll send a ballpark range during our first conversation and a fixed quote after discovery.
That’s the bar we set. Nepal Rastra Bank’s litigation system is on year five in production. DiNePa is years into operation. Every long-running client from our portfolio remains operational. We architect for the second year, not the demo.
Yes — it’s one of our most common engagements. We’ll audit the existing codebase, write a remediation plan, and either keep it running or rebuild the problem pieces. We’ve done this for clients whose original team disappeared or whose platform stopped scaling.
By design from day one. Encryption at rest and in transit, role-based access control, immutable audit logs, secure deployment targets matched to client regulatory environment (intranet for central banks, EU-region cloud for EU public sector, etc.). We’ve shipped to central-bank security standards — ask us about NRB.
You do. Every custom software engagement transfers full source-code ownership to the client on final payment. We can hold the code in escrow during the build if required for enterprise engagements.
We’re listed on Capterra at 4.8★ across 25 verified client reviews — with verified reviewers across real estate, automotive, sports, non-profit, marketing, and auction industries. Read the reviews on Capterra →
Same engineering team. Same architecture bar. Your software, with a foundation that already survived five years inside a central bank.
Inherited a codebase that’s falling over? +977 9851038796 — Roshan Subedi, Founder & MD · takeover audits reviewed directly