Segment, mParticle and RudderStack rent the pipe that copies events into other tools. RudderStack is not listed here as the owned answer: we did not confirm an open-source licence for the control plane that would let a client keep running it on their own terms. The owned move is duller and better. Put the customer in the CRM you run, and put the events in a database you run.
What were people paying Segment for?
Connectors. A hundred destinations, maintained by someone else. If the company uses twelve of those destinations, the pipe is the product, and replacing it means replacing twelve connectors or dropping them. Count the destinations before you cancel the pipe.
What do we build instead?
The two or three pipes the business actually uses, into systems the client owns, with a log they can read. That is automation, not a CDP. Business process automation is the right shape for it.
When does the pipe stay rented?
When the destination list is long, changes monthly, and nobody will maintain connectors. Keep the pipe. Still copy the customer record into a system the client holds, so the pipe is not the only copy.
What do we hand over?
We select the system, deploy it on infrastructure you control, connect it to the tools you keep, and write the runbook so your own team can operate it. Support after handover is optional. The rest of the map is in software you can stop renting; the engagement behind it is open-source business systems.
Name one process that still needs a person. We will tell you what a one-time build takes.
Contact us today