Project
A defined piece of work with an agreed price and delivery date. Best when you know what you need built. We quote after a scoping call, not before.
Home/Services
Four practices, one team. Below is what each actually involves, including the parts that usually get left out of a proposal.
01 — Web & app development
Most of our work is here. Company sites, booking and enquiry systems, customer portals, admin dashboards, school and clinic management tools, and Android apps for teams working in the field.
We build for the connection people actually have. That means the first screen is usable on a 3G phone, images are sized properly, and the site does not need eight megabytes of JavaScript to show a phone number. This is a design constraint from the start, not an optimisation pass at the end.
Where payment is involved we integrate eSewa, Khalti, ConnectIPS or card gateways depending on who your customers are and what your bank supports.
02 — AI & automation
We will be straight about this one: most requests that arrive as "we want AI" are solved better by a form, a database and a scheduled job. We check that first, because it is cheaper for you and it does not break in strange ways.
When a language model genuinely is the right tool, we use it for what it is good at: reading unstructured documents, answering questions over your own material, drafting, classifying and summarising. We keep a human approval step wherever the output touches money, records or customers.
Everything is built so you can see what it did and why. Automation you cannot audit is a liability, not an asset.
03 — Cloud & DevOps
We host on edge platforms and major cloud providers depending on the workload. For most sites in Nepal, serving from a global edge network is both faster and cheaper than a single VPS, because the content is cached close to the person loading it.
Accounts are created in your organisation's name and your billing, not ours. We have seen too many businesses discover their domain and hosting belong to a developer who stopped replying. Your infrastructure should be yours on day one.
Ongoing support is a written arrangement with a response time in it, not a vague promise to be around.
04 — Design & branding
A logo is the easy part. The hard part is a system that still works when it is 18 pixels wide in a browser tab, embossed on a letterhead, or sitting next to Devanagari text at a different optical size.
So we deliver systems, not single files: vector masters, every icon size you will actually be asked for, colour and type rules, and a written guide so the next person to touch your brand does not have to guess.
On the interface side we work in design systems rather than page mockups, which is what keeps screen twenty consistent with screen one.
Working together
A defined piece of work with an agreed price and delivery date. Best when you know what you need built. We quote after a scoping call, not before.
A set number of days each month for continuing development, changes and support. Suits organisations with a product that keeps evolving.
A few days to review an existing system, an architecture, a vendor proposal or a security posture, and write up what we find. No obligation to build anything with us afterwards.
Pricing depends on scope and is quoted in NPR after we understand the work. We do not publish package prices, because the honest answer to "how much for a website" is always "what does it need to do".
Book a scoping call