ABOUT PROMPT KEEPER

built by someone who needed it

I’m the cofounder of a post house. We work on both long-form and commercial projects, and over the past couple of years AI tools have become a genuine part of how our creative teams works — not a novelty, but a real part of the creative process.

That raised a question I couldn't find a good answer to: if we ever needed to demonstrate that our use of AI was deliberate and documented — for a client, an insurer, or a legal conversation — what would we show them? The honest answer was nothing. Our prompts lived in chat windows, Word docs, and memory.

I built Prompt Keeper to fix that. The goal was simple: make capturing prompts so frictionless that it actually happens — without asking creatives to change how they work or introducing steps that slow them down.

What surprised me was the feedback from beta testers. The legal case resonated with producers and owners, but the creatives were excited about something else entirely — having a record of their own process. A way to look back at what they'd made and remember how they got there. That turned out to be just as valuable as the documentation angle, and it's shaped how I think about where Prompt Keeper goes next.

Prompt Keeper was built with the help of AI coding tools. I'm an editor at heart, not a software developer — which felt like the right kind of irony for an app about AI workflows.