Business context
Vietnam's Ministry of Construction has identified 29 priority expressway projects for public-private investment during 2026–2030. The proposed portfolio covers about 2,829 kilometres of new routes plus 1,187 kilometres to be expanded or completed, with an estimated total capital need of VND 1.269 quadrillion. Around VND 846 trillion still has to be mobilised beyond budgeted and committed funds. For suppliers, contractors and technical service companies, this creates a visible opportunity landscape—but not a simple list of accounts ready to buy.
An infrastructure programme becomes commercial demand only through a chain of decisions. Project mandate, traffic and revenue assumptions, state participation, land clearance, material access, financing, design authority, procurement method, construction readiness and operating responsibility all shape whether a requirement becomes an order. A large published pipeline can therefore coexist with slow, uneven or redirected demand.
Core management problem
Traditional key-account plans are often organised around one customer, one relationship owner and one annual revenue target. A major infrastructure project behaves differently. The party defining the technical requirement may not fund it; the party procuring a package may not operate the asset; and the organisation with final acceptance authority may enter the process late. Influence moves as the project passes from policy to bankability, design, tender, delivery and operation.
The management problem is not merely identifying stakeholders. It is maintaining a current view of who owns each decision, what evidence that decision requires, how one gate changes the next, and which commercial commitments are justified now. Without that discipline, teams confuse access with authority, specifications with demand and a tender notice with an executable opportunity.
Common mistakes
The first mistake is assigning the whole opportunity to the organisation with the most visible name. The second is building relationships only with procurement while design consultants, lenders, project sponsors and operators shape the commercial conditions. The third is forecasting the full project value even when the company's addressable package, approved specification and delivery window remain unknown.
Another mistake is treating every stakeholder meeting as progress. A meeting matters only when it clarifies a decision, evidence requirement, dependency or next commitment. Teams also over-invest in product promotion before confirming bankability and design authority, or wait for a tender before testing qualification, local service, capacity and partner readiness. Both approaches create expensive timing errors.
Practical framework: the infrastructure decision network
Build one decision network for each priority project or repeatable project family. Map six nodes. The mandate node confirms the sponsoring authority, project scope, public support and decision timetable. The bankability node records the revenue basis, financing structure, risk allocation and conditions precedent. The design-authority node identifies who controls specifications, approved alternatives and technical evidence.
The procurement node defines package boundaries, bidder eligibility, evaluation method and contracting route. The delivery-readiness node tests local partners, manufacturing capacity, material availability, logistics, installation, commissioning and working-capital exposure. The operating-acceptance node identifies the party that will accept performance, maintain the asset and judge lifecycle value.
For every node, record five controls: decision owner, influence map, required evidence, current status and next authorised commitment. Use evidence states rather than optimistic percentages: unverified, confirmed, qualified, approved or released. Link every commercial action—engineering support, sample, bid cost, capacity reservation or price validity—to a specific node and expiry date.
The network should also show transfer points. A design preference may fail procurement eligibility; a finance delay may invalidate price or capacity assumptions; a construction schedule may move before land or connecting infrastructure is ready. These are not separate account notes. They are dependencies that determine whether the opportunity can convert and be delivered responsibly.
Patrick Lee Business Lens
Growth asks which packages the company can legitimately win, repeat across projects and expand through credible performance. Manufacturing asks whether specifications, capacity, suppliers, quality evidence and local execution can support the promised schedule. Risk asks where financing, authority, land, materials, currency, partners or acceptance can create an exposure larger than the addressable return.
Growth × Manufacturing × Risk prevents the account team from celebrating pipeline size while the operating system absorbs unpriced obligations. A strong opportunity is not simply large. It has a visible path through the decision network, a defensible role for the company, an executable delivery model and controlled downside if a gate changes.
Management process
Run a monthly project-network review led by the key-account owner with commercial, engineering, operations, supply chain, finance and local leadership. Review changed authorities, evidence gained, expired assumptions, resource consumed and the next decision. Separate relationship health from opportunity readiness so senior access does not conceal unresolved technical or financial conditions.
Use four management decisions: advance, hold, redesign or exit. Advance only when the next gate and its evidence are clear. Hold when timing is external but the strategic position remains valid. Redesign when package scope, partner model or delivery architecture must change. Exit when the addressable value, authority path or risk-adjusted economics no longer justify pursuit.
Management implication
Vietnam's expressway programme illustrates a broader rule for complex B2B markets: a national pipeline is not a company pipeline, and a project stakeholder is not automatically a customer. Key-account management must connect policy, capital, technical authority, procurement and operating acceptance into one managed commercial system.
The purpose of the decision network is not to predict every institutional move. It is to ensure that each investment follows verified authority and evidence, that manufacturing commitments do not outrun bankable demand, and that risk owners are visible before the company commits price, capacity or reputation. That discipline converts infrastructure visibility into selective, executable growth.
