Fixed quote after a free call

Law firm client intake that arrives ready for a conflict check

We build an intake workflow with practice-area questionnaires that capture the facts a lawyer needs and every name a conflict search needs: the client, opposing parties, related companies, directors and spouses where relevant. It runs those names against your practice system, summarises potential matches and hands the result to a lawyer to clear or decline, then starts client identification where your rules require it. A typical build costs $1,000 to $2,500 per workflow and takes about four to five weeks.

The problem

Why matter opening stalls at the conflict check

A conflict search is only as good as the names put into it. When intake notes say "dispute with former employer" without the employer's legal name, its parent company or the individual managers involved, someone has to go back to the prospect before the search means anything. Matters wait, and prospects lose patience.

The duties are real on both sides of the Atlantic. In the US, state conduct rules based on ABA Model Rule 1.7 govern conflicts with current clients, and Rule 1.18 protects what a prospective client shares. In England and Wales, the SRA Code says a solicitor does not act where there is a conflict of interest. Intake has to collect enough to search properly, without collecting more confidential detail than the lawyer needs before the check.

What we build

What our law firm client intake software includes

Practice-area questionnaires

Separate intake for family, employment, personal injury, property, probate, criminal or business disputes, written with your lawyers.

Every name for the search

Parties, companies, directors, spouses and former names extracted and listed for searching.

Search run and summarised

Names checked against contacts and matters in your practice system, with potential matches listed for review.

Lawyer clears or declines

A clear task for the responsible lawyer with the summary attached; nothing proceeds until they decide.

Decline and non-engagement letters

Drafted from approved templates when the firm cannot act, for the lawyer to approve.

Client identification next

Once cleared, identity and, where required, source of funds requests start through your verification provider.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Intake completed

    The prospect or receptionist completes the practice-area questionnaire.

  2. 02 Automated

    Names extracted

    Every party, company and related name is listed for searching.

  3. 03 Automated

    Search summarised

    Names are searched in the practice system and potential matches summarised.

  4. 04 Staff review

    Intake team checks

    Staff confirm the names are complete and chase anything missing.

  5. 05 Attorney or solicitor decides

    Conflict decision

    A lawyer reviews the results and decides whether the firm can act.

How it behaves

How intake and conflict preparation behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the prospect sees

  • A clear questionnaire for their type of matter
  • A note that no legal advice has been given yet
  • A prompt decision on whether the firm can help

What staff see

  • Complete name lists ready for searching
  • Potential matches summarised with context
  • Tasks only where something is missing

What the automation does

  • Extracts and searches every relevant name
  • Drafts decline letters from templates
  • Never decides whether a conflict exists

Edge cases and fallbacks

Company name spelled differently
Variants and former names are searched and close matches listed.
Prospect shares sensitive detail early
Kept to the intake record with restricted access until the conflict is cleared.
Practice system search limits reached
Searches are queued and the intake lead is told.
AI extraction unavailable
The intake team lists names by hand from the form; nothing is skipped.

Architecture

Client intake and conflict preparation at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Intake form By practice area n8n workflow Intake rules Name extraction Parties, companies Practice system Conflict search Match summary Potential conflicts Lawyer Clear or decline
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 The prospect or receptionist completes the questionnaire for the right practice area.
  2. 2 Every party, company and related name is extracted and listed.
  3. 3 The names are searched against contacts and matters in the practice management system.
  4. 4 Potential matches are summarised and a lawyer clears or declines the matter.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Client intake & conflict check preparation project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Practice areas, current intake notes, conflict process, practice system search and verification provider.

  2. 02

    Design

    About 1 week

    Questionnaires with your lawyers, name rules, match summary format, decline wording and retention.

  3. 03

    Build

    1 to 2 weeks

    Forms, extraction, practice system search, lawyer tasks and letter drafts.

  4. 04

    Shadow run

    About 1 week

    New enquiries run both ways while the conflicts lead compares results.

  5. 05

    Launch

    1 to 2 days

    Switch on and train reception and the intake team.

  6. 06

    Support

    Ongoing

    New practice areas and questionnaire changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Clio Manage API v4, MyCase Open API, PracticePanther API, Smokeball API or Actionstep API Secure web forms Claude or OpenAI for name extraction, under the firm's vendor terms Your identity verification provider DocuSign for non-engagement or engagement letters

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Practice areas, questionnaires and conflict rules.

    $250 – $550

  • Build

    Forms, extraction, search, tasks and letter drafts.

    $450 – $1,150

  • Integrations

    Practice system, verification provider and e-signature.

    $150 – $450

  • Testing and shadow run

    Parallel intakes checked by the conflicts lead.

    $100 – $250

  • Launch and training

    Switch-on and reception training.

    $50 – $100

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Search depth depends on what your practice system exposes through its API; identity verification is billed by your provider.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Practice system: Your vendor's own plan; API access may need a particular tier.
  • AI model usage: Billed by the provider per use; usually a small monthly amount at firm volumes.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually) or €50 (Pro).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: conflicts with current clients

ABA Model Rule 1.7, which most state rules follow, governs concurrent conflicts of interest. The workflow surfaces potential matches; the lawyer applies the rule.

Source: www.americanbar.org

US: prospective client information

Under Model Rule 1.18, information from a prospective client is protected even if no matter follows, so intake asks only what the conflict check and first assessment need.

Source: www.americanbar.org

England and Wales: SRA Code

Paragraph 6.2 of the SRA Code of Conduct for Solicitors says you do not act where there is a conflict of interest, subject to narrow exceptions; 6.3 requires keeping clients' affairs confidential.

Source: www.sra.org.uk

UK: customer due diligence

Where a matter falls under the Money Laundering Regulations, regulation 28 requires identifying and verifying the client and beneficial owners. The workflow gathers evidence; the firm decides.

Source: www.legislation.gov.uk

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Client intake & conflict check preparation questions, answered.

Software that captures a prospective client's details and facts in a structured way, by practice area, and passes them into the firm's CRM and practice system. Ours also collects every name needed for a conflict search.

It prepares and runs the search in the practice system you already use, such as Clio, and summarises potential matches. The decision on whether a conflict exists, and whether it can be waived, stays with a lawyer.

Yes. The questionnaire works on a phone, explains that no lawyer-client relationship exists yet, and asks only what is needed before the conflict check.

The lawyer sees the match and the context, and decides. If the firm cannot act, a non-engagement letter is drafted for the lawyer to approve.

Once a matter is cleared, it can start identity and source of funds requests through your verification provider and file the results. Risk assessments stay with the firm.

Time from enquiry to conflict decision, share of intakes needing a call back for missing names, and matters opened per week.

Free 20-minute call

Want this for your law firm?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call