As a Software Asset Management (SAM) Service Delivery Director, my world has always revolved around compliance, cost control, and process efficiency. But as software ownership models evolved and the market shifts towards low-code, AI-powered, and SaaS-driven ecosystems, it became clear that organisations would increasingly build and own their own software—bringing with it a whole new level of licensing complexity.
We knew this change was coming. Cloud adoption had already been driving inefficiencies and creating monthly budget waste, making it difficult for organisations—regardless of size—to maintain visibility and control over software costs. Meanwhile, with service resources becoming more limited, the need for flexible, on-demand expertise was becoming a business-critical requirement.
Having navigated the challenges multiple times previously with Infraware, eventually being part of the core team creating SAM Sentry, which was successfully sold to Software One, I was no stranger to the challenges of software creation, so when Appstrato set out to build software to automate elements of our internal processes, I had the benefit of prior experience. But I also knew just how challenging the road ahead would be.
The Synergy Between ITAM Process Creation and Software Development
At first, software development can feel like an entirely different discipline. But I quickly realised that the structured thinking required in ITAM process creation, understanding stakeholder needs, mapping workflows, and designing step-by-step operational processes, has strong parallels to software development.
Both disciplines require a methodical approach:
- Breaking down complex requirements into logical steps
- Designing processes for efficiency and scalability
- Engaging with stakeholders to ensure usability and effectiveness
With this perspective, the leap from SAM process development to software creation felt far less daunting. What originally had seemed like a foreign discipline soon became an exercise in logic, efficiency, and stakeholder engagement.
Keeping Focus on Core Requirements and Avoiding Scope Creep
One of the key challenges was staying disciplined around requirements. In the world of SAM and ITAM, every edge case can feel like an essential component. It’s tempting to continuously expand functionality, but software development requires prioritisation—building the must-have features first, while resisting the temptation to accommodate every possible scenario.
I learned that trying to do everything leads to doing nothing well. Overcomplicated software not only delays delivery but also results in a system that tries to be everything to everyone but serves no one effectively.
Translating Visuals and Ideas into Meaningful Development
Perhaps the most frustrating part of the process is communicating the vision in a way that developers could execute. I always have a clear picture in my mind of how the software should function, but translating that into developer-friendly documentation, wireframes, and logic can be another story entirely.
What seemed intuitive to me often required layers of explanation and iteration before becoming tangible. It can be like learning a new language—one where precision, clarity, and technical feasibility determine how close the final product aligns with the original concept.
Balancing Technical Possibilities with Business Needs
Reality check: Not everything you envision is technically feasible, or at least not within budget or timeline constraints. I found myself constantly negotiating between idealistic solutions and practical realities.
This meant:
- Revisiting core objectives regularly to ensure alignment with the end goal
- Identifying when compromises were necessary to keep the project viable
- Balancing innovation with what was actually deliverable
Every software development project is a trade-off between time, cost, and functionality. Learning where to draw the line is a skill in itself.
Lessons Learned
Reflecting on this journey, a few key takeaways stand out:
- Process First, Automation Second – Ensure that underlying processes are well-defined before attempting to build software.
- User-Centric Design Matters – A solution is only as valuable as its usability to stakeholders.
- Resist the Urge to Overcomplicate – Simplicity leads to functionality; scope creep leads to failure.
- Communication is Everything – Translating ideas into actionable development steps is a skill that requires constant refinement.
Building software to support SAM and ITAM services has been an eye-opening experience. While I approached it with expertise in the domain, I quickly learned that software development is a discipline of its own, requiring patience, adaptability, and a willingness to rethink established ways of working. But despite the challenges, the potential to transform inefficient manual processes into seamless, automated workflows makes the journey worthwhile. Would I do it again?….. absolutely!
The Next Evolution: A Full-Service Ecosystem
The best part? We’re just getting started.
As Appstrato evolves, we’re expanding beyond software automation—building a full-service ecosystem that welcomes industry service and technology partners onto the platform.
Soon, we’ll be introducing software development and AI specialists, further strengthening our ability to support organisations with the tools, expertise, and automation capabilities they need to manage the new era of software licensing.
This isn’t just about fixing internal processes—it’s about creating a flexible, scalable, and on-demand resource model that meets the growing demands of modern software environments.
What’s Next?
I’m excited to start welcoming industry service and technology partners onto the platform and build a thriving ecosystem for SAM, ITAM, and software automation.
If you’re a service provider, technology partner, or industry expert, now is the time to get involved—the landscape is changing, and we’re shaping its future together.
Let’s connect. The next wave of ITAM transformation starts here.
