Lively Icons
Creator and maintainer
Icons that come alive. 1300+ open source motion icons — the toolkit every UI needs.
Building scalable, conversion-driven digital products that bridge strategy, design, and engineering. From Next.js and React to Stripe and Python — I craft seamless user experiences that grow businesses and delight customers.
Nick Jensen · Product engineering
I build developer tools, SaaS platforms, and practical AI workflows. I help teams turn a clear problem into something people can use.
An open source icon library I built for interfaces that feel alive.
Heart
Developer tools, open source projects, and a game about the work itself.
Creator and maintainer
Icons that come alive. 1300+ open source motion icons — the toolkit every UI needs.
Creator and maintainer
CLI-first secrets manager for dev teams with end-to-end encryption.
Creator and maintainer
Most advanced user testing suite for Claude Code + Chrome extension.

Creator
A startup management game about shipping features, growing a team, and keeping technical debt under control.
A clear problem, a useful first version, and room to grow.
Get close to the people using the product. Work out what matters, what’s getting in the way, and what a useful result looks like.
Start with a focused version people can actually use. Make the technical choices that fit the problem and leave room for what comes next.
Watch what happens in real use. Refine the experience, strengthen the foundations, and automate the work that keeps repeating.

My background spans marketing systems, product engineering, and technical leadership. I like making complex things easier to use, whether that’s a developer tool or the systems behind a growing business.
Notes from building products, working with AI, and figuring things out.
We are migrating TonyRobbins.com from Shopify Storefront API to native Stripe checkout. Not because Shopify is bad. Because we outgrew what it can do for us. Here is the 8-phase playbook we are using to do it without breaking anything.
I manage three engineering teams across two products with an AI system that runs daily standups, triages PRs, monitors production, and manages my inbox. Here is the actual architecture and what it gets wrong.
The Claude Code source code became publicly accessible. I spent a day reading it. The engineering is impressive, but there's an architectural blind spot: the system optimizes for content delivery but not attention management. Here are 7 concrete changes I'd make.
Tell me what you’re working on. We can figure out the next step together.