What we do
FAQ
Including the uncomfortable ones about price, ownership and what happens if you want to leave. If something is still unclear, ask us directly.
How a project starts and what the first weeks look like.
It starts with a call. We ask what you are trying to achieve, what exists today and what your deadline is driven by. If we are a fit, you get a written scope with phases, deliverables and a timeline. If we are not a fit, we say so and point you somewhere better.
Discovery and a reviewable start. We agree the scope and the success measure, set up the repository and a preview environment, and get something on screen you can click. You should never wait a month to see progress.
We are in Birtamode, Jhapa, and we work with clients across Nepal and abroad. Most collaboration is remote with scheduled calls. For clients in eastern Nepal we meet in person when it helps.
Yes, with one condition: we scope the smallest version worth launching rather than the full vision. The common way early products fail is building for eighteen months before meeting a user.
The people building your project. We are a small team, so there is no account manager relaying messages to an engineer you never meet.
What drives the price, and how we handle change.
It depends on scope, and anyone who quotes before understanding the scope is guessing. What we can promise is a written, itemised quote after one discovery call, so you can see what each part costs and remove anything you do not need.
Because a five page company site and a logged-in platform with payments and roles are different projects with the same word on the tin. A published price would be either useless or misleading. We give a firm number per project instead.
Fixed price for well-defined work, which is most first projects. A monthly retainer for ongoing development where priorities change month to month. We recommend whichever genuinely fits, and explain why.
Small changes are absorbed. Anything that moves the timeline or the cost gets a short written change note that you approve before we build it. No surprise invoices, and no quiet scope creep either.
Typically a deposit to start and the remainder against agreed milestones, so payment follows delivery. Terms are in the proposal before you commit.
What we build with, and what you own at the end.
Yes. The repository, domain, hosting and third-party accounts are in your name, and the code is yours on final payment. Nothing is held hostage and nothing is locked to us.
Mainly Next.js, React, TypeScript and Node.js on the web, React Native or Flutter on mobile, and PostgreSQL or MySQL for data. We choose boring, widely known tools on purpose, so you can hire for them.
Often, yes. We start with a short code and infrastructure review and tell you honestly whether it is better to continue or rebuild, including when continuing is cheaper and we would earn less.
Usually. We build static exports for shared cPanel hosting, and server-rendered or containerised deployments where that is available. We confirm what your hosting supports before the build, not after.
We use AI tooling where it genuinely speeds up development, and we review everything that ships. We also build AI features into client products where there is a real use case, and talk you out of it where there is not.
Support, maintenance and what happens next.
Thirty days of bug fixing on what we built is included with every project. Anything that does not match the agreed scope gets fixed at no cost in that window.
Yes, as a monthly retainer covering dependency and server patching, backup checks, uptime monitoring, small content changes and a short monthly report. Larger feature work is quoted separately.
Yes. Handover includes a walkthrough session and a recording, plus written documentation for the content and admin workflows. If your developers are taking over the code, we do a technical handover too.
We build so that is straightforward, and we are happy to keep working with you. You are also free to take the project elsewhere, which is why the handover documentation is written properly.
For clients on a maintenance retainer, response times are written into the agreement. For everyone else, urgent production issues get our attention the same working day.
Still unclear?
You will get a reply from someone who works on projects, not a template. If the answer is that we are the wrong fit, we will tell you that too.
One call, no obligation. You will get a straight answer on whether we are the right fit, what it would take and roughly how long.