VAON is the technical partner for your new product: a 1 to 2 week fixed-price Spec Lock, then an MVP built in 1 to 2 week cycles, with working software for you to try at the end of each one.
After the Spec Lock you hold the requirements, wireframes and an MVP quote, and only then decide whether to go further.
1–2 weeks
Spec Lock, fixed price, free to stop afterwards
4 checks
Before a feature counts as done
60 min
First call with our CEO, no commitment
These are the four situations we run into most often when people come to us mid-product. Each one has an answer built into how we work.
You know what you want, but nobody has turned it into something developers can build from.
How we handle it
The Spec Lock Phase, led by a bridge engineer (the person who turns business needs into a spec) and a tech lead, ends with written requirements and a wireframe for every screen.
You're signing off on technical decisions without the background to judge them.
How we handle it
Our CTO and a Tech Lead are on every project and review the big technical decisions with you: architecture, scope, trade-offs.
Everything about the system lives in one freelancer's head. When they leave, nobody can read the code.
How we handle it
Knowledge lives in documentation kept in step with the code: design decision logs and meeting notes.
The MVP works, and then it sits there with nobody responsible for what comes next.
How we handle it
The roadmap already includes a Growth stage. You choose to continue with us or take over the handover.
01
1 to 2 weeks (2 to 4 for large projects), fixed price. Ends with requirements, wireframes, architecture and an MVP quote.
02
We build the agreed scope in 1 to 2 week cycles with a demo at the end of each. It ends with working software in production, not a demo.
03
Continue with a dedicated team, or take a handover. Documentation stays current throughout, so whoever takes over doesn't start from zero.
A separate package with a name, a scope and an end date. You commit to nothing for the build stage until the spec and a fixed quote are on your desk.
Booking this phase does not require you to hire us for the build.
AI drafts the plan, the Tech Lead approves it.
AI writes code with tests; it passes three reviews and security gates.
At the end of the cycle, you try working software.
Your feedback shapes the next cycle.
A feature is done only when:
A fixed quote for each stage: Spec Lock, then MVP. Best when you want to know the total cost upfront.
A stable team on your product, billed per person per month within an agreed budget cap. Best when the product keeps changing.
Part of the development fee is exchanged for a share of revenue. Available for some projects with a clear business model, decided case by case.
Ownership of source code and intellectual property is set out in the contract, and the code can live in your repository from day one. Revenue Share has its own terms on percentage, duration and ownership, all set out before signing.
Some clients haven't agreed to be named. For those projects, we still share the real numbers and simply leave out the name.
Kochi University of Technology
About 5 weeks from sorting out requirements to live use. Students get started in 4 steps, in about a minute.
Web services company, Japan
20–35%
Less manual effort
85–92%
Accuracy
A 60-minute first call with our CEO, no documents needed. You tell us the problem, we ask questions and tell you honestly whether we're the right fit. If we go ahead, the 1 to 2 week Spec Lock Phase turns that problem into a spec, wireframes and a fixed quote.
It's a fixed price that depends on the size of the product, so we quote it after the first call. The price doesn't change during the phase, and booking it doesn't commit you to building with us.
After the Spec Lock, the MVP is built in 1 to 2 week cycles. By the end of the first cycle you can already try the first part in a test environment. Time to release depends on the MVP scope you agreed.
Nothing you haven't approved. Work outside the scope comes with a written price and schedule impact; it starts only after you approve, and without approval there is no work and no charge.
You receive every document from the Spec Lock Phase and are free to stop after it. How you may use the documents, including with another team, is set out in the phase contract, and we walk you through that clause before you sign.
You review wireframes of every screen, not technical documents. During the build, you try working software at the end of each cycle. Big technical decisions are explained by their consequences: cost, time and risk.
Ownership of the source code and intellectual property is set out in the contract, and we explain it before you sign. The code can live in your repository from day one. Your data goes into AI tools only with your permission. When the project ends, VAON removes its access and hands over or deletes data as you request.
Not yet. Our information security rules are built on the ISO 27001 framework by a CEO who previously led a 120-person company to that certification. We are happy to walk you through the process and sign a confidentiality agreement on your template.
VAON engineers use Claude Code and GitHub Copilot every day, but no code is merged just because AI wrote it. The author re-reads it, AI reviews it, another engineer approves it and the team lead decides the merge. Review and test records are kept for every project, and you can see them.
Another question? Email us at sales@ai.vaon.com.vn
The first call needs no documents and no commitment. We listen to the problem and tell you honestly whether we're the right fit.
