Should a Law Firm Record Business Development Calls With AI?

Client intake calls, referral relationship calls, and business development conversations with prospective clients who haven't yet engaged the firm are reasonable candidates for either tool. Calls where privilege attaches, discussing case strategy with an existing client, conferring with co-counsel about a matter, deposition or witness prep, generally should not go through a general-purpose consumer or SMB recording tool without your firm's own review of its confidentiality, security and data handling terms first.

A missed follow-up from a badly organized sales call costs a deal. A privilege waiver from an improperly handled recording can affect an entire matter and create a duty to disclose to the client. That asymmetry is why a law firm's answer to Fathom vs Fireflies has to start with a policy about which calls are in scope, agreed with your firm's general counsel or ethics counsel, before it becomes a tooling question at all.

Most other professional services firms can treat a recording mistake as an embarrassment to clean up. A law firm has to treat it as a question for its own risk management process, which is a meaningfully higher bar for getting the scope decision right up front.

A solo practitioner or small firm partner running their own referral relationships and intake calls benefits from Fathom's speed: a same-day recap after a referral lunch or an intake call that turns straight into a conflict check and an engagement letter draft, without a separate note-taking step.

A firm with multiple partners generating business development independently benefits from a searchable library across those relationship calls: which referral sources send which kind of work, what a prospective client said about why they're switching firms, patterns a managing partner can only see by searching across many calls, not one at a time.

That pattern-level view is hard to build any other way. Asking each partner to self-report referral outcomes in a spreadsheet tends to produce a thin, inconsistent record next to what a searchable transcript library captures automatically.

• Confirm the call is intake, referral or business development, not privileged matter work
• Disclose recording clearly and get verbal consent at the start of the call
• Check your state's consent requirements for recorded calls, since some require all-party consent
• Confirm the vendor's data handling terms with your firm's own IT or compliance review, not just the vendor's marketing page
• Set a clear policy for who inside the firm can access a given transcript

Walk a new partner through this checklist directly rather than assuming they'll read a policy document on their own. A five-minute conversation when someone joins the firm does more to keep the scope boundary intact than a page buried in the associate handbook.

Firms sometimes adopt a recording tool informally, one partner starts using it, colleagues notice and follow, and a written policy about what's in scope never actually gets drafted. By the time someone asks whether a specific call should have been recorded, the tool is already embedded in daily use across the firm. Write the scope policy first, even briefly, and have it reviewed by whoever handles ethics questions at your firm, before rolling either tool out beyond one partner's own use.

Only about 22% of B2B sellers hit their target in a recent industry dataset¹, and attorneys running business development on top of billable work face a version of the same challenge: origination targets compete directly with client work for the same hours. A searchable BD call history at least removes one source of wasted effort, chasing a referral relationship whose actual history and preferences the firm has already captured and then forgotten.