Custom Software Development · Guide
Questions to Ask a Software Company Before Signing in Nepal
Before you sign with any software company, ask how they define scope, who owns the code and data, how they handle changes, who hosts the system and what happens after launch. Most failed projects are not caused by bad code. They come from unclear agreements, missing communication and no plan for the day after go-live. Use the questions below.
About the scope
- Will you write a requirements document before quoting?
- Is the quote fixed for that scope?
- What is explicitly excluded?
- How are changes requested, priced and approved?
- How will the work be split into phases?
About the people and process
- Who will actually build my system, and who is my contact?
- How often will you show progress, and on what test link?
- How do you test before delivering?
- What do you need from my team, and how fast?
About ownership and data
- Who owns the source code, and what licence do I get?
- Who owns the data, and can I export it at any time?
- Are third-party components used, and under what terms?
- What happens if we stop working together?
About hosting, security and support
- Who hosts the system, where and with what backups?
- How are passwords, roles and activity logs handled?
- How do you handle security updates?
- What support is included after launch and for how long?
- How fast do you reply to a fault, and through which channel?
- How do you quote new features after launch?
About proof
- Can I see a similar system working, and speak to someone who uses it?
Be wary of any company that gives vague answers, avoids writing things down or promises everything for a very low price. Honest firms are comfortable saying what they cannot do.
Eight common mistakes
1. Starting without a brief
If you do not write down what you want, you will argue later about what was promised. See our guide to writing a requirements brief.
2. Choosing on price alone
The cheapest quote often leaves out data import, training, hosting or testing. Compare what is included.
3. Trying to build everything in version one
A smaller first release is faster to finish and teaches you what you truly need.
4. Leaving staff out
The people who use the system every day must see the screens before they are final.
5. Ignoring data cleanup
Importing messy data into a clean system gives you a messy system. Tidy first.
6. No plan for hosting and backup
If the server fails and no backup exists, the project fails with it. Ask for a restore test.
7. Weak approvals on your side
Name one person who can say yes or no for your business. Without that, requests contradict each other.
8. Forgetting training
A good system used badly is a bad system. Schedule time for staff practice on real examples.
A short walkthrough
A distribution company with two warehouses tracks orders in Excel and loses track of dues. The owner writes a brief with roles, steps and reports, then asks two companies the questions above. The scope is split into three phases: orders and stock, dues and payments, then a dealer portal. After the first phase is live for a month, the team finds a missing report and adds it to phase two through the agreed change process. The project is not dramatic, which is exactly why it works.
How WebsNP works
We start with discovery, write the scope, quote a fixed price, deliver in phases and support the system after launch. We also tell you when a ready-made product such as document management software or helpdesk software is the better choice. Read the custom software development page for details.
How to run the vendor meeting
Send your brief ahead of the meeting so the conversation is about your project, not a sales presentation. Bring one person who understands the daily work and one who controls the budget. Ask the questions in order and write down the answers on the spot. After the meeting, send a short email summarising what you understood and ask the vendor to confirm it. This simple step turns spoken promises into written ones.
What a healthy first month looks like
- You receive a written scope and a phase plan within an agreed time.
- You see screens or a test link early, not only at the end.
- Your questions are answered in writing.
- Both sides stick to the agreed review dates.
- Any change is estimated before it is built.
If the first month feels chaotic, say so right away. Early correction is cheap, and late correction is not.
Your next step
Take this list into your next vendor meeting and note the answers. Then message WebsNP on WhatsApp on +977 9846280400 to start a discovery conversation.
Get a demo and quote for Custom Software Development
Tell us about your business and we will reply the same working day with a demo and a clear quote. No obligation.
Chat on WhatsAppOr call / WhatsApp +977 9846280400
More guides on Custom Software Development
Custom Software or Ready-Made Software? How to Choose in Nepal
Ready-made is right for most businesses. Here is how to tell whether yours is one of the exceptions that justify a custom build.
Read guide ›How to Write a Software Requirements Brief Developers Can Quote
Write one clear brief and every software company can quote the same thing, which makes proposals comparable and projects smoother.
Read guide ›Building Business Software for Nepal: Local Requirements
A checklist of the Nepal-specific details that decide whether a custom system fits daily work or fights it.
Read guide ›What Drives the Cost of Custom Software in Nepal?
Price depends on scope, not on a magic rate card. Learn what moves the cost and how to keep a project predictable.
Read guide ›