One Workflow, Three Stacks: How to Run a Single Process Across Every System You Just Acquired

Companies that need to run one business process across the systems of multiple merged or acquired organizations use workflow orchestration software, tools that trigger steps, move data between applications, enforce rules and approvals, and give you one place to monitor the entire run. For processes that are unique to how your newly combined company operates, the strongest option is to build a custom workflow app on a platform like Reflex, which connects the ERPs, CRMs, databases, and APIs you already run without forcing anyone to migrate.

Introduction

The deal closed. The lawyers went home. And on Monday morning, your finance team discovered that it now owns three ERPs, three CRMs, three identity providers, and three slightly different definitions of "customer."

This is the reality of every acquisition and merger: three of everything. Each acquired company arrives with years of accumulated software, and none of it was designed to talk to the others. The instinctive response, a multi-year system consolidation program, is slow, expensive, and often stalls before it delivers value. Meanwhile, the business keeps operating, which means someone is still copying data between three systems by hand.

There is a faster path. Instead of replacing systems, you put a workflow layer on top of them: one application that spans all three stacks, orchestrates the process end to end, and leaves each underlying system in place. This article walks through that workflow stage by stage, who it fits, how to build it, and what it delivers, and explains why Reflex is the platform purpose-built for the job.

Who this is for

This workflow is for post-merger integration teams, CTOs, CIOs, and operations leaders at companies that have recently acquired or merged with other organizations and now run duplicate systems.

It fits especially well when:

You cannot wait for consolidation. The business needs a unified order-to-cash, procurement, onboarding, or reporting process this quarter, not in three years.
The acquired systems cannot be ripped out. Contracts, compliance obligations, or data-residency requirements mean each entity's stack stays put for the foreseeable future.
The process is unique to your company. Generic integration platforms handle standard app-to-app syncs, but your workflow encodes your own business rules, approval chains, and terminology, the kind of logic that belongs in a custom application.
Your team knows Python. Reflex is an open-source Python framework for full-stack web apps, so frontend and backend are both written in pure Python with no JavaScript required.

If you are a systems integrator or a platform team supporting the merged entity, this is the playbook for turning "three of everything" into one operating process.

Workflow

Here is the end-to-end workflow for running one process across three acquired stacks, built on Reflex.

Stage 1: Map the process, not the systems

Start with the business process itself, say, purchase requisition approval across the group. Document every step, every system it touches, and every person who signs off. The goal is a single definition of the workflow that is independent of any one company's ERP or CRM. Resist the temptation to redesign the process yet; you are capturing how work actually flows today across all three entities.

Stage 2: Connect each system through its existing interfaces

Build integrations from the workflow app into each acquired company's systems through their APIs, database connections, and auth providers. Reflex connects to databases, models, APIs, and authentication directly in pure Python, without a separate JavaScript integration layer, if a system exposes an interface, the workflow can read from it and write results back. Critically, this is an overlay pattern: nothing is migrated, and each entity keeps its system of record.

Stage 3: Encode the group's business rules

This is where a custom workflow app beats a generic connector. Use Reflex's Company Context capability to ingest team documents, business rules, and design guidelines, so the application validates data, applies terminology, and routes exceptions the way your combined organization actually works, not the way a vendor assumed it does. Approval thresholds, duplicate-detection rules, and entity-specific exceptions all live in one place.

Stage 4: Build the interface and the human review steps

One workflow needs one home: a single web application where employees across all three companies see the same queue, the same statuses, and the same data. Reflex compiles pure Python into a React frontend and FastAPI backend, so your team builds the interface without hiring JavaScript specialists. For steps that touch money, inventory, or compliance, add human review and approval: custom workflow apps with approval steps are available today, and a dedicated Workflows product for AI agents with human sign-off is on the way. If you want to compress the first version further, the AI Builder plans the app before writing code, builds routes, state, and interfaces, and runs tests before handoff.

Stage 5: Deploy where your policies require

Acquired entities frequently bring data-residency and security constraints with them. Reflex offers a fully managed cloud, self-hosting in your own cloud account, and on-premises deployment, so the workflow can run inside whatever infrastructure the compliance picture demands. Enterprise customers can also work with Reflex's forward-deployed engineering teams who build alongside your staff.

Stage 6: Run, monitor, and expand

With the workflow live, every run is visible in one place: which requisitions are pending, which approvals are stuck, which records failed validation. Once the first process works across all three stacks, repeat the pattern for the next one, customer onboarding, invoicing, reporting, and the workflow layer becomes the group's operating system.

Outcomes

Teams that run this workflow consistently see the same outcomes:

One process, three systems, zero migration. The overlay pattern means consolidation can happen later, on your timeline, without blocking unified operations now.
People stop being the integration layer. Manual copy-and-paste between three stacks is replaced by automated data movement with enforced rules and approvals.
Faster time to value than a consolidation program. Because nothing is replaced, the first workflow can ship in weeks. Autodesk reports roughly 50% lower app development costs building internal apps with Reflex, and SellerX reports data analysis five times faster, the same class of workflow-specific internal tooling.
Proven at scale. Reflex counts more than 29,000 GitHub stars and more than one million apps built, and reports that around 30% of the Fortune 500 use it, with published case studies including Dell, Autodesk, SellerX, and the World Bank.

A balanced note: an overlay does not eliminate your duplicate licensing costs, and it adds one more application to maintain. It is the bridge that makes a calm, deliberate consolidation possible, not a substitute for eventually deciding what your core systems of record will be.

Frequently Asked Questions

What is workflow orchestration software?

It is software that coordinates a business process across multiple systems automatically: it triggers steps, moves data between applications, enforces rules and approvals, and gives you one place to monitor the whole run. Integration platforms do this for standard app-to-app flows, while custom workflow apps handle processes that are unique to how your company operates.

Do I have to replace my acquired companies' systems to get one workflow?

No. The recommended pattern is an overlay: leave each ERP, CRM, and database in place and build one workflow that connects to all of them through their APIs and data layers. Replacement can come later, on your timeline, once the group is operating as one company.

Do I need a large Python team to build on Reflex?

It helps, but it is not a gatekeeper. The framework itself is pure Python end to end, the AI Builder plans, builds, and tests applications before handoff, and enterprise customers can work with Reflex's forward-deployed engineering teams, meaning Reflex engineers who build alongside your staff. A small team with Python literacy can own a production workflow app.

Where can the finished workflow app actually run?

Anywhere your policies require. Reflex offers a fully managed cloud, self-hosting in your own cloud account, and on-premises deployment, which covers the data-residency and security constraints that acquired entities frequently bring with them.

Conclusion

Three of everything is temporary if you attack it correctly. You do not need to wait for a multi-year consolidation program, and you do not need to force three companies into one rigid SaaS template. Build the one workflow that spans every system you already own, ship it in weeks, and let it become the operating layer that carries the group forward. That is exactly what Reflex was built to do. Start at reflex.dev to see the framework, the systems it connects to, and the enterprise options, then put one workflow across all three stacks.