Skip to content

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

research-market

Verified

Market research and brand watch: which market the brand is in, how big the reachable part is, what's changing, how buyers buy and what they pay, what people are saying now, and what it means for positioning. Use when the marketer asks for market research, "how big is my market", "what's changing in my category", "what do others charge", "what are people saying about us", "is there demand for <idea>", or "watch my brand / tell me if something blows up" (alerts only, risk first). Also writes positioning choices and finished messages ("position my product", "write our positioning"). Researches first, asks only decisions at the end, and saves the output to the brand. Not for who the buyers are and their own words — use research-audience; not for a deep look at rivals — use research-competitors.

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

View on GitHub
# Papertrail — positioning options, 22 October 2026

## In short

**What we looked at:** supplied product/pricing evidence, eight buyer interviews and three deal notes dated 19–22 October. This is a fictional fixture, not live validation.

1. **An accountable review record is the stronger proposed lead** — first look: three of five controller interviews asked for it.
2. **The current “fully automatic accounts payable” position promises beyond this product** — confirmed within the supplied product sheet: the tool neither pays invoices nor writes back to an ERP.

**So, do this first (because of 1 and 2):** the owner should choose which review problem to test with buyers before replacing the current positioning. The two choices below include finished safe messages.

## Decisions for you

Choose the controller-led review-record option or the AP-handover option. Both remain unvalidated. No current positioning brief or brand field has been changed; no option has been approved in the supplied evidence.

## Evidence and current position

The product has a shared review queue, a recorded reviewer decision and a CSV review-history export. Human approvals remain. The exact approved lines are “Review invoice exceptions in a shared queue”, “Export the review history as CSV”, and “Keep your existing approval steps” ([supplied evidence](../../fixtures/positioning-evidence.md), owner sign-off 22 October).

The controller said, “I need to see who decided, not another score.” An AP lead said, “The next person asks me what happened, every time” ([supplied interview excerpts](../../fixtures/positioning-evidence.md), 19 October). These show a need, not proof of time saved. Two deals preferred keeping their approvals; another stayed with BillPilot for native write-back. This small sample cannot establish a win rate.

## Two strategic choices

| | Option 1: accountable review before approval | Option 2: shared exception handover |
|---|---|---|
| Buyer and situation | Controller reviewing disputed invoices across entities | AP lead passing unresolved invoices between staff |
| Plain category | Invoice-exception review tool | Shared invoice-exception queue |
| Alternative replaced | Email/spreadsheet notes lacking a connected review record | Unstructured staff-to-staff handover |
| Attribute → buyer value → proof | Recorded reviewer decision plus CSV history → a record to hand to a finance reviewer → supplied product sheet, 22 Oct | Shared queue → a place to continue the review → supplied product sheet, 22 Oct |
| Why choose it | Review record with existing human approval kept | Shared review workflow for the team |
| Where it loses | Buyer requires native ERP write-back/payment execution | Buyer already handles exceptions well in the existing tool; another queue adds little |
| Evidence strength | First look: three of five controller interviews asked for a record | First look: three AP interviews, one explicit handover quote |
| Unresolved proof | Whether buyers find the exported fields sufficient; no compliance or audit certification | Whether the queue improves handover; no measured time or error change |

Neither choice creates a new category or claims exclusive features. BillPilot's captured Enterprise history/export details are too thin to claim it lacks a record.

## Recommendation and counterargument

Test option 1 first. It links a specific buyer's decision to a documented output and fits the product's manual-review boundary. The strongest counterargument is that the controller's existing ERP already supplies a sufficient record. If buyers can retrieve the same decision history there, the supposed wedge weakens; compare the actual export fields before making a claim.

Option 2 is a real alternative buyer/problem priority, not just a warmer headline. Choose it if AP leads own the purchase and the handover example proves more important than the controller's review requirement.

## Finished draft messages — option 1

**Internal positioning statement:** For controllers who need a record of disputed-invoice review before approval, Papertrail is an invoice-exception review tool with a shared queue and CSV review history. It keeps the existing human approval step. The proposed alternative is loose email and spreadsheet notes; superiority over a specific tool is not established.

**One-line pitch:** Review invoice exceptions in a shared queue. Export the review history as CSV. Keep your existing approval steps.

**Homepage headline:** Review invoice exceptions in a shared queue.

**Subhead:** Export the review history as CSV. Keep your existing approval steps.

**CTA:** See the review queue.

| Supporting message | Proof available now |
|---|---|
| Review invoice exceptions in a shared queue. | Product sheet and exact owner-approved line, 22 Oct |
| Export the review history as CSV. | Product sheet and exact owner-approved line, 22 Oct |
| Keep your existing approval steps. | Product boundary and exact owner-approved line, 22 Oct |

**Boilerplate:** Papertrail is an invoice-exception review tool. Review invoice exceptions in a shared queue. Export the review history as CSV. Keep your existing approval steps. Papertrail does not pay invoices or write back into an ERP.

**For controllers:** “Need the reviewer decision before approval? Export the review history as CSV.” Pain evidence: the controller's recorded-decision quote; product proof: the export. This is a proposed question plus an approved fact, not a compliance promise.

**For AP leads:** “Review invoice exceptions in a shared queue.” Pain evidence: the handover quote; product proof: the queue. Do not add “no more chasing” without evidence.

## Needs proof — excluded from usable copy

| Candidate | Why excluded | What would unlock it | Safe wording now |
|---|---|---|---|
| “Cut invoice review time in half” | No measured time result or approval | Defined before/after comparison with representative invoice cases and scoped approval | “Review invoice exceptions in a shared queue.” |
| “Audit-ready, automatically” | No audit standard/certification; automation conflicts with product | Exact required standard, demonstrated capabilities and scoped approval | “Export the review history as CSV. Keep your existing approval steps.” |

## Validation test

The owner shows the two message variants in alternating order to five suitable controllers/AP leads. Each buyer describes the product, names the actual exception they would use it for and checks a sample exported decision against their current workflow. **Pass for option 1:** at least four correctly describe review-before-existing-approval, and at least three identify a current decision-record task for which the sample fields are sufficient. **Fail:** they expect payment automation or cannot name a useful record requirement. These are proposed learning criteria, not industry benchmarks. The owner records answers and counterexamples; the next positioning run reads those actual results before strengthening the claim. No paid test is launched.

## What to do

1. The owner chooses the option to test; success is a recorded choice and observed buyer-test answers, not an automatically changed homepage.
2. A finance reviewer checks one sample export before anyone promises it meets their review needs.

## What we're not doing

No immediate rebrand, invented leadership, customer result, savings promise, certification or claim BillPilot lacks history. No change to the existing current brief before an owner's choice.

## What we couldn't check

Live pages, the full interview transcripts, procurement authority, export sufficiency and message response in a real buyer test. Voice is taken from the supplied confirmed rules only.

## Sources

[Supplied product, competitor, interviews/deal notes and exact owner approvals](../../fixtures/positioning-evidence.md), 19–22 October 2026. Source skew: tiny fictional owner-supplied sample, no independent market check. This output proves the fixture synthesis path only; no live brand save or publication was tested.
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