Portfolio Concept Project — fictional firm, no client data

Legal Operations Workflow Redesign

Designing a scalable matter-management system for a growing boutique law firm.

Project Type
Concept / Spec Project
Role
Operations & Process Designer
Focus
Workflow Design · CRM Architecture · Automation · SOP Development
Tools
Pipedrive · Google Workspace · QuickBooks · Calendly · DocuSign/PandaDoc · Asana

A concept operations redesign for a fictional, growing boutique entertainment and creator contracts law firm. Every stage, rule and document below was written for this case study.

02The operational challenge

As a firm grows, the process quietly moves into people's heads.

Work becomes increasingly dependent on individual memory, inboxes, manual follow-ups and informal handoffs. It functions — until volume, headcount or a single absence exposes it.

  • 01

    Unclear task ownership

    Work moves forward only when someone remembers it belongs to them.

  • 02

    Missed or delayed follow-ups

    Follow-up lives in an inbox rather than in a system with a due date.

  • 03

    Incomplete intake information

    Matters begin before the details needed to progress them are captured.

  • 04

    Difficulty identifying matter status

    Answering “where is this?” requires reading a thread instead of a record.

  • 05

    Inconsistent processes as the team grows

    Each new person inherits a slightly different version of the same process.

Convergence

Five scattered sources of truth, consolidated into one standardized workflow.

Email
Calendar
CRM
Documents
Billing

Single system

Standardized matter workflow

Stage · Owner · Required action · Exit criteria

03 — Design principle

“The system shouldn’t rely on memory.”

Each stage of the matter lifecycle should have a defined owner, required action, completion criteria and next step. Automation should reduce repetitive administrative tracking while legal judgment, contract drafting and legal advice remain with attorneys.

Owner
Required action
Completion criteria
Next step
04Master matter workflow

Fourteen stages, each with an owner and an exit condition.

Select any stage to see its purpose, owner, key actions, automation opportunity and the criteria required to move forward.

  1. Stage purpose

    Capture an inbound inquiry as a structured record rather than an email.

    Primary owner

    Legal Assistant / Operations

    Key actions

    • Log inquiry source
    • Create CRM record
    • Send acknowledgement

    Possible automation

    New inquiry creates a CRM record and an intake activity.

    Exit criteria

    Inquiry recorded with contact details and matter type.

05Role ownership

Legal judgment stays with attorneys. Everything around it is operational.

A responsibility matrix makes the boundary explicit: filled markers indicate primary ownership, outlined markers indicate a supporting role.

Primary owner Supporting
ResponsibilityFounder / Managing AttorneyAssociate AttorneyParalegalLegal Assistant / OperationsBookkeeper
Legal work
Legal strategy
Contract drafting
Legal review
Legal advice
Negotiations
Review calls
Operational work
Client communication
CRM management
Intake
Scheduling
Invoicing coordination
Document preparation & cleanup
Task tracking
Follow-ups
Contract circulation
Signature coordination
File management
Matter closeout
06Automation architecture

Trigger, system response, action — written as rules, not reminders.

Each rule removes a piece of administrative tracking. None of them make a legal decision.

A-01Automation rule

Trigger

New inquiry received

System

Create CRM record

Action

Create intake activity

Owner: Legal Assistant

A-02Automation rule

Trigger

Retainer signed

System

Move matter to Retained

Action

Create invoice task

A-03Automation rule

Trigger

Invoice unpaid after 2 days

System

Create follow-up activity

Action

Send payment reminder

Rule: Matter remains on hold until payment is confirmed

A-04Automation rule

Trigger

Payment received

System

Move matter to Drafting

Action

Create attorney drafting task

A-05Automation rule

Trigger

Redlines received

System

Update CRM activity

Action

Create attorney review task

A-06Automation rule

Trigger

All parties have signed

System

Move matter to Execution Complete

Action

Create matter closeout checklist

07CRM pipeline mockup

A conceptual board where matter status is visible at a glance.

Fictional matters only. Stage names map one-to-one to the workflow above, so a card's column is its status.

Potential Client

2

Matter 112

Creator brand deal

Inquiry logged

Ops

Matter 111

Licensing

Awaiting reply

Ops

Intake

1

Matter 109

Talent agreement

Form 60% complete

Ops

Retained

1

Matter 104

Production services

File opened

Ops

Payment

1

Matter 103

Sponsorship

Invoice day 2

Bookkeeper

Drafting

2

Matter 098

Content licensing

Draft v1

Associate

Matter 097

Collab agreement

Inputs prepared

Associate

Client Review

1

Matter 094

Merch license

Comments due Fri

Ops

Opposing Counsel

1

Matter 091

Distribution

Sent, day 3

Ops

Redlines

1

Matter 088

Music sync

Round 2 compare

Attorney

Signatures

1

Matter 084

Appearance release

2 of 3 signed

Ops

Complete

1

Matter 079

Series option

Closeout checklist

Ops

Conceptual board · fictional matter IDs · no real names, businesses or client information

08Operational decision-making

Knowing What Happens Next

Operational decisions rely on context and matter status rather than simply completing individually assigned tasks. The same message means different things at different stages.

Scenario 01

Incoming message

“We accept the proposed changes.”

Operational response

Review current matter stage and determine whether acceptance should be relayed to opposing counsel or whether the contract is ready for final preparation and execution.

Scenario 02

Incoming message from opposing counsel

“All changes are accepted. Please send finals.”

Operational response

Prepare the clean final document, send the final to opposing counsel, prepare the client copy for electronic signature, update matter status and monitor execution.

Scenario 03

Situation

Invoice remains unpaid two days after being issued.

Operational response

Send payment follow-up, keep drafting workflow on hold and document the activity in the matter record.

09SOP library

Twelve documented procedures, one shared standard.

Every SOP follows the same structure so a new team member can execute it on their first day. Expand the first card for the full format.

01

New Client Intake

02

CRM & Matter Setup

Documented
03

Consultation Scheduling

Documented
04

Retainer & Engagement

Documented
05

Billing & Payment Follow-Up

Documented
06

Contract Drafting Handoff

Documented
07

Client Review

Documented
08

Opposing Counsel & Redlines

Documented
09

Final Contract Preparation

Documented
10

E-Signature & Notarization

Documented
11

Matter Closeout

Documented
12

Email & Task Management

Documented
10Before vs after

The same firm, operating on a different substrate.

This is a concept project, so no performance metrics are claimed — only structural differences in how the work is held.

Before

Email-dependent operations

  • Manual tracking
  • Unclear ownership
  • Follow-ups dependent on memory
  • Difficult status visibility
  • Inconsistent documentation

After

Workflow-driven operations

  • Defined CRM stages
  • Assigned ownership
  • Automated task creation
  • Standardized handoffs
  • Documented SOPs
  • Clear matter visibility
11Skills demonstrated

What this project required.

  • Workflow Design
  • Operations
  • CRM Architecture
  • Process Improvement
  • Task Management
  • Automation
  • SOP Development
  • Legal Operations
  • Client Experience
  • Project Coordination
  • Cross-Functional Communication
  • Quality Control