Kirkland & Ellis runs $8.8B revenue from Chicago, and that is the floor — not the ceiling — of Illinois Big Law gravity.

PAA

People also ask

• Why is Kirkland & Ellis the gravity center of Chicago professional services?

  Kirkland & Ellis posted $8.8B in revenue for 2024 — the #1 US law firm by revenue per the American Lawyer Am Law 100 — running ~3,500 attorneys out of the Aon Center at 333 N La Salle, with profits-per-partner among the highest globally (~$8M PPP). Sidley Austin ($2.7B revenue, ~2,000 attorneys), Mayer Brown (~$1.7B, ~1,700 attorneys), McDermott Will & Emery (~$1.7B, ~1,400 attorneys), Winston & Strawn (~$1B), Jenner & Block, and Katten Muchin Rosenman all keep global HQ inside the Loop. The Big-4 Chicago offices employ ~25,000 professionals combined.

• How does ABA Model Rule 1.6 affect AI vendor selection at Chicago Big Law?

  ABA Model Rule 1.6 is the binding standard — a lawyer shall not reveal information relating to representation of a client unless the client gives informed consent. Use of generative AI on matter-related data without protecting confidentiality is a discipline trigger. The practical posture: client matter data is not used to train any model the vendor or sub-processors operate, data is encrypted at rest and in transit, access is audit-logged, sub-processors are listed and approved, and the firm retains the right to delete its data on demand. Areza routes documentation through the firm's General Counsel + CISO + outside cyber-insurance carrier before any production rollout.

• Can Areza work alongside Harvey AI, Lexis+ AI, or Casetext CoCounsel?

  Yes — we sit above, not parallel. Harvey AI is the de-facto reference deployment (Allen & Overy / A&O Shearman ~3,500 lawyers across 43 offices, PwC ~4,000 legal professionals). Lexis+ AI integrates against Microsoft Word, Outlook, iManage / NetDocuments. Casetext CoCounsel (Thomson Reuters acquisition, $650M in 2023) handles document review, deposition prep, contract analysis. Where the firm has Harvey or Lexis+ AI deployed, Areza covers the BD + AI Search + Voice Agent + Knowledge Bot layer these tools do not address — citing the firm's published thought leadership in ChatGPT and Perplexity answers, routing inbound BD intake.

• Does the ARDC enforce communications rules against AI-generated content?

  Yes. Illinois Rules of Professional Conduct (modelled on ABA Model Rules) are enforced by the ARDC — Rule 7.1 (no false or misleading communications), Rule 7.2 (advertising — written, recorded, or electronic), Rule 7.3 (solicitation), Rule 7.5 (firm names + letterheads). Every AI-generated communication that touches an Illinois lawyer's marketing or client-intake surface must satisfy Rule 7.1 — no false claims, no implication of guaranteed outcomes. Voice Agent intake scripts are configured with Rule 7.3 solicitation guardrails — the agent does not initiate matter-specific contact with a prospective client.

• Is selling into a Big-4 Chicago office different from a Big Law firm?

  Yes — and any vendor pitching otherwise is misunderstanding Big-4 procurement. The Chicago partner can champion, advocate, co-design the pilot, and get the engagement onto the firm-global vendor management queue — but cannot sign the contract. Procurement runs through firm-global teams in NYC, London, or the firm's chosen hub, and global infosec + privacy + brand teams must sign off before regional commit. Big-4 Chicago engagement design: 90-day regional pilot with firm-global documentation pack ready at day 1, firm-global procurement gate at day 60, regional production rollout at day 120 contingent on firm-global commit.

Frequently asked

• How do you handle ABA Model Rule 1.6 confidentiality for AI surfaces at an Illinois law firm?

  Rule 1.6 is the binding constraint and we treat it as the starting point, not an afterthought. The posture: client matter data is not used to train any model we or our sub-processors operate, data is encrypted at rest and in transit with the firm's keys where the firm prefers customer-managed keys, access is audit-logged, sub-processors are listed and approved by the firm's General Counsel + CISO + cyber-insurance carrier before production rollout, and the firm retains the right to delete its data on demand. We route the documentation through the firm's risk + compliance committee at engagement start and never put matter-related data through a public LLM API without the firm's explicit Rule 1.6 sign-off. Where Harvey or Lexis+ AI or CoCounsel is already deployed inside the firm, we integrate above those tools rather than duplicate them.

• Do you support ARDC Rule 7.1, 7.2, 7.3, and 7.5 communications review?

  Yes. Every AI-generated communication that touches an Illinois lawyer's marketing or client-intake surface goes through ARDC Rule 7.1 (no false or misleading communications) + Rule 7.2 (advertising — written, recorded, electronic) + Rule 7.3 (solicitation — direct contact with prospective clients) + Rule 7.5 (firm names + letterheads) review before publication. The workflow is built into the publish pipeline with a registered-attorney sign-off gate — typically the firm's general counsel or a senior partner with marketing-committee delegation. Voice Agent intake scripts are configured with Rule 7.3 solicitation guardrails — the agent does not initiate matter-specific contact with a prospective client. Where the firm represents broker-dealer or RIA clients, FINRA Rule 2210 and SEC Reg BI overlays apply and we route through the broker-dealer principal-review workflow in addition.

• How do you handle BIPA for Voice Agent and call-recording surfaces at an Illinois firm?

  Every Illinois professional-services Voice Agent deployment starts with the BIPA consent architecture configured before any voice surface goes live. The flow: pre-call disclosure of recording (`this call may be recorded and analysed for service-quality and compliance with the Illinois Biometric Information Privacy Act; you may opt out at any time`), recorded consent capture in the audit log, no voiceprint retention beyond the consented session, audit-log retention compliant with potential discovery in a BIPA class action. Statutory damages are $1,000 per negligent violation and $5,000 per intentional violation per individual, with private right of action. Illinois law firms have settled BIPA class actions over employee-fingerprint clock-in systems and voice-biometric phone authentication — we bake the consent flow into the deployment so the firm does not become the next defendant.

• Can you sell into a Chicago Big-4 office without going through firm-global procurement?

  No, and any vendor that tells you otherwise is misunderstanding Big-4 procurement. The Chicago partner can champion, can advocate, can co-design the pilot, and can get the engagement onto the firm-global vendor management queue — but cannot sign the contract. Procurement and vendor management run through firm-global teams in NYC, London, or the firm's chosen hub, and global infosec + privacy + brand teams must sign off before regional commit. Our Big-4 Chicago engagement design accepts this reality: 90-day regional pilot with firm-global documentation pack ready at day 1, firm-global procurement gate at day 60, regional production rollout at day 120 contingent on firm-global commit. Compressing this timeline is not possible. Trying to shortcut it loses the engagement.

• What about Illinois state tax (4.95%) and Chicago city overlay for service-delivery footprint?

  Illinois levies a flat 4.95% state income tax on individuals and a 9.5% combined corporate income tax (including the personal property replacement tax) on C corporations. Chicago adds a personal property lease transaction tax of 9.0% on cloud-software lease transactions where the lessor or lessee is in Chicago — this catches some SaaS arrangements where the city characterises the subscription as a lease. For our engagements, the Chicago lease tax exposure typically falls on the firm where the firm is the customer in Chicago — we surface the exposure at contract-pricing time so the firm's tax + procurement teams can plan accordingly. For multi-state firms with non-IL offices, apportionment + nexus questions sit with the firm's tax team — we provide the data feed not the tax opinion.

• How do you handle CST timezone scheduling across Big Law office hours and global Big-4 hours?

  Chicago is Central Standard Time (UTC-6) and Central Daylight Time (UTC-5). Big Law Chicago partner-level work routinely starts at 7:00 AM CT and runs past 9:00 PM CT during deal heat. Big-4 Chicago partners coordinate with NYC (UTC-5/-4), London (UTC+0/+1), Frankfurt (UTC+1/+2), and Mumbai (UTC+5:30) — meaning the Chicago partner is often the bridge between US daytime and EMEA daytime. Voice Agent coverage defaults to 7:00 AM – 9:00 PM CT M–F with extended deal-heat hours configurable; calendar scheduling defaults to CT primary with automated conversion to participants' local zones (Calendly + Outlook + Salesforce calendar integration). For cross-border M&A or restructuring matters where European counterparties run on CET / WET, we configure the Voice Agent and scheduling to surface the European business-day window inside the Chicago workflow.

• What pricing should a Chicago Big Law boutique, Big-4 Chicago practice, or mid-market firm expect?

  Foundation starts at USD $5,200 for a 2–4 week conversion-first build with ARDC + ABA Model Rule 1.6 + BIPA-aligned practice-area pages, schema-marked attorney bios + reported matters, FAQPage markup, llms.txt configured, ADA WCAG 2.1 AA compliance. AI Search retainer starts at USD $430/month with named-target citation tracking against Chambers + Partners, Vault, Law360, American Lawyer, Crain's Chicago Business, and the firm's chosen trade-press surface. Voice Agent for inbound BD qualification with BIPA consent + ARDC Rule 7.3 solicitation guardrails + conflicts-screening trigger phrases + iManage / NetDocuments matter lookup adds USD $1,400–$2,300/month. A typical Chicago mid-market firm engagement combines Foundation + AI Search + Voice Agent at USD $6,800–$9,500 setup plus USD $1,800–$3,000/month for the first six months. Big Law and Big-4 Chicago engagements typically scale beyond this range given the integration map (iManage + NetDocuments + Salesforce + Aderant + Elite + Snowflake + firm-global vendor management for Big-4) — we quote those engagements per-scope rather than from the price list.

• Are you SOC 2 Type II ready for Chicago Big Law procurement gates?

  SOC 2 Type II report is attached to every Illinois professional-services proposal. The report covers our infrastructure controls — access management, change management, encryption at rest and in transit, audit-log retention, sub-processor management, vulnerability management, and incident response. For Big Law engagements, we additionally map ABA Model Rule 1.6 + Illinois Rules of Professional Conduct + ARDC posture at engagement start and route any AI-generated content through audit-log retention compliant with the firm's matter-retention policy (typically 7+ years for client matter content). For Big-4 Chicago engagements, we map the firm-global infosec + privacy posture at engagement start and align our sub-processor list to the firm-global approved-vendor list before production rollout. Our home jurisdiction is the EU, which carries GDPR + NIS2 baseline controls that complement US legal-sector compliance — we surface the deltas explicitly at engagement start.