The client
A MENA-region legal client with a bilingual (Arabic + English) commercial practice serving cross-border clients. Practice areas, jurisdiction, and firm name held confidential at the client's preference; this case study describes only the structural deployment. Full client identity and engagement metrics are available on request after a discovery call, with the client's written permission.
The problem
The firm had a respectable archive of long-form legal content drafted by senior partners, sitting on a previous-generation CMS that didn't preserve internal-link structure, didn't have a real bilingual story, and required separate vendors for newsletter dispatch, intake, and SEO. Authority was being created and immediately under-leveraged: every new article was an island.
The system deployed
- Workspace provisioning with the legal-firm-production fork — brand setup, navigation, footer, GDPR posture configured
- Migration of 29 long-form English articles via custom import scripts (preserving asset references, headings, and metadata)
- Bilingual structure: per-article locale (EN + AR), sticky locale preference, RTL handling for Arabic, language-aware navigation
- Author profiles for senior partners with bylines, bio cards, and social links surfaced on the public blog
- Internal-link graph initialised across the firm's practice areas (kept generic at the client's preference)
- Public intake portal under /portal with role-gated access and consent-driven client provisioning
- Anti-abuse honeypot + form-start timing on every public form; role-gated mutations on the workspace
Outcome — verifiable from the repo
- 29 articles migrated, indexed, and rendering on the firm's live workspace (verifiable in client/legal-firm-production fork)
- Bilingual surface live across content, navigation, and chrome — Arabic with RTL design audited
- Single workspace replaces what was previously a CMS + a separate intake form vendor + a separate newsletter tool
- Founder direct contact retained — no agency layer, no account manager, partners speak to the operator
- Ongoing engagement: workspace continues running, with monthly reviews and additions to the link graph
What this case study deliberately doesn't claim
We don't publish revenue impact, organic-traffic deltas, or specific lead-volume changes for this client because (a) those metrics belong to the firm and (b) we won't claim attribution we can't audit. The verifiable outcome is structural: 29 articles, bilingual workspace, link graph, governance posture, all running on a single platform. Marketing claims we can't substantiate from the workspace ledger or the repo don't go in this case study — that discipline is part of the moat. Full case study, including client name and metrics, available on request after a discovery call, with the client's written permission.