ConflictCheck · conflict screening for United States law practices Support 9 a.m. to 6 p.m. Central, Monday to Friday

ConflictCheck / Author

Jimenez Julien

Founder of MLJ, SASU, publication director of ConflictCheck, and the person who answers your demo request.

Portrait of Jimenez Julien

Why a conflicts tool, and why for solo attorneys

ConflictCheck started with a phone call I could not stop thinking about. A friend who runs a two attorney practice in the Midwest described taking a family law matter, working it for five weeks, and then learning at a status conference that she had met the opposing party once, in her own conference room, three years earlier. Nothing improper happened. She withdrew, refunded the retainer, wrote the awkward letter, and absorbed the loss. What struck me was her explanation of how it happened: the consult had never become a matter, so it existed nowhere except in a calendar entry with a first name on it.

I build small, narrow software for people who run businesses without a back office. Most of my work sits in that gap between a spreadsheet that has outgrown itself and enterprise software written for a department that a two person practice does not have. Conflict screening is the sharpest example of that gap I have found. Large firms employ conflicts analysts and buy systems priced accordingly. Solo attorneys carry the same ethical duties under Rules 1.7, 1.9 and 1.18, face the same disqualification motions and the same grievance exposure, and do the check themselves between a hearing and a school pickup.

So I spent 2024 and 2025 talking to attorneys instead of writing code. I sat with a family law solo in Ohio while she took intake calls. I read the screening logs a construction defect firm in Oklahoma had kept on paper since 2011. I asked a malpractice underwriter what documentation actually changes the conversation at renewal, and the answer was blunt: a dated record showing what was searched, what came back and who decided. Not a policy document. Not an intention. A record with a date on it.

That is what the product is organized around. The structured intake form exists because the questions that catch conflicts are the ones you stop asking when you are tired. The automatic search exists because the human failure mode is not laziness, it is confident recall. And the dated screening record exists because a check nobody can prove is worth very little when a motion to disqualify arrives eighteen months later. Everything else in ConflictCheck is in service of those three pieces, and I say no to features that pull attention away from them.

I am not an attorney and ConflictCheck does not give legal advice. Whether a hit is disqualifying, waivable or irrelevant is a professional judgment that belongs to the lawyer of record, and the product is written to hand you the file rather than a verdict. What I am accountable for is narrower and entirely mine: that the search finds what is in your data, that the record is accurate and cannot be quietly altered, that your client names never leave your account, and that a person answers when you write.

Experience and expertise

I founded MLJ, SASU in Paris in October 2024 to publish a focused family of operational tools for small businesses in the United States and Europe. Before that I spent eleven years building internal systems for service companies, mostly the unglamorous kind: scheduling, intake, compliance records, and the reporting that keeps a regulator or an insurer satisfied. That work taught me that the hardest part of a compliance product is never the algorithm. It is asking the right question at the moment somebody is busy, and making the answer worth keeping.

  • Interviews and working sessions with 46 US practices between March 2024 and December 2025, from single attorney offices to five lawyer firms.
  • Time studies with 14 subscribing practices measuring intake duration before and after structured screening.
  • Review of the product's conflict language against the ABA Model Rules by two practicing attorneys, repeated at each major release.
  • Direct responsibility for support: I read every request that arrives through the form on the home page.

How this product is built and maintained

ConflictCheck ships on a fixed rhythm rather than on impulse. Every release goes through a regression suite built from real, anonymized matter lists donated by subscribers, so a change to name matching cannot quietly reduce recall. When the matching logic changes at all, subscribers are told in plain language what changed and what it means for searches they have already run, because a screening record is only useful if you know how it was produced.

Editorial standards on this site follow the same rule. Every number published here comes from product usage or from a study we ran, and each one is dated so you can judge whether it is still current. Testimonials are published with the attorney's name, firm and city, with written permission, and quotes are edited only for length. Pricing on the pricing section is the price you pay, with no setup fee held back for the sales call. If something on this site is wrong, write to me and it gets corrected with a note of the change.

Documentation, the FAQ and the guidance inside the product are reviewed twice a year, and again whenever a state bar publishes an opinion that touches screening or lateral hires. That review is scheduled work, not a reaction to complaints. The most recent full pass was completed on March 2, 2026.

Contact the author

Write to jimenezjulien42@gmail.com and you reach me, not a queue. Demo requests sent through the form on the home page are answered within one business day, usually the same afternoon Central time. If you want to argue with a design decision, that email works for that too, and those conversations have changed the product more than once.