How we work. The tools read. A lawyer decides.
Every lawyer here works with advanced AI. It reads, cross-checks, and drafts, so more of the record is read and fewer things are missed. The judgment, and the responsibility, stay with a Texas-licensed attorney.
One method, on a contract and on a dispute.
The same four stages apply to both. What changes is what the tools read and what the lawyer has to decide.
- 01What you sendOn a contract
The agreement, by email, a shared channel, or a shared folder, with the business context: the deal, the counterparty, anything already promised.
On a disputeA short account of what happened, then the agreement, the correspondence, invoices, and messages, through a secure channel we set up after the first call.
- 02What the tools doOn a contract
Check every clause against your positions and your prior deals, and prepare a draft redline, an issues table, and a response to the other side.
On a disputeOrganize and review the whole record, not a sample, and assemble a dated chronology, a key-document set, and the gaps in the other side's account.
- 03Where the lawyer decidesOn a contract
Which terms matter for this deal, what to ask for, what to give, and what goes to your decision-maker. The attorney corrects the draft and signs off.
On a disputeWhat the documents prove, where the exposure is, and which approach serves the business: demand, response, negotiation, mediation, or court.
- 04What you get backOn a contract
A redlined draft, an issues table with recommended positions, a drafted counterparty response, and decision flags.
On a disputeAn early case assessment with the chronology and key documents attached, then a demand or response grounded in the record.
Timing depends on the matter, the documents, and how quickly decisions come back. We agree on expectations in the written scope.
The redline, and the decisions in it.
Every change is visible in the markup. The issues table pulls out the points that matter, with a recommended position and the fallback you can accept. Anything above your threshold is marked for your decision.
- strucklanguage removed
- underlinedlanguage added
9.2 Each party's aggregate liability arising out of or related to this Agreement shall not exceed the fees [deleted: paid by Customer in the one (1) month][inserted: paid or payable by Customer in the twelve (12) months] preceding the event giving rise to the claim.
9.3 The limitation in Section 9.2 shall not apply to [deleted: Customer's payment obligations.][inserted: either party's indemnification obligations, breach of Section 7 (Confidentiality), or gross negligence or willful misconduct.]
| Clause | Counterparty asked | Recommended position | Acceptable fallback | Status |
|---|---|---|---|---|
| § 9.2 Liability cap | Cap at fees paid in the prior one month | Cap at fees paid or payable in the prior twelve months | Six months, if carve-outs below are accepted | Within your positions |
| § 9.3 Cap carve-outs | Carve-out for Customer's payment obligations only | Mutual carve-outs: indemnities, confidentiality, gross negligence, willful misconduct | Drop gross negligence; keep the rest | Within your positions |
| § 10.1 Indemnification | Customer indemnifies for any use of the service | Limit to Customer's breach and Customer content | No agreed fallback | Escalated to [decision-maker] |
Illustrative issues table excerpt
- § 9.2 Liability cap
- Counterparty asked
- Cap at fees paid in the prior one month
- Recommended position
- Cap at fees paid or payable in the prior twelve months
- Acceptable fallback
- Six months, if carve-outs below are accepted
- Status
- Within your positions
- § 9.3 Cap carve-outs
- Counterparty asked
- Carve-out for Customer's payment obligations only
- Recommended position
- Mutual carve-outs: indemnities, confidentiality, gross negligence, willful misconduct
- Acceptable fallback
- Drop gross negligence; keep the rest
- Status
- Within your positions
- § 10.1 Indemnification
- Counterparty asked
- Customer indemnifies for any use of the service
- Recommended position
- Limit to Customer's breach and Customer content
- Acceptable fallback
- No agreed fallback
- Status
- Escalated to [decision-maker]
- 01You do
Send
Forward the agreement by email, drop it in a shared channel, or save it to a shared folder. Add the business context: the deal, the counterparty, anything already promised.
- 02We do
Scope and positions
For a one-off agreement, we confirm the fixed fee and your priorities. For recurring work, we apply the positions we have written down with you. Anything outside scope is flagged before work starts.
- 03We do
Prepare the markup
Our tools check the agreement against your positions and prior deals and prepare a draft redline, issues table, and response.
- 04We do
Attorney review and sign-off
A Texas-licensed attorney reads the agreement and the draft markup, decides what it should say, and signs off. Nothing leaves without that review.
- 05We do
Deliver
You receive the redline, the issues table, and the drafted response in the channel you used to send it.
- 06Together
Decide and negotiate
Points above your thresholds go to your decision-maker with a recommendation. You decide; we carry the decision into the next round.
The whole record, read.
Early in the matter, every document is reviewed and placed on a dated chronology. The documents that carry the case are flagged, and the lawyer's view of what they show goes on the page.
sampled read in full
If the matter goes to court, we bring in litigation counsel suited to the case and stay on as your lead, and this record goes with it.
Business Disputes| Date | Event | Source | Note | Flag |
|---|---|---|---|---|
| Mar 3 | MSA and SOW 1 signed. Acceptance within 10 business days of delivery; silence counts as acceptance. | MSA § 4.2; SOW 1 § 3 | Deemed-acceptance clause | Key doc |
| Jun 14 | Phase 1 deliverables sent to Customer's project lead. | Email, delivery receipt | Starts the acceptance window | Key doc |
| Jun 30 | Customer's lead: "looks good, sharing with the team." No rejection notice follows. | Email thread | Window closes with no rejection | Key doc |
| Jul 2 | Invoice 1042 issued for Phase 1. | Invoice | Net 30 | Not a key document |
| Aug 19 | Customer disputes the invoice, citing defects for the first time. | Letter | Conflicts with Jun 30 email | Key doc |
Illustrative dispute chronology with key-document flags
- Mar 3
- Event
- MSA and SOW 1 signed. Acceptance within 10 business days of delivery; silence counts as acceptance.
- Source
- MSA § 4.2; SOW 1 § 3
- Note
- Deemed-acceptance clause
- Flag
- Key doc
- Jun 14
- Event
- Phase 1 deliverables sent to Customer's project lead.
- Source
- Email, delivery receipt
- Note
- Starts the acceptance window
- Flag
- Key doc
- Jun 30
- Event
- Customer's lead: "looks good, sharing with the team." No rejection notice follows.
- Source
- Email thread
- Note
- Window closes with no rejection
- Flag
- Key doc
- Jul 2
- Event
- Invoice 1042 issued for Phase 1.
- Source
- Invoice
- Note
- Net 30
- Flag
- Not a key document
- Aug 19
- Event
- Customer disputes the invoice, citing defects for the first time.
- Source
- Letter
- Note
- Conflicts with Jun 30 email
- Flag
- Key doc
The first written complaint about defects arrives after the acceptance window closed and after the invoice was issued. Lead the demand with the Mar 3, Jun 14, and Jun 30 documents.
- 01You do
Tell us what happened
A short call, then the agreement, the key correspondence, and a timeline in your own words. We arrange a secure channel for documents.
- 02We do
Written scope and fee arrangement
We define the first piece of work, usually assessment and demand, and agree the fee arrangement in writing before it starts.
- 03We do
Read the whole record
Our tools organize and review the documents in full; a lawyer builds the chronology, picks the key documents, and assesses the claims and defenses.
- 04Together
Decide the approach
You receive the assessment and a recommendation. You decide whether to demand, respond, negotiate, or prepare for court.
- 05We do
Act on it
Demand or response, negotiation, mediation, or arbitration preparation, each drafted from the record and checked against it.
- 06Together
Resolve or escalate
We document a settlement, or bring in litigation counsel and lead the matter with them.
We do the work. You make the calls.
Applied Legal
- Read the agreement or the record in full
- Prepare and check every draft against your positions or the documents
- Attorney review and sign-off on every deliverable
- Recommend a position, and say plainly where the risk is
- Flag anything outside the written scope before doing it
- Keep a record of your positions and decisions for the next matter
- Bring in and manage litigation counsel if a dispute goes to court
You
- Business context: the deal, the relationship, what matters commercially
- Decisions on contested terms and on settlement
- Approval of the written scope and any change to it
- Final signature on agreements and settlements
When the work turns into something else.
A negotiation can stall into a dispute. A demand letter can draw a lawsuit. An agreement can turn out to be a different deal than the one described.
When that happens, we stop and tell you before doing the new work. You decide how to proceed, and any change to the scope or the fee is agreed with you in writing first.
Each matter starts where the last one ended.
Your positions, prior agreements, and past decisions are kept for your account. When the same counterparty comes back, or the same clause comes up again, we can see what was agreed before.
When a contract becomes a dispute, the history of how it was negotiated is already in the file.
How your documents are treated.
In plain words. Specific systems and terms are listed in your engagement letter.
- Your documents are not used to train AI models.
- We do not use client agreements or case files to train models, ours or anyone else's.[confirm: AI vendor terms prohibit training on client data]
- Documents stay in your systems where possible.
- When you use Google Drive, SharePoint, or a CLM, we work on documents there rather than copying them elsewhere.
- Access is limited to the people doing the work.
- Only the lawyers and staff on your matter can see your documents, positions, and case file.[confirm: storage location, access controls, and retention period]
- Confidentiality is a professional obligation.
- Client information is protected under the Texas Disciplinary Rules of Professional Conduct once an engagement is in place.
Please do not send confidential documents through the website form. An attorney-client relationship begins only after a signed engagement letter; we arrange a secure channel at that point.
Tell us what is happening. A lawyer will reply.
Describe the agreement, the dispute, or the question. EJ reviews each submission and replies to set up a short call. If a deadline is days away, call instead.