ChiefOSby ConversintStart free
Menu
← Back to the library
Research and business strategy

Vendor evidence synthesis

Synthesize reusable vendor and industry evidence from source-backed research observations. Use for vendor intelligence summaries, vendor profiles, pricing observations, unsummarized evidence reports, or migration of reusable vendor findings. Preserves the evidence trail and does not invent, publish, or overwrite unsupported claims.

Works with the context you provideVersion 3.1.0

# Vendor evidence synthesis

Use this method to keep a reusable vendor-evidence store concise without losing the observation trail that supports it. It has three modes: summarize one profile, report evidence status, or migrate source-backed observations.

Common rules

Treat a reusable observation as a dated claim with source URL, subject, confidence, and distinction between vendor-specific pricing and broader market economics. Preserve the raw observation trail. Do not rewrite unrelated profiles, turn weak clues into a profile, or create a summary claim that its observations do not support.

Classify an observation as official vendor claim, attributable customer evidence, independent reporting, analyst or directory discovery, supplied first-party evidence, or unknown. Record checked date, scope, and conflicts. A summary must preserve the distinction between observed fact, reported claim, and inference; it may identify a gap but must not fill it with a conclusion.

Summarize mode

  1. Read the requested profile and its unsummarized observations.
  2. Update only the relevant synthesized sections: current summary, pricing snapshot, operating-pattern summary, or named-vendor coverage.
  3. Keep each summary claim linked to the supporting observations and sources.
  4. Mark only the observations actually used as summarized.
  5. Report the updated file, observation identifiers used, remaining count, and research gaps.

Report mode

List profiles with total observations, unsummarized observations, last summary pass, and recommended next action. Highlight evidence sets large enough to benefit from a focused summary, without silently starting one.

Migrate mode

  1. Read the supplied source material.
  2. Extract only reusable, source-backed vendor, platform, pricing, or industry-operating observations.
  3. Keep generic service estimates, lead costs, and unsupported interpretations out of vendor evidence.
  4. Propose a broad migration plan for confirmation before making many durable additions.
  5. Append observations with their source metadata; then recommend focused synthesis when the threshold or user request warrants it.

Quality rules

  • Record public plan prices, fees, quote-required language, and checked dates as vendor evidence when available; otherwise say `unknown` or `not disclosed`.
  • Do not auto-upload, email, update CRM, or modify another operating ledger.
  • When a host owns a durable evidence store, request its authorized write capability or return proposed entries instead.
  • Handoff a bounded profile or evidence packet to screening, evaluation, market, or pricing work rather than making a decision inside the evidence store.