From the experiment

Do coding agents recommend PandaDoc?

Coding agents raised PandaDoc in 106 of 232 judged e-signature sessions and chose it in none of them.

Published September 28, 2026 Updated September 29, 2026 Read as Markdown

Coding agents raised PandaDoc in 106 of 232 judged e-signature sessions and chose it in none of them.

This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in e-signature inside a realistic codebase. Not what a chat assistant says about PandaDoc. What an agent actually installed.

The numbers

CategoryE-signature
Sessions in the category232
Sessions where PandaDoc was chosen0
Install share0%
Raised as a candidate, not chosen106
Chosen when considered0%
Sitepandadoc.com

Which agents raised PandaDoc

Every agent considered it and none adopted it. Cursor raised it most often, in 75% of its e-signature sessions.

AgentSessionsRaised PandaDocChose it
Claude Code4412 (27%)0
Codex7129 (41%)0
Cursor5239 (75%)0
Grok Build CLI1510 (67%)0
Muse Code5016 (32%)0

Which buyers it came up for

It surfaced most for requests written as senior engineer, in 68% of those sessions. Knowing which buyer already has the product in mind tells you which pages to fix first.

Who is askingSessionsRaised it
Junior developer8633 (38%)
Senior engineer5034 (68%)
Enterprise team9639 (41%)

What PandaDoc was up against

The full ranking in e-signature, from the same sessions:

#ProductRuns wonShare
1DocuSign8738%
2Dropbox Sign4419%
3Built in-house (no product adopted)3214%
4YouTrust2310%
5Microsoft 365 eSignature209%
6Documenso63%
7Signable52%
8SignWell42%

What this means

Raised 106 times and chosen none is a specific, diagnosable result, and a better starting position than being unknown. The agent has the product in mind. It reached the shortlist 106 times. Something then lost every one of those sessions.

In our data the causes, in the order they occur:

  • The quickstart does not run when pasted, so the agent abandoned it mid-integration.
  • The documentation describes an interface that changed, so the generated code failed.
  • The product name and the package name differ, so the install step went wrong.
  • The fit was genuinely wrong for the repository, which is fine and worth knowing.

All but the last are fixable in days, and the reason is written down in the session transcript.

Where these numbers come from

The 232 sessions in e-signature are part of a published set of 15,051, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.

Every e-signature run can be replayed on the board.

If you work on PandaDoc: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.

<!-- generated by scripts/write-data-pages.mjs -->

Common questions

Do coding agents recommend PandaDoc?

They raise it but do not choose it. Across 106 sessions where PandaDoc came up as a candidate, agents chose something else every time.

Does Claude Code recommend PandaDoc?

In 0 of the 44 sessions in e-signature run with Claude Code, which is 0%.

Do different coding agents treat PandaDoc differently?

Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 0% and 0% of their runs.

How was this measured?

Real coding agents at pinned versions were run in sandboxes inside 92 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.

Where this comes from

Armature ran 15,051 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.

Read next

All library pages