Skip to content

gooseworks-ai/goose-skills / skills/marketing/research-competitors

research-competitors

Verified

Competitor research: what every main rival is running, launching, charging and saying now, what works for them, and what that means for you. Use when the marketer asks for competitor research or a teardown, "what ads are my competitors running", "how do they price", "find gaps and angles", "what changed this week" (a weekly watch), or "X just launched / shut down / cut prices" (react now). Also builds a sales battlecard, checks a competitor page's tools/pixels, or studies who engages with their LinkedIn posts. Delivers a readable report saved to the brand, so the next run reports what changed. Never copies their words or disparages them. Not for what people say about you or your market — use research-market; not for who your buyers are — use research-audience.

tests/examples/2026-10-22/battlecard.md

View on GitHub
# Papertrail vs BillPilot — sales battlecard, 22 October 2026

## In short

**What we looked at:** the supplied product/pricing sheets, buyer interviews and three deal notes dated 19–22 October. All are fictional fixtures, not live market evidence.

1. **Lead with the review record for a team keeping its approvals** — first look from the small supplied deal sample.
2. **BillPilot fits a buyer needing native ERP write-back and payments** — confirmed within the supplied product capture; Papertrail does neither.

**So, do this first (because of 1 and 2):** the salesperson should ask whether the buyer needs a record before approval or a new payment system, on the next call.

## Decisions for you

Confirm that this deal's buyer is a controller keeping the current ERP and approvals. The supplied owner sign-off covers the exact product lines and price comparison below; broader claims remain unapproved.

## Deal fit

- **Lead with:** “Review invoice exceptions in a shared queue. Export the review history as CSV. Keep your existing approval steps.” These three lines are approved in the [supplied evidence](../../fixtures/focused-evidence.md), 22 October.
- **Where we may win:** controllers needing an accountable record while keeping approvals. Two supplied deal notes support this as a hypothesis, not a win-rate claim.
- **Where they fit better:** native ERP write-back and executing payments are essential. One supplied deal stayed with BillPilot for write-back. Do not promise a workaround we have not documented.
- **Where it is close:** both discuss invoice review. The available BillPilot capture puts history in Enterprise but leaves its export format and price unknown; do not claim we alone offer a review record.

## Evaluation questions

1. Which decision needs to be visible before your existing approval? If the problem is the review record, show that flow; if it is payment execution, explain our limit.
2. Does your process require native ERP write-back? If yes, Papertrail does not meet that requirement today.
3. What must the reviewer-history export contain? Test a real disputed invoice in both products before asserting parity.
4. How many reviewers need access? Compare the required tiers and seat minimums for that scenario, not just each headline price.

## Objections and finished responses

| Buyer says | Safe response |
|---|---|
| “We already use BillPilot.” | “What part of the invoice review is still unresolved? If native write-back is essential, BillPilot may fit better. If you need a review record before your current approval, we can show our shared queue and CSV history.” |
| “Is this another approval system?” | “Keep your existing approval steps. Papertrail records the review decision before approval; it does not pay the invoice or write back into your ERP.” |
| “Why not use a spreadsheet?” | “A spreadsheet may be enough. What does the next reviewer need to see? Papertrail gives you a shared review queue and a CSV review-history export; test whether those help with your actual handover.” |

The objections come from the [supplied interview notes](../../fixtures/focused-evidence.md), 19 October. The responses rely on the product facts and exact approved lines, not invented savings.

## Five-reviewer cost and capability check

| Requirement | Papertrail | BillPilot | Evidence, 22 October |
|---|---|---|---|
| Five reviewers, monthly Standard/team plans | $120/month | $250/month; ten-seat minimum at $25/seat | [Supplied price capture and explicit price-only sign-off](../../fixtures/focused-evidence.md); taxes excluded |
| Shared queue and CSV history | Both documented in Papertrail | History in Enterprise; export format unknown | [Supplied product capture](../../fixtures/focused-evidence.md) |
| Native ERP write-back / payment execution | Neither | Both documented | [Supplied product capture](../../fixtures/focused-evidence.md) |

Approved price wording: “For five reviewers, Papertrail is $120/month; BillPilot Standard is $250/month because it requires ten seats. This does not compare Enterprise features.” It is not a like-for-like history-feature comparison.

## Two short replies

**Already using them:** “What still needs a decision before approval? We can show the shared review queue and CSV history; if you need native ERP write-back, we do not provide that today.”

**Why choose you:** “Review invoice exceptions in a shared queue. Export the review history as CSV. Keep your existing approval steps. Let's test the disputed invoice you actually need to hand over.”

## What to do

1. The salesperson confirms the required workflow on the next call. Success: the buyer names the required review output and whether write-back is essential.
2. If review history matters, the buyer and salesperson compare one actual disputed invoice and the exported fields before choosing a product.

## What we're not doing

We are not claiming faster processing, universal savings, exclusive history features or compliance certification. Those lack proof or approval.

## What we couldn't check

BillPilot Enterprise pricing/export format, annual terms and migration services are unknown. There is no live verification, large win/loss sample or measured time-saved result.

## Sources

[Supplied product/pricing sheets, owner approvals and interview/deal notes](../../fixtures/focused-evidence.md), 19–22 October 2026. Source skew: a fictional owner-supplied sample; this example tests the method and wording, not market truth. Nothing was published or saved to a live brand.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall