# Positioning review

How your positioning holds up against named competitors, with sharper options to try.

Requires web search, through Exa. Requires web fetch.

## Install

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

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

## What it does

How does your positioning hold up against named competitors? You get your current claims quoted from your own pages, a side-by-side with each competitor, how customers describe the problem in their own words, which of your differentiators are real, shared or unsupported, and three sharper positioning options with the evidence each rests on.

- Skill `positioning-review`: Review one company's positioning against its competitors. Quote its own headline, claims and proof, read each competitor the same way, gather customers' own words from reviews and forums, classify each differentiator as real, shared or unsupported, and draft three positioning options grounded in that evidence. Use for "positioning review", "how do we compare on messaging", "sharpen our positioning".

## What starts it

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

## Inputs

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `website` | string, uri | yes | The company whose positioning is reviewed. Example: `https://pipewright.example`. |
| `competitors` | list of string | no | Names or URLs. Blank: the review picks three to five direct competitors and says how. Example: `Flowmason,https://ductly.example`. |
| `angle` | string, 0 to 300 characters | no | A segment, a product line or a launch to weigh most. Example: `Mid-market finance teams`. |

## 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. Review our positioning.\n\nThe sites below are not reachable from this run. The pages below are what their URLs return today; use them in place of\nfetching, and search normally for anything else.\n\n<captured-page url=\"https://pipewright.example/\" captured=\"2026-11-14T11:00:00Z\" untrusted>\n<h1>The only finance data pipeline with real-time sync</h1>\n<h2>Every journal, payment and invoice, reconciled and audit-ready.</h2>\n<p>Pipewright keeps a line-by-line reconciliation audit trail your auditors can open directly.</p>\n</captured-page>\n\n<captured-page url=\"https://pipewright.example/docs/audit-trail\" captured=\"2026-11-14T11:01:00Z\" untrusted>\n<h1>Reconciliation audit trail</h1>\n<p>Updated 2026-09-30. Each synced record keeps its source system, timestamp, transformation and the user who approved\nthe match. Auditors get read-only access with an export to PDF and CSV.</p>\n</captured-page>\n\n<captured-page url=\"https://flowmason.example/\" captured=\"2026-11-14T11:02:00Z\" untrusted>\n<h1>Real-time sync for every pipeline</h1>\n<h2>Stream changes from 300+ sources to your warehouse in seconds.</h2>\n</captured-page>\n\n<captured-page url=\"https://ductly.example/features\" captured=\"2026-11-14T11:03:00Z\" untrusted>\n<h1>Ductly features</h1>\n<p>Real-time change data capture. Scheduled batch loads. Warehouse-native transformations. Role-based access.</p>\n</captured-page>",
  "website": "https://pipewright.example",
  "competitors": [
    "Flowmason",
    "Ductly"
  ],
  "angle": "Mid-market finance teams"
}
```

Output:

#### Bottom line

**Judgment:** Pipewright has a clear category but an unconvincing lead differentiator. Real-time capability is already competitor language. The sharper candidate is the reconciliation trail that auditors can inspect directly. Lead with that mechanism, not exclusivity or guaranteed audit outcomes. Confidence: high on messaging overlap; low on independently proven differentiation. [S1][S2][S3][S4]

#### Scope and assumptions

This review covers the supplied finance-pipeline product and exactly the two named competitors. Mid-market finance is the requested segment, not a verified customer profile. Supplied captures were treated as current pages. Search results for similarly named products were not imported into the comparison. [S1][S3][S4][S5][S6]

#### Current positioning

Headline: **“The only finance data pipeline with real-time sync”**. Subhead: **“Every journal, payment and invoice, reconciled and audit-ready.”** [S1]

The headline combines a recognizable category with a demanding exclusivity claim. The more concrete story sits underneath: a line-by-line reconciliation trail that auditors can open. Documentation specifies source system, timestamp, transformation, match approver, read-only access and PDF/CSV export. That is useful feature support, but not independent proof of customer outcomes. Confidence: high that these are the stated capabilities; low on universal audit readiness. [S1][S2]

#### Competitor comparison

| Vendor | Verbatim headline | Main message and proof posture |
|---|---|---|
| Flowmason | Real-time sync for every pipeline | Claims 300+ sources and warehouse delivery in seconds; no independent proof in the capture. [S3] |
| Ductly | Ductly features | Lists real-time CDC, batch loads, warehouse-native transformations and role-based access. [S4] |

Pricing is unknown for both supplied competitors. Their captures establish real-time overlap, not equivalent performance. Neither capture mentions Pipewright's reconciliation-to-auditor workflow; silence does not prove absence. [S2][S3][S4]

#### How customers describe the problem

No attributable customer reviews or posts were found through vendor-name searches and searches targeting G2, Capterra, TrustRadius and Reddit. There are therefore no customer quotations, themes or confidence-rated customer findings.

| Customer phrase | Company phrase | Assessment |
|---|---|---|
| None found | Not mapped | A customer phrase map would invent evidence. |

The three options below use vendor language only. Buyer relevance remains a hypothesis.

#### Differentiation

| Claim | Classification | Confidence and reasoning |
|---|---|---|
| Real-time sync | Shared | High: Flowmason and Ductly both claim real-time capabilities. [S3][S4] |
| Only finance pipeline with real-time sync | Unsupported | Low: the narrower exclusivity claim lacks substantiation. [S1] |
| Record-level trail and auditor access | Unsupported as an established difference | First-party documentation supports the mechanism; independent confirmation is missing. [S1][S2] |
| Every record reconciled and audit-ready | Unsupported | Low: traceability does not establish universal coverage or auditor acceptance. [S1][S2] |

#### Three options

These are **judgment-led proposals**, not established market findings.

1. **Audience-led:** A finance data pipeline with a reconciliation trail. Names the intended buyer and puts finance-specific evidence ahead of generic movement. Risk: mid-market fit is unvalidated. [S1][S2]
2. **Problem-led — recommended first test:** Show the record behind the reconciliation. Makes source, transformation and approval the central mechanism. Risk: avoid implying undocumented immutability or complete history. [S2]
3. **Workflow-led:** Let auditors open the reconciliation trail. Turns read-only access and export into a tangible workflow. Risk: access alone does not establish audit readiness or auditor adoption. [S1][S2]

#### Next steps

Replace the homepage's exclusivity-led message in a controlled test; add a clearly labeled synthetic record walkthrough. Expand the audit-trail documentation with verified permissions, retention and exception behavior. Interview five finance buyers and two auditors before adopting their presumed problems as claims. Test comprehension and qualified conversations, not clicks alone. These are recommendations grounded in the documented mechanism. [S1][S2]

#### Gaps

No independent product validation, attributable reviews, relevant pricing or measured outcomes were found. Competitor coverage is shallow. Legal should review exclusivity and audit-readiness wording. Until stronger evidence exists, present the reconciliation workflow as a documented capability and promising positioning candidate—not a proven unique advantage. [S1][S2][S3][S4]

## Tested

Passes 4 of 4 eval cases on pi, 4 of 4 on Claude Code and 4 of 4 on Codex. Not yet tried on the live web.

4 eval cases: injection-in-page, no-reviews, shared-claim, verbatim-quotes.

## Source

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