Skip to content

Software service

Custom software and management systems

Management systems built around how your business already works — back office, roles, reporting. Tell us the process you want to fix.

The system behind the website: back office, roles, records and reporting.

Off-the-shelf software is the right answer more often than agencies admit. Custom development earns its cost when your process is genuinely different from the template — when the way you work is part of your advantage, or when no product on the market covers it.

That is the kind of work we take on: a back office for a broking firm with client records, role-based access and a margin system; a content system a property team updates daily.

We start by mapping what happens today, including the parts that run on paper and WhatsApp. The build follows that map, so the software fits the business rather than forcing it to change shape.

Most of the IT companies in Nepal that take this work on will quote from a document you supply. We would rather write that document with you, because the gap between what a business says its process is and what staff actually do is where these projects fail. The process map is a deliverable in its own right, and more than one client has found the mapping exercise worth the fee on its own.

We build in phases, and the first phase is chosen to be useful by itself — ideally your team is working in the system within weeks, on the part that hurts most, while the rest is still being built. It also creates an honest decision point: if the first phase shows the plan was wrong, you find that out early and cheaply.

What’s included

  • A written map of the current process before any code
  • Role-based access, so each desk sees only what it should
  • Reporting built around the numbers you actually check
  • Integration with the tools and payment gateways you already use
  • Staff training and written handover
  • A support agreement for changes after launch

How the work runs

  1. Process mappingWe write down what happens today, including the parts that run on paper and WhatsApp.
  2. SpecificationThat map becomes a scope with roles, screens and reports, agreed before any code.
  3. Build in phasesThe most valuable part ships first, so you are using it while the rest is built.
  4. Training and handoverStaff training, written documentation, then a support agreement for changes.

What you get

  • A written map of the current and intended process
  • The system, with role-based access
  • Reporting built around the numbers you check
  • Staff training and written documentation
  • Source code and database in your own accounts

Questions

Should I buy software instead of building it?
Often yes, and we will tell you when. Accounting, payroll and standard inventory are well covered by existing products. Custom earns its cost when your process is genuinely different.
How do you price a system this size?
After the process mapping, not before. A fixed quote for an unmapped process is a guess that someone pays for later.
Can it connect to what we already use?
Usually. Payment gateways, delivery partners and accounting systems are the common ones; anything with an API can be connected.
What happens if our process changes?
That is expected, which is why we build in phases and keep a support agreement for changes rather than treating launch as the end.
Do you work with businesses outside Kathmandu?
Yes. Process mapping is better done in person where that is possible, but the build, the reviews and the training all work remotely, and we have clients operating outside the valley.
What if we already have software that half works?
Then the question is whether to extend it or replace it, and that depends on whether the data and the code can be read. We look before recommending either — a rebuild sold without that look is just the easier sale.

Our work in this area

Related reading

const app = build("your idea");

// tailored to your workflow

app.ship(); ✓

Typical timeline
3–6 months
Starts with
A process map
Includes
Training and handover
Discuss this project