Case study
An engineering function built from the operation out
ERP, a call-center CMS, an ATS, a knowledge base and an executive cadence — stood up because the operation had outgrown informal tools.
Before
A services operation without an engineering function to match its size. Critical work lived in inboxes, shared sheets and the memory of a few people.
Friction
There was no internal platform for the work the company repeated every day: hiring flow, call-center knowledge, operational reporting, and a single picture for leadership. Every new initiative started from zero and ended in another tool.
Result
An engineering area stood up with internal systems — ERP, call-center CMS, ATS, knowledge base — plus KPIs, OKRs and a reporting cadence leadership could actually use. Adoption mattered more than the catalog of systems.
Building internal tools is easy to romanticize and easy to waste. The constraint was not “can we build it.” It was whether the operation would leave the inbox and the sheet.
The sequence mattered. First the team and the cadence, so there was someone to own what got built. Then the systems that removed a daily pain people could name: hiring, call-center knowledge, the executive picture. A platform without that pain is a side project.
The result I care about in this kind of case is not the list of acronyms. It is that the company could see its own work without asking a single person to remember it.