PitchMender guide · English

How to verify sales comparison claims against official sources

Verify each claim against an exact passage on an official product page, preserve its conditions and check date, then narrow or remove wording the evidence does not establish. A source link alone is not proof: it must support the same product, capability, plan, market and time period as your sentence.

This is an editorial workflow for B2B sales comparison pages and battlecards, not independent product testing or a guarantee that every statement can be verified. Use it before publishing a comparison and when its underlying sources change.

A six-step evidence review

  1. Separate the claims in each sentence

    Save the original wording and its location in the sales asset. Split a sentence that combines price, capacity and features into separate checks. Words such as “every,” “unlimited,” “only” and “never” need evidence for their full scope, not just one example.

  2. Choose the official page that answers the claim

    Start with the vendor’s current pricing, product documentation or plan comparison, rather than a search snippet or third-party summary. Record the exact URL and section. Check that the page refers to the same product and edition. If it redirects, record the final source you actually read.

  3. Capture the passage and its conditions

    Keep a short evidence excerpt and your check date. Include plan, region, currency, taxes, billing cycle, contract commitment, minimum seats and promotional dates wherever relevant. Read footnotes: a monthly-equivalent amount billed annually is not necessarily a month-to-month price. Work through the fictional pricing examples below.

  4. Compare meaning, not matching keywords

    Ask what the passage directly establishes. A feature listed for one plan does not establish availability on every plan. A missing mention on one page does not prove that a capability is absent. Keep any unresolved part separate from the part you can support.

  5. Write the smallest defensible revision

    Preserve the supported meaning and add the necessary conditions. If official pages conflict or the relevant page is unavailable, mark the claim unresolved rather than selecting whichever source favors your comparison. Have a reviewer inspect both the original and the proposed wording before publication.

  6. Set a reason to check again

    Record a next review date or trigger, such as a plan change, a promotion ending, a source edit or a sales asset revision. Keep the previous evidence date so readers do not mistake an old check for a current one. A scheduled check that did not complete is not fresh verification. Use the manual change log below to record what changed and where you applied the revision.

Worked examples: compare prices on the same basis

Illustrations prepared November 10, 2026. Vendor A, Vendor B, their plans and every amount below are invented, not real price quotes. Each exercise has separate assumptions. All amounts are in USD, before tax, for the same hypothetical region, without discounts or currency conversion.

1. Monthly equivalent, minimum seats and cash due

Assume a three-person team needs the same features and stays within both plans' included usage, with no extra fees. Vendor A advertises USD 20 per seat per month on a 12-month contract, with full payment upfront and a five-seat minimum. Vendor B charges USD 24 per seat per month, billed month to month, with no seat minimum.

Vendor A: count billable seats first
Billable seats = max(3 required, 5 minimum) = 5. The monthly equivalent is 5 x USD 20 = USD 100. Cash due upfront for the 12-month contract is USD 100 x 12 = USD 1,200, not USD 100 each month.
Vendor B: separate this month's bill from a projection
This month's bill is 3 x USD 24 = USD 72. If seats and prices stay unchanged for 12 paid months, projected spend is USD 72 x 12 = USD 864. That is an annualized projection, not an annual contract or an amount due today.
A claim the arithmetic can support
Under these invented assumptions, Vendor A requires USD 1,200 upfront for a year. Vendor B would total USD 864 over 12 paid months if seats and prices remained unchanged, with a USD 72 bill for the current month and no annual commitment. A lower advertised per-seat rate alone does not establish lower team spending or better value.

Contract length and payment frequency are separate fields: an annual commitment can also be billed monthly. Full upfront payment is an explicit assumption in this example, not a rule for every annual plan.

2. Per-seat versus per-organization pricing

Start a separate exercise using different fictional plans, with four users and 1,200 units of usage in one month. Here, Vendor A charges USD 15 per seat per month with no seat minimum. Vendor B charges USD 50 per organization per month, including five seats and 1,000 usage units. Assume both vendors measure the same usage unit.

Vendor A: known base, incomplete total
The base is 4 x USD 15 = USD 60. Its included usage, overage charges and required add-ons are unknown. Record the total as unknown rather than treating missing charges as zero.
Vendor B: add only stated charges
Assume extra usage costs USD 0.05 per unit, a required add-on costs USD 10 per organization per month, and no other fees apply. Four users fit within the five included seats. Overage is (1,200 - 1,000) x USD 0.05 = USD 10. The pre-tax monthly total is USD 50 + USD 10 + USD 10 = USD 70.
The unresolved comparison
USD 60 is Vendor A's base, while USD 70 is Vendor B's total under the stated assumptions. They are not comparable totals. Confirm Vendor A's usage terms and add-ons, and both plans' required features, before making a total-cost claim. If more than five seats are needed on Vendor B, its extra-seat terms must also be checked.

For real claims, put the exact source passages, check time and assumptions in the evidence worksheet. These are manual editorial examples, not a PitchMender pricing calculator or a purchasing recommendation.

Official explanations of these billing concepts: Google Workspace on commitment and payment plans, and Supabase on organization subscriptions and usage charges. The invented figures above do not describe either service.

Fictional example: a claim that is too broad

Acme, its plans and the following evidence are invented solely to illustrate this workflow. They are not claims about a real vendor.

Original sales sentence
“Acme includes audit exports on every plan.”
Fictional official passage
“Team plan: audit exports included.”
Review outcome
Needs qualification. The passage establishes Team-plan availability, not every-plan availability.
Defensible revision
“Acme lists audit exports for its Team plan.”

The revision does not imply that other plans lack audit exports. That would require separate evidence. Record the fictional source as an exercise placeholder, never as a real citation.

Keep uncertainty visible

These are human editorial labels for the worksheet below, not a description of PitchMender’s interface labels.

  • Supported: the evidence directly supports the full sentence and its conditions.
  • Needs qualification: evidence supports a narrower statement, such as a specific plan or region.
  • Contradicted: official evidence explicitly conflicts with the claim under the same conditions.
  • Could not verify: evidence is missing, ambiguous, inaccessible or conflicting. This does not mean the claim is false.

If the result is unresolved, avoid publishing it as a categorical competitor claim. Keep it in the review queue, use narrower supported wording, or remove it until sufficient evidence is available. Translations can help interpretation, but retain the original passage and do not let a translation erase conditions.

Copyable evidence worksheet

Copy or download this blank template into your own review document. Use one record per claim. Keep customer names, confidential terms and other private details out of public evidence notes.

You can also select and copy the text below. The blank download works without JavaScript; neither action submits a review or sends your document to PitchMender.

Original wording:
Sales asset and paragraph (URL or internal reference):
Product and specific claim:
Exact official URL and section:
Short evidence excerpt:
Checked on (date, time and time zone):
Plan / region / currency / tax / billing cycle / contract conditions:
Pricing unit / included usage / required add-ons / overage terms (if relevant):
What the source does and does not establish:
Reviewer:
Outcome (supported / needs qualification / contradicted / could not verify):
Suggested revision and reason:
Next review date or trigger:

Keep a manual change log for your battlecard

When a source changes or a review finds unsupported wording, connect the evidence to every affected sentence. Keep the earlier evidence date, note what the new check established, and record whether a reviewer accepted a revision and where it was applied. A failed check should leave the last successful verification date unchanged.

Use the evidence worksheet above for the full claim review. Add a short entry to your own change log for the resulting decision. If the same claim appears in a comparison page, battlecard and sales deck, list each location so an edit to one copy is not mistaken for an update to all three. Choose review dates based on how quickly the underlying information changes and how the asset is used.

This is a manual editorial record you maintain outside PitchMender. The approval and publication fields below do not describe built-in approval, notification or version-history features. Keep confidential sales details and internal links out of any public log.

Manual change-log template

Change recorded on (date, time and time zone):
Claim / evidence worksheet reference:
Reason for review:
Previous evidence reference and check date:
New evidence reference, check date and outcome (or why unavailable):
Affected sales assets and exact locations:
Proposed wording and reason:
Reviewer and decision (pending / accepted / declined):
Revision applied to each asset on (or still pending):
Next review date or trigger:

Fictional example

In the Acme example above, a review finds that the evidence supports Team-plan availability, not every-plan availability. The proposed revision is “Acme lists audit exports for its Team plan.” Link that decision to the claim’s worksheet and list every copy that needs review. Leave the decision and applied-on fields pending until a person has completed those steps. Acme and the evidence remain fictional.

Using this workflow with PitchMender

PitchMender lets B2B software teams submit a public comparison page or redacted sales text, select official sources, and inspect the original claim, captured evidence and suggested revision. See the historical review sample for an illustration, not current vendor pricing, and the product overview for scope and limitations.

The public beta allows one project per account. Free accounts can add up to three official source pages; eligible accounts can add up to ten. You can submit public HTTPS pages from any official website. Some sites may block automated access or use a pricing view that cannot be verified, in which case the report will explain the gap.

Public documents and official sources are rechecked daily, subject to capacity. Pasted text remains the last submitted version. The interface supports 15 languages through 16 catalogs; suggestions use the document’s language. This guide is available only in English.

AI results can be incomplete or unable to verify a claim. Review every suggestion against its original evidence. Automated checking does not establish universal coverage or independently validated accuracy across all languages and sources.

Delete comparison

Delete this comparison and its private documents, reports and feedback?