How AssetControl Cloud Prioritized Accountability and Simplicity to Drive Growth

The company I work for (KeyTracker) deals with lots of different kinds of organizations and businesses. From the military to car dealerships and security firms. I kept seeing the same problem play out across different businesses. Teams were relying on spreadsheets, whiteboards, handwritten notes, or disconnected systems to track their assets and keys. It only worked until it didn’t. Items went missing, no one knew who had what, audits became stressful, and simple tasks like finding out where certain keys or assets were became guesswork. The real turning point was seeing teams waste time chasing information that should have been instantly available. It isn't just inefficient; it creates risk, especially in environments where accountability matters. There were other solutions out there, but these are convoluted or required time and effort to get set up and operational. So I set out to create something simple, reliable, and accessible from anywhere, at a price point that works for even the smallest of businesses. Which ultimately led to me building AssetControl Cloud, a system designed to give individuals and teams greater visibility, control, and confidence in day-to-day operations.

One tactic that worked well was actually speaking to our potential customers either on the phone or via online meetings. Walking them through the software in real time and showing exactly how it could work for their specific setup made a huge difference. It turned abstract features into something tangible, and they could immediately see the value for themselves. It wasn't just all about selling; it showed me new insights into what customers wanted and how the software could work or be adapted to work in different scenarios that I hadn't originally accounted for. From these conversations, I learned and understood their challenges and how my system could fit into their daily operations. What I found that flopped was un-targeted and broad campaigns early on. Trying to cast a wide net across different industries with the same generic message just ended up diluting the marketing. It became too generic and wasn't resonating with anyone in particular.

Most common complaints that tended to become friction points were small, things that break the flow of what should, in theory, be simple actions. For example, I have had an issue with selections not persisting across paginated pages and validation errors on inputs that were filled in correctly. Although individually they were small, they would quickly frustrate users. I handled this by tightening error reporting and the speed at which these minor bugs were resolved, treating them as a priority fix rather than just edge cases. This also meant improving the whole validation logic and moving the complex logic into smaller classes and functions, making them easier to manage and maintain. The main shift was recognising that, although the usability bugs were small and somewhat trivial to me, to a paying customer, these were real pain points which inevitably impact trust. Fixing them quickly and transparently has made a noticeable difference in user confidence.

Most people underestimate how critical accountability is in this space. They assume that asset tracking is just about knowing where things are, but in reality, it is also about knowing who has them, when they took them, and then being able to prove it. A lot of solutions just focus on basic inventory, but I have found that this starts to fall apart in real-world environments, especially when multiple sites and teams are involved. The moment something goes missing or an audit happens, 'roughly tracked' just isn't good enough. What’s then often missed is that this isn't just an operational problem; it can quickly become a risk and compliance issue. Without the clear accountability, businesses and organizations can expose themselves to loss, downtime, and even liability. The real value isn't just the tracking of assets, but also the reliability through audit trails that can be trusted and relied upon.

Over the next 6–12 months, the focus is on deeper integrations that make AssetControl Cloud part of a team’s everyday workflow rather than a separate system they have to check. A big area is real-time alerts and notifications. I will be integrating directly with tools like Slack and Microsoft Teams so users can receive updates where they already work. This includes things like overdue assets, upcoming maintenance, or key activity events, all pushed instantly instead of relying on emails or manual checks. We’re also looking at tighter integration with Microsoft Intune, allowing better visibility and control over IT assets alongside operational ones. This bridges the gap between physical asset tracking and device management. The goal is to reduce friction, increase visibility, and make asset management something that runs in the background.

Over 9,000 different assets and keys tracked daily within the software.

I have spent the last 10 years working in the security industry, specifically key control and security - working for KeyTracker Ltd. In those 10 years, I have honed my skills within PHP and full web stack knowledge. I had previously worked on a more basic iteration of AssetControl, which had various users across different industries and sectors, called Key Control Software, which was primarily aimed at the tracking of keys. So I had an idea of what would be needed in a software and what end users wanted in a software, which allowed me to build the product quicker when starting out from scratch.

The biggest mistake early on was trying to build for too many use cases at once. I aimed to make the product flexible enough for every industry and scenario, which led to overcomplicating certain areas and slowing down my decision-making. In practice, that meant features that were technically powerful but not always intuitive for the core users we were trying to serve. It also diluted the message because I was trying to speak to everyone and didn't resonate overly with anyone. The lesson was to focus more tightly on real-world use cases and let those drive the product forward. Prioritising simplicity, clarity, and solving specific problems has had a much bigger impact than trying to cover every edge case upfront.