How we run a software project, step by step
From the first conversation to operating the product after launch: the five stages of every vnLOOP project and what you can expect in each one.
Choosing a software partner is a matter of trust, and trust starts with knowing what will happen. This post describes how we run a project, from the first conversation to the months after launch. It is the same process we use for our own products.
1. Discovery
Every project begins with understanding the business, not the technology. In a few conversations we clarify what you want to achieve, who the users are, which systems already exist, and what constraints apply: budget, deadlines, regulations.
The result is a short written document: goals, scope, main user flows, technical approach, risks and an estimate. We prefer a clear document of a few pages to a long specification nobody reads. If something is uncertain, we say so and propose how to find out.
Discovery is also the moment to decide what not to build. A smaller first release, launched sooner, is usually the better business decision.
2. Design
Next we design how the product will work and look. We start with simple flows and wireframes, then move to visual design for the key screens. You review and comment at each step, so there are no surprises later.
We design for real conditions: mobile screens in sunlight, slow connections, users who are busy and in a hurry. For apps that need it, we also design tablet layouts and an admin interface for your team.
On the technical side, we define the data model, the API and the integrations. Getting these foundations right is what allows a product to grow without a rewrite.
3. Build in short iterations
We build in iterations of one to two weeks. Each iteration has a clear goal and ends with a working build you can try: an app on your phone, a page on a test server. You see progress continuously instead of waiting months for a big reveal.
Some practices we follow in every project:
- Automated tests for important logic, written alongside the code.
- Code review for every change.
- A shared task board, so you always know what is in progress.
- Regular short check-ins, in Vietnamese or English.
If priorities change, we adjust the plan at the start of the next iteration. Change is normal; the process is designed for it.
4. Launch
A launch involves more than code: app store submissions, domains, hosting, monitoring, privacy text, and training for your team. We prepare a launch checklist early and work through it together, so the release day is calm.
After release we watch the product closely during the first days, fixing issues quickly while users form their first impression.
5. Operate and improve
Software is never finished. After launch we can keep the product running for you: monitoring, security updates, backups, and keeping up with new iOS and Android versions. We also continue developing features based on real usage data and user feedback.
We take backward compatibility seriously. When your mobile app is in users' hands, changes to the server must keep older versions working, because not everyone updates immediately.
How we communicate
Good communication prevents most project problems. You have one main contact who knows your project well. We report progress in plain language, raise risks as soon as we see them, and never hide bad news. Decisions are written down, so everyone can find them later.
What we expect from you
A good project is a partnership. We ask for a decision maker who can answer questions within a reasonable time, access to the people who will use the product, and honest feedback on each build. In return, we commit to transparency about progress, costs and trade-offs.
Getting started
The first step is a conversation. Tell us what you want to build and what matters most to your business, and we will suggest how to approach it, even if the answer is that you need less software than you think.