From Runtime to Tier-1

September 2019. aicas had a brilliant piece of technology — a real-time Java runtime trusted in industrial systems and vehicles. What it didn't have was a product story the market was buying. The company's president (also COO) brought me in with one line of mandate:

Build better products.

Beneath that mandate: build a cloud platform capable of ingesting and managing the data streams coming off IIoT systems. Which meant repositioning the runtime from the product to an ingredient inside a larger platform.

Every engagement has an external problem and an internal problem.

The external problem was clear. The market had shifted from embedded runtime libraries sold per-seat to edge-to-cloud platforms sold as data infrastructure. Connected vehicles were the forcing function — OEMs no longer wanted a clever library, they wanted a partner who could handle data from the car up to the cloud and back.

The internal problem was harder. The company had been built around the runtime for decades. Strategy discussions inside aicas centered on whether the path forward was deeper runtime capability or broader platform capability — and that debate cut across the executive team. The mandate I'd accepted was to deliver the platform answer.

I wasn't going to win that argument in a strategy meeting.

The CES proof was the wedge, not the work. The engagement ran 33 months with full product and budget responsibility. The partner stack was rebuilt: AWS, Google and Red Hat on cloud; Verizon, Vodafone, Deutsche Telekom and Bell Canada on 5G MEC; Stellantis, VW, Ford and GM on the automotive side. The runtime stayed in the architecture, but the company position around it changed entirely — from a specialty Java-runtime vendor to a V2X platform partner.

What that meant in practice: every conversation with a major OEM had to lead with what aicas delivered at the platform level, not at the runtime level. Procurement teams re-tiered the company in their supplier lists. Engineering teams on the OEM side had to be brought along on a story they had not previously associated with aicas. None of that happens through a deck. It happens through code that runs at trade shows, through partners who back the framing, and through 33 months of staying with the same story until the buyer can repeat it back.

1. The frame around the technology, not the technology itself, is usually the problem. Companies with great technology and flat revenue rarely need better technology. They need a product context that lets the technology matter to a bigger buyer. At aicas the runtime was excellent. The frame around it had stopped reaching the buyer the company actually needed.
2. Internal orthodoxy doesn't yield to slides — it yields to proof. The strategy debate inside aicas wasn't going to be settled by a better presentation. It was going to be settled by something running on stage at CES, end-to-end, on real silicon and real cloud, while everyone else was still arguing about the deck. Three months of proof beat thirty-three months of persuasion in a company that had spent decades convinced of a different story.
3. Repositioning is a 33-month commitment, not a marketing repaint. Anyone who tells a runtime company that they're really a platform company in a single workshop has not done this work. It takes the partner stack, the procurement-tier change, the OEM-engineering acceptance and three financial years of consistent execution. Shorter timelines may move the website. They don't move the buyer.