# Capacity Conversation with Timothy Lopas

> A working session for managing partners and senior equity partners at scaling Accounting, Tax, Advisory, Wealth Management, Fractional CFO, and Corporate Law firms whose senior time is being consumed by work that should never have reached their desk. This is not a demo. It is not an automation walkthrough. And it is not for firms exploring AI casually. This session looks at where senior capacity is leaking inside your firm, and whether that leak is constraining your scale, your margin, or your options. We will assess: Where senior time is being absorbed by avoidable review cycles and repeated corrections Where the quality of first-pass work coming up from your team is creating drag across accounting, tax, advisory, wealth management, fractional CFO, and corporate law workflows Where growth has added review burden instead of capacity What could be cleaned up before it reaches review, without adding compliance or control risk Whether a firm-specific capacity system is the right move now, or premature Most firms don't stall because of weak teams. They stall because every piece of work eventually converges on the same few people. By the end, you'll leave with one of three outcomes: A contained, high-value capacity opportunity worth scoping Structural issues that need resolving before any system is built A clear recommendation to wait You'll leave with clarity, not a pitch. This session is reserved for the people responsible for firm-wide performance, margin, and long-term capacity.

- Host: Timothy Lopas
- Duration: 30 min
- Location: Google Meet
- Host time zone: America/New_York
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/workstreamai/conversation
- Event type id: 4888869

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=4888869&start=YYYY-MM-DD&end=YYYY-MM-DD&timeZone=<IANA time zone>
cal-api-version: 2024-09-04
```

The response is `{"data":{"YYYY-MM-DD":[{"start":"<ISO 8601 with offset>"}]}}`; no API key is needed.

## Book

```http
POST https://api.cal.com/v2/bookings
cal-api-version: 2026-02-25
Content-Type: application/json

{
  "eventTypeId": 4888869,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  }
}
```

- Required fields: `name` (Your name), `email` (Email address)
- Optional fields: none
- `name` and `email` go in `attendee` and `guests` is a list of emails; every other field goes in `bookingFieldsResponses` under its name.