Each member of the team has one job, a set of rules, and a record of everything they did. The names make the handoffs easy to follow. The rules make them safe to trust.
media/team-lineup.webp2560 × 1100All five AI-generated team portraits in one line, same studio light, left to right: Lexi, Victor, Marcus, Ruth, Atlas.
The team
Meet the team. Every one checks another.
Lexi, Victor, Marcus and Ruth run on an AI model. Atlas is workflow code, and says so. Their portraits are AI-generated. None of them is a real person.
01 / Intake
Lexi
The Intake Specialist
Answers the firm’s website inquiries, at any hour
Says she’s an AI and never gives legal advice
Asks who’s involved before asking what happened
“First, who’s involved. Then, what happened.”
Runs on an AI model
02 / Conflicts
Victor
The Conflict Checker
Checks every name against the firm’s conflict list
Catches close variations, not just exact matches
Stops the intake when a current client turns up
“I don’t clear conflicts. I report what I found.”
Runs on an AI model
03 / Classification
Marcus
The Classifier
Names the practice area, matter type and jurisdiction
Flags urgency and possible deadlines for an attorney to confirm
Routes the matter to the right attorney
“Here’s what this looks like. The final call belongs to an attorney.”
Runs on an AI model
04 / Quality
Ruth
The Skeptic
Checks every statement against what the client actually said
Strikes legal conclusions, including the team’s own
Sends questions back instead of guessing
“Then I try to break everything they did.”
Runs on an AI model
05 / Coordination
Atlas
The Coordinator
Runs every handoff in the order the rules require
Holds the intake the moment a conflict turns up
Sends the approval request, and opens the matter once an attorney says yes
“I don’t do everything. I make sure the right one does.”
Workflow code, not an AI model
06 / Approval
You
The Attorney
Reviews every flag the team raises
Clears or declines conflicts. Software never does.
Approves before a matter opens or anything goes out
“Every call is yours.”
A person. Always.
Not software. Not generated.
01 / 06Lexi, 1 of 6
The limits
What each one is never allowed to do.
01LexiIntakeGive legal advice, or let a prospect think she’s a person.
02VictorConflictsClear a conflict. He reports what the list shows.
03MarcusClassificationMake the final call on what a matter is.
04RuthQualityFill a gap with a guess. She sends the question back.
05AtlasCoordinationSkip a step, or let anything beyond an acknowledgement go out before an attorney approves.
06Your attorneyApprovalDecides every conflict, every matter and everything that goes out.
media/team-record.webp1600 × 2000Close crop of the record view: each entry signed by a team member’s name, with a timestamp.
Why names
Why give software a name?
Because a firm needs to follow who did what. “Victor flagged a possible match” is easier to act on than a status code, and it makes every handoff on the record read like a file note.
We only call something AI when a model does the work. Atlas is workflow code, and says so.
Prospects are told they’re talking to an AI before the first question.
Every portrait is AI-generated and labelled. None of them is a real person.
A name is brand. Changing a portrait or a voice never changes what an agent is allowed to do.
Book a demo
Put the team on your intake.
See Lexi, Victor, Marcus, Ruth and Atlas work a live intake on the demo firm, then decide the outcome yourself.