Websites and catalogues
Business sites, institution sites and product catalogues that load quickly on local mobile connections and can be updated by your own staff.
iSoftro is based in Birgunj and works with businesses across Parsa, Bara, Kathmandu and beyond. Local enough to meet in person when a project needs it, set up to work remotely when it does not.
Most of our Birgunj work starts with a conversation about a process that has stopped scaling, not a request for a specific technology.
Business sites, institution sites and product catalogues that load quickly on local mobile connections and can be updated by your own staff.
Stock, orders, subscriptions, bookings and reporting for businesses that have outgrown spreadsheets and phone calls.
Face-to-face training for the people who will use the system daily, plus support when something needs to change after launch.
Remote-only delivery works until a workflow needs to be watched in the room where it happens.
Sitting with the accounts desk or the dispatch table tells us things a questionnaire never will: the exceptions, the shortcuts, and the step nobody documents.
Staff learn faster when someone is beside them for the first week. We can be there for handover, and again when new people join.
Meetings run in English, Nepali or Hindi depending on who is in the room, which matters most when the people using the system are not the people buying it.
Being in Birgunj does not limit the work. Projects with Kathmandu and international teams run on scheduled calls, shared documents and clearly written decisions.
Schools, suppliers and community organisations around Birgunj and Parsa.
Yes. A first meeting is for understanding the problem, not for signing anything. Bring the messy version: the spreadsheet, the register, the process nobody enjoys. If we are not the right fit, we will say so and point you elsewhere.
No. Birgunj is where we are based, and most of our long-running work is with organisations in Nepal and abroad. Local projects get more in-person time; remote projects get more structured written updates.
Projects are divided into milestones, each with a deliverable you can review. The schedule, currency and invoicing details are agreed in writing before work begins, and invoices are issued against completed milestones.
Often, yes. We review the codebase, hosting and documentation first, then tell you honestly whether continuing is cheaper than rebuilding. Taking over a system we did not write is normal work for us, as long as access and ownership are clear.
Send a message with the problem in one paragraph. We will suggest a time and the questions worth bringing.
Get in touch ↗