Case study · Legal · Content Creation
How a corporate law firm took time to first draft from days to hours
A corporate law firm of 20-80 staff moved content creation off a manual queue and onto agents that run it continuously. The build, the numbers, and what stayed human.
Time to First Draft
A legal contact went quiet — handle the content creation.
3 AI agents · 5 tools connected · live in 3 hours · no code
- Company
- Corporate law firm
- Team size
- 20-80 staff
- Industry
- Legal
- Time to live
- 3 hours
- Agents deployed
- 3 AI agents
- Tools connected
- 5 integrations
The context
Why Content Creation is hard in legal.
Content Creation is not hard in the abstract. It is hard in legal, where the work arrives as client intake forms, opposing counsel email, court notices, and document requests — every channel a different shape, none of them waiting their turn. The team runs against the docket and the billable hour, so the real cost of a slow content creation step is never the step. It is a deadline that was in an email nobody opened.
Constraints the build had to hold
Matter-scoped access
Agents work inside a matter, so a workflow set up for one client cannot read another’s file.
Privilege is preserved
Privileged material never leaves firm systems. Where a step needs the substance, it works from a firm-written summary.
Nothing is filed automatically
Agents prepare, calendar, and chase. Filing and advice stay with the attorney.
The change
Same job. Two chains.
Every handoff in the left-hand chain is somewhere Content Creation used to wait. The right-hand chain has the same steps and none of the waiting.
By hand
- Topic picked from the planthen the blank page
- Research, hours of itfor four hundred words
- Rewritten to sound like the branda second full pass
- One piece ships
the other three slip
With agents
- Work arrives on any channelpicked up in seconds
- Brief agenthanded straight on
- Draft agenthanded straight on
- Repurpose agent
logged, and reviewable
When the work can happen
Before and after
What Content Creation cost them, and what replaced it.
The challenge
This corporate law firm had a content plan and no way to execute it. The legal strategy was sound: publish consistently, answer the questions buyers actually ask, build a library that compounds. The reality was one piece a month, published late, written by whoever could carve out a day.
The full background
The bottleneck was not ideas — it was the distance between an idea and a finished draft. Research took hours. Structuring took more. Getting the tone right took a rewrite. With 20-80 staff and no dedicated writer, that work competed with everything else and lost most weeks. Meanwhile competitors publishing weekly were accumulating exactly the compounding advantage the plan had described, and the gap widened every month the plan went unexecuted.
What they built
The team used DeskFerry to remove the blank page, not the writer. A brief agent researches the legal angle, gathers sources, and produces an outline with the argument already settled. A draft agent writes to that outline in the brand voice, keeping every claim tied to a source the brief collected.
How it was wired
What arrives is an editable draft, and a person edits it — nothing publishes without a human read. The time that came back is the structural time: the research, the outlining, the first-pass rewrite to make it sound like the brand. A repurpose agent then cuts each published piece into the formats other channels need and files everything back to Google Drive, which is how a two-day piece stopped producing two days of value and started producing five.
The impact
What changed, measured the same way on both sides.
Before and after across the metrics that matter for legal Content Creation.
Time to First Draft
Dramatically faster
Pieces Published
Significant increase
Voice Consistency
Notable improvement
Formats per Piece
More value per piece
Cost per Piece
Major savings
How these were measured
- Baseline
- The "before" column is the team’s own measurement of their manual content creation process, taken over the four weeks before anything was connected.
- Comparison
- The "after" column is the same measurement repeated on the same process once the agents were live, so both sides count the same things in the same way.
- Why no percentages
- These are composite scenarios built from patterns across many deployments, not one audited customer’s books. Directional language is the honest way to report that — your own numbers will depend on your volume, your process, and your starting point.
A day, either side
The same day, before and after.
What Content Creation actually looked like for this legal team — the version they described in the first call, and the version they run now.
Before DeskFerry
9:00
Open a blank document. Close it. Open the calendar instead.
11:00
Research for two hours to write four hundred words.
14:00
Rewrite it to sound like the brand rather than like the research.
16:30
Publish one piece. The other three slip another week.
Month end
The legal content plan is a third done.
After DeskFerry
9:00
Briefed drafts are waiting, each with sources and an outline already agreed.
10:00
Edit for judgement and voice — the structural work is done.
14:00
Repurposed variants for other channels are generated from the approved piece.
16:30
Three pieces ship, not one.
Month end
The plan is complete and the backlog is ideas, not drafts.
The build
The 3 agents that run it.
One job each, with an explicit handoff between them. Splitting Content Creation this way is what makes a failure legible — you can see which step it went wrong at instead of debugging one agent that does everything.
- 01
Brief agent
Trigger
A topic enters the calendar
Researches the legal angle, gathers sources, and produces an outline with the argument already settled.
Agent 1 of 3 in the Legal workflow.
- Sends the brief for a quick human yes or no.
- 02
Draft agent
Trigger
A brief is approved
Writes to the outline in the brand voice, keeping claims tied to the sources the brief collected.
Agent 2 of 3 in the Legal workflow.
- Hands an editable draft to the writer, not a finished piece.
- 03
Repurpose agent
Trigger
A piece is published
Cuts it into the formats other channels need and files everything back to Google Drive.
Agent 3 of 3 in the Legal workflow.
How they did it
From nothing to production in 3 hours.
No code, no IT ticket, no vendor implementation team. These are the steps in the order this team took them.
Step 01
Connected the legal stack
Clio, LawPay, and DocuSign via pre-built connectors. No API keys, no custom code.
Step 02
Wrote the business rules
Scoring, routing, escalation thresholds, and exception handling for legal content creation — in the visual builder.
Step 03
Tested on real history
Replayed a week of past content creation to check accuracy and surface edge cases, then adjusted the weights.
Step 04
Launched and watched
Live with close oversight for 48 hours, then down to a weekly review.
The stack
Nothing was replaced. Everything was connected.
The legal team kept the tools they already ran — DeskFerry sits between them.
Clio
Matter, deadline, and document context, scoped per matter
LawPay
Billing and trust accounting events
DocuSign
Signature events that start the workflow the moment a deal is real
Google Drive
Document intake and the filing destination once processing is done
Slack
Where the team is told, and where approvals happen in one tap
Content Creation handled end to end · hours, every time
What stayed human
The parts they deliberately did not automate.
Automating Content Creation end to end was never the goal. Removing the volume so the judgement calls got proper attention was.
Every published word
Nothing publishes without a human edit. The drafting agent removes the blank page and the structural work; the judgement, the opinion, and the voice are added by a writer.
Claims and figures
Anything asserting a fact is checked against the source the brief collected. Unsourced claims are cut rather than softened.
The client intake efficiency question
Asked first by every legal team. Agents run on the access the staff account already had, every action is logged, and any step can be stopped without unwinding what ran.
Takeaways
What transfers to your team.
The parts of this that are not specific to one company's tooling or volume.
- 01
The routine content creation volume stopped needing a person. The judgement calls still get one.
- 02
Live in under a day — no IT queue, no development cycle.
- 03
Errors fell because validation runs before the write, not after.
- 04
It paid for itself on saved hours, not on a headcount cut.
In their words
“The difference is night and day. Our legal clients used to wait days for content creation to be completed. Now it happens in minutes, and the quality is consistently higher than what we achieved manually. Customer satisfaction scores went through the roof.”
Composite — written from what teams running this workflow report, not a single named customer.
FAQ
Questions people ask about this build.
Automating Content Creation in legal — what it takes, and where it stops.
How long does it take to set up content creation automation for a legal business?
This team was live in 3 hours. Pre-built legal templates cover the wiring, so most of that time goes on your business rules rather than on connecting things. No code.
How many AI agents does content creation automation actually need?
3 here: brief agent, draft agent, repurpose agent. The split matters more than the count — one job and one handoff each means a failure tells you which step broke. One agent doing everything does not.
What results can a legal business expect?
The figures here are directional, not audited — composite scenarios, not one customer's books. What transfers is the shape: routine volume stops needing a person, exceptions surface instead of sinking, and nothing waits for office hours. Your numbers depend on your volume and starting point.
How does DeskFerry handle legal data and access?
Agents run on the same access the staff account already had — throughput widens, permissions do not. Every action is logged with what it read and changed, and any step can be stopped without unwinding what ran. DeskFerry holds no formal legal certification, so scope it as you would any other system in your control environment.
What still needs a person?
More than most automation pages admit. Anything outside the rules stops and goes to a named owner with context attached, rather than being guessed at. The rules themselves are changed by people — agents never widen their own tolerances. The carve-outs this team kept are named above.
What tools does this connect to?
1,500+ integrations. This build used Clio, LawPay, DocuSign, Google Drive and Slack; most legal stacks are a variation on that. CRM, email, chat, databases, and industry-specific software all connect without code.
Run this in your own stack.
Describe how Content Creation should work at your legal business, in a sentence. DeskFerry builds the agents, wires your tools, and takes the routine volume from there. Start free — no credit card.
Or start from a template — Content Creation agent for Legal.
Keep exploring
Related case studies.
The same job in another industry, or another job in this one.
More Legal case studies
Content Creation in other industries
Composite scenario — built from patterns across many legal Content Creation deployments rather than one customer's books. Figures are directional; your own depend on your volume, process, and starting point.