BLANE WARRENE shares insights on the latest trends and challenges in AI development.
APR 22, 2026
What changes when product leaders can ship the things they spec
For most of my career, there has been a predictable distance between the product I could describe and the product I could build. I had the vision. Someone else had the compiler. That gap defined the tempo of every roadmap I have ever owned. Now, with AI development, the gap is closing fast.
Three weeks ago, I released Notes2Notion, a macOS utility that exports Apple Notes into Notion-importable Markdown with full attachment support. I built it because I needed it. I have lived in Apple Notes for years, but recently needed everything in Notion, and the export path simply does not exist. Apple Notes has no clean Markdown output. Most workarounds abandon your attachments along the way. So I built the thing.
TLDR: GitHub URL at the bottom!
What makes it worth writing about is not the utility itself. It is how it got built.
What is Notes2Notion?
Notes2Notion connects to Apple Notes via AppleScript, extracts HTML and attachments, converts the content to clean Markdown, and packages everything into a ZIP that Notion imports natively. It started as a CLI and grew into a native macOS GUI with folder selection, progress tracking, and a batch mode for automation. It ships with YAML frontmatter for titles, dates, and folder structure. I tested it against my own 6,000+ note library. This was important to validate my AI development, and it held up.
I built it with Claude Code as my development partner. I am a product leader, not a full-time engineer. In a prior era, this project would have sat on a Notion page titled “things I would build if I had a team.” Instead, it sits on GitHub, open source and shipping.
AI Development from Prototype to Active Roadmap
Then the second half of the story began, the part I want operators and builders to sit with for a moment.
Feedback came in. I opened a public backlog. The most requested enhancement was a time-based filter, last 30, 60, and 180 days, so users could wire Notes2Notion into recurring automations rather than treating it as a one-time migration. Yesterday, I shipped it.
Three weeks. Launch community feedback to release the enhancement. One person. Without hiring, without sprint planning, without a handoff.
Here is what I want leaders to take from this:
Product Leaders Can Ship
The binding constraint on internal tooling, personal utilities, workflow glue, and the long tail of “we should probably build that” ideas is no longer engineering capacity. It is clarity of specification. If you know exactly what the product should do, you can now get to a working version faster than you can get a meeting on the calendar to discuss how to build it.
That has consequences for how we staff, where we allocate engineering leverage, and what we reasonably ask of leaders who do not write code for a living. The organizations that internalize this shift first will quietly compound their advantage, one shipped utility at a time.
I will keep building in public. The Notes2Notion repo is open, the backlog is visible, and contributions are welcome.
If you are a product or operations leader who has been circling an idea you never had the resources to ship, the resources have changed. Get started.
Notes2Notion is available on GitHub: blanewarrene/Notes2Notion
Leave a Reply