Systems should outlast the people who build them.
Muhammad Umar Irfan is a legal systems architect and systematic thinker focused on one problem: how can a law firm keep moving without depending on someone remembering what has to happen next?
Umar takes processes that live across inboxes, PDFs, spreadsheets, forms, CRMs, websites, staff knowledge and attorney memory, then reconstructs them as connected operating systems.
Not automation for the sake of automation. Infrastructure that knows what happens next, when human judgment is required, where information belongs, and when the system should stop.
He does not start with tools. He starts with the system.
A workflow may look like ten separate tasks: intake, conflict checking, retainer signing, payment, matter creation, document generation, client communication, marketing, follow-up and reporting.
Umar looks for the relationships between those tasks. The work begins by understanding the rules, dependencies, decisions, data and failure points underneath the visible process.
Systems thinking across operations, documents, marketing and infrastructure.
Umar's work has crossed the departments that usually operate in isolation. That broader view makes it easier to see where one team's process becomes another team's bottleneck.
One client journey, not five disconnected apps.
Umar has architected workflows connecting intake, conflict decisions, retainers, payments, document collection, matter creation, attorney approvals and client updates across tools such as Gavel, Clio Manage, Make.com, Stripe, Gmail and Google Calendar.
Information should have one source of truth.
Estate-planning architecture was rebuilt around reusable people records, role logic, successor logic and document-ready variables so one identity or legal decision could flow consistently through a coordinated document package.
Build the production system before asking AI to write.
For law-firm content operations, Umar has connected research, freshness rules, relevance scoring, bilingual drafting, media generation, approval gates, persistent records and multi-channel publishing into one governed content system.
Every change must work without damaging the rest of the system.
The systems-first lens extends into websites, SEO, performance, structured data, AI discoverability, accessibility and regression prevention so growth infrastructure remains maintainable as the site evolves.
Most businesses see tasks.
Umar sees dependencies.
A process becomes reliable when every important event has a defined input, rule, decision owner, next action, failure path and record of what happened.
That is how systems learn when to continue, when to wait, when to loop and when to stop.
Build systems that survive absence.
A good law firm should not slow down because someone is travelling. It should not depend on an employee remembering to send a retainer. It should not require an attorney to search an inbox to determine whether a client paid. And the same person's name should not need to be typed into six different documents.
The system should carry the repeatable work. People should carry the judgment.
Experience shaped by real law-firm workflows.
The perspective comes from working directly with attorneys and legal teams on the systems being redesigned, not from looking at the business from outside.
Operational flow, not just tool connections.
Across law-firm projects, Umar has worked through the business logic behind intake, legal decisions, documents, payments, CRM data, content, approvals, publishing, websites and quality control.
“What I appreciated most was his ability to think through the full operational flow, not just connect tools together.”
Systems take you where tools can't.
Tools can automate an action. Systems coordinate the firm. Muhammad Umar Irfan founded Firm in Motion around that distinction: understand the business first, identify how its parts depend on one another, then engineer the infrastructure that keeps those parts moving together.
One process. One architecture. Less dependence on memory.