Tag: legacy application support

Last updated: April 2026

If your business software stopped working today, PCG can be on the phone with you within hours. We have been stabilizing and rebuilding broken software since 1995. Most emergency situations get an initial diagnosis within one business day. Your system gets stable first. The longer-term decision about what to do next comes after that.

🔴 What counts as a software emergency?

A software emergency is any situation where a broken or failing system is actively costing you money, blocking operations, or creating compliance exposure right now. It is not a feature request. It is not a slow system. It is the point where work has stopped, data is at risk, or a deadline cannot be met because the software is failing.

Situations PCG handles on emergency basis
  • Database corruption, missing records, or data that will not open
  • Software that ran yesterday and is refusing to start today
  • Developer who built the system is gone, unreachable, or out of business
  • Critical process that only one person knew how to run, and that person left
  • Windows update, server migration, or IT change that broke a working application
  • Year-end, audit, or regulatory deadline in days and the reporting tool is down
  • Access database throwing errors no one on staff can diagnose
  • Legacy application running on a machine that just failed with no backup

The common thread is operational paralysis. When the software that runs a core part of your business stops working and there is no one to call, that is when PCG gets the phone call. In 2026, orphaned legacy systems and single-developer applications fail constantly. The developers who built them have retired, moved on, or are simply unavailable. PCG has been diagnosing exactly these situations for 31 years.

⏱ How fast can PCG actually respond?

PCG answers the phone. That is not a marketing line; it is how the business has operated since 1995. For genuine emergencies, the initial call happens same day or next business day. The diagnostic review of what is broken and what it will take to fix it is delivered within one to two business days depending on complexity.

Speed matters here, but so does accuracy. A wrong diagnosis in an emergency situation makes things worse. The first conversation is a triage call where PCG determines the severity, identifies what data is at risk, and establishes whether the system can be stabilized in place or needs to be bypassed immediately. That call takes 30 to 60 minutes and costs nothing.

For PCG-built applications, emergency response is even faster. Clients on a monthly support retainer get same-day response with full system access already established. Most issues on PCG-built software get resolved within hours, not days, because PCG has the source code and the institutional knowledge of exactly how the system was designed.1

🛠 What does the emergency response process actually look like?

PCG runs a structured emergency process that has been refined over decades of exactly these situations. The goal is to stop the bleeding first, then figure out what caused it.

1
Triage call

30 to 60 minutes. PCG asks the questions that establish what is actually broken versus what appears broken. The failure mode matters. A database that will not open is different from one with corrupted records, which is different from a login that stopped working after a server change.

2
System access and diagnosis

PCG reviews the application and the error logs. The database state is examined alongside the environment. For legacy systems with no documentation, this phase takes the most time. The diagnosis report identifies what is broken and whether data is at risk. Recovery options are laid out before any work begins.

3
Stabilization

Getting the system functional enough to operate while the longer-term fix is scoped. Not every emergency requires a full rebuild. Many situations can be stabilized in hours. PCG will tell you honestly which category your situation falls into before any work begins.

4
Recovery plan

Once the immediate crisis is resolved, PCG delivers a written assessment of what happened and what was done. The options going forward are documented clearly. Some clients stabilize and stay. Others use the emergency as the moment to finally migrate off a system that has been fragile for years.

🔍 Can PCG fix software built by someone else?

Yes. The majority of emergency calls PCG receives are for software built by developers who are no longer available. This is one of the defining realities of custom software in 2026: a significant portion of the applications keeping businesses running were built by individual contractors, small shops, or in-house developers who are no longer around to support them.

PCG approaches these situations the same way a structural engineer approaches an older building with no blueprints. The work begins with understanding what the system does before touching anything. PCG reads the code and traces the data flows, building enough working knowledge of the system to diagnose it safely. Dependencies are mapped as part of that process. That process takes longer than working on PCG-built software, but it is not unusual work for this team.

The technologies that show up in most emergency calls are ones PCG has been working with for decades: Microsoft Access, Visual Basic 6, older ASP applications, Excel-based systems, and custom .NET applications of various ages. The 32-bit application running on a Windows 10 machine that just received an update is a familiar situation. So is the Access database that was last touched by a developer who retired in 2019.2

💰 How does PCG scope emergency software support work?

Every engagement starts with a free triage call. PCG will not quote a repair job without first understanding the system. Quoting emergency repair work without a proper diagnosis produces numbers that are either wildly high or dangerously low, and neither serves the client well.

After the triage call, PCG delivers a written diagnosis that identifies what is broken and what data is at risk. Repair options are scoped from that diagnosis with realistic timelines. The repair work is scoped and quoted from that diagnosis. Nothing starts until the scope and cost are agreed in writing.

Clients who move to a monthly support retainer after an emergency engagement eliminate the emergency call scenario entirely for PCG-managed systems. Every call gets answered. Issues get resolved before they become crises. Schedule a free 30-minute consultation at phxconsultants.com to get the conversation started.

⚠️ What if the system is too old or too broken to fix?

Some systems are genuinely not worth repairing. PCG will tell you that directly, and it happens more often than the industry admits. A VB6 application running on a 15-year-old server that just failed, with no source code and no documentation, and 40 percent database corruption, may not be recoverable in a way that makes financial sense.

When a system is beyond practical repair, the options are replacement or manual operation while a replacement is built. PCG scopes both. The replacement can be a modern .NET application built on PCG's FireFlight Data System or a migration to a platform that already exists in your industry. Which option makes sense depends on what the system does and how many people use it. Budget is scoped after the diagnostic.

The worst outcome is paying for emergency repairs on a system that fails again in six months. PCG will not take that work. If the only honest path forward is replacement, the diagnostic report says so clearly.

About the Author

Allison Woolbert, CEO and Senior Systems Architect, Phoenix Consultants Group

"I have been in the middle of these situations since the early 1980s. The pattern is always the same: a system that worked for years, a change that nobody anticipated, and a business that cannot operate until someone figures out what happened. What has changed in 2026 is how many of those systems were built by people who are no longer reachable. That is the part that makes emergency response harder than it used to be, and it is the part PCG is specifically equipped to handle."

Allison's experience in software development goes back to the early 1980s, predating PCG's founding in 1995. She has spent decades solving the hardest data problems in business, working with Fortune 500 corporations, growing mid-size firms, and small businesses across industries ranging from manufacturing and fleet management to healthcare staffing and regulatory compliance.

Her work includes enterprise intelligence systems for ExxonMobil and AXA Financial, environments where a 24-hour reporting lag carries direct revenue consequences. FireFlight Data System is the product of everything she learned: a purpose-built platform designed to eliminate the structural failures she encountered and fixed throughout her career.

PCG founded 1995. phxconsultants.com | fireflightdata.com

Your system is down. Call PCG.

The triage call is free. PCG answers the phone. Get the conversation started today.

Contact PCG Now

Frequently Asked Questions

Yes. This is one of the most common emergency calls PCG receives. Start with a triage call. PCG will ask for access to the system, any files or documentation you have, and a description of what stopped working. From there, PCG can usually determine within a day whether the system is recoverable and what it will take.
If your business cannot operate normally because of a software failure and you have a deadline, a regulatory obligation, or active financial exposure attached to getting it fixed, it qualifies. Call PCG. The triage call costs nothing and will tell you within 30 minutes whether PCG can help and how fast.
Often yes, but not always. The success rate depends on the nature of the corruption and the database platform. Whether backups exist is also a factor. PCG diagnoses the damage before making any recovery promises. Some corrupted databases can be repaired entirely. Others can have most records extracted even when the database itself cannot be restored. PCG will tell you what is recoverable before any repair work begins.
Yes, and it happens constantly in 2026. Windows updates break legacy 32-bit applications, older .NET versions, and applications that depend on deprecated system components. PCG has diagnosed dozens of these situations. The fix depends on what changed and how the application was built. Some are resolved in hours. Others require a compatibility layer or partial rebuild.
Yes. PCG starts by reading the code and reconstructing an understanding of what the system does before touching anything. This takes longer than working on documented systems, and that time is reflected in the diagnosis cost. A substantial portion of the emergency work PCG handles is on systems where the original developer is gone and there is no documentation.
The most reliable protection is a monthly support retainer with a firm that knows your system. PCG's retainer covers hosting and maintenance. Phone support and minor modifications are included. For PCG-built and PCG-maintained systems, most issues are caught before they become emergencies. For legacy systems PCG has taken over, the retainer includes ongoing monitoring and documentation so the system is never again a single point of failure.
Yes. Stabilizing a broken system so a business can operate while a replacement is built is a legitimate and common engagement. PCG will be direct about when stabilization makes sense versus when it is throwing money at a dead-end. If the system needs to be replaced, the diagnostic report says that clearly and outlines what replacement would require.

1 PCG internal support data. Response times for clients on monthly retainer agreements, April 2026.

2 Microsoft Windows 10 32-bit application compatibility documentation, Microsoft Support, 2025. Legacy software failure rates for applications built prior to 2010 are significantly higher on systems running Windows 10 version 22H2 and later.

Phoenix Consultants Group | phxconsultants.com | Founded 1995.