Improve The Proof Plan

Inspect the source files and list the specific doubts buyers raise, in their own words, ordered by how often they appear.

Catalogue every piece of evidence the source files actually contain — demonstrations, specifications, process documentation, credentials, sample outputs, third-party references — and record where each is documented.

Match each doubt to the proof type that resolves it: does-it-work doubts need demonstration, will-it-work-for-me doubts need situational similarity, can-they-deliver doubts need process or track record, and is-it-worth-it doubts need comparison or specificity.

Place each matched proof directly adjacent to the claim that triggers its doubt, rather than in a separate evidence block far from the relevant statement.

Record every unmatched doubt as an evidence gap with a note on what would close it, and do not paper over any gap with generic reassurance or invented material.

Separate structural changes from copy changes: structural work is proof placement, the collection process for missing evidence, and consent or permission tracking for anything customer-supplied; copy work is captioning each proof with the doubt it answers and removing evidence that answers no listed doubt.

Specify responsive behavior: on mobile, each proof sits immediately beneath its related claim with media constrained to viewport width; on tablet, claim and proof render as paired columns; on desktop, proof appears in the margin alongside its claim so both are read together.

Define tracking: measure conversion rate, scroll depth through claim-and-proof sections, and the change in pre-sale question volume per doubt category. Rollback rule — if a doubt category's question volume does not fall after its matched proof ships, replace that proof type rather than adding more of the same.