Frequently asked questions
Answers to the questions clients usually ask before working with us. If yours is not here, ask us directly.
Pricing and engagement
How do you price projects?
We offer fixed prices for clearly defined projects, and time-and-materials pricing for discovery or open-ended work. We will recommend the model that fits and explain why. Either way, you receive a written scope that also lists what is not included, which prevents more misunderstandings than any other part of a contract.
What is the minimum project size?
Around US$8,000 for a clearly defined project. For smaller needs, we usually recommend a short consulting engagement instead, because assembling a full team would not be cost-effective for either of us.
Can you work with our existing team?
Yes. About a third of our work is done alongside a client’s own team, using their code repositories, daily meetings and review process. We adapt to your standards rather than imposing ours.
Delivery
How long does a typical project take?
A focused first release usually takes 8 to 14 weeks. Replacing a whole platform, or building a system in a regulated industry, takes longer: typically five to nine months. We deliver in phases, so you get something useful early.
How will we know how the project is progressing?
You get a demo at the end of every two-week sprint, a shared project board you can check at any time, and a short written update each week covering what was completed, what was delayed and what changed. If a date is going to move, you will hear it from us first.
What happens if our requirements change during the project?
Requirements usually do change. Each change is described in a short written note covering its effect on scope, schedule and cost, and you decide whether to go ahead. We never absorb changes silently and then miss a deadline.
Ownership and handover
Do we own the code and the intellectual property?
Yes, completely, once the final payment is made. That includes the code repositories, infrastructure configuration, design files and documentation. There are no licence fees for anything we build for you, and you do not depend on us to keep it running.
What does handover include?
The source code, infrastructure as code, environment settings, a deployment guide, written records of architecture decisions and a live handover session with your team. If you wish, we can also run a period in which your engineers lead and we advise.
Security
How do you handle confidential information?
We are happy to sign your non-disclosure agreement before discovery begins. Your data stays in your own infrastructure wherever possible. Where we do hold it, access is limited to named engineers, protected by multi-factor authentication and recorded in audit logs.
Do you carry out security testing?
Yes. Every project includes dependency scanning and security-focused code review as standard. Formal penetration testing is available as a separate engagement where the level of risk calls for it, and we can also assess systems you already have.
Working with Nepal
How does the time difference work?
Kathmandu is UTC+5:45. We share the full working day with South Asia and the Gulf, and most of the morning with Europe. For clients in North America, our team shifts its working hours to share part of your day, rather than relying on handover notes.
How do payments and contracts work for international clients?
We invoice in US dollars, euros or pounds sterling, payable by bank transfer. Contracts can be governed by Nepali law or, as is common for international clients, by the law of your own country. We are used to both.
Still have questions?
A short call often answers more than a long email. We are happy to talk, with no sales pitch.