gtmpodStart

Source policy

How gtmpod evaluates AI GTM claims

gtmpod exists to separate AI GTM hype from implementable workflows. We look for source-backed evidence, data dependencies, human review points, writeback paths, failure modes, and measurable GTM outcomes.

Evidence tiers

official
Vendor docs, changelog, official blog, filing, or first-party product page.
first-party
Founder, operator, or customer post describing their own launch or usage.
independent
Practitioner review, benchmark, teardown, or community discussion.
operator-story
Specific workflow story from LinkedIn, Reddit, HN, podcast, or interview.
market-analysis
Directory, analyst post, market map, or roundup used only as context.
unverified
Single-source claim that cannot be traced to a reliable primary source.

What every strong signal should answer

  • What GTM job does this help with?
  • What data enters the workflow?
  • Where does AI act?
  • Where does a human review?
  • Where does the output write back?
  • What can break?
  • What metric proves it worked?

Affiliate independence

Some outbound links may be affiliate links. gtmpod does not let affiliate economics determine editorial conclusions. Tool recommendations must still explain workflow fit, implementation constraints, alternatives, and failure modes.