We introduced ProcessOS by laying out the four stages of the Great Process Re-Engineering and the case for why re-engineering a process delivers structural improvements, whereas simply adding AI to it only produces modest gains. That case is now playing out with real customers.
Four engagements are underway, and many are about to start, spanning industries as different as telecommunications and industrial real estate. All of these organizations share the common theme of asking AI to solve the slower, more expensive problem underneath every transformation—figuring out how a process runs today and how to improve it.
A global industrial real estate operator brings in ProcessOS
One of the new engagements comes from a global industrial real estate operator managing a large portfolio of properties. Their use case is the operating expense lifecycle, the onboarding and offboarding work tied to properties entering and leaving operation. It is exactly the kind of high-volume, repeatable, and often-messy back-office process that gets harder to manage by hand as a portfolio grows.
This operator's standard technology stack is built on Python rather than the Java-based stack ProcessOS teams work with most often, which means part of the engagement involves adapting the approach to an existing environment. Our delivery partner BP3 has embedded with the company and is doing hands-on implementation work alongside the core team.
Trends cross the broader ProcessOS pipeline
The real estate operator and other engagements are progressing alongside our earlier banking work, but there are dozens of other companies who will be starting soon. Here are a few examples:
- A major European telecommunications provider is migrating more than a thousand legacy processes at once, using fiber rollout as the pilot to prove out migration and modernization together rather than as sequential projects.
- A large insurer in Germany is testing whether a high-volume manual request process can move to automation fast enough to justify a much bigger systems rework.
- A global container shipping and logistics group is targeting the exception-handling gap in an already-automated booking process.
- A large national bank is mapping an anti-money-laundering (AML) review process that has only ever existed as tribal knowledge, which echoes the same discovery challenge our earlier piece on the discovery phase described.
- A global professional services network is rebuilding an audit procedure as a template it plans to reuse across dozens of similar tools firm-wide.
These companies are in different industries with different starting points, but share the same underlying request. Each of these organizations wants to migrate off something legacy, re-engineer a process that has outgrown manual handling, or document work that nobody has fully mapped before. The volume and variety of use cases are exciting, and we can’t wait to dig in and update you more in the coming weeks.
Momentum now, the delivery story next
Three months ago, this series introduced ProcessOS through its founding thesis and lifecycle stages, then followed with the people doing the work, from Forward-Deployed Engineering to the discovery methodology that makes fast documentation possible. The engagements above show that thesis moving into practice with real customers, constraints, and targets they are holding us to. The real estate operator and other examples in progress are very different tests of the same idea, and the broader pipeline behind them suggests this is only the beginning.
The next chapter in this series will turn toward how this work gets delivered, including the partner ecosystem behind engagements like the real estate operator's. Stay tuned!
