Knowledge ERP is the flagship product of Pelton Solutions, and the project I have put more years into than anything else I have built. I have been its architect and developer since 2016.
What it is
Knowledge ERP is inventory management software with customization at its core. Most inventory tools force a business to adapt its process to the software. Knowledge ERP works the other way around: the fields, the tracking, and the workflows can be shaped to match how an organization actually handles its stock.
Beyond detailed item tracking, the feature I get asked about most is check in and check out. Organizations that rent or loan equipment can see what is out, who has it, and when it came back. For a business whose gear leaves the building and needs to come home again, that visibility is the whole ballgame.
Why I built it
I founded Pelton Solutions in 2012 as a bootstrapped one-person company. My favorite kind of problem has always been the unoptimized business process, the thing a team does by hand or by spreadsheet that a well-built web application could take over. Inventory is full of those problems, and I had been working on inventory systems for years before I started Knowledge ERP.
I also wanted Pelton Solutions to be more than consulting. Knowledge ERP is the cornerstone of that plan: a real product the company owns, and the first step toward a larger suite of software.
Being bootstrapped means I wear every hat. I write the code, but I also handle the SEO, do the CSS and design work in Bootstrap, run the digital marketing across Google, LinkedIn, Facebook, and Instagram ads, and give the sales demos myself. It is a lot, but it means I hear directly from the people using the product, and that feedback goes straight back into development.
How it's built
For most of its life, Knowledge ERP ran on a custom PHP framework. That was a reasonable choice for a solo developer who knows PHP inside and out; I have been writing it professionally since 2007, and a custom framework gave me complete control.
It also became the product's biggest constraint. A custom framework means every new developer has to learn a codebase that exists nowhere else, and every capability a mature framework ships for free has to be built and maintained by hand.
So I am migrating Knowledge ERP to Laravel and FilamentPHP. This is the most interesting engineering work I have done on the product: taking a decade of accumulated features and moving them onto a standard foundation without breaking what customers rely on. The payoff is scalability and, just as important, onboarding. A Laravel developer can be productive in Knowledge ERP without months of ramp-up on a bespoke framework, which is exactly what the product needs as Pelton Solutions grows beyond one developer.
Where it's going
The Laravel and FilamentPHP migration is the current focus. Once the product sits on that foundation, adding developers gets easier, shipping features gets faster, and Knowledge ERP can anchor the suite of software I want Pelton Solutions to become.
If you want to see what else I have built, have a look at my projects. And if your business has an inventory process that a spreadsheet is barely holding together, get in touch. That is exactly the kind of problem I like.