Capture structured intake
The system captures scope, project type, legal constraints, and delivery goals in a standardized intake form so the estimate does not start with missing context.
LLA.UCP Estimator helps PMs, IT procurement teams, and advisors produce Use Case Point estimates aligned with QĐ 671/QĐ-BTTTT, with explicit traceability for assumptions, technical factors, environmental factors, and final cost.
This page is rebuilt around real software-cost estimation workflows: smart intake, actor/use-case classification, UCP baseline, assumption governance, draft comparison, and direct handoff into Jira/Confluence. The generic integration visual is removed.
LLA deploys UCP Estimator through a sequence: standardized intake, explainable UCP calculation, assumption governance, and dossier export for independent review. The goal is not a pretty number, but a defendable software-investment decision.
The system captures scope, project type, legal constraints, and delivery goals in a standardized intake form so the estimate does not start with missing context.
Actors, use cases, technical factors, and environmental factors are quantified under QĐ 671 with explanations that procurement and review committees can challenge and validate.
Each assumption has ownership, status, and revision history; estimation drafts are comparable so teams can see budget and timeline impact clearly.
After approval, scoped workloads and cost components are handed to Jira/Confluence so delivery teams execute against the same governed baseline.
Vietnamese IT companies that bid on government software projects face a specific, recurring problem: their cost estimates must comply with QĐ 671/QĐ-BTTTT (Ministry of Information and Communications regulation), but most estimation tools are generic. The team manually applies UCP complexity coefficients in Excel, documents assumptions in a separate file, allocates staff in another spreadsheet, and reconciles everything before submission. When a procurement auditor asks for cost justification three months later, reconstructing the evidence takes days — and the original Excel is already two versions out of date.
For Vietnamese government IT procurement, an estimate that cannot be traced to its UCP calculation, documented assumptions, and authorised approval is not just inconvenient — it is a compliance failure. Procurement regulations require evidence, not just numbers. For IT companies competing on both technical quality and commercial credibility, a robust, auditable estimation process is a competitive differentiator — and a protection against post-contract disputes.
The UCP methodology is not complicated. What makes it difficult is doing it consistently, documenting it completely, and maintaining the audit trail across project revisions, client negotiations, and regulatory reviews. LLA UCP Estimator encodes the methodology as a governed process — not a calculation shortcut. Every coefficient, every assumption, and every revision is recorded. The AI Intake module classifies functional requirements into UCP components, and the Atlassian integration delivers the approved estimate as Jira epics and Confluence specifications — closing the loop from costing to delivery.
Government agencies, public-sector technology departments, IT project managers, and software procurement teams in Vietnam that need compliant cost estimates for software projects following Thông tư 04 and QĐ 671.
Modular ASP.NET Core services, PostgreSQL-backed operational records, role-based access, API-first integrations, and audit-ready workflows.
Each capability is designed around a specific operational problem - not a generic feature checklist.
UCP calculation is done manually in Excel with individually maintained coefficient tables and no version control.
Automated UCP calculation with configurable complexity coefficients, adjustment factors, and cost conversion rates — all traceable to QĐ 671/QĐ-BTTTT.
Classifying functional requirements into UCP components is the most time-consuming step — done manually by a senior estimator.
AI Intake module reads natural language requirements and suggests UCP functional component classifications — accelerating the most labour-intensive step.
Assumptions underlying the estimate are documented informally in the proposal document — or not at all.
Every assumption is registered in the system with a rationale, risk level, and owner — before the estimate is submitted.
Moving from an approved cost estimate to project execution requires manual re-entry of requirements into Jira and Confluence.
Approved estimates generate Jira epics and Confluence specification documents automatically — eliminating re-entry and ensuring the delivery spec matches the priced scope.
Estimate revisions are managed in separate Excel files. Comparing versions requires manual side-by-side review.
Draft Compare shows side-by-side differences between estimate versions — including changes to assumptions, UCP components, and cost totals.
Configurable operating workflows with status tracking and approval visibility.
Permissions designed for admins, managers, operators, reviewers, and external users.
Connects to ERP, CRM, payment, invoice, shipping, warehouse, document, and AI systems.
Tracks important actions, status changes, and operational records for review and reporting.
These showcase panels are built from operating screens, workflows, demo data, and control evidence.
LLA does not begin with software configuration. LLA begins with operating model design.
Project requirements are captured using AI-assisted intake — natural language requirements are classified into UCP functional components automatically.
Use Case Points are calculated from the component classification with configurable complexity coefficients per QĐ 671/QĐ-BTTTT.
All assumptions underlying the estimate — complexity factors, technology adjustments, risk provisions — are registered in the system with rationale.
HR allocation and cost rates are applied to convert UCP to monetary cost, including commission and overhead structure.
Estimate is reviewed, compared against previous drafts, approved, and delivered as an Atlassian Spec Pack (Jira + Confluence).
Collect structured data, documents, roles, and required validation at the point work begins.
Move requests through role-based workflows, approvals, assignments, and exception handling.
Synchronize external services, files, payment, invoice, shipping, AI, or storage events through APIs.
Provide dashboards, audit trails, exports, and management views that reflect the real operating state.
Role-based permissions, audit logs, validation, secure file handling, approval workflows, and environment-based configuration.
Private cloud, VPS, Docker/Coolify, IIS, or hybrid deployment depending on the customer's security and infrastructure requirements.
This platform is designed to connect with the broader LLA ecosystem and third-party systems.
Approved estimates generate Jira epics and Confluence specifications for project execution.
Project cost records connected to the ERP operational and financial record.
External data connections for reference cost tables and regulatory coefficient updates.
Approved cost estimates issued as governed documents with e-signature capability.
Each phase includes clear delivery gates, ownership, and control checkpoints so operations teams can track progress week by week.
QĐ 671 coefficients configured, staff cost rates loaded, project templates set up.
Delivery milestoneFirst real project estimated through the platform — AI intake, UCP calculation, assumption registry.
Delivery milestoneJira and Confluence connection established and tested with spec generation.
Delivery milestoneAll estimators trained. Historical projects migrated. Go-live for all new bids.
Delivery milestoneEach function gets specific, measurable outcomes - not vague benefits.
A software project cost estimation tool built to the Vietnamese government standard QĐ 671/QĐ-BTTTT, applying Use Case Points methodology for accurate, audit-ready project budgets.
LLA designs this platform around auditability, role-based access, API integration, operational dashboards, bilingual-ready content, and deployment models that can run in private cloud, Docker/Coolify, IIS, or hybrid enterprise infrastructure.
LLA UCP Estimator maintains a full audit log of all estimation activities: requirement classification, coefficient selection, assumption registration, version creation, approval decision, and delivery. Staff allocation and cost rates are role-controlled. All changes require named user authorisation. The audit log is exportable for government procurement review and post-contract audit.
LLA UCP Estimator is built specifically for QĐ 671/QĐ-BTTTT — not adapted from a generic estimation tool.
LLA's AI Intake module classifies functional requirements into UCP components — accelerating the most labour-intensive estimation step.
LLA's Atlassian integration closes the loop from approved cost estimate to Jira epics and Confluence specifications.
LLA maintains a complete audit trail of every estimation decision — satisfying Vietnamese government procurement accountability requirements.
LLA has directly implemented government IT projects and understands the procurement accountability standard from the inside.
Yes. LLA uses the product foundation as a starting point, then adapts workflows, data fields, roles, integrations, and reports to the customer's operating model.
Yes. LLA supports private deployment using Docker/Coolify, IIS, PostgreSQL, object storage, and customer-controlled infrastructure when needed.
The architecture supports English and Vietnamese content, including translated entity slugs for public detail pages.
LLA can adapt this platform to your workflows, integrations, compliance model, and deployment environment.
Book a Consultation →