Your Software Doesn’t Have an API? That’s No Longer an Excuse.

I was talking to Chris Murphy about automating some of the weekly reporting at his salon locations. He runs multiple sites, all on SalonBiz — a point-of-sale system that most salons use, and that every developer who’s tried to integrate with it knows as “the one that doesn’t really have an API.”

His first question was the one I hear from every small business owner: “But we use SalonBiz. It doesn’t have an API. Can you still do something?”

I showed him a grocery agent I’d built.

The HEB Agent

Here’s what it does: it reads a Google Sheet with my grocery list, navigates to HEB.com, logs in with my credentials, searches for each item, adds it to the cart, and sends me a confirmation email when it’s done.

No API integration. No developer needed. No special access to HEB’s backend systems.

Just an agent doing exactly what I’d do if I sat down at my computer, opened a browser, went to HEB, and shopped.

The technical name for this is “computer use.” The agent has access to a virtual browser. It can navigate pages, click buttons, fill out forms, read what’s on the screen, and take actions. Same as a human — but on autopilot and without needing to be watched.

Why This Changes the “No API” Problem

For the last decade or so, business automation followed a specific pattern: you hire a developer, they find the API documentation for your software, they write code to connect two systems, and you pay ongoing maintenance for that integration.

That works great for modern software that’s built with developers in mind. Salesforce, HubSpot, Stripe — they have robust APIs because they designed for it.

But a huge percentage of actual small business software doesn’t work like that. SalonBiz. Many medical practice management systems. Restaurant POS platforms. Industry-specific tools built 10 or 15 years ago, before API-first was a design philosophy. These are web-based, they run in a browser, and you interact with them by logging in and clicking around.

The old answer was: you can’t automate these. Too closed. No integration path.

Computer use changes that answer entirely. If you can log into it and click through it, an agent can log into it and click through it.

A Less Delightful, More Useful Example

The grocery agent is fun to talk about. But the place where this actually matters is in business workflows.

I was working with a real estate client who needed to pull property listings from their MLS system. MLS platforms are notoriously locked down — they have paywalls, closed databases, and very limited API access even for paying subscribers.

We built a virtual machine agent that logs into their account, searches for listings matching their criteria, extracts the relevant data, and drops it into a Google Sheet that triggers the rest of their pipeline. It runs 24 hours a day, seven days a week. They don’t have a human doing manual searches anymore.

As the person who built it described it: “You don’t know these solutions exist until you’re in the weeds with the tech.”

That’s the thing. Most business owners have been told “you can’t automate that system” so many times that they stopped asking. The answer was correct a few years ago. It isn’t anymore.

What This Unlocks

Go through your list of web-based software and ask: which of these do I interact with by logging in and clicking?

All of those are now candidates for agent automation.

Some examples:

• Weekly reports pulled from a POS system and emailed to your team automatically
• Inventory checks that run on a schedule and flag items below a threshold
• Data entry from one web app to another, without an integration layer
• Form submissions, status updates, routine lookups — anything that follows a consistent pattern

The constraint isn’t “does this software have an API?” anymore. The constraint is “does this workflow follow a consistent enough pattern that an agent can reliably do it?”

For most routine admin work, the answer is yes.

One Thing to Keep in Mind

Computer use is genuinely powerful, but it’s also less stable than a real API integration. Web pages change. Login flows update. Elements move around. An agent that works perfectly today might need adjustment next month when the site redesigns.

So the practical approach is this: for high-value, high-frequency workflows, it’s worth the setup and occasional maintenance. For one-off tasks or workflows that change constantly, it’s more trouble than it’s worth.

But for the weekly grocery order? The monthly SalonBiz report? The twice-daily MLS search? That tradeoff is easy.

The “we can’t automate it because there’s no API” objection needs to retire. It was true once. It mostly isn’t anymore.

Thanh Pham is the founder of Asian Efficiency. He works with business owners to find the workflows that AI can handle so humans can focus on what AI can’t.