Draftwise paid ads audit: a precedent-led legal AI story with hero copy as the main lever
Draftwise sells precedent-driven contract review for in-house and Big Law legal teams. Its LinkedIn campaign concentrates 40 landing-page ads across five vertical destinations: in-house SaaS, in-house investment funds, Big Law, in-house ad tech, and in-house life sciences and pharma. Each destination already proves the precedent-and-redline story with examples, named firms, and stat blocks. The consistent gap is the hero: pages either narrow the promise to one document type or pivot to a clever line, when the highest-converting move is to repeat the ad's precedent hook word for word in the H1 and add a vertical-specific subhead.
Snapshot
- Total ads found
- 10+ ads
- Channels
- Matched destinations
- 5
- Unmatched ads
- 0
- Top destination
- /in-house-saas (10+ ads)
- Audited
- 2026-05-24

How this account runs paid ads
Draftwise runs a vertical-segmented LinkedIn program with one landing page per legal buying motion. The 40 landing-page ads we sampled cluster around five destinations matched to ICP: in-house SaaS legal, in-house investment funds counsel, Big Law partners and associates, in-house ad tech legal, and in-house life sciences and pharma legal. Each ad variant within a vertical sells a specific document type (NDA, MSA, SPA, side letter, LPA, IO, DPA, CRO clause) under the same precedent-driven framing.
Creative is consistent across the account: the dominant promise is acceleration of contract review using the firm's own precedent, with a 'Request Demo' or 'Learn more' CTA. That gives Draftwise a clean message-match story to optimize. Where pages echo the ad's precedent hook in the hero, scores cross 8; where pages default to clever metaphor or a document-narrow framing, scores hover in the mid-7s. The campaign is already in a strong position; the lift work is mostly hero copy and an above-the-fold demo CTA on the verticals that lack one.
Page report card
Page proves the precedent story but the hero narrows to NDAs and to legal teams generally instead of echoing the broader in-house SaaS framing in the ads.
Hero names NDAs only; the ads promise SPA, side letter, and LPA acceleration with preferred-position language that belongs in the H1 and subhead.
Page delivers the precedent story but the hero pivots to firm-wide consistency instead of echoing the ad's 'unlock your firm's precedent' phrase.
Hero drifts into clever metaphor while the ads sell IO precedent and DPA standards. Surfacing the 60%+ first-pass time saved above the fold would close the gap.
Hero already centers precedent. Adding a vertical-specific subhead naming playbooks, licensing benchmarks, and CRO clause recall would let each ad variant see itself.
This table only shows pages with a reviewed ad sample and a published score.
Common patterns
// Pattern 01
Hero narrows the offer, ads sell the full document set
Three of five vertical pages reuse a hero that names one document type (often NDA) while the ad set advertises acceleration across the full document mix for that vertical. Broadening the hero to repeat the ad's full document scope is the single highest-leverage copy edit across the account.
// Pattern 02
Precedent is the consistent campaign-wide hook
Every vertical leans on the same core differentiator: your own precedent. The pages that win mirror that hook in the H1. The pages that lose pivot to a metaphor or to consistency framing in the H1, then prove precedent further down. Standardizing 'powered by your precedent' or 'unlock your precedent' across hero headlines is a clean way to enforce continuity.
// Pattern 03
Demo CTA is missing above the fold on multiple verticals
Several captured heroes do not surface the 'Request Demo' CTA that the LinkedIn ads use. The page CTAs exist further down, but the click expectation set by the ad is immediate. Adding a hero-level Request Demo button on the SaaS, funds, and Big Law verticals shortens the click path.
// Pattern 04
Vertical-specific subhead is the lowest-cost lift
Where pages already echo the precedent hook, a subhead that names the vertical's distinct document types (SPA + LPA for funds, IO + DPA for ad tech, CRO + licensing for pharma) gives each ad variant a direct on-page confirmation without requiring full hero rewrites.
Should you copy this playbook?
If you sell a horizontal product with deep vertical use cases, Draftwise's destination structure is worth borrowing. One landing page per buying motion lets each ad variant route to a page that names its ICP, its documents, and its proof. The cost is editorial discipline: every vertical page needs its own hero, subhead, and proof set, or the model collapses back into a generic homepage. Draftwise has paid that cost on the page bodies; the heroes are the remaining cleanup.
What is worth doing differently is locking the hero language to a campaign template. A repeatable shape, 'precedent hook H1 + vertical-specific subhead naming the document set + Request Demo CTA + named-firm proof,' would let Draftwise standardize the first viewport across verticals while keeping the body content vertical-specific. That single change would likely move three of the five pages from the mid-7s to the high 8s.
Sources
- LinkedIn Ad Library: https://www.linkedin.com/ad-library/
Want the same teardown for your account?
Run a full PostClickSignal audit of your paid program and get scored pages, top fixes, and rollup patterns in one report.
Audit my full account