Build — Software
Custom software development in Kathmandu.
Nine Technology builds custom business software in Nepal — billing, inventory, CRM, portals and dashboards — around how your business actually works. Every system is scoped and priced in a written proposal, delivered in stages, and handed over in your name.
- Problem, solution and timeline
- Documented scope
- Working software at each stage
- Delivered in stages
- Post-launch support
- 60 days
- Code, data and accounts in your name
- Yours
Systems we build most often
Software should remove operational friction. We focus on clarity, roles, predictable data, and a baseline that is easy to maintain.
-
Portals
Customer or partner portals with role-based access.
-
Dashboards
Operational views for sales, support, inventory, or admissions.
-
Workflow automation
Cron jobs, queues, notifications, and data sync.
-
Integrations
Payments, email, CRM, spreadsheets, and external APIs.
-
Data systems
Search, filtering, exports, and clean admin UX.
-
Reliability upgrades
Refactors, caching, indexing, and performance fixes.
Common uses
- Billing
- Inventory
- POS
- CRM
- School management
- Clinic management
- HR
- Cooperative systems
- Booking
Why custom, not off-the-shelf
Ready-made software makes you change how you work to fit it. Custom software fits how you already work. You own it, we build only what you need, and it grows with you.
| Aspect | Off-the-shelf software | Custom software from Nine |
|---|---|---|
| How it fits | Your team adapts to the product | The system is built around how your team works |
| Ownership | A licence you keep paying for | Code, data and accounts registered in your name |
| Features | Many you pay for and never use | Only what the business needs |
| Change | Limited to the vendor’s roadmap | Extended as the business grows |
| Local fit | Often built for other markets | eSewa, Khalti, Nepali SMS and your existing files |
Integrations and payments
Business software is only as useful as what it connects to. We wire it to the providers you already use and test every connection end to end before launch.
-
Payments
eSewa, Khalti, Fonepay and bank transfers, with payment status updated automatically and a record of every transaction.
-
SMS, WhatsApp and email
Confirmations, reminders and alerts sent by the system, not typed out by your staff.
-
Spreadsheets and existing tools
Import from and export to Excel and Google Sheets, so nothing your team relies on today is thrown away.
-
APIs and webhooks
Connections to couriers, accounting and other services, with a log of what was sent and received.
Engineering standards
Three principles we do not trade away to deliver faster.
-
Security
Each person sees only what their role allows. Every connection is encrypted, and important changes are logged with who made them.
-
Performance
Fast on ordinary office computers and phones, with the database organised for the reports you actually run.
-
Maintainability
Clean, documented code and written handover notes, so any capable developer can work on it later — not only us.
What you receive
Every system is delivered complete: built, connected, documented and handed over.
The system
- Roles and permissions that actually hold — each person sees only what they should
- A dashboard your team can run without calling us
- Reports that answer the questions you will ask six months from now, not only today
- A database designed for where the business is going, not only where it is today
Integration and data
- Payments, SMS and other integrations wired to real providers and tested end to end
- One round of migration from your existing Excel or files
- Works on phone and computer
Handover and support
- Written documentation and training, so this is maintainable by anyone
- 60 days support after launch
- Everything in your name
How we deliver
Four stages, in this order, with your approval at each one. Most systems take 6 to 12 weeks.
-
Scope
We walk through how the business runs. You get the modules, the price and the timeline in writing.
-
Design
Screens and data structure agreed before building, so you can see how it will work.
-
Build
In stages. Each part is usable as it is finished, so you try it while it is built.
-
Harden and hand over
Tested with your real data, fixed, then handed over in your name with training.
Delivery models
We do not fit every project into one model. How a project is delivered depends on how settled the requirements are, how much certainty you need on cost, and how the product is expected to grow. After the consultation we recommend a model — or a combination, such as a prototype followed by incremental delivery — and name it in the written proposal.
-
Clarity of requirements
Fully defined, partly known, or still to be discovered with you.
-
Certainty of cost
One fixed price for the whole scope, or a fixed price per stage.
-
Pace of change
Whether the product is finished at launch or keeps evolving.
Incremental Common for software Delivered in usable parts, the most important first.
- Core release
- Increment 2
- Increment 3
- Further increments
The system is divided into increments. Each is designed, built, tested and handed over as working software, so your team uses the first part while the next is built.
- Best suited to
- Business software replacing several manual processes — for example, billing first, then inventory, then reporting.
- Pricing and approval
- A fixed price for each increment, agreed before that increment starts.
Agile (Scrum) Common for software Short sprints, with priorities reviewed with you every two weeks.
- Backlog
- Sprint planning
- Two-week sprint
- Review and demo
- Next sprint
Work is organised into a prioritised backlog and delivered in two-week sprints. Each sprint ends with a demonstration of working software and a review of what comes next, so the plan adapts as you learn.
- Best suited to
- Products whose requirements will evolve: mobile apps, customer platforms and systems that grow after launch.
- Pricing and approval
- Priced per sprint or per phase, agreed in writing, with priorities set by you.
V-Model Common for software Every build phase paired with a planned test phase.
- Requirements — acceptance tests
- System design — system tests
- Module design — integration tests
- Development — unit tests
Testing is planned alongside each phase of design, not left to the end. Each level of the build is verified against the matching level of requirements before handover.
- Best suited to
- Systems where accuracy is critical: billing, payments, financial records and anything audited.
- Pricing and approval
- One fixed price, with the test plan agreed as part of the scope.
Iterative Waterfall Common for software Waterfall with a review and correction point at every phase.
- Requirements
- Design
- Development
- Testing
- Launch
The same sequence as waterfall, but each phase ends with a formal review. Anything the review finds is corrected in that phase, or fed back to the previous one, before work moves on.
- Best suited to
- Defined projects where early approval matters — for example, a website whose design is signed off before development starts.
- Pricing and approval
- One fixed price. Corrections found at a review within the agreed scope are included.
Waterfall Sequential phases, one fixed scope and price.
- Requirements
- Design
- Development
- Testing
- Launch
Each phase is completed and approved before the next begins. The full scope is agreed at the start, so cost and timeline are known in advance.
- Best suited to
- Projects with clear, stable requirements: most business websites, landing pages and well-defined systems.
- Pricing and approval
- One fixed price for the whole scope, approved in the proposal.
Prototyping See and test a working prototype before development begins.
- Requirements
- Prototype
- Your feedback
- Refinement
- Development
A clickable prototype of the key screens is built first. You and your users test it, and it is refined until it is right. Only then does full development begin.
- Best suited to
- New products and unclear requirements — especially apps and customer-facing systems, where seeing the flow changes the brief.
- Pricing and approval
- The prototype is priced on its own. Development is priced once the prototype is approved.
Kanban A continuous flow of improvements after launch.
- Request
- Prioritised
- In progress
- Review
- Done
Requests are placed on a shared board, prioritised with you and worked through continuously, with a limit on work in progress so each item is finished properly.
- Best suited to
- Ongoing improvements, maintenance and support once a website, system or app is live.
- Pricing and approval
- Covered by a monthly care plan or an agreed monthly scope.
Not sure which applies to your project? That is what the consultation is for — the proposal states the model we recommend and why.
Hosting and operations
A system has to keep working long after launch day.
- Hosting set up and registered in your name
- Automatic backups
- A separate test version, so changes are tried before your team sees them
- Updates and security patches
- Monitoring, so we hear about a problem before your staff do
Engagement and pricing
Every system is different, so each engagement is priced individually. After the consultation you receive a written proposal with the scope, a fixed price and the timeline. Once approved, the price changes only if the scope does.
What determines the price
- Modules and features
- Number of users
- Integrations
- Complexity of reports and workflows
Software questions
How much does custom software cost in Nepal?
It depends on what the system has to do, so each one is priced individually in a written proposal after a consultation. The price is set by the number of modules, the number of users, the integrations it needs and how complex the reports and workflows are. You get a fixed price in writing before anything starts.
How long does custom software take?
Most projects take 6 to 12 weeks, built in stages so you see and use each part as it is finished. The written scope gives the timeline for your project before anything starts.
Will I own the software?
Yes. The software, its data and the accounts it runs on are registered in your name. You are never locked in to us to keep using it.
Can it replace my Excel files?
Yes, that is the most common reason people come to us. One round of migration from your existing Excel files or records is included, so you start with your real data rather than an empty system.
Can it connect to eSewa, Khalti and the tools we already use?
Yes. We connect it to eSewa, Khalti, Fonepay, SMS, WhatsApp, email, Excel and Google Sheets, and to other services through their APIs. Every connection is tested end to end before launch.
Can you fix or take over an existing system?
Often, yes. We review the code and the data first, then tell you honestly whether it is worth fixing or cheaper to rebuild, with a written price for either.
Is our data safe?
Each person sees only what their role allows, every connection is encrypted, backups run automatically, and the data is stored on hosting registered in your name.
Which software development model do you use?
We do not force every project into one model. Business software is usually delivered incrementally, so you use the first module while the next is built. Evolving products use agile sprints, and systems where accuracy is critical, such as billing and payments, follow the V-model with testing planned for every phase. The proposal names the model and explains why.
Do you support it after launch?
Yes. 60 days of support are included after launch. After that you can move to a monthly care plan, or call us when you need something.
Discuss your system with our team
Tell us which files, registers and message threads your team works from today. We will outline what a system would replace, and follow with a written proposal.