In hardware-enabled SaaS, “looks great on the screen” is not a business outcome, but an expense until proven otherwise. Yes, it is hard to tie a specific feature to revenue in the short term. But it is non-negotiable to make it traceable in the long term. Here is the rule: Every line of code is a liability (cost) until it proves it is an asset (value). If a capability cannot be traced to a New Revenue Stream, it must be traced to a Financial Outcome:

This diagram illustrates a pattern I see in hardware-enabled SaaS initiatives. You start with initial requirements and an (optimistic) roadmap. Then reality shows up: ❌ The field data disagrees. ❌ Ops workflows change. ❌ Customers/stakeholders ask for “just one more adjustment." ❌ The team constantly refactors APIs, reshapes the data model, rewrites logic, etc. Each iteration does improve the product… …but it also creates iterative debt: leftover code paths, half-migrated schemas, compatibility layers, rushed fixes, duplicated logic.

In a properly managed environment, the delta between your Infrastructure-as-Code (IaC) and your actual cloud environment should be zero. When your monitoring solution triggers a drift alert (you do have automated drift detection, right?), it typically points to one of two scenarios: 🔴 Scenario A (The Rogue Operator): Someone bypassed the governance and manually modified resources in the AWS Console. This is problematic as manual actions are error-prone and hard to track (and even harder to revert).

Recently, I created a simple solution that automatically turns the hall’s light on and off. Yes, I know, nothing fancy, but please don’t stop reading just yet. I could have bought a lamp with that functionality built in, but that simple solution had several shortcomings: Searching for a lamp that matches the hall design. Fitting the new lamp in the same spot. What about my other lamps? Upgrading a single piece of hardware does not improve the overall user experience, as legacy devices remain non-smart.

There are various cases when you need to disconnect a specific device from your IoT system. An attacker might have compromised that device. Maybe the device started behaving strangely and you want to isolate it until you investigate. Or perhaps your customer stopped paying and you need to suspend service until they clear the debt. Here’s the thing: disconnecting a device from AWS IoT Core is not as simple as one might think.

Here’s the thing - I didn’t plan to become a full-stack IoT developer. It just happened, one AWS service at a time, one project at a time, one challenge at a time… It Started with AWS IoT Solutions My journey began with designing and building AWS IoT solutions for real-world deployments. I wasn’t just reading documentation - I was experimenting, connecting thousands of devices to the cloud, managing their lifecycle, and ensuring secure communication at scale.