AI answer monitoring · boldsign

Headline

This run queried no engines, so there is still no BoldSign AI-visibility data for 2026-10. No MCP servers were connected. The openrouter server is defined in maintain/mcp-servers.json but wasn't attached to this run. Google AI Overviews and Microsoft Copilot need a manual check, which an unattended run can't do. All 42 prompt × engine rows are marked not checked. This is the second run today with the same result: the published run 20261112-1428_ai-answer-monitoring_boldsign_040f also collected no answers. The BoldSign baseline is still missing.

Score

None. This checklist has no score, so overall_score is null.

Top 3 actions

1. Fix the openrouter connection before the next pbmaintain run. Set OPENROUTER_API_KEY and enable the openrouter server for this skill. Then run its self-test (list_engines plus one ask_engine call). Two runs in a row have failed for this reason, and rerunning without the fix will give the same empty result.
2. Rerun this skill this week for ChatGPT, Gemini, Perplexity and Claude, and check Google AI Overviews and Microsoft Copilot by hand. Use the seven prompts in raw/prompt-set.json in a clean, signed-out session and record the country.
3. Make the rerun the BoldSign baseline (GTM plan, "First 30 days" step 3). Look closely at P5 (licensing) and P7 (security and compliance). Any wrong claim there goes to the product marketing lead and the COE Team the same day.

Findings

AI answer monitoring: boldsign, 2026-10

Run by: Claude | Location: n/a (no engine queried) | Date: 2026-11-12

Prompts used (fixed set; category "e-signature software and e-signature API"; top competitor DocuSign):

• P1: "What are the best e-signature software and e-signature API?"
• P2: "What is the best e-signature software and e-signature API for an enterprise / midsize company?"
• P3: "BoldSign vs DocuSign: which should I choose?"
• P4: "What are the best alternatives to DocuSign?"
• P5: "What is BoldSign, how is it licensed and who uses it?"
• P6: "Best e-signature API for embedding signing in a SaaS app?" (GTM plan, AI-monitoring prompt 2)
• P7: "Is BoldSign secure and compliant for enterprise use?"

Summary

• Mention rate: 0 of 0 answers collected (no comparison: the only earlier run, 20261112-1428, also collected no answers)
• Citation rate: 0 of 0 answers collected (no comparison, for the same reason)
• Wrong or outdated facts: none recorded because no answers were collected. This means unknown, not zero.

Gaps and fixes

No gaps could be found because no answers were collected.

Not checked

• P1–P7 on ChatGPT, Gemini and Perplexity (21 rows): no MCP servers were connected for this run, so the openrouter ask_engine tool wasn't available. There was no other way to reach these engines.
• P1–P7 on Claude (7 rows): openrouter wasn't connected. I didn't answer the prompts from this agent session because it isn't a clean session. It has the repo's BoldSign positioning in context, so its answers wouldn't be comparable month to month.
• P1–P7 on Google AI Overviews and Microsoft Copilot (14 rows): these have no API, and an unattended run can't check them by hand.
• Phase 2 (month-over-month comparison, gap list, hand-off to the SEO/GEO and blog programs, deltas for the weekly GTM review): skipped because there is no data. The only earlier published run (reports/publish/boldsign/ai-answer-monitoring/20261112-1428_ai-answer-monitoring_boldsign_040f/) has no answers to compare against.

Proposed changes (need approval)

None. This run changed nothing and proposes no changes to live systems. The openrouter fix in Top 3 actions is a tooling setup step for the operator, not a change to a live system.

Data sources

• Fixed prompt set and category: demand-gen/search/ai-answer-monitoring.md.
• Top competitor (DocuSign) and the P6 use-case prompt: products/boldsign/gtm-plan.md (Competitors; AI-monitoring prompts, prompt 2).
• openrouter server definition: maintain/mcp-servers.json (read only, not changed).
• Earlier runs: reports/publish/boldsign/ai-answer-monitoring/20261112-1428_ai-answer-monitoring_boldsign_040f/ (no answers collected).
• Engines: none queried (no MCP servers connected).
• Exports: raw/prompt-set.json (the resolved prompts, worded the same as the earlier run; no answers).
• Choices made without an operator: the metrics period uses the run's date_range (2026-10-15 to 2026-11-11), and the logged month is 2026-10. Metric values are null (not measured), not zero. previous is null because the earlier run has no values.