“`html
Background
I started out as a systems analyst evaluating SaaS platforms for a healthcare company. That meant building evaluation frameworks, running pilots, and making the case to stakeholders who didn’t want to hear about edge cases — until an edge case became their problem. I learned early that the gap between what a tool does in a demo and what it does under production load is where most software decisions go wrong.
From there I moved into the VP of IT Operations role at a 400-person logistics firm, where I owned the entire tech stack. Every renewal, every migration, every integration that broke on a Friday afternoon — that was mine. I was the person finance called when a subscription renewed at a 30% increase, and I was the person the CEO called when something went down. That experience changes how you evaluate software. You stop caring about the feature roadmap and start caring about uptime, admin controls, escalation paths, and what it actually costs to get out of a contract when a tool stops working for you.
I started writing reviews because I kept running into the same problem: the sites that ranked highest in search were written by people who tested tools in a sandbox for a weekend and called it a review. I still consult part-time on SaaS evaluations for organizations going through platform decisions, so this isn’t background I’m pulling from memory — it’s work I’m doing right now. I write for the IT manager, the ops leader, the technical founder who has to pick the tool, deploy it, and answer for it when it breaks.
What I Cover on Tech Watch Review
My focus is enterprise-informed SaaS and business technology — productivity tools, security software, cloud platforms, and the infrastructure decisions that actually matter to people running teams. Every review I publish includes the admin and operations perspective, not just the end-user experience. I test on the plan tier that reflects real deployment conditions, I note the specific version I evaluated, and I document support interactions including response times and escalation quality. I always address migration cost alongside subscription price, because comparing sticker prices without switching costs is how organizations end up locked into tools they hate.
I don’t review enterprise software based solely on a free trial or a vendor demo. I don’t write generic roundups — if I’m comparing project management tools, I’m comparing them for a specific use case and team type. I won’t recommend a tool without addressing what it costs to switch away from what you’re already using. And I won’t bury security, compliance, and admin features at the bottom of a review as an afterthought — for most of my readers, those aren’t secondary considerations.
Credentials & Experience
- VP of IT Operations at a 400-person logistics firm — owned full tech stack, all procurement, renewals, and infrastructure decisions
- Systems analyst at a healthcare company — SaaS platform evaluation, vendor assessment, and stakeholder reporting
- 9 years in enterprise IT procurement and operations
- Active part-time consultant on SaaS evaluations for organizations in active platform selection
- Based in Chicago
Get in Touch
If you’re evaluating a tool and want to know whether it’s been covered here, or if you have a review request that fits the site’s scope, you can reach me through the contact page. Vendor inquiries are welcome, but sponsored content is always disclosed — that’s not negotiable.
“`