· 9 min read · 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.
Most contact-API landing pages sell certainty. Hit rates. Guarantees. Screenshots of inboxes that somehow always fill. Buyers who run desks already know that language is theater. When we have them is the opposite claim: coverage coverage, honest empties, and marketing that matches the API contract.
Invenitor is a people search and lookup API, not a sales cloud. Profile URL in; email, phone, or links out when we have them; empty means not found. We do not publish hit-rate percentages. Coverage varies by profile – and that variance belongs in the copy, not in a footnote after the purchase.
Honesty pillar: Empty Means Not Found – Why Guessed Emails Break outreach. Primary fields: One Primary Contact, Never Invented. Billing semantics: Credits, Empty Results, and Timeouts. Trust buyers: Trust Checklist Before You Buy Any Contact API. Category: What a Contact Lookup API Actually Does.
What "when we have them" means in public copy
| Claim style | Buyer hears | Honest alternative |
|---|---|---|
| "95% emails found" | Guaranteed coverage | Coverage – contacts when we have them |
| "Never miss a lead" | Invented fills OK | Empty means not found |
| "Unlimited enrichment" | Seat tax forever | Prepaid found-only credits |
| "AI verifies everything" | Magical certainty | Documented empty + error paths |
Marketing that invents certainty trains desks to invent contacts when the API returns empty. That breaks placements, brand trust, and WhatsApp hygiene. Layer clarity: Contact Lookup API vs CRM vs Sequencer. Pay-per-lookup definition: What Is Pay-Per-Lookup Pricing?.
Copy rules that match the product
- Lead with the job: profile URL → contact fields when found – hub LinkedIn or GitHub Profile URL → Contact Lookup API.
- Say coverage out loud. Coverage varies. Do not invent a percentage.
- Separate empty completed finds from errors and timeouts – Credits, Empty Results, and Timeouts.
- Price in INR packs buyers can sample – /pricing, INR Credit Packs, 25 to 1,000 Credits.
- Point agents and builders to the same contract – /docs, /mcp.md.
Words to retire (and what replaces them)
Retire "guaranteed," "always," "100%," and "verified for every profile" unless you can prove each row. Replace with when we have them, empty means not found, and found-only credits. Primer: What Are API Credits in Enrichment Products?. Seat contrast: Seat Subscriptions vs Pay-Per-Lookup Credits. No-seat rail: No Monthly Plan Contact Enrichment, Pay-as-You-Go Contact APIs.
Why desks punish dishonest demos
How content and sales stay aligned
Blog, pricing tiles, OpenAPI, and MCP docs must share empty semantics. Keys: Rate Limits and Keys.
What should you do next?
Rewrite one hero line with when we have them. Link /docs and /pricing. Run five free lookups on real URLs. Leave empties empty. Size a pack from found history – not from a vanity percentage.
Procurement one-liner
We buy a soft-mesh contact lookup API marketed with when-we-have-them language – empty means not found, found-only credits, no invented hit rates.
Worked rewrite: hero before/after
Sales enablement card
Print found-only billing and when-we-have-them on one card. Refuse invent-on-empty demos. Category: What a Contact Lookup API Actually Does.
Questions
What does "when we have them" mean for contact APIs?
Contacts return only when the coverage has them. Empty means not found – not a prompt to invent emails.
Why avoid publishing hit-rate percentages?
Coverage varies by profile and changes over time. A fixed % in marketing trains buyers to expect certainty the API cannot promise.
How should pricing pages talk about empties?
State found-only rules clearly. Empty completed finds and error/timeout paths should not be sold as guaranteed spends.
Is honest marketing slower to convert?
It converts desks that already distrust vanity demos – boutique services, freelancers, and builders who ship empty states.
What copy should replace "guaranteed enrichment"?
Coverage, when we have them, empty means not found, prepaid found-only credits.
Where should buyers verify the contract?
/docs for REST, /mcp.md for agents, /pricing for packs, plus the trust checklist and credits pillar posts.
How does this relate to Invenitor's brand?
A people search and lookup API, not a sales cloud – marketing must match that product shape.
