Web systems
Portals, browser-based management systems, service sites with sign-in and payments.
- Responsive UI, light/dark, WCAG 2.2 AA accessibility
- API, database, role-based access
- Technical SEO and load speed as hard requirements
Start a project
Your idea. The next product.
No documents or solution needed yet. The request lets the studio assess fit before the first conversation — and say so plainly if it isn’t a match.
Send the request
Get a request code on screen.
Fit assessment
A “go” or “no”, with reasons.
Discovery call
30–45 minutes on context, users, goals.
Proposal
Scope, milestones, risks, cost.
Services
Four kinds of product, one process
Every kind of product goes through the same 21 stages; what differs is which stages carry more weight.
Mobile apps
iOS apps sharing one API with the web system; beta via TestFlight before store release.
- Platform-guideline design, offline handling
- Privacy policy and store listing
- Testing on real devices
Internal tools & automation
Replace spreadsheets and manual steps with a system that fits how the business really works.
- Business analysis, as-is and to-be process maps
- Excel import/export, reports, audit logs
- Legacy data migration and user training
AI integration
Assistants answering from internal documents, text classification and extraction, LLM-driven automation.
- An evaluation set of real questions before picking a model
- Daily and per-user cost ceilings
- Prompt-injection defence, personal-data filtering
Sample projects
9 concrete product packages
Pick the package closest to your need so the first conversation starts from a clear scope. Timeframes are rough estimates for one lead engineer, confirmed after discovery; cost is quoted in the proposal. Demos only point to products actually running on this site.
Showing package: Company website & landing page
Selected package
Company website & landing page
Who it’s for
Small businesses, studios, clinics and service offices that need a credible web presence.
Problem it solves
Customers can’t find you on Google, or find an old, slow page that breaks on phones.
Standard scope
- Up to ~6 pages: home, services, about, contact…
- Responsive, light/dark, WCAG 2.2 AA
- Technical SEO: sitemap, meta tags, social share images
- Contact form delivered to email
Optional extras
- Vietnamese – English
- Admin area to edit content and post news
- Blog / news
Technology
- Next.js
- TypeScript
- Tailwind CSS
Timeframe
2–4 weeks
A rough estimate for one lead engineer, confirmed after discovery. Cost is quoted in the proposal.
Deliverables
- Source code in a Git repository you own
- Operations runbook and user guide
- Domain and hosting in your name
Evidence / live demo
- This Studio site itself/about/studio
Engagement models
Choose the way of working that fits
Pricing is quoted in the proposal after discovery. No prices are listed here.
| Model | How it works | Fits when | Trade-off |
|---|---|---|---|
| Fixed scope | Scope, timeline and cost agreed per milestone in the contract. | Clear requirements, few changes, fixed budget needed. | Changes go through change requests. |
| Time & materials | Billed by actual time, with a transparent work log. | Small tasks, consulting, fixes, requirements still emerging. | Flexible, but the total is harder to predict. |
| Per sprint | Each 1–2 week sprint is a unit: pick work together at the start, demo at the end. | Evolving products where priorities follow feedback. | Needs regular client involvement every sprint. |
| Maintenance retainer | After warranty: monitoring, updates, security patches and support hours each month. | Live products that need someone watching them. | Support scope is defined by the SLA. |
Fixed scope
Scope, timeline and cost agreed per milestone in the contract.
- Fits when
- Clear requirements, few changes, fixed budget needed.
- Trade-off
- Changes go through change requests.
Time & materials
Billed by actual time, with a transparent work log.
- Fits when
- Small tasks, consulting, fixes, requirements still emerging.
- Trade-off
- Flexible, but the total is harder to predict.
Per sprint
Each 1–2 week sprint is a unit: pick work together at the start, demo at the end.
- Fits when
- Evolving products where priorities follow feedback.
- Trade-off
- Needs regular client involvement every sprint.
Maintenance retainer
After warranty: monitoring, updates, security patches and support hours each month.
- Fits when
- Live products that need someone watching them.
- Trade-off
- Support scope is defined by the SLA.
Deliverables
What you receive
Each document below belongs to a specific stage and has a template you can preview on that stage’s page. Browse by stage
Documents
- Requirements specification (SRS) and acceptance criteria
- Design documents: architecture, data, API
- Test plan and test report
- User guide and operations runbook
Code & ownership
- All source code in a Git repository you own, with full history
- Domains, cloud accounts and third-party services in your name
- A list of third-party libraries and their licences
Handover
- User acceptance testing against agreed scenarios, with sign-off
- Training for users and administrators
- Handover record of access rights and assets
After handover
- Defect warranty for the period set in the contract
- Optional maintenance with a service-level agreement (SLA)
FAQ
Common questions
How much does a project cost?
Cost is quoted in the proposal after the discovery call — once the scope is clear enough to estimate responsibly. No prices are listed because two projects of the same “type” can differ several times over in effort.
Can we sign an NDA before sharing details?
Yes. Send your company’s NDA and both sides sign it before the detailed discussion. In the request form, a general description of the problem is enough.
Who owns the source code?
It’s yours once the contract is paid in full, as set out in the IP clause. Third-party open-source libraries keep their original licences and are listed in full.
Who actually does the work?
Cường is the lead engineer and accountable for everything. If a project needs more people for a specific role, the proposal names each person, role and scope before signing.
Can you work with our existing systems?
Yes. Integrations (ERP, accounting, SSO, data stores…) are analysed during business analysis and written up as separate requirements, with any risks.
How is our data protected during the project?
Real data is used only when needed and as agreed; development uses synthetic data. Systems handling personal data are designed for the Law on Personal Data Protection No. 91/2025/QH15 and Decree 356/2025/ND-CP, and security verification against OWASP ASVS is a stage of its own in the process.
Request form
Send a project request
About 5–10 minutes. You get a request code as soon as you send; use it in later conversations or to view, correct or delete what you sent.