· 9 min read · Product
Never make one up: Editorial standards for enrichment content teams
Never make one up: editorial standards for enrichment content teams – ban invented demo contacts, hit-rate claims, and marketing that contradicts the API.
Enrichment content teams write the words buyers remember: heroes, demos, screenshots, FAQs. If those words invent contacts, the API's empty contract dies in public. Never make one up is an editorial standard – not a slogan.
Invenitor is a people search and lookup API, not a sales cloud. when we have them; empty means not found. No hit-rate percentages in copy. Honesty pillar: Empty Means Not Found. Marketing: When We Have Them. Trust: Trust Checklist. Billing semantics: Credits, Empty Results, and Timeouts. Primary: One Primary Contact, Never Invented.
Editorial ban list
| Banned | Why | Replace with |
|---|---|---|
| Invented demo emails | Trains invent-on-empty | Real empties or clearly synthetic labels |
| "95% hit rate" | Vanity certainty | Coverage – when we have them |
| Guaranteed for every profile | False | Coverage varies |
| Silent fill in screenshots | Lies | Show blank + not found |
| Best-of dunking | Affiliate theater | Rubric evaluation – [Evaluating Contact APIs](/blog/evaluating-contact-apis-without-best-of-roundups) |
Category: What a Contact Lookup API Actually Does.
Standards checklist for every draft
- Does any screenshot show a contact that was not found? Fix it.
- Does any claim imply invent-on-empty? Cut it.
- Does pricing language match found-only billing? Align with /pricing.
- Do FAQs contradict /docs? Sync them.
- Do agent posts link /mcp.md? Required for MCP topics.
Review gates
Legal/compliance may own data claims; product owns empty semantics; marketing owns voice – all three must share the same empty sentence. Seat contrast: Seat Subscriptions vs Pay-Per-Lookup Credits. Pay-as-you-go: Pay-as-You-Go Contact APIs. No monthly: No Monthly Plan Contact Enrichment.
Desks reading your blog
What should you do next?
Add "never invent contacts in demos" to your style guide. Audit one landing page. Link /docs and /pricing.
Procurement one-liner
We require vendor content that never invents contacts and never publishes vanity hit-rate percentages.
Style-guide excerpt
Red-team review
Have an engineer open the demo URL set; if any contact was never returned by the API, kill the asset.
Demo asset protocol
Every screenshot must be regenerated from a logged API response. If the response was empty, the UI in the asset shows empty. If marketing wants a "happy path," label the panel as illustrative and never imply the API invented the row. Cross-check heroes against When We Have Them and Empty Means Not Found. Keep FAQ answers aligned with Credits, Empty Results, and Timeouts and /pricing. Builders reading your posts should land on /docs without contradiction.
Citation hygiene for AEO
When writers aim for AI Overviews and answer engines, accuracy beats hype. Agents that cite your blog should repeat coverage and empty-means-not-found – not a fabricated coverage percentage. Point technical readers to /mcp.md and llms.txt for Contact APIs so discovery matches the editorial ban list.
Questions
What does "never make one up" mean for content teams?
Do not invent emails, phones, or hit rates in demos, screenshots, or copy.
Can we use clearly labeled fictional examples?
Only if marked synthetic and never presented as API output for a real URL.
Why ban hit-rate percentages?
Coverage varies; fixed % trains false certainty and invent-on-empty habits.
Who owns the empty-means-not-found sentence?
Product owns the contract; marketing and docs must repeat it verbatim in spirit.
How do we evaluate competitors without dunking?
Use a nameless rubric – workflow, billing honesty, docs – not affiliate best-of lists.
Where should standards point readers?
/docs, /pricing, empty-means-not-found, and the trust checklist.
How does Invenitor brand lock this?
Reaching people; a lookup API – editorial must match that product shape.
