Can AI automate our old business software without replacing it?

Sometimes. AI can help operate a browser or desktop application when a suitable integration is unavailable. Whether that is sensible depends on the task, the application's stability, and how you verify the result. First check for a supported API, connector, export, or import route; those may be simpler to maintain than an assistant clicking through screens.

Anthropic's March 23, 2026 computer-use announcement described Claude navigating applications through the screen when a suitable tool connection is unavailable. That announcement makes older systems worth reassessing. It does not establish that unattended automation will be reliable in your particular application.

Which legacy tasks are reasonable starting points?

Look for repetitive work with stable inputs and a clear result. Downloading a weekly report, preparing a draft order, or transferring an approved set of fields can be candidates. A staff member should be able to check the result quickly.

Avoid starting with unrestricted payments, bulk deletion, or tasks requiring frequent judgment about exceptions. Screen access can give an assistant more authority than the first workflow requires. Create a separate user account with limited permissions wherever the application supports it.

Write down the process as it works today, including the steps people take when a record is missing or a screen behaves differently. These exceptions often determine the maintenance cost.

How do I compare the integration options?

A short-term screen-based solution can be reasonable while a larger modernization project is planned. Include the cost of maintaining that bridge. If the application changes every week, an apparently cheap automation may demand constant attention.

How do we know the task really finished?

Define the business result separately from the clicks. For order entry, success means that the correct order exists with the right customer, items, quantities, and status. A screenshot of a pressed Save button is insufficient.

Ask the implementation team how it verifies the saved record. Ideally the assistant receives or retrieves a record ID and checks the important fields in the destination system. Where that is impossible, decide what independent review is needed.

Retries need particular care. Suppose the application saves an order but the confirmation page never loads. Starting the same task again could create a duplicate. The workflow should check for an existing result using an appropriate reference before repeating the action.

What should the supplier demonstrate?

Use a test account and representative data. Include a slow page, an expired session, a record that already exists, and a missing field. Change a label or move a button if the test setup permits it.

Watch what happens when the assistant cannot be certain. It should pause and ask for help rather than guessing which customer record to select. The person taking over needs the original request, completed steps, and any uncertainty, so they can continue without repeating an action.

Treat text inside documents and web pages as untrusted input. A supplier note should not be able to tell the assistant to ignore approval requirements or export unrelated records. Keep action limits enforced by the system where possible.

When is replacing the software the better decision?

Consider replacement when missing capabilities affect many workflows, the vendor cannot support a reliable integration, or staff spend substantial time correcting the underlying records. Automating an unstable process can preserve the problem and add another layer to maintain.

Compare the full cost over a realistic period, including outages and manual fallback. Our app modernization service can help assess whether to integrate, automate a narrow task, or replace part of the system. Bring a recording of the current process and examples of its exceptions.

Frequently asked questions

Can AI work with software that has no API?

Potentially, through the browser, desktop, or supported file operations. Feasibility depends on the interface and task. Require a demonstration in your actual environment before committing to a rollout.

Can it run overnight without supervision?

Only for a scope whose failure cases, verification, and escalation arrangements have been tested. Begin with reviewed runs and define what happens when no one is available to answer a question.

Will we still need the software vendor?

Usually. You still depend on the application, licensing, access controls, and supported operating arrangements. Check that the proposed automation is compatible with your contract and support requirements.