The question is whether you'd forward the result with your name on it. This battlecard was produced on the demo company that ships in the kit, then reviewed and edited by hand. The review found a timeline the rep could have repeated without a source. The note below shows the sentence, why it was flagged, and what replaced it. Read to the end: the Verification Audit lists what still needs checking, sorted by who has to act.
In the approved counter: "Ironclad is powerful, and you'll spend a quarter configuring it and an admin maintaining it."
In the closing talk track: "So before you commit a quarter to configuration: what would a two-week go-live be worth to this quarter's pipeline?"
Ironclad's site, implementation page and docs publish no rollout timeline. The card's own audit marked the duration as unconfirmed, and the card still gave the rep the quarter to say in two places. The counter was company-approved wording. Approval covers how a line is phrased. It does not source the fact inside it.
One more line went for the same reason: "against a CLM industry standard of 3 to 6 months" carried no source on the card.
"With two people on your legal team, who would own configuration in the first month, and how much time would they need?"
The change was made in angle 1 and in two places in the talk track: the close, and the line "you'll live in setup instead of contracts", which was the second half of the same counter. The objection responses and landmine questions were checked and carried no timeline. The approved counter now sits in the audit under "Yours to answer", waiting on whoever approved it.
Deal context, as the rep gave it: Series C fintech, ~800 employees, legal team of 2. Stage: evaluation. The GC added Ironclad to the shortlist after an analyst call. In the room: Head of Legal Ops (champion), GC, CFO joins the final review.
Ironclad is the strongest brand in CLM, built on deep, configurable workflows that reward a real legal-ops team. It is portal CLM; Harborline is embedded CLM, and this deal turns on which of those a two-person legal team can actually live with.
If this account had a legal-ops team of five, Ironclad would be a defensible pick. It has a team of two.
1. Setup burden vs. a team of two → 9-day implementation.
Their depth is bought with configuration, and configuration needs an owner. Our median implementation is 9 days across the last 14 deployments. Their own implementation page describes a guided onboarding programme with a named customer-success contact. [SOURCE: ironcladapp.com/implementation · read 2026-08-09] [VERIFY:unconfirmed] How long a rollout actually takes at 200-2,000 employees. Their site gives no timeline. [/VERIFY]→ so do not assert one. The brain's approved counter says "a quarter". It is held back until someone sources it (audit, list 1). Ask instead: "With two people on your legal team, who would own configuration in the first month, and how much time would they need?"
2. Portal adoption vs. where redlines actually happen → embedded CLM.
Ironclad is a destination; contract work happens in Slack, email, and the CRM. For a lean team, a portal nobody opens is the old shared-inbox problem with a login screen. Our number: 78% of redlines completed without opening Harborline (last 20 customers, average). Safe wording: "Most redlines never require logging in."
3. The GC's AI fear → redlines that cite THEIR playbook.
The GC is the skeptic here, and generic AI on legal docs should scare them. Harborline flags off-playbook clauses with their specific fallback; 63% first-pass acceptance by counsel across 8 customers. Safe wording: "It redlines like your best associate, not a search engine." [VERIFY:unconfirmed] Whether their AI reviews against generic clause standards or the customer's own fallbacks. Their product page does not say. [/VERIFY]→ do not claim it. Give the GC the landmine question: "when your AI flags a clause, is it comparing against our playbook or a general standard?"
"Ironclad is a good product with a strong brand. I won't pretend otherwise. But here's the question that matters for a legal team of two: who runs it? Ironclad's depth comes from configuration, and configuration needs an owner. If you have a legal-ops team, that's a fair trade. If you don't, the question is which of your two people becomes that owner.
Harborline takes the opposite bet. Median implementation across our last 14 deployments: 9 days. Give us your top five contract types and your playbook, and we do the rest. And your team won't move into another portal. Across our last 20 customers, 78% of redlines were completed without opening Harborline at all. The work stays in Slack and email, where your counterparties already are.
Finch, a Series C fintech, went from a 21-day contract cycle to 6 days within seven weeks, and pulled $1.2M of deals into Q4.
So here's what I'd ask any vendor, us included: with two people on your legal team, who would own configuration in the first month, and how much time would they need?"
This block closes every StoryOS asset, sorted by who has to act. Shortest list first, on purpose.
1. Yours to answer
2. Ours, and unmeasured
None. The three numbers used each carry a source and a date in the brain.
3. Sourced, spot-check (the system's work, not yours)
4. Wording needs approval
None.
Everything else traces to the company brain: differentiator table, proof inventory, the Finch mini-case and approved objection responses.
Note the shape. Two competitor facts were researched and cited. Two could not be confirmed, so they became questions to ask rather than claims to make. One of those was also sitting inside company-approved wording, so it went to list 1. The rep can use this card today, and the brain's counter waits on its owner.
This card was written on the demo brain and then reviewed by hand. With your own positioning and proof loaded, the card is about your competitors, and the evidence check is about your claims.
Get the kit