gooseworks-ai/goose-skills / skills/marketing/research-competitors
research-competitors
VerifiedCompetitor 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.7 KB |
| references/angles-and-gaps.md | markdown | 7.4 KB |
| references/battlecard.md | markdown | 3.8 KB |
| references/focused-outputs.md | markdown | 2.7 KB |
| references/linkedin-engagers.md | markdown | 6.3 KB |
| references/page-technology.md | markdown | 2.7 KB |
| references/reading-ads-honestly.md | markdown | 8.6 KB |
| references/report-format.md | markdown | 10.0 KB |
| references/research-spec.md | markdown | 34.5 KB |
| references/rival-craft.md | markdown | 16.0 KB |
| references/run-memory.md | markdown | 6.6 KB |
| references/watch-and-react.md | markdown | 12.7 KB |
| skill.meta.json | config | 5.5 KB |
| tests/examples/2026-10-22/battlecard.md | markdown | 5.5 KB |
| tests/examples/2026-10-22/engagement-report.md | markdown | 3.7 KB |
| tests/examples/2026-10-22/engagers.csv | other | 1.7 KB |
| tests/examples/2026-10-22/excluded.csv | other | 1.0 KB |
| tests/examples/2026-10-22/technology.md | markdown | 3.2 KB |
| tests/fixtures/engagers.csv | other | 1.9 KB |
| tests/fixtures/focused-evidence.md | markdown | 3.8 KB |
| tests/fixtures/page-source.html | other | 614 B |
| tests/test-by-hand.md | markdown | 7.5 KB |
tests/fixtures/focused-evidence.md
View on GitHub# Focused research fixture — fictional evidence
All companies, people, prices and source pages in this fixture are invented test data. Use only this supplied evidence; do not browse, call GooseWorks or spend. The test date is 22 October 2026. Setup, source reads and approval state are simulated, not live acceptance. Relative file citations refer to supplied evidence, not public verification.
## Brand / product source — supplied product sheet, checked 22 Oct
Papertrail is an invoice-exception review tool. It has a shared review queue, a CSV review-history export and a recorded reviewer decision. It keeps existing human approvals. It does not automatically pay invoices or write back into an ERP. It has no certified compliance claim or documented time-saved result. Its current brand position is “fully automatic accounts payable”. Brand voice is confirmed: plain, specific, no superlatives. Team plan: $120/month for up to five reviewers; tax excluded. Hero product: the review queue.
## Rival source — supplied BillPilot pricing/product captures, 22 Oct
BillPilot describes itself as “Accounts payable from intake to payment”. It supports native ERP write-back and payment execution. Its review history is available on its Enterprise tier; the supplied capture does not show an export format or Enterprise price. Standard is $25/reviewer/month, minimum ten seats, taxes excluded. Annual discounts and migration services are unknown. The five-reviewer comparison therefore costs $250/month for Standard, but history/export parity cannot be priced from the supplied sheet.
## Buyer groups / owner win-loss notes — supplied interview notes, 19 Oct
Primary: controllers at multi-entity businesses whose invoice exceptions need an accountable review before approval. Five interviews; three explicitly want a record they can hand to a finance reviewer. One said “I need to see who decided, not another score”. Secondary: AP team leads handing disputed invoices between staff; three interviews; one said “The next person asks me what happened, every time”. Both use an ERP and keep its approvals.
Actual deal notes: two prospects chose a manual review pilot because they wanted to keep their approvals. One prospect stayed with BillPilot because native ERP write-back was essential. These observations are a tiny deal sample, not win-rate evidence.
Objection excerpts: “We already use BillPilot.” “Is this another approval system?” “Why not use a spreadsheet?” The last buyer described searching email for the reviewer decision; no measured time or error result was captured.
## Approvals — simulated owner, 22 Oct
Owner says: “Approve these exact product lines for this test: Review invoice exceptions in a shared queue. Export the review history as CSV. Keep your existing approval steps.”
Owner says: “Approve this dated, price-only comparison: For five reviewers, Papertrail is $120/month; BillPilot Standard is $250/month because it requires ten seats. This does not compare Enterprise features.”
No approval for “faster”, “cheaper for everyone”, “compliant”, “fully automatic”, or a time-saved claim. No positioning option has been selected. No sending or publishing is requested.
## LinkedIn post export metadata — supplied export, captured 22 Oct
Company: BillPilot. Requested window: posts published 1–22 Oct; engagement dates are not the filter. Post https://www.linkedin.com/posts/billpilot_review-activity-101/ was published 10 Oct; 220 reactions and 12 comments. Post https://www.linkedin.com/posts/billpilot_export-activity-102/ was published 12 Oct; 110 reactions and 8 comments. These are the only two posts supplied; they are not the company's full feed. Requested posts: these two; no ranking substitute. Company/team fields are statements in this export, not independently checked titles. The original private export is engagers.csv.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| 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: 115k | Updated | Claude CodeCodex | Verified | Install |
| 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: 115k | Updated | Claude CodeCodex | Verified | Install |