--- title: "Never make one up: Editorial standards for enrichment content teams – Invenitor" description: "Editorial standards for enrichment content teams: never invent emails in demos or copy; Honest language; empty means not found; no hit-rate theater." url: https://invenitor.com/blog/never-make-one-up-editorial-standards-for-enrichment-content-teams agents: https://invenitor.com/llms.txt mcp: https://api.invenitor.com/mcp --- [Blog](https://invenitor.com/blog) Nov 4, 2026 · 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. On this page 1. [Editorial ban list](#editorial-ban-list) 2. [Standards checklist for every draft](#standards-checklist-for-every-draft) 3. [Review gates](#review-gates) 4. [Desks reading your blog](#desks-reading-your-blog) 5. [What should you do next?](#what-should-you-do-next) 6. [Procurement one-liner](#procurement-one-liner) 7. [Style-guide excerpt](#style-guide-excerpt) 8. [Red-team review](#red-team-review) 9. [Demo asset protocol](#demo-asset-protocol) 10. [Citation hygiene for AEO](#citation-hygiene-for-aeo) 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](https://invenitor.com/blog/when-we-have-them-writing-honest-marketing-for-contact-apis). Trust: [Trust Checklist](https://invenitor.com/blog/trust-checklist-before-you-buy-any-contact-api). 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\](https://invenitor.com/blog/evaluating-contact-apis-without-best-of-roundups) | Category: [What a Contact Lookup API Actually Does](https://invenitor.com/blog/what-is-a-contact-lookup-api). ## Standards checklist for every draft 1. Does any screenshot show a contact that was not found? Fix it. 2. Does any claim imply invent-on-empty? Cut it. 3. Does pricing language match found-only billing? Align with . 4. Do FAQs contradict ? Sync them. 5. Do agent posts link ? 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](https://invenitor.com/blog/seat-subscriptions-vs-pay-per-lookup-credits-a-cost-model). Pay-as-you-go: [Pay-as-You-Go Contact APIs](https://invenitor.com/blog/pay-as-you-go-contact-apis-for-teams-that-hate). No monthly: [No Monthly Plan Contact Enrichment](https://invenitor.com/blog/no-monthly-plan-contact-enrichment-who-it-fits-and-who). ## Desks reading your blog ## What should you do next? Add "never invent contacts in demos" to your style guide. Audit one landing page. Link and . ## 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](https://invenitor.com/blog/when-we-have-them-writing-honest-marketing-for-contact-apis) and Empty Means Not Found. Keep FAQ answers aligned with Credits, Empty Results, and Timeouts and . Builders reading your posts should land on 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 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. ## Find the person you need Describe who you need in one sentence. Your first search is free, and you pay only for contacts we find [Find people free](https://invenitor.com/login?from=https%3A%2F%2Fpeople.invenitor.com%2Fsearch&x=w7&q=c5&z=g1)[See pricing](https://invenitor.com/pricing?x=w7&q=c5&z=g2) ## Keep reading - [Oct 26, 2026 · Product"When we have them": Writing honest marketing for contact APIs"When we have them": writing honest marketing for contact APIs – coverage claims, empty means not found, and found-only billing without vanity hit-rate percentages.](https://invenitor.com/blog/when-we-have-them-writing-honest-marketing-for-contact-apis) - [Oct 21, 2026 · ProductWhat is pay-per-lookup pricing?What is pay-per-lookup pricing?](https://invenitor.com/blog/what-is-pay-per-lookup-pricing) - [Oct 15, 2026 · ProductTrust checklist before you buy any contact APITrust checklist before you buy any contact API – found-only credits, written billing.](https://invenitor.com/blog/trust-checklist-before-you-buy-any-contact-api)