Every number has a source. Here's the machine.

InsightZing is built as an audit, not a media site. Collectors run daily, claims are graded against a fixed evidence table, and a human gate reviews the draft before anything ships.

01

Collect

Daily automated runs over public sales feeds, launch boards, and revenue disclosures

02

Tier

Each claim graded against the evidence table below — no tier, no publication

03

Human gate

The drafted issue is reviewed line-by-line before sending — 15 minutes, every claim checked

04

Publish

Issue ships with source links and as-of dates; corrections are logged publicly

Editorial coverage targets

The suggested weekly mix. It's a target, not a quota — evidence quality always outranks the allocation.

50%

AI product revenue

Primary focus: AI SaaS and apps, disclosed MRR/ARR, monetization models, founder milestones

25%

Emerging niches & demand

AI niches gaining traction, customer problems people pay to solve, launch and adoption signals

15%

Product failures & lessons

Confirmed shutdowns, clearly labeled weak launches, evidenced monetization lessons

10%

Domain & digital assets

Supporting signal: notable sales and brandable-domain trends, included when relevant to builders

The evidence-tier table

What we found → what we're allowed to publish. Fixed by policy, not mood.

What we findCriteriaLabel we publish
Confirmed shutdownFounder publicly confirms closure, or company files official discontinuationCONFIRMED SHUTDOWN
Confirmed discontinuationCompany announcement — product sunset, deprecation notice, official postCONFIRMED SHUTDOWN
Weak launch signalsLaunch with visibly low engagement (e.g. sub-20 upvotes, no traction trail)WEAK SIGNALS
Founder disclosureFounder publicly shares revenue (MRR, sales) with verifiable numbersFOUNDER-DISCLOSURE
Public dataRevenue/sales from public databases, registries, or reported feedsPUBLIC DATA
Insufficient evidenceDead site, silent founder, anonymous claims — anything unverifiableEXCLUDED ENTIRELY

What we never do

  • No unverified failure claims — a quiet week is not a shutdown
  • No fake reader counts or fabricated testimonials, ever
  • No sponsored content inside the data sections
  • No anonymous sources — every claim links a public origin

Corrections log

Wrong datapoint? Reply to any issue or email us — the correction ships in the next issue and is logged here permanently.

corrections.log — 0 entries

Empty is the honest state: no published errors to correct yet. This log stays public either way.

Hold us to it — subscribe

Free weekly · 2-min read · no spam, unsubscribe anytime.