Squads commit to sprint goals based on historical throughput — not optimistic guesses. Velocity is tracked per team and adjusted when scope or staffing changes, so timelines stay defensible.
The People
The Team Behind Every Delivery
Engineers, PMs, and specialists in Cần Thơ — one standard, named owners, and demos that show real progress on clinic, queue, education, and logistics systems.
Cần Thơ Talent, One Standard
LTU Soft is a Cần Thơ–based technology company building practical management software for clinics, hospitals, schools, and trading businesses across the Mekong Delta — not a rotating contractor bench.
Founded on 31 December 2021 by Đặng Thị Hồng Cúc (tax ID 1801715611), we keep delivery close to the floor: discovery at client sites, squads with named owners, and go-live support from Phong Điền. Our depth spans clinic HIS, outpatient queues, education ops, and distribution — so teams reuse playbooks instead of starting from zero every project.
- Named account owners on every project
- Cần Thơ squads with shared code review standards
- On-site discovery and go-live for clinic partners
- Clear escalation paths — no anonymous ticket queues
Practice Groups, Real Depth
Open any key on the roster — width reflects how deep each bench runs.
20 specialists · 01 → 06 squad roster
Tap a squad to read details, or swipe sideways to browse
What Our Squads Deliver Reliably
Measurable strengths backed by process — tap any card for details.
Every project inherits baseline security templates: env vaults, least-privilege IAM, dependency scanning, and OWASP-aware API patterns. Security findings block release until resolved or explicitly accepted by the client.
Engineers specialize but cross-train — a backend lead can review frontend PRs, and designers understand component constraints. Guild sessions share patterns for caching, auth, and real-time features.
We maintain shared UI primitives so new screens ship faster and stay visually consistent. Design debt is tracked like technical debt — refactored in dedicated sprint capacity.
Lighthouse budgets are set during discovery. Marketing and engineering pair on schema markup, sitemap strategy, and image optimization — not handed off after launch.
Infrastructure is codified, environments are reproducible, and rollbacks are tested. On-call rotation covers managed clients with defined SLAs and incident communication templates.
How We Work Together
Four principles in sequence — expand any band to see how it shapes daily delivery.
01 → 04 culture stack
Clients know who owns architecture, who owns QA sign-off, and who joins weekly calls. When someone is out, a documented backup steps in — continuity is planned, not improvised.
Engineers are expected to push back on unclear requirements. PMs simplify scope instead of padding estimates. Leadership joins demos when stakes are high — transparency is cultural, not procedural.
LTU-SOFT selectively accepts work. Squads stay focused — fewer context switches, deeper product knowledge, and codebases that remain maintainable years after launch.
Your primary contact sits in the Mekong Delta. Engineers visit clinics, hospitals, and warehouses for discovery and go-live. You never wonder who owns the relationship or who writes the code.
Moments From Behind the Scenes
Scroll the feed — tap any pin to open the full chapter.
6 / 12 moments
Ready to meet the team behind your build?
Tell us about your product goals. We'll propose a team shape — roles, seniority mix, and engagement model — within one business day.

