Federal IT Modernization in FY2027: Where Agencies Should Start

Fiscal year 2027 opened on October 1, and most agency IT shops are now looking at a modernization mandate, a budget that is smaller than the mandate, and a portfolio of systems that all seem urgent. The agencies that make visible progress this year will not be the ones with the biggest plans. They will be the ones that choose the right first move.

Why the first quarter of the fiscal year matters

The opening months of a fiscal year are when modernization priorities actually get set. Spend plans are being finalized, task orders are being scoped, and Technology Modernization Fund (TMF) proposals that will be funded this year are being drafted now. Decisions made before the holidays tend to shape what gets built by next summer.

That makes October through December the right time to answer one question clearly: of everything we could modernize, what should we do first? The three steps below are how we help federal program offices answer it.

Step 1: Inventory what you actually run

Most agencies have an application inventory. Fewer have an accurate one. Systems get stood up under a program office, absorbed into a contract, and quietly carried forward year after year. Before choosing what to modernize, it is worth knowing what exists, who depends on it, and what it costs to keep alive.

A usable inventory does not need to be exhaustive on day one. It needs four fields for every system that matters:

  • Mission dependency. What breaks for the public or the workforce if this system goes down for a week?
  • Technical risk. Unsupported platforms, single points of knowledge, and components that no longer receive security patches.
  • Annual cost to operate. Licenses, hosting, contractor support, and the staff hours spent on workarounds.
  • Data exposure. Whether the system holds personally identifiable information or other sensitive data, and how it is protected.

Scored honestly, those four fields will usually surface a short list of systems where risk and cost are both high. That list is your modernization backlog.

Step 2: Pick one high-friction system and prove the model

The temptation at the start of a fiscal year is to launch a portfolio-wide modernization program. In our experience, the agencies that get traction do the opposite. They pick a single system that is visibly painful, modernize it well, and use that result to build the case for everything that follows.

The best first candidate usually has three traits:

  1. Everyone already agrees it is a problem. You should not have to sell leadership on why the system needs attention.
  2. It is bounded. A system with a handful of integrations is a better first project than one wired into a dozen others.
  3. Success is measurable. Processing time, error rates, help desk tickets, or cost to operate: pick something you can report on in six months.

A legacy application modernization project with those traits does more than replace one system. It establishes the delivery model, the security review path, and the governance that every later project will reuse. That is why we treat the first project as a template, not a one-off.

Step 3: Write the business case the way it will be read

Whether funding comes from the agency’s own IT budget or a TMF request, the business case is where modernization efforts most often stall. A strong one is short, specific, and answers the questions reviewers are actually asking:

  • What does the current system cost, in dollars and in risk, and how do we know?
  • What will change for the mission, and when will that change be visible?
  • What is the delivery approach, and who has done this before?
  • How will security and compliance be handled, from the authorization boundary to continuous monitoring?
  • How will the agency sustain the result after the project team leaves?

Business cases that lead with technology choices tend to lose. Business cases that lead with mission outcomes and a credible delivery plan tend to get funded. The system inventory from step 1 and the pilot from step 2 give you the evidence to write the second kind.

Three mistakes to avoid this year

Modernizing the interface and leaving the data model alone

A new front end on an old data structure buys a year or two before the same constraints return. Modernization that sticks addresses how data is stored, validated, and shared.

Treating cloud migration as the goal

Moving a legacy application to a cloud environment without changing it reduces some hosting burden and almost none of the technical debt. Cloud is a destination, not a strategy. Our article on cloud migration approaches covers when to lift-and-shift and when to re-architect.

Skipping the authorization conversation until the end

Security authorization is where modernization timelines go to die. Bring the ISSO and the authorizing official into scoping, not acceptance testing.

How SFA approaches federal application modernization

Susan Fitzgerald & Associates delivers application services for government clients under a CMMI-appraised process, which means the inventory, pilot, and business case steps above are not improvised for each engagement. They are repeatable, documented, and measured.

SFA put this approach into practice on a fleet configuration management modernization, using PTC Windchill and related product lifecycle management (PLM) tools to change how teams manage fleet configurations and engineering and software changes. By connecting configuration data to change workflows, we helped teams confirm what was approved, trace what changed, and understand how each change affected the fleet.

If your agency is deciding where to start this fiscal year, we are glad to walk through your inventory and help identify the right first project.

Frequently asked questions

What should a federal agency modernize first?

Start with a system that is widely recognized as a problem, has a limited number of integrations, and offers a clear metric for success. A bounded, high-friction system lets you prove the delivery model before scaling it across the portfolio.

How does the Technology Modernization Fund work?

The TMF is a centrally managed fund that agencies can apply to for modernization projects. Proposals are evaluated on mission impact, technical approach, and the agency’s plan to sustain and, in many cases, repay the investment. Strong proposals lead with outcomes and a credible delivery plan.

Is cloud migration the same as IT modernization?

No. Moving an application to the cloud without changing its architecture or data model reduces hosting burden but leaves most technical debt in place. Modernization addresses how the system is built, secured, and maintained, and cloud may or may not be part of that answer.

Susan Fitzgerald & Associates provides application services, cloud services, cybersecurity, and managed IT for government agencies. Talk with our team about your FY2027 modernization priorities.