Case Study

Bay Legal, PC:
4.2× Revenue Growth Through Operator-Designed Infrastructure

Estate planning, probate, and real estate/construction disputes in Palo Alto, CA. This is the firm that XPRTS was built inside — and the proof that our systems actually work.

FIRM PROFILE

Bay Legal, PC

Palo Alto, CA

Managing attorney

Jayson R. Elliott, Esq.

Reported team size

30+ employees
25+ remote

Case-study practices

Estate planning, probate, real estate and construction disputes

Core technology

Clio Manage, Lawmatics, QuickBooks and Zapier/Make

4.2x

Revenue growth in 2025 — built on operator-designed infrastructure

98.5%

2026 year to date

Collections rate — driven by automated billing workflows in Clio

<5min

Speed-to-lead — every inquiry hits the Lawmatics pipeline within minutes

25+

Remote staff deployed, trained at Bay Legal, retained across the team

The starting point

Growth Depended on the Founder

The case study describes a firm with strong demand but limited operational capacity.

Jayson Elliott was involved in client communication, intake strategy, legal drafting, hiring, and management. As the practice expanded, more matters also meant more decisions and coordination returning to the founder.

The issue was not presented as a lack of demand. The firm needed a way to add capacity without making every new hire another management burden. XPRTS’s response was to define the work, document repeatable processes, configure the technology, and develop a training pipeline before expanding the team.

The operational constraints

  • Recurring work depended on individual knowledge rather than documented procedures.
  • New hires needed clearer roles, onboarding, and reporting lines.
  • Intake, matter management, and billing needed more consistent handoffs.
  • Leadership needed visibility into performance without assembling information manually.

The aim was to make growth less dependent on one person’s availability.

The infrastructure build

Four Workstreams, One Operating Model

The source describes the infrastructure as having been developed between 2023 and 2025. The work combined technology configuration with process design and staff preparation.

Build period: 2023–2025, as reported in the case study

Clio Manage Configuration

A structured practice-management environment for the firm’s casework.

  • Matter templates for estate planning, probate, real estate disputes, and construction claims.
  • Task sequences, document organization, and defined stages for recurring work.
  • Invoice generation, payment reminders, collections escalation, and KPI reporting.

Lawmatics Intake Pipeline

A defined process from the first inquiry through engagement and follow-up.

  • Lead capture, source attribution, and automated initial responses.
  • Pipeline stages, consultation scheduling, reminders, and engagement documents.
  • Longer-term re-engagement sequences for leads who are not ready to retain.

Remote Staff Deployment

A training and placement model developed within the operating law firm.

  • Role-specific preparation for intake, legal assistance, billing, and administration.
  • Training on live workflows with feedback from Bay Legal’s team.
  • Documented SOPs, defined responsibilities, and structured onboarding before placement.

Systems Integration

Connections intended to reduce duplicate entry and preserve context between teams.

  • Lawmatics-to-Clio handoff when an intake converts to a matter.
  • Zapier/Make connections involving QuickBooks, Google Workspace, and the phone system.
  • Configured task transitions and reporting across the firm’s operating tools.
How the work connects

From Inquiry to Reporting

The individual platforms serve different purposes. The operational value comes from designing the handoffs between them, not simply adding more software.

Bay Legal’s reported setup brings intake, matter management, billing, and supporting business tools into a connected workflow. The implementation includes both platform configuration and additional automation where needed.

The precise fields, triggers, and routing rules should be determined by the receiving firm’s processes. The case study does not establish that every integration or feature is available natively in every subscription.

01

Inquiry & intake

Lawmatics: An inquiry enters the intake pipeline, where response, qualification, scheduling, and follow-up can be managed.

02

Conversion & handoff

Lawmatics → Clio: The configured integration creates the matter and transfers mapped contact and intake information.

03

Matter delivery

Clio Manage: The team works through matter templates, assigned tasks, documents, deadlines, and time records.

04

Billing & reporting

Clio + QuickBooks: Billing and accounting information follows the configured processes, with reporting used to review collections and operations.

Illustrative overview of the reported configuration. It is not a live system diagram or a guarantee of a particular platform’s capabilities.

Results & context

What the Case Study Reports

The outcomes are meaningful as a record of Bay Legal’s experience, but they should be read in the context of the wider infrastructure build.

XPRTS attributes Bay Legal’s reported 4.2× revenue growth in 2025 to the combination of systems, staffing, and web infrastructure. The case study also reports a 98.5% collection rate for 2026 year to date, sub-five-minute speed-to-lead, and a 30+ person team including 25+ remote staff.

These are firm-level outcomes. The source does not isolate the effect of any one software product, automation, staffing placement, or website. It also does not provide the underlying revenue baseline or a complete financial analysis.

Evidence & limitations

What is, and is not, established

  • The infrastructure build is dated 2023–2025.
  • The revenue-growth figure is reported for 2025.
  • The collections figure is labeled 2026 YTD, without an exact cutoff date.
  • The staffing and response-time figures are reported operational results.
  • The source does not provide audited financials, a controlled comparison, or a client-outcome guarantee.

The original page also contains an industry-average comparison and a revenue calculation that are not sufficiently supported. They have been omitted rather than repeated as verified facts.

“

XPRTS isn’t a theory. It’s the operating system for Bay Legal. We used our own firm as a live laboratory to stress-test every workflow, staffing model, and AI integration before offering them to you.

— Jayson R. Elliott, Founder

Related services

Explore the Work Behind the Case Study

These service pages explain how XPRTS approaches the individual operational areas described above.

01

Systems & Automation

Configuration, integrations, dashboards, and workflow improvements for the systems a firm already uses.

02

Staffing & Operations

Defined roles, SOPs, onboarding, and remote legal support trained within Bay Legal’s environment.

03

Fractional Operations

Ongoing operational review and leadership support for firms that need help managing the system as they grow.

Ready to Build the Same Infrastructure for Your Firm?

Every XPRTS engagement starts with a free Strategy Review — where we identify your firm’s primary bottleneck and map the path to results like these.