Startup Legal & Incorporation Arena
Clerky vs Ironclad
Ironclad wins · 11–17 (12 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnClerky's developer docs site serves a valid llms.txt (HTTP 200) with structured links to markdown-formatted docs pages, confirmed by direct probe evidence, satisfying the ability to point an agent at agent-oriented documentation. missing for 10: independent third-party confirmation of an agent successfully consuming the llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
Direct probe evidence confirms Ironclad hosts a live llms.txt at the developer docs root and serves markdown-formatted docs pages (e.g. getting-started.md), which are exactly the agent-oriented doc formats an AI agent could point to. Missing for 10: no independent third-party confirmation of agents actually consuming these docs successfully in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.ironcladapp.com/llms.txt # Ironclad CLM API Documentation | Ironclad Developer Hub Documentati…”
- [probe] “PROBE docs-md: HTTP 200 at https://developer.ironcladapp.com/docs/getting-started.md --- updatedAt: 2026-08-11T20:11:21.000Z --- Fetch the …”
- [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to IroncladClerky exposes a Partner API (create document sets, list forms, submit JSON, poll status) that could in principle be scripted, but authentication is an OAuth authorization-code flow tied to a human sign-in ('coming soon' per docs), and legal documents still require human e-signature, so true unattended/CI automation isn't demonstrated. Missing for 10: machine-to-machine/service-account auth, CLI or CI examples, and confirmation the workflow can complete without a human signing step.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
Ironclad exposes a REST API with OAuth bearer tokens, webhooks, and endpoints to launch workflows, trigger exports, and manage records — all of which can be scripted/automated without the UI, supporting headless-style automation. However there is no CLI, no explicit CI/CD integration examples, and workflow launch still requires a pre-published design from the in-app Workflow Designer, limiting full headless autonomy. Missing for 10: dedicated CLI or SDK for CI pipelines, explicit CI/CD examples, and evidence that workflow publishing itself can be done headlessly.
- [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
- [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
- [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
- [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
- [claimed-docs] “Client submits an API request via Public API with request body payload to trigger an export job”
- [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
ai-native userConnect an agent via an official MCP server
weight 3 · round to ClerkyClerky publishes an official remote MCP server (https://mcp.clerky.com/mcp) with documented setup for Claude, ChatGPT, and other AI assistants, and a live probe confirms the endpoint is real and OAuth-gated as documented. Missing for 10: independent/community confirmation of real-world agent usage and full detail on the OAuth authorization flow completion.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
Ironcladnone0/10Ironclad is not an AI agent itself, so publishing an official MCP server is a plausible, applicable axis, but no evidence pack item mentions MCP at all—only REST API, webhooks, and OAuth are documented.
- [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”
ai-native userDrive the product through a documented public API
weight 3 · round to IroncladClerky publishes real developer documentation for a Partner API (developers.clerky.com, discoverable via llms.txt) covering document-set lifecycle, form schemas, and endpoints like POST /v1/document_sets and GET forms, which is genuine documented programmatic access. However, the docs themselves state OAuth-based authentication is 'coming soon' and not yet live, meaning the API isn't fully operational for external partner integration yet, and scope is limited to Delaware C-Corp formations only. Missing for 10: live/functional authentication flow, evidence of broader API scope, and independent developer reports of successful integration.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
Ironclad ships a documented public REST API (Records, Workflows, Records) with OAuth2 authentication, webhooks, and detailed guides for launching workflows, exports, and embedding clickwraps, clearly enabling programmatic/agentic control of contracting processes. missing for 10: no discoverable OpenAPI/Swagger spec (all candidate paths 404), and no independent/hands-on developer corroboration beyond first-party docs.
- [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
- [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
- [claimed-docs] “integrations can interface directly with underlying contract documents, reading contract text or updating new versions of the document”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to ClerkyClerky documents an OAuth 2.0 bearer-token model for its Partner API with an 'access model' limiting what each token can do, and a live remote MCP server gated by OAuth ('team access you authorize') confirmed via a 401 invalid_token probe rather than being open. However, OAuth for the Partner API is explicitly marked 'coming soon' with scopes/lifetime 'to be published,' and the MCP scoping described is team-level, not clearly a fine-grained least-privilege credential model for individual agents. Missing for 10: published granular scopes/permissions list, confirmed live least-privilege token issuance flow, and independent verification of scope enforcement.
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
Ironcladnone0/10Ironclad's docs confirm OAuth 2.0 bearer token authentication for its API, but there is no evidence of scoped or least-privilege credential issuance (e.g., configurable permission scopes, role-based API keys, or agent-specific credential grants). The axis applies since an API platform could plausibly offer this, but no supporting evidence exists.
- [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
ai-native userBuild against official SDKs
weight 2 · round to ClerkyClerky publishes an official Partner API (REST, JSON schema-driven forms, document-set lifecycle) with docs and an llms.txt developer portal, plus a documented remote MCP server for AI assistants — both usable for programmatic/agentic integration. However there is no evidence of a packaged SDK (client libraries in Python/JS/etc.), and the API's OAuth authentication is explicitly still 'coming soon,' meaning full client access isn't yet live. Missing for 10: language-specific SDK packages, completed/live OAuth client registration, independent developer corroboration of successful integration.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
Ironcladnone0/10Ironclad documents a REST API (Records, Workflows, webhooks, OAuth2) but the evidence pack contains no mention of official SDKs or client libraries in any language, and an OpenAPI spec probe returned 404s across all standard paths.
- [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”
ai-native userSubscribe to events via webhooks
weight 2 · round to IroncladClerkynone0/10The Partner API docs explicitly describe a poll-based lifecycle model (create, submit, poll for state) rather than any webhook/event-subscription mechanism, and no evidence anywhere mentions webhooks or push notifications.
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
Ironclad's developer docs explicitly document webhooks that POST to a user-specified URL when events occur, directly supporting event subscription. Missing for 10: details on event types/filtering, payload schema, retry/security (signature verification) documentation, and independent/hands-on confirmation of reliability.
- [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to IroncladClerkynone0/10Clerky is a legal document/formation platform with an MCP server and partner API for workflow automation, but there is no evidence of AI-generated insights or suggestions surfaced from the user's own data (e.g., analytics, recommendations, anomaly detection) inside the product. The MCP server exposes tools for AI assistants to act on data, not the product itself generating insights.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
Ironclad has a dedicated 'Ironclad AI' product page marketed as 'A New Era of Contract Intelligence,' implying AI-driven insights over contract data, but the evidence pack contains only page titles/taglines with no detail on what specific insights, suggestions, or analytics are actually generated or how a user interacts with them. Missing for 10: concrete feature descriptions (e.g., risk analysis, clause suggestions, obligation extraction), first-party documentation of AI capabilities, and independent/hands-on corroboration of the AI features working as described.
- [claimed-docs] “Built on how contracts really move.”
- [claimed-docs] “A New Era of Contract Intelligence | Ironclad”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to IroncladClerkynone0/10Clerky's MCP server and Partner API let AI assistants or partner products interactively invoke Clerky tools (with team-scoped OAuth access), but nothing in the evidence describes autonomous, unattended background automations (e.g., scheduled triggers, event-driven workflows) running without a live user/assistant session initiating each action.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
Ironclad's API and webhooks allow workflows to be triggered and events to fire automatically in the background (e.g., launching workflows via API, webhooks posting on contract events, integrations that can 'automatically block or push forward approvals'), which supports building autonomous automations. However, this requires custom integration/dev work rather than a native no-code 'set up an automation' feature aimed at AI-native users, and there's no evidence of an agent-oriented automation builder or scheduler. Missing for 10: a first-party no-code automation/agent builder, evidence of AI-driven autonomous triggers, and independent confirmation these automations run reliably unattended.
- [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
- [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
- [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
- [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
- [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to IroncladClerkynone0/10Evidence shows Clerky exposes an MCP server so external AI assistants (Claude, ChatGPT) can call into Clerky's tools, but this is the reverse of a built-in assistant inside Clerky's own product that a user delegates tasks to. No evidence of any in-app AI assistant/chat feature for delegating formation, hiring, or document tasks.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
Ironclad has a dedicated 'Ironclad AI' product page referencing 'contract intelligence,' suggesting some built-in AI capability, but the evidence pack contains only marketing taglines with no detail on what tasks can be delegated to an assistant, how it's invoked, or its scope. Missing for 10: description of assistant task delegation, concrete feature list, hands-on or independent corroboration of AI assistant functionality.
- [claimed-docs] “Built on how contracts really move.”
- [claimed-docs] “A New Era of Contract Intelligence | Ironclad”
ai-native userOperate the product with natural-language commands
weight 2 · round to ClerkyClerky ships a live MCP server (mcp.clerky.com) enabling Claude/ChatGPT and other AI assistants to invoke Clerky tools with team-scoped access, which is the mechanism for natural-language operation; a probe confirms the endpoint is real and OAuth-gated rather than vaporware. Missing for 10: no hands-on transcript or independent report of actually issuing natural-language commands through the MCP tools, and no evidence of a broader in-app conversational/NL command interface beyond the MCP integration.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
Ironcladnone0/10Evidence shows Ironclad offers APIs, webhooks, and a no-code workflow builder, but nothing indicates a natural-language command interface for operating the product; the 'Ironclad AI' page is only a marketing teaser with no described NL capability.
- [claimed-docs] “Built on how contracts really move.”
- [claimed-docs] “A New Era of Contract Intelligence | Ironclad”
- [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnClerkynone0/10Clerky's developer docs describe the Partner API lifecycle, forms, and authentication in prose (clerky-docs-19/20/21) and llms.txt lists doc pages, but there is no evidence of an interactive API reference (e.g., Swagger/OpenAPI explorer) or runnable examples; explicit probes for openapi.json/swagger.json all returned 404 (clerky-probe-3).
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
Ironcladnone0/10Ironclad publishes a standard API reference (getting-started, authentication, webhooks, workflows) but nothing in the evidence indicates an interactive console or runnable code examples; a probe for an OpenAPI/Swagger spec (which typically powers interactive 'try it' consoles) returned 404 on all candidate paths, suggesting no such tooling exists.
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
- [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnClerkynone0/10Clerky has a documented Partner API with REST endpoints and JSON schema forms, but explicit probes for OpenAPI/Swagger spec files (openapi.json, swagger.json, .well-known/openapi.json) all returned 404, and no docs page offers a downloadable machine-readable spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
Ironcladnone0/10Ironclad has extensive API documentation (Records, Workflows, Webhooks) but a direct probe of common OpenAPI spec locations returned 404 for all candidates, and no evidence pack item shows a downloadable machine-readable spec file. missing for 10: an actual OpenAPI/Swagger JSON or YAML file accessible for download, any documented endpoint serving the spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnClerkynone0/10Clerky's Partner API and MCP server docs describe production workflows (document sets, OAuth, live formation filings) but no evidence anywhere mentions a sandbox, test mode, or staging environment separate from production data.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnClerkynone0/10The Partner API docs show endpoints prefixed with /v1/ but there is no evidence of a documented API versioning scheme, changelog, or deprecation policy anywhere in the docs, llms.txt index, or OpenAPI probes (which 404). Missing for 10: any explicit versioning/deprecation policy documentation, changelog, or migration guidance for breaking changes.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
Ironcladnone0/10Evidence shows a documented REST API (Records, Workflows, Webhooks) but no mention of API versioning scheme or a documented deprecation policy anywhere in the docs pack, and OpenAPI spec probes all 404. missing for 10: explicit API version numbering, changelog/release notes, deprecation policy or sunset timeline documentation.
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”
Audit trust — stories about audit trust in this arenaAudit trust
Stories about audit trust in this arena
Audit
legal-ops leadRely on a tamper-evident audit trail and completion certificate for every signed document
weight 2 · round to ClerkyClerky documents that it logs every change made to a document set or workspace so admins can see who did what, which is a basic audit-log capability, but there is no mention of tamper-evidence (e.g., cryptographic sealing, hash-chained logs) or of a signing completion certificate being issued for executed documents. Missing for 10: tamper-evident/cryptographic audit trail mechanics, completion certificate artifact, and any independent verification of these claims.
- [claimed-docs] “We log every change anyone makes to a document set or workspace, so you can always see who was responsible for what.”
Ironcladnone0/10Ironclad is a CLM/e-signature platform where a tamper-evident audit trail and completion certificate would be a natural expected capability, but the evidence pack contains no mention of audit trails, certificates of completion, or tamper-evidence for signed documents—only generic pages about signing, storing, and API access.
- [claimed-docs] “Contract Signing Has Never Been Easier”
- [claimed-docs] “Contract Signing Has Never Been Easier | Ironclad”
- [claimed-docs] “Store Contracts Securely, Find Them Easily”
legal-ops leadRequire stronger signer identity verification (SMS, ID check, knowledge-based) on sensitive documents
weight 1 · round drawnClerkynone0/10No evidence anywhere in the pack mentions signer identity verification methods like SMS, ID check, or knowledge-based authentication for document signing; Clerky's documentation focuses on formation workflows, collaboration, and audit logs, not signer verification strength.
Ironcladnone0/10No evidence in the pack mentions signer identity verification methods such as SMS, ID check, or knowledge-based authentication for e-signature; the docs cover contract signing generally but not these verification tiers.
- [claimed-docs] “Contract Signing Has Never Been Easier”
- [claimed-docs] “Contract Signing Has Never Been Easier | Ironclad”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to IroncladClerkynone0/10Evidence shows Clerky's Partner API and MCP server operate on a single document set at a time (create, fill forms, submit, poll) with no batch/bulk endpoints or bulk document/task operations documented; task assignment features are per-item, not bulk. Missing for 10: any bulk create/update endpoint, batch API operations, or bulk import/export capability across multiple items.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
Ironclad's Records/Workflows APIs allow retrieving, creating, and updating records/workflows programmatically, which enables scripted bulk operations across many contracts/records, and data-export jobs support bulk data retrieval. However, there is no explicit documentation of a native bulk/batch endpoint, rate-limit guidance for bulk calls, or first-party bulk-operation UI/API designed for AI-native agents. Missing for 10: dedicated bulk/batch API endpoints, documented pagination/batching best practices for large-scale operations, and independent evidence of successful bulk automation at scale.
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [claimed-docs] “Client submits an API request via Public API with request body payload to trigger an export job”
- [claimed-docs] “Template IDs can be obtained in-app or via API”
Compliance registered agent — stories about compliance registered agent in this arenaCompliance registered agent
Stories about compliance registered agent in this arena
Compliance
legal-ops leadSee a compliance calendar of upcoming filing deadlines and get reminders before each one
weight 2 · round drawnClerkynone0/10No evidence in the pack of any compliance calendar, filing-deadline tracking, or reminder feature; Clerky's evidence covers document formation, collaboration, task assignment, and API/MCP integrations but nothing about deadline tracking or reminders.
Compliance agentic
ai-native userDelegate an annual report or compliance filing to an agent that prepares it through the platform with minimal human input
weight 2 · round to ClerkyClerky offers a remote MCP server and Partner API that let an AI assistant interact with document sets, forms, and workflow state (clerky-docs-19/20/22), and IRS forms can be completed and submitted online (clerky-docs-5/15), suggesting some agent-driven compliance work is possible. However, the probe shows the MCP tools are read-only with team-scoped OAuth access (clerky-probe-5), and there is no evidence of an actual 'annual report' or ongoing compliance-filing product, nor of an agent completing filings end-to-end with minimal human input. missing for 10: evidence of annual report/compliance-filing capability specifically, evidence the MCP/API can autonomously submit filings (not just read/collect data), and confirmation that human sign-off isn't required at each step.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine. 100% in-house, not outsourced.”
Ironcladnone0/10Ironclad's evidence covers APIs, workflows, and webhooks for contract lifecycle automation, but nothing describes an agent autonomously preparing an annual report or compliance filing end-to-end with minimal human input; 'Ironclad AI' references are generic marketing without this specific capability.
- [claimed-docs] “Built on how contracts really move.”
- [claimed-docs] “A New Era of Contract Intelligence | Ironclad”
- [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
- [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
Contract lifecycle — stories about contract lifecycle in this arenaContract lifecycle
Stories about contract lifecycle in this arena
Clm agentic
ai-native userHave an agent monitor contract renewals and deadlines through the product's API and act before they lapse
weight 2 · round to IroncladClerkynone0/10Clerky's API and MCP server are scoped to formation document-set workflows (create, fill forms, sign, poll lifecycle state) — there is no evidence of tracking contract renewal dates, deadline alerts, or proactive lapse-prevention actions via the API or MCP tools.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
Ironclad exposes a Records API, Workflows API, and webhooks that could let an external agent poll contract data or receive event notifications and then trigger workflow actions via the API, which is the raw plumbing needed for automated renewal/deadline monitoring. However, there is no explicit documentation of a renewal-date or deadline field/endpoint, no webhook event specifically for upcoming expirations, and no mention of an agent-oriented monitoring pattern. Missing for 10: explicit renewal/deadline tracking endpoints or webhook events, documented example of automated pre-lapse action, independent/hands-on confirmation that this workflow works in practice.
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
- [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
Clm authoring
legal-ops leadDraft, negotiate, and redline contracts in a controlled workflow instead of email attachments
weight 3 · round to IroncladClerky offers real-time collaboration, attorney review/comment, customization of key terms, and full audit logging of document set changes, which supports a 'controlled workflow instead of email attachments' for its own formation/equity documents. However, there is no evidence of redlining, track-changes, or multi-round negotiation with external counterparties—Clerky's workflow is field-based data entry and e-signature for standardized startup legal docs, not general contract redlining. Missing for 10: explicit redline/track-changes tooling, version comparison, negotiation cycles with external parties, and support for arbitrary (non-template) contracts.
- [claimed-docs] “We log every change anyone makes to a document set or workspace, so you can always see who was responsible for what.”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time. Rest easy knowing everyone is looking at t…”
- [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
Ironclad's docs show core CLM capabilities relevant to the story—no-code contract creation, workflow designer for approvals, APIs to update contract language and control the process, and structured storage/signing—supporting a controlled workflow model instead of email attachments. However, the pack lacks explicit evidence of a redlining/track-changes or counterparty negotiation feature, and community citations are thin/tangential rather than corroborating negotiation workflows in practice. Missing for 10: explicit redline/version-comparison feature documentation, first-hand or independent evidence of negotiation collaboration replacing email attachments.
- [claimed-docs] “Create Contracts in No-Code Builder”
- [claimed-docs] “Built on how contracts really move.”
- [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
- [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
- [claimed-docs] “integrations can interface directly with underlying contract documents, reading contract text or updating new versions of the document”
- [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
- [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
Clm repository
legal-ops leadStore executed contracts in a searchable repository with key terms and metadata extracted
weight 2 · round to IroncladClerkynone0/10Clerky is a formation/document-generation tool; evidence covers document sets, activity logs, and collaboration but nothing about a searchable repository of executed contracts with extracted key terms/metadata—no full-text search, term extraction, or metadata tagging is described anywhere in the pack.
Ironclad's marketing and developer docs explicitly describe a 'Store Contracts Securely, Find Them Easily' repository and a Records API for retrieving/updating structured contract metadata, plus an 'Ironclad AI'/Contract Intelligence product implying key-term extraction. Missing for 10: detailed documentation of specific extracted fields/metadata schema, search functionality specifics, and independent/hands-on corroboration of extraction accuracy.
- [claimed-docs] “Store Contracts Securely, Find Them Easily”
- [claimed-docs] “Store Contracts Securely, Find Them Easily | Ironclad”
- [claimed-docs] “Built on how contracts really move.”
- [claimed-docs] “A New Era of Contract Intelligence | Ironclad”
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
Clm workflow
legal-ops leadRoute contracts through configurable approval workflows before signature
weight 2 · round to IroncladClerkynone0/10Clerky's evidence covers document generation, collaboration, task assignment, and attorney review invites, but nothing describes configurable approval workflows/routing before signature (e.g., multi-step approval chains, conditional routing rules, or sign-off gating). Collaboration/task features are not the same as an approval workflow engine.
- [claimed-docs] “We've built features that let you easily assign tasks to co-founders and work on everything together.”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time. Rest easy knowing everyone is looking at t…”
Ironclad's docs describe Workflow Designer for building and publishing approval workflows, launching workflows via API/UI, and explicitly reference 'approval and signature policies' being enforced by the platform (docs-8, docs-15, docs-16, docs-20), directly matching the story of routing contracts through configurable approval steps before signature. Missing for 10: independent/hands-on verification of the approval-workflow configuration UI and no detailed walkthrough of multi-stage approval logic beyond brief doc mentions.
- [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
- [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
- [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
- [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
- [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
Document automation — stories about document automation in this arenaDocument automation
Stories about document automation in this arena
Doc api
ai-native userHave an agent draft an NDA and route it for signature end-to-end via the product's API or MCP server
weight 3 · round to IroncladClerkynone0/10Clerky's Partner API and MCP server are real and documented, but the API explicitly states it 'currently supports Delaware C-Corporation formations' only, and the MCP server tools are scoped to Clerky's startup-formation document sets (cap tables, safes, stock plans) — there is no evidence of NDA drafting or NDA e-signature routing via either channel.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
Ironclad's Public API supports creating records from templates, launching workflows, and retrieving/interacting with workflows and contract data (ironclad-docs-2,5,13,23), which could technically support an agent drafting and routing an NDA end-to-end. However there is no evidence of an official MCP server, no explicit NDA-drafting example, and the docs note that approval/signature policies are handled by the platform rather than fully exposed for programmatic completion (ironclad-docs-15). Missing for 10: official MCP server, concrete NDA-draft-to-signature API walkthrough, independent confirmation of full automation without manual signature steps.
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
- [claimed-docs] “Template IDs can be obtained in-app or via API”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”
developerGenerate, populate, and send legal documents programmatically through a documented API
weight 3 · round to IroncladClerky publishes a documented Partner API with concrete lifecycle steps (create document set, GET forms with json_schema, POST values, poll state) covering document generation and population (clerky-docs-19, clerky-docs-20). However, the API currently only supports Delaware C-Corp formations, OAuth-based authentication is explicitly stated as 'coming soon' rather than live (clerky-docs-21), and 'sending' is really 'user signs on Clerky' rather than a programmatic send step, so the story is only partially realized in production. Missing for 10: live/production authentication for partners, broader document-type coverage beyond formations, and independent/hands-on evidence of a working end-to-end integration.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
Ironclad's developer docs describe a documented API (Workflows API to launch workflows, Records API to create/retrieve contract data, template IDs obtainable via API, webhooks for events) that supports generating, populating, and sending contracts programmatically. However, launching workflows still requires a pre-published Workflow Designer template (admin-gated, no-code step) rather than fully programmatic document creation, and there's no independent/hands-on developer corroboration of the API in practice, nor a discoverable OpenAPI spec (probe found only 404s). Missing for 10: independent developer testimonials of using the API end-to-end, a public OpenAPI/swagger spec, and evidence of fully code-driven document creation without the Workflow Designer dependency.
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
- [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
- [claimed-docs] “Template IDs can be obtained in-app or via API”
- [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”
Equity fundraising — stories about equity fundraising in this arenaEquity fundraising
Stories about equity fundraising in this arena
Fundraising
founderGenerate and sign SAFEs or convertible notes on standard terms without drafting from scratch
weight 3 · round to ClerkyClerky's core startup product explicitly supports issuing SAFEs and convertible notes on standard forms with customizable key terms, collaborative editing, attorney review, and e-signature—removing the need to draft from scratch. Community feedback corroborates ease of use and frictionless process for founders using Clerky's paperwork workflows. Missing for 10: independent hands-on account of actually generating/signing a SAFE end-to-end and specifics on which standard SAFE variants (YC, pre/post-money) are supported.
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
- [community] “Wow, this is great. Props to the Clerky team. If this had existed in 2015 we would have used it, instead we paid a few thousand extra.”
- [community] “We were among the first companies to use this product at Crowdbotics... the process was almost totally frictionless and Clerky's support was…”
Ironcladnone0/10Ironclad is a general contract lifecycle management platform with no-code contract creation, e-signature, and workflow tools, but the evidence never mentions SAFEs, convertible notes, or startup fundraising document templates specifically — the community comments reference generic 'industry standard templates' causing legal concerns, not equity instruments.
- [claimed-docs] “Create Contracts in No-Code Builder”
- [claimed-docs] “Contract Signing Has Never Been Easier”
- [community] “What is up with the pre-loaded 'industry standard' templates? Are you guys a law firm? Do you carry malpractice insurance in case these temp…”
Governance
legal-ops leadPrepare board consents and resolutions and collect approvals online
weight 2 · round to ClerkyClerky's docs describe document-set collaboration, inviting co-founders/attorneys to review and comment in real-time, and issuing stock/options (which typically requires board approval) — these features generally support drafting and collecting sign-off on corporate paperwork online. However, no evidence explicitly names 'board consents' or 'resolutions' as a document type or confirms an approval-workflow specifically for board actions. Missing for 10: explicit mention of board consent/resolution templates, a dedicated approval/e-signature workflow for board members, and independent confirmation that board-level approvals are collected through the platform.
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time. Rest easy knowing everyone is looking at t…”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [claimed-docs] “We've built features that let you easily assign tasks to co-founders and work on everything together.”
- [community] “Clerky gives me management tools (including the post-incorporation package: Fundraising, Hiring and Maintenance) although this does not give…”
Ironclad is a general contract lifecycle management platform with workflow builders, e-signature, and approval routing that could be used to create and route a board consent/resolution document for approval, but there is no specific evidence of board-consent/resolution templates, cap-table/equity-fundraising features, or governance-specific workflows tailored to legal-ops board approvals. missing for 10: evidence of board consent/resolution-specific templates or workflows, evidence of equity-fundraising or governance use cases, and independent validation that Ironclad is used for board approvals specifically rather than generic contracts.
- [claimed-docs] “Create Contracts in No-Code Builder”
- [claimed-docs] “Contract Signing Has Never Been Easier”
- [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
- [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
Hiring
legal-ops leadRun hiring and equity paperwork — offer letters, confidentiality/IP agreements, and option grants — through the platform
weight 2 · round to ClerkyClerky's own product docs explicitly cover hiring paperwork (offer/hiring workflows), confidentiality/IP agreements implied via founder/employee onboarding docs, and equity issuance (stock, stock options, safes, convertible notes) via a stock plan, plus attorney oversight/collaboration features for legal-ops review. Community reviews corroborate real-world use of the hiring/fundraising/maintenance packages. Missing for 10: explicit mention of confidentiality/IP agreement templates by name and independent case studies detailing legal-ops workflows specifically.
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
- [claimed-docs] “Forming a startup on Clerky enables access to a legal dashboard that makes it easy to do additional legal paperwork.”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [community] “Clerky gives me management tools (including the post-incorporation package: Fundraising, Hiring and Maintenance) although this does not give…”
Ironclad is a general-purpose CLM platform with no-code contract creation, workflows, and e-signature that could technically be configured to handle offer letters or NDAs (ironclad-docs-9, ironclad-docs-10, ironclad-comm-6 mentions using it for contractor onboarding), but there is no evidence of purpose-built templates, workflows, or integrations for hiring/equity paperwork specifically, especially option grants which typically require cap-table integration. Missing for 10: dedicated HR/equity templates, option grant or cap-table integration evidence, and any case study showing legal-ops running full hiring paperwork through Ironclad.
- [claimed-docs] “Create Contracts in No-Code Builder”
- [claimed-docs] “Contract Signing Has Never Been Easier”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [community] “We use IronClad at Zinc and they are amazing. Whenever we have a new contractor, we shoot them an email (actually now we click a button) and…”
Esignature flows — stories about esignature flows in this arenaEsignature flows
Stories about esignature flows in this arena
Esign
founderSend a document for legally binding e-signature to multiple recipients with routing
weight 3 · round to IroncladClerky's document sets clearly involve multiple signers (collaborators, attorneys, co-founders) and a signing workflow (clerky-docs-13/17, clerky-docs-19/20), but this is signing within Clerky's own fixed legal document templates rather than a general-purpose 'send any document for signature with custom multi-recipient routing' capability. No evidence describes configurable signing order, roles, or routing logic for recipients. Missing for 10: explicit documentation of routing/sequencing controls, ability to send arbitrary documents (not just Clerky-generated ones) for signature, and independent confirmation of multi-recipient routing behavior.
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time. Rest easy knowing everyone is looking at t…”
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
Ironclad markets a dedicated 'Sign Contracts' capability and documents a Workflow Designer/Workflows API that lets processes 'follow approval and signature policies,' implying routing across multiple parties, and workflows can be launched via API for automation. However, the pack lacks concrete detail on multi-recipient routing order, legally-binding signature specifics, or independent verification of the e-signature flow working end-to-end. Missing for 10: explicit documentation of multi-recipient signing order/routing configuration, legal-binding compliance details (e.g., ESIGN/UETA), and independent/hands-on confirmation of the signature flow.
- [claimed-docs] “Contract Signing Has Never Been Easier”
- [claimed-docs] “Contract Signing Has Never Been Easier | Ironclad”
- [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
- [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
Esign embed
developerEmbed the signing experience inside my own app or website
weight 2 · round to IroncladClerky's Partner API lets a developer create a document set, render forms, and collect data inside their own product, but the docs explicitly state 'Users enter formation information in your product and sign documents on Clerky' — meaning the actual signing step happens on Clerky's own platform rather than being embedded, and OAuth authentication for partners is still listed as 'coming soon' rather than live. missing for 10: evidence of an embeddable signing widget/iframe, live partner OAuth flow, and any third-party confirmation of a working embedded integration.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
Ironclad provides documented Clickwrap Workflow embedding via iframe for signing/agreement flows directly on a developer's own page. Missing for 10: independent hands-on confirmation of the embedding working in production, and broader coverage beyond clickwrap (e.g., full contract e-signature embedding) is not detailed.
- [claimed-docs] “This is a simple example outlining how to embed a clickwrap within an iframe.”
- [claimed-docs] “Technical audiences will learn how to use Ironclad's Clickwrap Workflow to implement embedded clickwrap in their own pages.”
- [claimed-docs] “This guide will cover the steps for embedding a clickwrap in your own page, once you have created and published a Clickwrap Workflow.”
Esign scale
legal-ops leadBulk-send the same document to many recipients at once
weight 1 · round drawnClerkynone0/10Clerky's evidence describes single document-set collaboration, invitations, and signature workflows for specific named parties (co-founders, employees, attorneys) but nothing about bulk-sending one document to many recipients at once, a feature typical of e-signature platforms like DocuSign.
Ironcladnone0/10Evidence shows Ironclad's Workflow API can launch individual contract workflows and clickwraps can be embedded, but there is no documentation or feature reference to a bulk-send capability (sending one document to many recipients simultaneously). Missing for 10: any mention of bulk-send, mail-merge-style multi-recipient dispatch, or batch signature request tooling.
- [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
legal-ops leadSet signing order, automatic reminders, and expirations on outstanding signature requests
weight 1 · round drawnClerkynone0/10No evidence describes signing order, automatic reminders, or expiration settings for signature requests; Clerky's evidence focuses on document collaboration, workspace access, and formation workflows, not e-signature controls of this kind.
Ironcladnone0/10Evidence only shows generic e-signature and workflow/API pages but no mention of configuring signing order, automatic reminders, or expiration settings on signature requests. Missing for 10: any documentation of signing order configuration, reminder scheduling, or expiration/timeout settings for signature requests.
- [claimed-docs] “Contract Signing Has Never Been Easier”
- [claimed-docs] “Contract Signing Has Never Been Easier | Ironclad”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to IroncladClerky has a Partner API but it explicitly 'currently supports Delaware C-Corporation formations' only, a narrow subset of the 40+ products, safes, stock plans, hiring, banking integrations, and legal dashboard features described in the UI docs. OAuth authentication is also still 'coming soon,' meaning the API isn't even fully live yet, and there's no evidence of API coverage for post-formation workflows (safes, convertible notes, hiring, stock issuance, IRS filing, banking apps) that are core UI capabilities. Missing for 10: API coverage for post-incorporation products (safes, hiring, equity issuance, IRS/bank filings), live OAuth access, and evidence of parity across the 40+ advanced products.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Attorney accounts get access to over 40 advanced products that are not publicly available.”
- [claimed-docs] “Apply for accounts with the most popular banks for startups. Pre-filled applications make it as easy as possible.”
Ironclad exposes a broad API (Records, Workflows, Webhooks, Data Exports, launching published workflows) letting AI-native users read/write core contract data and trigger processes, but design-time actions like building/publishing workflows and templates are explicitly UI/no-code-builder only ('See your internal company admin for access to Workflow Designer'), and no public OpenAPI spec was found (probe returned 404s for all standard spec paths), indicating incomplete machine-discoverable parity with the UI. missing for 10: API-driven workflow/template design and publishing, a public OpenAPI/schema for full endpoint discovery, and independent confirmation that all UI actions (e.g., clickwrap embedding config, template creation) are API-accessible.
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
- [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
- [claimed-docs] “Create Contracts in No-Code Builder”
- [claimed-docs] “Client submits an API request via Public API with request body payload to trigger an export job”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to IroncladClerkynone0/10No evidence of any bulk data export in open/standard formats (e.g., document download bundles, JSON/CSV exports of legal data) for users to take their data and leave; the Partner API and MCP server are designed for partner integrations/AI assistants working within Clerky, not full data portability/exit. Probes also show no llms.txt/docs export or export-oriented endpoints beyond the legal-workflow API.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [probe] “PROBE llms.txt: HTTP 404 at https://handbooks.clerky.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://handbooks.clerky.com/legal-concepts.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
Ironclad documents a Data Exports API and Records/Workflows APIs that let customers retrieve their contract records and trigger export jobs, which supports data portability, but nothing explicitly states the export format is open/standard (e.g., JSON/CSV) or that a full, wholesale data exit is guaranteed. missing for 10: explicit statement of open export formats, documentation of a full account data export/deletion process, and independent confirmation that customers can fully migrate off Ironclad.
- [claimed-docs] “Client submits an API request via Public API with request body payload to trigger an export job”
- [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnClerkynone0/10No evidence in the pack addresses AI training data usage, opt-out settings, or any privacy policy statement about model training; Clerky's materials focus on legal document workflows, MCP/API integration, and formation services with nothing on this axis.
ai-native userControl data retention and deletion
weight 2 · round drawnClerkynone0/10No evidence in the pack addresses data retention policies, export, or deletion controls for user data within Clerky; the docs focus on formation, collaboration, and MCP/API features, none of which mention retention or deletion. Missing for 10: any documentation of data retention periods, deletion requests, or export/erasure controls.
Ironcladnone0/10The evidence pack covers API/webhook/workflow documentation and data export jobs, but contains no mention of data retention policies, deletion controls, or AI-training data opt-outs. This is a fair axis for any SaaS handling contract data, so absence of evidence means 'none' rather than 'na'.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnClerkynone0/10No evidence in the pack addresses telemetry, usage tracking, or any opt-out mechanism for Clerky; the documentation focuses entirely on legal/document workflows with no privacy-controls content.
Templates library — stories about templates library in this arenaTemplates library
Stories about templates library in this arena
Templates
founderAnswer guided questionnaires that fill in legal documents correctly and flag choices that need attorney review
weight 1 · round to ClerkyClerky's docs show forms with structured fields/json_schema that collect info to fill documents (clerky-docs-19, clerky-docs-20), easy customization of key terms (clerky-docs-11), and the ability to loop in an attorney to review and comment on entered information (clerky-docs-12). However, there is no explicit evidence of a system that automatically flags specific choices as needing attorney review versus a general 'invite attorney' collaboration feature. missing for 10: explicit automated flagging/warning UI for attorney-review-needed choices, independent user account of the questionnaire flow itself, and confirmation the guided form correctly maps answers to legal documents.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
Ironclad's no-code builder and workflow designer support guided contract creation via questionnaires that populate templates, but there's no evidence of specific attorney-review flagging logic, and community comments explicitly raise concerns about unauthorized legal practice and lack of legal vetting for templates. missing for 10: explicit guided questionnaire walkthrough, evidence of attorney-review flagging/escalation logic, independent validation that generated documents are legally correct, resolution of unauthorized-practice-of-law concerns raised by community.
- [claimed-docs] “Create Contracts in No-Code Builder”
- [claimed-docs] “Create Contracts in No-Code Builder | Ironclad”
- [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
- [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
- [community] “This appears to be the unauthorized practice of law... I'll give you guys a week to rethink your service and get a lawyer on board, but next…”
- [community] “What is up with the pre-loaded 'industry standard' templates? Are you guys a law firm? Do you carry malpractice insurance in case these temp…”
- [community] “Full disclosure: Actual flesh-and-blood lawyer here. These tools are great when things are going well... you might be pushing off minor expe…”
founderStart from a library of vetted standard legal templates (NDAs, agreements, policies) instead of hiring counsel for routine documents
weight 2 · round to ClerkyClerky documents show a template-driven system for startup-specific legal paperwork (formation, safes/convertible notes, stock plans, hiring/equity agreements, IRS forms) that lets founders self-serve rather than hire counsel for those documents. However, the evidence never mentions NDAs, general contract templates, or company policy documents, which are explicitly named in the story. Missing for 10: evidence of NDA templates, general business agreement templates, and policy document templates beyond incorporation/equity paperwork.
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
- [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
- [community] “Clerky gives me management tools (including the post-incorporation package: Fundraising, Hiring and Maintenance) although this does not give…”
Ironcladdisputedcontradicted3/10Ironclad markets contract creation tools (No-Code Builder, workflow templates) that could serve as a template library, but hands-on community feedback from early users directly disputes the 'vetted standard legal templates' framing: users questioned whether the templates constituted unauthorized practice of law and whether Ironclad carried malpractice insurance, and the company pulled the product to rethink it rather than defend the templates as reliable substitutes for counsel. Missing for 10: any current documentation of a curated NDA/agreement/policy template library, evidence of legal vetting or counsel review, and independent validation that founders can safely skip a lawyer.
- [claimed-docs] “Create Contracts in No-Code Builder”
- [claimed-docs] “Create Contracts in No-Code Builder | Ironclad”
- [community] “This appears to be the unauthorized practice of law... I'll give you guys a week to rethink your service and get a lawyer on board, but next…”
- [community] “What is up with the pre-loaded 'industry standard' templates? Are you guys a law firm? Do you carry malpractice insurance in case these temp…”
- [community] “Hey everyone, thanks a ton for your comments and interest. Now that we've had a chance to get some feedback, we'll be closing up the site wh…”
- [community] “Full disclosure: Actual flesh-and-blood lawyer here. These tools are great when things are going well... you might be pushing off minor expe…”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableClerkyn/aClerky is a legal-paperwork SaaS, not an AI agent/assistant platform; the evidence shows it exposes its own remote MCP server (mcp.clerky.com) for other AI assistants to consume its tools, which is the opposite direction from this story (a user plugging external MCP servers into Clerky so it can use their tools). There is no evidence Clerky itself acts as an MCP client consuming outside tools, and this capability is outside its product category.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
Ironcladn/aIronclad is a contract lifecycle management SaaS product, not an AI agent client; there is no mention of MCP server integration in any evidence, and the product's own AI features are not framed as an agent capable of consuming external MCP tools. This axis applies to agent-type products or platforms with an MCP ecosystem story, but no such angle exists here — the evidence only covers REST/webhook APIs and OAuth for traditional integrations.
- [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
- [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
- [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
ai-native userUse an official CLI
weight 2 · not comparableClerkynone0/10Clerky provides a Partner API and a remote MCP server, but no evidence of an official CLI tool for AI-native workflows; probes for docs/llms.txt found no CLI references.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · not comparableClerkyn/aClerky is a legal document/incorporation product, not a rules/automation-engine platform; defining event-triggered automation rules is a category error for this type of product.
Ironclad supports webhooks to trigger outbound notifications on events and an API/Workflows API to programmatically launch or update workflows, plus integrations that can block/push forward approvals automatically — this gives event-driven automation. However there's no evidence of a native rules engine where AI-native users can define arbitrary conditional 'if event then action' automations without building custom integration code. Missing for 10: a first-class rules/automation builder, documented trigger-condition-action configuration UI, and independent confirmation of automated rule execution in practice.
- [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
- [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
- [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
- [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableClerkyn/aClerky is a legal/formation document platform; scheduling recurring automated jobs or workflows is not a fit for its product category (document sets, formations, partner API, MCP tools for legal paperwork), and no evidence suggests any job-scheduling capability.
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableClerkyn/aClerky is a legal-document/formation automation service (document sets, e-signatures, filings), not a workflow/automation-builder product with versionable automations to review or roll back; the closest evidence is basic audit logging of document-set changes, not automation versioning.
- [claimed-docs] “We log every change anyone makes to a document set or workspace, so you can always see who was responsible for what.”
Ironcladnone0/10Ironclad's docs mention publishing workflows via Workflow Designer and admin access, but there is no evidence of version history, review/approval flow for automation changes, or rollback capability for workflows/integrations themselves.
- [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
- [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
founderFile annual reports and franchise tax on time through the platform
weight 2 · not comparableClerkynone0/10No evidence anywhere in the pack mentions annual report filing, franchise tax filing, registered agent services, or compliance deadline tracking; Clerky's documented scope is formation, equity, hiring, banking, and IRS forms only.
founderUse the platform as my registered agent and receive scanned legal mail and service of process digitally
weight 2 · not comparableClerkynone0/10No evidence anywhere in the pack that Clerky offers registered agent services or digital mail/service-of-process scanning; its documented scope is document generation, e-signature, IRS filings, banking, and API/MCP integrations. Registered agent service is a plausible offering for a startup-formation platform, so absence of evidence yields 'none' rather than 'na'.
legal-ops leadTrack contract renewals, expirations, and obligations with automatic alerts
weight 2 · not comparableClerkyn/aClerky is a startup legal-document formation and equity/incorporation platform, not a contract-lifecycle management tool; there is no evidence of contract renewal tracking, expiration alerts, or obligation management, and this is not the kind of capability Clerky's product category would offer.
Ironcladnone0/10The evidence pack covers Ironclad's contract creation, storage, signing, workflows, and API/webhooks, but nowhere mentions renewal tracking, expiration dates, obligation management, or automatic alerts—core to this story. Missing for 10: any documentation of renewal/expiration tracking, obligation management, or alerting/notification features.
- [claimed-docs] “Store Contracts Securely, Find Them Easily”
- [claimed-docs] “Store Contracts Securely, Find Them Easily | Ironclad”
- [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
founderObtain a federal EIN for my new company through the platform
weight 2 · not comparableClerky explicitly advertises completing and submitting IRS forms (including EIN application, a core IRS form for new companies) fully online without fax, done in-house — clerky-docs-5/15. Community evidence corroborates general ease/friction of the incorporation process but doesn't specifically dispute the EIN step. Missing for 10: independent hands-on confirmation specifically of the EIN application step (vs. general process reviews) and detail on turnaround time.
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine. 100% in-house, not outsourced.”
- [community] “We were among the first companies to use this product at Crowdbotics... the process was almost totally frictionless and Clerky's support was…”
founderIncorporate a Delaware startup end-to-end online, including the filing, bylaws, and initial board approvals
weight 3 · not comparableClerky is purpose-built for online Delaware incorporation, covering formation filing, customizable bylaws/legal documents, board approvals, and post-incorporation paperwork, corroborated by positive hands-on founder accounts of using it for incorporation. missing for 10: independent verification of the full end-to-end filing-to-board-approval flow (vs marketing pages), and a documented step-by-step walkthrough showing bylaws/board consent generation explicitly.
- [claimed-docs] “Forming a startup on Clerky enables access to a legal dashboard that makes it easy to do additional legal paperwork.”
- [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
- [community] “I used Clerky in 2016. I found them pleasant and easy to work with. Took the time to answer all of my questions. Prices quite reasonable.”
- [community] “We were among the first companies to use this product at Crowdbotics... the process was almost totally frictionless and Clerky's support was…”
- [community] “I love Stripe Atlas overall for fast/excellent UX, but Clerky supports PBCs and a higher degree of customization (eg useful for incorporatin…”
Ironcladn/aIronclad is a contract lifecycle management (CLM) platform for drafting, signing, and managing contracts/workflows, not a Delaware incorporation or company-formation service — filing articles of incorporation, generating bylaws, and initial board consent packages is outside its product category.
founderComplete post-incorporation setup — founder stock purchases, IP assignment, and 83(b) elections — with correct standard paperwork
weight 2 · not comparableClerky's docs confirm founder stock/equity issuance (clerky-docs-9, clerky-docs-16) and completing/submitting IRS forms online (clerky-docs-5, clerky-docs-15), which covers 83(b) elections, and community confirms a post-incorporation 'Maintenance' package (clerky-comm-3). However, IP assignment agreements are not explicitly named in the evidence pack, so full coverage of that specific document isn't directly confirmed. missing for 10: explicit documentation of IP assignment agreement generation, independent verification that 83(b) filings are correctly executed, and hands-on account of the full post-incorporation flow.
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine. 100% in-house, not outsourced.”
- [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
- [community] “Clerky gives me management tools (including the post-incorporation package: Fundraising, Hiring and Maintenance) although this does not give…”
Ironcladn/aIronclad is a contract lifecycle management platform for enterprises, not an incorporation/formation service; it has no offering for founder stock purchase agreements, IP assignment, or 83(b) elections as part of company setup — this axis belongs to incorporation-specific products (e.g., Stripe Atlas, Clerky, Firstbase), not general contract management software.
ai-native userRead the product's source under an open license
weight 2 · not comparableClerkynone0/10Clerky is a closed-source legal SaaS product; there is no evidence of any open-source license or public source repository, and probes for open documentation/API artifacts returned 404s. Missing for 10: any open-source license, public code repository, or source availability statement.
- [probe] “PROBE llms.txt: HTTP 404 at https://handbooks.clerky.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://handbooks.clerky.com/legal-concepts.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
ai-native userSelf-host the core product
weight 3 · not comparableClerkyn/aClerky is a SaaS legal/formation platform tied to legal filings and attorney workflows; self-hosting the core product is not a coherent capability for this category, as it depends on Clerky's own infrastructure, attorneys, and IRS/state filing pipelines.
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableClerkyn/aClerky is a legal document/formation service, not infrastructure with configurable data residency; the evidence pack contains no mention of region/residency options, and this is not a fair capability to expect from this type of product (a US-focused legal filing service).
Ironcladnone0/10No evidence in the pack mentions data residency, regional storage options, or geographic hosting controls for Ironclad; the docs focus on API, workflows, and contract management only. Missing for 10: any mention of region selection, data residency guarantees, or geo-specific hosting infrastructure.