Why Every Marketing Claim Should Have a Code Citation

During a routine audit of my NestForge Pro landing page, I found 6 claims that were either false or unverifiable. Not lies — things that were true at some point but drifted as the code evolved.

The Problem

Developer products have a trust problem. Developers check your repo. They read your code. They compare your marketing claims against what actually ships. And when they find discrepancies, they leave.

The Claims Registry

I built a simple pattern: every marketing claim maps to a code evidence entry with a status.

```

Claim: "227 passing tests"

Evidence: `pnpm test` output, CI pipeline logs

Status: VERIFIED

Last checked: 2026-04-01

```

This isn't a testing framework. It's a product process. Before any claim goes on the landing page, it needs a code citation.

How AI Agents Drift

When you're building with AI, claims drift faster than manual development. The AI doesn't track what the landing page says — it just writes code. Features get renamed, APIs change, modules get restructured. Without explicit verification loops, your marketing diverges from your product.

The Fix

I built a modes system into my AI workflow:

- **Leadership mode**: strategic decisions, no code

- **Product mode**: feature scoping, user stories

- **Engineering mode**: implementation

- **Marketing mode**: claims verification, copy review

Each mode has different rules about what the AI can and can't do. Marketing mode requires checking every claim against the codebase before approving copy.

Build Your Own

The pattern is simple: create a `claims-registry.md` file. For every claim on your landing page, add an entry with the claim text, code evidence, and verification status. Run through it before every deploy.

Developers deserve honest marketing. The claims registry is how I keep myself honest.

See it in action at [nestforge.dev](https://nestforge.dev).