Choosing who writes your software
Eight questions to ask before you pay a deposit
Finding someone to write your software is easy now. Knowing who you are handing money to is the hard part. This page is the eight questions we think you should ask, and our own answer to each one — in things you can open and check, not promises.
This is not a recruitment page. We do not do staff augmentation and we do not join your team. It is for someone commissioning one fixed-scope system who needs to know who they are signing with.
The eight questions
Not one of these requires you to take anyone's word. Each is a lookup you can do with public tools in a few minutes, and most of the bad outcomes are blocked right here.
01
Does this person actually exist?
Name, address, phone. It sounds obvious, but it filters the most, and it takes ten seconds: look the name up on the national tax portal, then send a Zalo message and see whether a human answers.
02
Can this person invoice us and sign a contract?
This is the most practical question on the list and the one most often skipped. A registered household business has a tax code and can sign a contract — which matters when your own accountant has to justify the spend.
03
Can we turn up at the address?
An address that is only a screenshot proves nothing. A real address gives you a way to check — and it filters out the cases where there is nothing behind them.
04
Can we read this person's code?
A normal project portfolio gives you exactly one thing: ask for a reference. A public source account gives you more — you read how they write tests, whether they package carefully, before you hand over any money.
05
Has this person done this kind of work before?
This is the one of the eight we answer worst, and saying so plainly beats hiding it: We have not handed over a project to a client. What we have is eight years of software development, an MSc in Computer Science, and public repositories.
06
Can we see how this person works?
Ask once, and watch how the questions are framed and whether the answer to something they do not know is “we do not know, let us check”. Someone who answers that honestly is more trustworthy than someone who answers everything identically.
07
Where does our money go, and against which milestones?
This has to be in the contract before you sign, not after. If someone wants everything up front, you have nothing to hold them to — and “where has our money gone” is a question you cannot ask once it has gone.
08
Is the communication itself odd in any way?
Telegram only, no call, no contract, no address you could visit — all four at once is reason enough to stop. Not because any one of them is proof of fraud, but because all four together usually means the explanation is somewhere else.
The last two are not about skill. They are about how you lose money — and in twenty jobs that fail, losing money is how the software fails. Swapping the order of those two is fine. Dropping them is not.
My answer, one question at a time
The same eight questions, in the same order. We are not marking our own homework — you open the links and check. Where we have nothing, it says “nothing”, not a promise.
- 01Does this person actually exist?
- Nguyen Minh Tam, a registered household business in Vinh Long. We are in this city, we answer this phone number, and a Zalo message gets a human reply — usually during working hours.
- 02Can this person invoice us and sign a contract?
- Yes, and I am precise about which part is not there. We are registered as a household business, we sign a contract carrying the name NGUYEN MINH TAM matching our registration, and we issue an invoice for each payment stage. But no VAT is calculated on that invoice, because software products and software services are a không chịu thuế object — so your accountant cannot deduct input VAT from this spend. If your company needs a creditable invoice to justify the cost, this is not that kind of invoice, and I would rather tell you now than have you find out later.
- 03Can we turn up at the address?
- Yes — we are in Vinh Long, same timezone as Can Tho and Ho Chi Minh City. But we do this work online: an in-person meeting can be arranged, but it needs notice and carries an extra cost, so we do not treat it as the normal way to work.
- 04Can we read this person's code?
- Yes, and it is the only evidence we can offer without asking anyone's permission. My account is entirely public: open `viact` for a system that actually runs, `OptimizedGASDemo` for the C++ side.Open github.com/ngmitam →
- 05Has this person done this kind of work before?
- Not yet — no project has been handed to a client. We have no client names to put here and we will not invent them. Everything we use day to day (TypeScript, NestJS, React, Next.js, MySQL, TypeORM, Docker, Jest, Cypress) is in the public repositories, visible immediately.See the repositories →
- 06Can we see how this person works?
- Yes, and it is free. The first conversation carries no consulting fee, and it ends in a priced scope document — including when the conclusion is “we are not the right fit”.
- 07Where does our money go, and against which milestones?
- 30 / 40 / 30: deposit at signature, second tranche when the first working build is live on your infrastructure, third on handover of source. Anything outside the scope is quoted separately and waits for your written agreement before we start.
- 08Is the communication itself odd in any way?
- Nothing odd about it: a real phone number, a real Zalo account, a contract with a name on it, and a real address in Vinh Long. We work online, but we do not agree to work through a channel where we cannot check who we are dealing with.
What we do not take on
These four are refusals, written down so you do not spend a month finding out. They are here because they are what people look for when they need software written — and we would rather say no early than say no late.
IT staff augmentation
No. We do not supply people by the month and we do not staff a team of our own inside your project. If you want someone sitting inside your existing team, that is a different model and we are not able to deliver it.
Projects needing three or more people
No. We run one large build at a time — that is the real limit of one person, and it is the basis of every price on this site. From three upward a larger company does it better than we do — and for less than you are probably assuming.
Security, ISO 27001, SOC 2
No. That is a certification-and-team business, not a one-person business. If your supplier-selection process makes that line mandatory, we are the wrong supplier and we will point you at the right people.
24/7 cover
No. We do not sell a one-hour response commitment for a system with one maintainer. What we sell is a system that runs and one person who replies within one business day, and we are telling you plainly that this is the whole of what one person can promise.
If you clear those eight
This part is what you would actually be buying. It is short, because it is the entire working model.
01
One conversation
You describe the systems you are running and where they fail to meet, plus the outcome you need. We ask questions; we do not send a generic quote. Reply within one business day.
02
Scope and price in writing
No scope document, no start. That document says what is in, what is out, and a fixed price for exactly that list.
03
Three payments at 30 / 40 / 30
Deposit on signature. Second tranche when you see a working build on your own infrastructure. Third on handover of source and documentation. The money follows something running, not a date on a calendar.
04
The source is yours from the start
That right is effective when the project begins, not at handover. We do not hold your source code to collect the last payment.
05
A defect warranty of 30 days for short work, 90 for multi-week builds
Bugs inside the delivered scope are fixed free. The software package runs 6–10 weeks and carries 90 days, because a 30-day window on a build that long is not proportionate. A code audit or an AI assessment hands over a report, not a running system — there is no warranty clock on a report, only our obligation to correct it if it is wrong. Third-party services — hosting, SMS, e-invoicing — you contract with them directly; we do not sit in the middle.
My evidence
A testimonial needs somebody else's permission. A repository does not — you open it and there is real code, real tests and a real Dockerfile. These are the ones worth opening in our account.
- viact2023
A full-stack system that actually runs: a NestJS REST API with JWT and Swagger, a React interface, MySQL with TypeORM migrations, Jest and Cypress tests, running under Docker. This is the one to open if you need an internal system.
- OptimizedGASDemo2025
A Gameplay Ability System written in C++ for Unreal Engine 5, focused on performance and module structure.
Common questions
- What deposit should we pay?
- 30% on signature, 40% when the first working build is live on your infrastructure, 30% on handover of source and documentation. If someone asks for 100% up front, that is your answer.
- What if we stop halfway?
- The source is yours from the beginning — you do not wait for handover. One commit at a milestone gives you a running version. Being honest, though: most abandoned projects are scope that was never fixed at the start, which is exactly why the scope document exists before we write the first line.
- Do we need to know how to code to work with you?
- No. You need to know that the job you want is not the job you are doing now. The rest is mine. What we need from you is a description of the current process and the outcome you want — in your own words, the way you would explain it in a meeting.
- Do you work with overseas clients?
- Yes, with two conditions. Timezone: APAC and Europe work, the US does not — one person cannot survive that. And we read and write English better than we speak it, so before accepting we need to see the English part of what you send, to know whether we can actually talk.
- Are you a company?
- No. The signing party is a household business — a hộ kinh doanh, registered under the name HỘ KINH DOANH MINH TÂM. That is a real legal form in Vietnam: it has a tax code and it can sign a contract. It is not a company, and we do not pretend to be one. What it does not issue is a VAT invoice — software products and software services are a không chịu thuế object, so no VAT is calculated and your accountant cannot deduct input VAT from this spend. If your process needs a corporate entity, or a VAT invoice to deduct, we are not the right supplier — and I would rather say so now.
Send us a description of the work and you will get a written scope and price back. If we are not a fit, we will say so in the first line rather than leave you waiting.