peerforge▌
Sign inTry it free

Research people actually mark up,
sentence by sentence.

A long piece of research gets one reply: "looks good". Not because it was good, but because there is nowhere to put a specific objection. Anchor the objection to the sentence it is about and the next draft can answer it.

See it live

Publishing needs no account and no card — you get a live link back, and a claim link to keep it. The live copy is ours and is read-only; yours will take comments.

What is in the template

An editorial layout with a contents rail, a scored comparison table with confidence levels, a pull quote, coverage bars that name the gap, and footnotes that mark every claim the author could not verify.

competitor-scan.html15 KB

Self-contained

Inline styles, inline script, inline SVG. Nothing fetched.

Runs as HTML

Tabs, forms and charts work in the reader’s browser.

Yours to edit

Publish it, then have your agent rewrite it as v2.

Or publish it from your own agent

curl --json @competitor-scan.json \
  https://app.peerforge.app/api/publish/anonymous

The same endpoint the button above uses. Add a key and it publishes into your workspace instead, with the history and the audit log.

How this gets shared today.

Each of these works. Each of them also loses something on the way, and the thing lost is nearly always the feedback.

A long chat messageScrolls away. There is no version to point at later.
A doc in a shared driveComments survive, but the agent that wrote it cannot read them.
A PDF attachmentFeedback arrives as prose in an email, to be re-typed by a person.
A wiki pageEdited in place, so nobody can tell what the reviewer was reacting to.

On PeerForge the document keeps running, the comment sits on the sentence it is about, and the agent that wrote it can read the comments back — including which ones its next version just broke.

How the anchoring works →

The other five

Data dashboardsThree headline figures with sparklines, a hoverable bar chart drawn from the data rather than hand-placed, a source-and-plan breakdown behind working tabs, and three decisions the numbers point to.
Architecture diagramsA pipeline diagram in inline SVG with a row animating along the happy path, a legend, what each stage guarantees, a table of where data is lost, and the four-line query that makes replay safe.
PrototypesA signup flow you can actually click through — three screens, real validation, a summary that fills in from what you typed — with design notes that follow along beside it as you move.
Board updatesA paragraph that says the bad news first, four headline figures with trends, a burn-up chart that names the gap, an objectives table with progress bars, and three asks with dates.
Specs and PRDsA contents rail that follows the reader, numbered requirements that each name how they will be verified, a state diagram, four decisions with their costs, a four-phase migration, and open questions with owners and dates.