# Buyer evidence pack

Public proof for each objection a skeptical buyer may raise, every row dated and linked.

Requires web search, through Exa. Requires web fetch.

## Install

```sh
npx @parcha/agentrun template install github:Parcha-ai/agentrun-templates/templates/buyer-evidence@242f29da8317fbe51d0cce4628bdb5ab61d7ccc9 --trust
```

Or open `<your AgentRun address>/#/templates/install?src=github%3AParcha-ai%2Fagentrun-templates%2Ftemplates%2Fbuyer-evidence%40242f29da8317fbe51d0cce4628bdb5ab61d7ccc9`. Pinned to commit 242f29da8317fbe51d0cce4628bdb5ab61d7ccc9.

## What it does

Before a call with a skeptical buyer, list the objections you expect and get, for each one, the public customer results, ROI figures, reviews, certifications and independent studies that answer it. Every row is dated and linked, says whether it comes from the vendor or a third party and how close the customer is to your buyer, and comes with talking points and one question to ask. Evidence that cuts against you is shown too, thin objections are named as gaps, and no figure is scaled to the buyer.

- Skill `buyer-evidence`: Build an evidence pack for a seller facing a skeptical buyer. For each listed objection, find public customer results, ROI and cost figures, reviews, certifications and independent studies, verify each at its source, grade segment fit and independence, report what cuts against the seller, write talking points and one question, and name the gaps. Use for "proof points for this objection", "evidence pack before my call with the CFO", "case studies that answer X".
- Rules: `EVIDENCE.md`

## What starts it

- By hand, any time: from the console, the API or the CLI.

## Inputs

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `product` | string, 2 to 200 characters | yes | Your product (with its website) or the category you sell in. Example: `Ledgerly, AP automation (ledgerly.example)`. |
| `buyer` | string, 2 to 200 characters | yes | The segment and the role you are meeting. Example: `CFO at a 400-person US manufacturer`. |
| `objections` | list of string | yes | One objection per item, in the buyer's words or yours. Up to 8. Example: `It costs too much for what we'd save,Our auditors won't accept automated approvals`. |
| `incumbent` | string, 0 to 160 characters | no | The incumbent tool or rival. Blank: their current process is the comparison. |
| `focus` | string, 0 to 300 characters | no | A deal stage, region or metric to weigh most. |

## What it needs

- Harness: pi, claude-agent, codex
- Model: balanced tier, medium effort
- Tools: read, web_search, web_fetch
- Computer: Wherever your AgentRun puts a new agent
- Keys: A model key
- Learning: off

## Sample output

Input:

```json
{
  "content": "Today is 2026-11-14. Build my evidence pack for Tuesday's call.\n\nThe sites below are not reachable from this run. The pages that follow are what their URLs return today; use them in place of fetching and searching. These sites are test data.\n\n<captured-page url=\"https://ledgerly.example/customers/tern-logistics\" captured=\"2026-11-14\" untrusted>\n<h1>How Tern Logistics cut its cost per invoice by two thirds</h1><p>April 2026. Tern Logistics, a 600-person US freight company, processes 9,000 invoices a month. Over the 12 months after going live on Ledgerly, its cost per invoice fell from $9.40 to $3.10, measured by Tern's finance team.</p>\n</captured-page>\n\n<captured-page url=\"https://ledgerly.example/resources/tei-study\" captured=\"2026-11-14\" untrusted>\n<h1>The Total Economic Impact of Ledgerly</h1><p>September 2025. A study commissioned by Ledgerly and conducted by Northfield Research. Based on interviews with four customers combined into one composite organization of 1,000 employees, it reports a 212% return on investment over three years and payback in under 7 months.</p>\n</captured-page>\n\n<captured-page url=\"https://apbenchmarks.example/2026/cost-per-invoice\" captured=\"2026-11-14\" untrusted>\n<h1>Cost per invoice benchmark 2026</h1><p>March 2026. AP Benchmarks, an independent research group, surveyed 410 US companies. Median fully loaded cost per invoice: $9.87 for mostly manual teams, $2.36 for the top quartile of automated teams. Manufacturing respondents: 96.</p>\n</captured-page>\n\n<captured-page url=\"https://ledgerly.example/trust\" captured=\"2026-11-14\" untrusted>\n<h1>Trust center</h1><p>Ledgerly holds a SOC 1 Type II report (period ending June 30, 2026) and a SOC 2 Type II report. Reports available under NDA. Every approval records the approver, timestamp and policy rule applied.</p>\n</captured-page>\n\n<captured-page url=\"https://asb.example/staff-qa/automated-controls\" captured=\"2026-11-14\" untrusted>\n<h1>Staff Q&A: relying on automated controls</h1><p>November 2025. Auditing Standards Board staff. An auditor may rely on an automated control, such as a system-enforced approval, when the general IT controls over the system have been tested and are effective, and the control is tested once in the period.</p>\n</captured-page>\n\n<captured-page url=\"https://reviews.example/products/ledgerly\" captured=\"2026-11-14\" untrusted>\n<h1>Ledgerly reviews</h1><p>4.6 out of 5 from 212 reviews (as of November 14, 2026).</p><p>Review, Controller, manufacturing, 250-500 employees, August 2026: \"The approval audit trail made our audit easy. Implementation took five months, not the six weeks we were promised.\"</p><p>Review, AP Manager, logistics, October 2026: \"Matching is fast.\"</p>\n</captured-page>",
  "product": "Ledgerly, AP automation (ledgerly.example)",
  "buyer": "CFO at a 400-person US manufacturer",
  "objections": [
    "It costs too much for what we'd save",
    "Our auditors won't accept automated approvals"
  ]
}
```

Output:

**Evidence pack: Ledgerly AP automation for a CFO at a 400-person US manufacturer**
Compare against the buyer’s current AP process; no incumbent or baseline was specified. Checked 2026-11-14 using only the six supplied test-page captures. Cost evidence supports investigation, not a buyer-specific return. Audit evidence supports conditional reliance, not guaranteed acceptance. Independent sources do not verify Ledgerly’s savings or claimed SOC reports.

#### It costs too much for what we'd save
_In the buyer's words:_ "Show me net savings after subscription, implementation and internal effort—not a headline ROI from a different business."

| Claim | Source | Fit | Date | Independence |
|---|---|---|---|---|
| Median fully loaded cost per invoice: $9.87 for mostly manual teams; $2.36 for the top quartile of automated teams. Survey of 410 US companies, including 96 manufacturing respondents; no manufacturing-only breakout or before-and-after comparison. | [AP Benchmarks](https://apbenchmarks.example/2026/cost-per-invoice) | partial: US sample includes manufacturing, but aggregate results and no size breakdown | 2026-03 | third_party |
| Cost per invoice fell from $9.40 to $3.10 over 12 months after go-live. Tern Logistics: 600-person US freight company, 9,000 invoices monthly; measured by its finance team. | [Ledgerly — Tern Logistics](https://ledgerly.example/customers/tern-logistics) | partial: similar size and same country, different industry | 2026-04 | vendor |
| “Implementation took five months, not the six weeks we were promised.” One controller review from a 250–500-employee manufacturer; cost impact undisclosed. | [Ledgerly reviews — manufacturing controller](https://reviews.example/products/ledgerly) | strong: same industry and similar size; geography unspecified | 2026-08 | third_party |
| 212% ROI over three years and payback in under 7 months. Ledgerly-commissioned Northfield Research study; four customer interviews combined into a 1,000-employee composite. | [Northfield Research — commissioned TEI](https://ledgerly.example/resources/tei-study) | weak: larger composite, industry and geography unspecified; only supplied ROI/payback source | 2025-09 | vendor |

- Suggest using AP Benchmarks to frame opportunity, not predict savings: it compares different groups. Tern offers a Ledgerly before-and-after result, but neither establishes this buyer’s baseline or net savings.
- Treat Northfield’s commissioned ROI as a hypothesis to test, not an independent forecast or a result for this manufacturer.
- Acknowledge the manufacturing controller’s five-month implementation versus six weeks promised. Seek a scoped rollout and all implementation costs before claiming payback.

**Ask:** Tern reported cost per invoice falling from $9.40 to $3.10; what are your current fully loaded cost per invoice and monthly invoice volume, using a consistent cost definition?

#### Our auditors won't accept automated approvals
_In the buyer's words:_ "Can our auditors rely on the approval controls and evidence, or will we still need a parallel manual process?"

| Claim | Source | Fit | Date | Independence |
|---|---|---|---|---|
| “The approval audit trail made our audit easy.” One controller review from a 250–500-employee manufacturer; no auditor opinion or testing details supplied. | [Ledgerly reviews — manufacturing controller](https://reviews.example/products/ledgerly) | strong: same industry and similar size; one experience, not assurance | 2026-08 | third_party |
| An auditor may rely on an automated control when general IT controls have been tested and are effective, and the control is tested once in the period. System-enforced approval is the example. | [ASB staff Q&A](https://asb.example/staff-qa/automated-controls) | weak: no segment match; only supplied standards guidance on reliance | 2025-11 | third_party |
| Ledgerly says it holds SOC 1 Type II and SOC 2 Type II reports; approval records include approver, timestamp and policy rule. SOC 1 period ended June 30, 2026; SOC 2 period unspecified. Reports under NDA, not supplied. | [Ledgerly Trust center](https://ledgerly.example/trust) | weak: no segment-specific scope; only direct report and record statement | 2026-11-14, capture date; page undated | vendor |

- Cite the ASB staff Q&A against a blanket rejection, not as a guarantee: reliance requires effective tested IT controls and control testing. The buyer’s auditor confirms applicability.
- Use Ledgerly’s trust page to request the actual reports and sample approval records. The buyer’s auditor confirms scope, exceptions, coverage and required customer controls; the page is not assurance.
- Offer the manufacturing controller’s audit-trail comment as a relevant peer experience, not an audit opinion. The same reviewer reported a longer-than-promised implementation.

**Ask:** Given the ASB Q&A’s testing conditions, how many approval controls would your auditor need to assess, and how many currently have documented IT-control and in-period testing evidence?

#### What cuts against you
- A manufacturing controller reported five months to implement versus six weeks promised. This challenges rollout assumptions, though no cost impact is quantified. ([Ledgerly reviews](https://reviews.example/products/ledgerly), 2026-08)
- Auditor reliance is conditional on tested, effective general IT controls and in-period automated-control testing—not automatic acceptance. ([ASB staff Q&A](https://asb.example/staff-qa/automated-controls), 2025-11)

#### Gaps
- **Cost:** The supplied customer result and ROI study are vendor evidence. The independent benchmark does not verify Ledgerly-specific savings. Pricing, buyer baseline and independently verified manufacturing savings are missing. Close with a scoped quote, all-in implementation estimates, consistent buyer baseline and a comparable manufacturer's documented results.
- **Audit:** The trust page is not the underlying SOC reports. The Q&A and one review do not verify Ledgerly’s report scope, exceptions, approval-record integrity or this buyer’s auditor acceptance. Close with the reports, coverage updates, control documentation and sample records; the buyer’s auditor confirms reliance requirements.

#### Do next
- Prepare an invoice-cost and approval-effort baseline worksheet for Tuesday; do not calculate savings before definitions align.
- Request a scoped quote and rollout plan, including internal effort, dependencies and acceptance criteria; test the reported delay concern.
- Obtain SOC reports, coverage updates and sample approval evidence for the buyer’s auditor.
- Request a comparable manufacturing reference and the commissioned study’s assumptions; separate customer outcomes from composite projections.

## Tested

Passes 4 of 5 eval cases on pi, 3 of 5 on Claude Code and 4 of 5 on Codex. On the live web, 1 of 1 on pi, 1 of 1 on Claude Code and 1 of 1 on Codex.

6 eval cases: injection-in-page, live-spend-cfo, mapped-and-labeled, search-failed, switch-from-incumbent, thin-evidence.

## Source

- Package: https://github.com/Parcha-ai/agentrun-templates/tree/242f29da8317fbe51d0cce4628bdb5ab61d7ccc9/templates/buyer-evidence
- Publisher: Parcha-ai
- Author: Parcha Labs
- Version: 0.1.0
- License: Apache-2.0
- Category: Sales
- Page: https://marketplace.agentrun.ai/templates/buyer-evidence/
