I spent two days checking whether my own marketing was true. Three claims weren't.

I'm non-technical so I built Crestfolio by directing Claude Code.

This week I stopped shipping features and started verifying claims as I continue to gain new customers. I picked the three differentiators my whole competitive positioning rested on. Things I'd written into strategy docs, comparison pages, and a directory listing. Then I had Claude read the actual codebase and tell me if they existed. None of three did.

The findings were a bit frustrating, as I had previously done a full audit/smoke test of each feature, then built out a full users "how to" guide. Not "partially implemented." Not "needs polish." The database column wasn't there. I'd been describing a product that I assumed I'd completely built out.

Here's the part that really stung. I'd spent a week researching a few competitors, based on some feedback from a user about what that product did and didn't do. Every claim I made about them, I sourced from their own help docs, website and verified each. Every claim about my own product, I had tested in some fashion, but I also made assumptions.

It turned out that I was more rigorous about their product than my own. So I decided that I needed to build a gate. One table, two columns: Verified and Claimed. Now, nothing goes into marketing copy unless it's in the Verified column with a file path next to it.

I was eleven rows into it and four of them say DOES NOT EXIST. If you're building solo with AI, you can ship faster than you can remember what you shipped. The docs drift from the code and nothing tells you. The bugs that hurt aren't the ones users report. They're the ones nobody's hit yet.

Anyone else doing verification passes on their own claims? Curious how you keep docs and code honest.