})(jQuery);

Automation Without the Frontier Bet: Practical Options for Cautious Leaders

The Deliberate AI Leader | When AI Goes Public, Part 3 of 3

Summary:

Plenty of leaders have read the IPO coverage and concluded that building on a frontier AI vendor is too risky right now. That conclusion does not require standing still. Rules-based workflow automation, system integration, AI features inside software you already own and self-hosted open-weight models each solve real problems with different levels of vendor exposure. For most companies, the strongest approach is a workflow layer they own, with AI added only at the steps where it clearly earns its place.

The first two posts in this series covered what the AI IPO wave means for companies using or evaluating frontier AI platforms. This one is for leaders who have looked at the losses, the pricing uncertainty and the safety debate and decided to wait. That can be a sound call. Waiting on AI is a different decision from waiting on automation, though, and most of the operational friction we see in growth-stage companies can be fixed without a frontier model.

The economics favor this route right now, too. As Part 1 described, borrowing costs more than it did a year ago, and energy and hardware prices are high. Projects with predictable costs and a quick payback clear that bar more easily than large AI bets whose returns are still uncertain.

The market is already moving this way

Gartner’s September 2026 forecast puts generative AI in the Trough of Disillusionment and notes that many companies are getting their AI through features added to tools they already run, using them for routine efficiency gains. Back in January, Gartner expected most companies to get AI from software vendors they already use, with few launching large standalone AI projects. Caution is the mainstream position this year.

Five options, from least to most vendor exposure

1. Rules-based workflow automation

Many processes labeled as AI projects are routing problems. A form comes in, data needs to land in two systems, someone has to approve it, and a customer needs an update. Rules-based automation handles this with triggers, conditions and approval steps. It behaves the same way every time, costs the same every time it runs and can be audited step by step. There is no model involved, so there is no usage-based AI pricing to renegotiate when a vendor goes public. Our guide to your first automated workflow covers how to pick a low-risk place to start.

2. System integration

A large share of operational friction comes from systems that do not talk to each other, which leaves staff re-keying data and reconciling spreadsheets by hand. Connecting your CRM, finance, operations and support tools removes that work directly. It also builds the clean, connected data foundation any future AI use will need, so the investment keeps its value whatever you decide about AI later. The people doing that re-keying are what we called human middleware earlier in this series, and integration frees them for work that needs judgment.

3. Robotic process automation for legacy systems

Where an older system has no usable connection point, robotic process automation can repeat the clicks and keystrokes a person would make. It works well on stable, repetitive screens and breaks easily when screens change. Treat it as a bridge until the underlying system can be integrated or replaced. Watch the labels, too. Gartner warned last year about “agent washing,” where vendors repackage older automation and chatbots and sell them as agentic AI.

4. AI features inside software you already own

Your CRM, help desk and accounting tools are adding AI features steadily. Using them keeps AI inside contracts, security reviews and data agreements you already have. These suites are turning into agent platforms themselves. Google’s new Gemini agent, announced in October, runs inside Workspace, Microsoft 365 and Slack, and Microsoft and Salesforce are building agents into their own products. The catch, as Futurum Group’s Mitch Ashley pointed out to Techstrong.ai, is that embedded AI often arrives folded into a higher renewal price. Before accepting an AI add-on at renewal, ask which model powers it, what happens to your data and whether you can turn the feature off without losing anything else.

5. Open-weight models you run yourself

Open-weight models can be downloaded and run in your own environment, and the main appeal is control. AI Business reported in October that new Western open-weight releases from Reflection AI and Mistral are widening the options for companies that have avoided Chinese models over security or compliance concerns. Running a model yourself lets you keep sensitive data in-house and decide when to upgrade. The same article is candid about the trade-offs. Jeet Pattanaik of Glokal AI noted that for smaller workloads, the savings can disappear once you pay for hardware, staff and testing, and running your own model shifts responsibility for security, updates and governance onto you. Arnal Dayaratna of IDC made a related point to CIO.com, arguing that open models are often harder to put into production at scale than buyers expect.

The hybrid most companies should consider

For most growth-stage companies, the right answer combines these options. Build the workflow in a layer you own, with rules, integrations and human approvals. Then add AI at specific steps where it clearly earns its place, such as summarizing an inbound request or drafting a first response that a person reviews before it goes out.

This is what we mean by orchestration. If an AI vendor raises prices, changes terms or retires a model, you swap one step and the rest of the process keeps running. Your exposure to any single company’s IPO, delay or strategy shift stays small.

Questions to decide which option fits

Ask this about the process

If the answer is yes, lean toward

Does the task follow clear rules every time?

Rules-based workflow automation

Is most of the pain re-keying data between systems?

System integration

Does the work happen in an older system with no usable connection point?

Robotic process automation as a bridge

Is the input unstructured, like emails, PDFs or call notes?

AI at that one step, inside a workflow you own

Would a wrong answer create legal, financial or safety exposure?

A human approval step before anything goes out; no full autonomy

Do you handle regulated or highly sensitive data?

Embedded AI under existing agreements, or a self-hosted model with strong governance

 

Holding off on a frontier AI commitment this year is a reasonable call. The cost of leaving manual work in place keeps growing, though, and the workflow layer you build now stays yours no matter which AI companies list, delay or stumble over the next two years.

Next Step

Not sure which of your processes need AI and which just need better workflow?

Book a Strategy Call. No pitch, just clarity.