I’m a founder with over a decade of operations and project management. I know how to build systems, run teams, and get things across the finish line. And I still hit the same wall every website owner hits when something looks wrong and the tools give them nothing. That’s why I built Loupely Lens.
Built by someone
who hit the same wall.
I’m a founder with over a decade of operations and project management. I still hit the same wall every website owner hits when something looks wrong and the tools give them nothing.
Join the Loupely Lens waitlist7-day free trial · No card required
Capable everywhere.
Invisible here.
I’ve spent over a decade running operations, managing teams of 3 to 500, delivering 98% of projects on time and under budget, and building the systems that kept things moving when nothing else did. Project management has been the thread through every role I’ve ever held.
And I was still regularly told, in ways both direct and indirect, that software wasn’t for me.
Not because I wasn’t capable. Because I couldn’t see what was happening. I’d change the button color in my theme settings and refresh. Still wrong. I’d add a CSS rule. Nothing moved. I’d open the browser inspector and find a panel full of rules with lines crossed through half of them, and I had no idea which one was winning or why. The browser had the complete answer sitting right there. It just never told me what it was.
I’d do what anyone does. I’d Google. I’d post in forums. I’d hire developers who would ask questions I couldn’t answer about a system I couldn’t read. And I’d wonder whether the problem was the software or me.
It was never me. The visibility layer didn’t exist. So I built it.
“There were moments I sat at my desk, completely stuck, staring at a panel of crossed-out CSS rules with no idea which one was winning. I’d changed the right thing. The browser knew exactly why it hadn’t worked. It just wouldn’t tell me. That specific helplessness is exactly why I built Lens.”
Teams of 3 to 500. Systems that had to work. 98% of projects delivered on time and under budget. Project management has been the thread through every role.
A science degree, not arts. Grounded in data analytics, psychological research, and evidence-based management. BA, Psychology · Ithaca College. The systems thinking came before both.
Rollback checkpoints. Staged rollouts. Diagnostic-first before features. Log-first testing. These are professional engineering disciplines translated into operating systems for people who run things without writing code.
Led product and operations for a B2B SaaS platform. 2,000+ users. 95% adoption on system rollouts. That’s where I learned what good diagnostic infrastructure looks like from the inside.
Six years building and running operations for fast-growing clients across industries. CRMs, LMS platforms, payment systems, email funnels, and process automation, all of it owned end to end.
About building software with no engineering background. What it actually looks like when the tools fail and you have to figure out why. Honest, specific, no performance.
Loupely Lens is the visibility I needed and didn’t have.
It doesn’t fix CSS for you. It shows you where to look, in real human terms, so you stop guessing and the developer you hire has something real to work from.
Click on what looks wrong. Lens reads the full CSS cascade behind it, shows you what rule is winning and why every competing rule lost, and gives you the specific next step: a ready-to-paste CSS override or a complete developer handoff package. Works on any website in Chrome.
CSS properties captured and analyzed on every element pick
Verdict templates covering the most common CSS failure patterns
Days free to try, unlimited diagnoses, no card required
Per year for unlimited Lens diagnoses on any site in Chrome
I built this for the website owner who changed the right thing and couldn’t see why it didn’t work.
I know what it feels like to be capable in every room except this one. To run teams, deliver projects, build systems, and still sit in front of a CSS panel full of crossed-out rules with no idea which one is winning.
You weren’t confused because you couldn’t think. You were confused because the browser wasn’t telling you what it already knew. That’s not a skill gap. That’s a missing visibility layer.
You’re looking at a website built by someone who was told software wasn’t for her. The Chrome extension you’re reading about, the diagnostic infrastructure underneath it, the triage page that tells you in real human terms exactly what’s in the way of your CSS change. That’s what happens when the person who needed the tool is the same person who built it.