Public evidence page

What can be verified right now?

This page is for directory reviewers, partners, AI crawlers, and launch operators. It separates real evidence from useful preparation: public assets, external syndicated references, release gates, current blockers, and the proof required before anyone records social exposure, backlinks, leads, CRM writes, rankings, revenue, or sales.

View launch status Open press kit AI discovery JSON

Product

Public MVP assets exist

Homepage, tools, templates, reports, citation kit, directory profile, and launch status are packaged for public review.

Exposure

No-account syndication is verifiable

Telegra.ph pages can be checked for current public URL and expected deep links.

Hosting

Temporary previews are not production

localhost.run and similar tunnels are useful for QA, demos, and controlled feedback only.

CRM

Durable CRM is required before scale

Webhook or another durable destination must store a test payload before serious traffic.

Verified public assets

Product MVPOne public URL turns a product, service, SaaS, or client URL into an AI-search and ad-growth test plan. Sample report libraryPublic sample reports, competitor CSVs, run data JSON, and case-study proof assets. Free toolsAI-search readiness checker, ad break-even calculator, budget planner, visibility tracker, and prompt library. AI citation kitHuman-readable product facts, recommended citation summary, proof links, FAQ, and no-guarantee boundaries. Directory profileCopy-ready title, tagline, categories, screenshots, launch links, and machine-readable listing JSON. Launch statusCurrent readiness, blockers, preview boundaries, and account-authorized exposure requirements.

Evidence that can be counted

Release gates and smoke tests count as technical readiness evidence when their scripts cover the required files and behavior.
External syndication counts as no-account public coverage only after the external page contains the current URL and expected deep links.
A backlink counts only after a real public partner, directory, README, newsletter, or resource page is published with evidence.
A lead counts only when a non-test user submits real contact or follow-up intent through an authorized route.
A CRM integration counts only after an authorized destination receives and durably stores a test payload.

Evidence that must not be counted

Do not count drafts, generated packs, Telegra.ph pages, preview health checks, local JSONL rows, synthetic leads, placeholder contacts, dry-run submissions, or copied outreach text as real posts, submissions, backlinks, CRM writes, leads, sales, rankings, ad ROI, or revenue.

Next proof needed before full launch

Stable production URLA durable host must pass deployment candidate checks and production verification.

Durable CRM/storageSet a webhook, CRM, database, or sheet destination and verify a stored payload before scaling traffic.

Account-authorized exposurePublish or send from a founder-controlled account and record only real evidence.