CEP might have continued on its trajectory longer if not for a seismic personnel change: the engineer who built and maintained the 15-year-old codebase announced his retirement. As a team of one, this engineer had been extremely valuable to the organization. Still, his retirement forced CEP to recognize that he had also become a single point of failure.
Early exploration helped CEP recognize that it needed to…
Simplify the command-line-driven processes for accessing data so that analysts could onboard more quickly.
Rearchitect its internal codebase so it could scale operations.
Create documentation so that the system would be easier to maintain, improve, and adapt for people who don’t have deep institutional knowledge.
CEP engaged with a partner that laid out potential SaaS and open-source products that it could integrate with its existing system––hundreds of pages of potential products, in fact. So many that the CEP team wasn’t sure where to start.
So they turned to TXI.