I Built the System Before the System Arrived

Before the ERP arrived, I had already built one.

Not the same scale. No vendor, no project manager, no six-month implementation. Just me, a centralized database, a few custom forms on a local network, and a clear picture of what the procurement team actually needed.

The company did not ask me to build it. Nobody handed me a spec. I just understood the problem from enough angles that building it was faster than waiting for someone else to solve it.

That is what people miss when they look at a background like mine. Mechanical engineering. Electrical engineering. Automation. Programming. Strategy. It looks like a list of credentials. It is not. It is a set of lenses that all point at the same problem at the same time.

When I sat with the procurement chaos, I did not see a software problem. I saw a workflow problem that needed a database solution that needed a network to run on that needed a UI people would actually use. A software developer would have built the database. An IT person would have set up the network. An ops consultant would have mapped the workflow. I did not need to hand it off between three people. I could see it whole.

That system ran for years before the ERP replaced it. When the ERP came in, the transition was smoother than anyone expected — because the team had already learned to trust a system.

I did not wait for the solution to arrive.

I built it.