NGC2 | Part III, Winning in the New C2 Marketplace

NGC2 is giving companies more ways to participate in Army command and control—and more ways to lose relevance after an initial win. Capability Program Executive (CPE) C3N is organizing the effort around modular layers and Team Lead/Teammate arrangements rather than a single closed system with a prime-led hierarchy. That changes the work on both sides of an award. Before selection, a firm must decide where it belongs, what roles they can credibly play, who needs to see their capabilities.  After selection, the Army will keep testing whether soldiers use the capability, how it fits in the wider architecture, and if the supplier can scale on schedule.

For CEOs, business-unit leaders, and capture executives, three questions now matter: 

1.    Where can the company lead or contribute within the NGC2 ecosystem? 

2.    Who must the company engage and when does engagement begin? 

3.    How will it meet earn adoption, adapt during execution, and prove it can scale? 

A strong proposal still matters, but it will not rescue a product that does not integrate, a team that cannot make timely decisions, or a supplier that cannot meet the next level of demand.

Map the Portfolio and the Stack

NGC2 will not move through one program office or one production decision. The transport, infrastructure, data and AI, applications, enablers, and network-modernization lanes sit with different Program Managers (PMs). CPE C3N expects production awards to be staggered as the Army validates each part of the architecture, rather than through one broad down-select. A company that tracks only the contract vehicle will miss half the picture; each lane carries a different customer, acquisition path, technical standard, and route to scale.

A firm entering at the data or application layer should map both the Army’s acquisition structure and NGC2’s architectural layers. The acquisition map shows where funding, contracting authority, and program decisions sit. The architecture shows where the company creates value, which standards it must meet, and which providers it depends upon. Together, those maps help leaders decide whether to lead, supply a component, serve as an integrator, or stay out.

The Department’s emphasis on open systems and direct-to-supplier relationships creates several viable positions. An incumbent integrator may lead integration. A specialist vendor may build stronger positions by providing a focused capability that works across multiple teams. Expansion into another layer makes sense only when the firm brings a demonstrated technical, customer, or operating advantage.

The strongest position is a role that fits the broader system, is difficult to replace, and is supported by deliberate partnerships.

Engage and Shape Before Solicitation

Once a firm has chosen its role within NGC2, it must identify the people who determine whether that role gains traction. Operators will judge whether the capability improves the mission. PMs and CPEs remain industry’s main route into experimentation and acquisition decisions. Contracting, cybersecurity, and technical officials will test whether the solution can feasibly be bought, secured, and supported. PAEs consider how proven capabilities contribute to broader portfolio priorities.

Each audience requires different evidence. An operator wants to see the capability work in the unit’s workflow. A program team needs confidence that it will integrate and that there is a practical path to contract. Senior leaders need to understand why the capability matters across the portfolio. A strong relationship with one official helps, but it does not carry a product through the entire process.

NGC2 also creates more opportunities for engagement before the final solicitation. Its Characteristic of Need is a living document informed by dialogue among Army stakeholders and industry teams. At TEM 15, Army leaders encouraged companies to participate through draft documents, industry days, demonstrations, and other exchanges before RFP release. The Army Open Solicitation further demonstrates the potential pace, with one action moving from RFP to award in 16 days.

The broader Acquisition Transformation Strategy pushes in the same direction. It calls for operational gaps to be presented through consortia and solution marketplaces, where companies can model or prototype potential answers. These exchanges are useful when industry explains what can be done now, what requires further development, and which tradeoffs affect cost or schedule. They are less useful when a company arrives with a generic capabilities brief or tries to reshape the need around its own product.

This requires internal work before the meeting. Engineers need enough authority to answer detailed questions and make bounded technical trades. The company also needs usable positions on cybersecurity, integration, pricing, and data rights. Otherwise, “early engagement” becomes a listening session while faster competitors help define the opportunity.

Industry has always tried to shape requirements early. The Acquisition Transformation Strategy has given the Army the structure and the push to formalize those exchanges and use them to refine the requirement, acquisition path, and likely team structure before the final RFP. Firms that wait for the solicitation may find themselves responding to decisions that are already partly made.

Earn Adoption, then Prove Scale

NGC2 creates two gates to scale. The first is operational: does the warfighter use the capability? The second is institutional and commercial: can the company deliver, integrate, secure, price, and sustain it at scale? Firms must pass both.

Earning adoption requires more than placing a prototype in an exercise. Participation in an exercise proves that the Army was willing to evaluate the product; it does not prove adoption. Operators need to see value in their actual tasks, and the capability must integrate with adjacent systems and processes. Companies also have to fix the small points of friction—poor data exchange, extra steps, unreliable connectivity—that cause soldiers to set a tool aside even when its underlying technology is sound.

The Army’s June 2026 common data-baseline decision illustrates how operational evidence can shape acquisition action. Ten months of validation with the 4th Infantry Division and 25th Infantry Division helped move the data layer from competing prototypes toward a shared baseline. The lesson for industry is direct: repeated operational use can earn a capability continued investment, but only when firms respond to feedback and demonstrate value beyond a single event.  

A company can clear that first gate and still fail the second. Broader fielding brings questions that may not matter during an early prototype: Can the product be accredited? Can it be produced and supported in larger numbers? Does the pricing hold up? Who owns the integration work when another part of the architecture changes? A supplier without credible answers can lose momentum even when soldiers want the capability.

That is why preparation for scale has to begin while adoption is still uncertain. Accreditation, production planning, supply-chain capacity, data rights, pricing, and sustainment all take time to resolve. Waiting until demand becomes obvious may leave the company unable to respond when the Army is ready to move.

The Competitive Moat Is Adaptability

The Army’s new acquisition model will continue to change as standards, requirements, team structures, and commercial positions evolve. A firm may enter an experiment in one role, face new integration requirements after operator testing, and encounter a different teaming or commercial structure as the capability moves toward production. Companies that cannot adjust will struggle to preserve their position even after a successful initial selection.

Adaptability begins with decision authority. Engineers and product leaders need enough authority to address technical tradeoffs during customer engagement and operational testing. Capture teams need direct access to finance, legal, cybersecurity, and operations so the company can respond with firm positions while the Army is still shaping the acquisition approach.

Commercial positions will also change as the opportunity becomes clearer. Pricing designed for a small prototype may not work at larger quantities. A licensing approach that was reasonable for a stand-alone product may become a problem when the component enters a common architecture. Leadership may need to increase investment, stage it against specific evidence, or stop funding an opportunity that is moving away from the company’s strengths.

Teaming decisions require the same flexibility. A company may lead one effort, support another, and rely on a different partner elsewhere in the stack. Standards may consolidate around another provider, or an operator-identified need may create a new opening in an adjacent layer. Firms should maintain more than one viable team configuration and avoid dependence on a single prime, vehicle, or architectural position.  

The advantage comes from making these adjustments without losing speed or strategic coherence. A firm that cannot adjust may remain on contract while losing the work that matters.

Align the Enterprise to Win

NGC2 is an early demonstration of a broader change in Army acquisition. Portfolio leaders are gaining greater flexibility to make trades across related capabilities. Program teams are using soldier feedback to refine requirements and acquisition plans. Open interfaces and direct-to-supplier pathways give companies more opportunities to enter—but also make it easier for the Army to change course when a capability or team stops performing.

Executives face three decisions: where to compete, how to engage before requirements harden, and how the company will pass both gates to scale.

These decisions cannot only live in a capture plan. If operations cannot deliver at the required pace, or commercial terms make integration impractical, the strategy will break down regardless of how well it was presented. The company’s role may also change. A supplier can be central during one round of testing and peripheral in the next as standards mature, teams are reorganized, or demand moves elsewhere. Handled well, cross-functional adaptability is the moat against being sidelined after award—and the path to sustained impact for the warfighter and durable value for the company.