How Medjik Software’s Founder Built Inventory SaaS from Warehouse Frustration

I work as a warehouse worker for an Italian company. We used to do the inventory on paper, and later we moved to Excel. Excel was better, but I still didn't really like using it. If someone asked me how much stock we had, I usually had to go to the shelf and check it myself. We also had a lot of different products and colors, so it was easy to lose track of things. After doing this for a while, I started thinking that there had to be an easier way. I had already been learning programming at home, so I thought I could try to make something myself. At first, I only wanted a simple program for the warehouse. I wanted to be able to open it and immediately see what we had in stock, what we used, and what was getting low. I started building it for myself and used it at work for months. I kept adding and changing things when I found something that was annoying or could be easier. That's basically how Medjik Inventory started.

I haven't used many growth tactics yet because I'm still at the early stage of growing Medjik Inventory outside my company. The first thing I did was show the software to my boss and my coworkers. They started using it at the company, and that gave me the first real proof that the product was useful to other people, not just me. That worked well for me because I could see how people actually used the software in their daily work. I also got the chance to fix things and improve features based on real use instead of just guessing what people might need. I haven't had a growth tactic completely flop yet, mainly because I haven't seriously started marketing the product outside the company. I'm only now starting to focus on getting Medjik Inventory in front of other businesses. I'm confident about testing different ways to reach potential users, but I also know that the results may be different outside my current workplace. For me, the next important step is getting real users from other companies and learning from that experience.

So far, I haven't had many complaints from people using MEdjik Inventory. Since the software is still mainly being used inside my company, most of the feedback has been about things that could make the daily work easier rather than actual problems with the product. In the first version, I left out some features that I later realized were important. For example, barcode scanning was missing, along with a few other smaller features that would make working with the inventory faster. I added these features over the past few days and am counting on improving the system based on how it is actually being used. I think this is one of the advantages of building the software myself and using it in a real warehouse. When something is annoying or takes too many steps, I notice it immediately and can work on it. So far, I haven't received any serious negative feedback. Now, I'd like to get some feedback from people outside my company too, because they might notice things that I don't.

One thing I think people get wrong about inventory software is that they often see it as something that is only useful for big companies with huge warehouses. Some people I know even think inventory software is unnecessary or pointless, especially if a company uses Excel or keeps track of things manually. I understand why they think that. If you only have a small amount of stock, checking a few things in Excel doesn't seem like a big problem. The problem becomes more obvious when there are many different colors, products, warehouses, or people working with the same stock. I see this difference every day at work. Before building Medjik Inventory, I often had to go to the shelf myself just to check how much of something we had. Now the information can be seen in the system without having to physically check everything. I think people sometimes underestimate how much time these small tasks add up to. For me, inventory software isn't about making things complicated. It is about making something that is already part of the daily work faster and easier.

I haven't planned everything for the next 6-12 months yet. Right now, my first goal is to get Medjik inventory in front of more businesses and see how people outside my company use it. I want to find out what they like, what they find difficult, and what features they actually need. Based on that feedback, I'll decide what to improve and add next. I also want to keep improving the existing features and make the software easier to use. For now, I'm more focused on getting real users and learning from them than trying to plan every detail in advance.

24 people are currently using the private beta version of Medjik Inventory.

I started building Medjik Inventory from scratch as a self-taught software developer. I didn't have a professional background in software development before this and few game scripts projects. I've been interested in technology since I was a child, and I always liked seeing what people could build with computers. I started learning at home and slowly worked on different small projects. I made my first website, then built my first small programs. Later, I started writing scripts for games using Lua, which also taught me a lot about programming and problem solving. My warehouse experience was also important for Medjik Inventory. I already knew the problems because I was dealing with them myself every day at work. So while I was new to building SaaS products, I wasn't new to the problem I was trying to solve.

I think my biggest mistake was working on the product for too long without getting enough feedback. At the beginning, my main goal was simply to replace Excel and make my own work easier. Because I was using the software myself, I kept adding things that I personally thought were useful instead of asking other people what they needed. I also went through about eight different design ideas before I found a look that I was happy with. Looking back, some of that time could have been saved if I had shown the product to more people earlier. The biggest thing I learned is that getting feedback early is important. Even if the product is not finished, other people can notice problems or have ideas that I would never think of myself.