# Consulting with Jeffrey Long

> You're a solopreneur with an AI problem you keep circling: Build the thing or buy it? Is the workflow you cobbled together worth saving? Why does the automation that worked in the demo fall over on real work? What should you learn next, and what can you ignore? I build production AI systems and teach people to run them. In an hour I can usually tell you which of those questions actually matters and what to do about it. Bring the mess. We'll rank it, pick one, and you'll leave with a one-page decision memo — written during the call, in your hands before we hang up.

- Host: Jeffrey Long
- Duration: 60 min
- Location: Cal Video
- Host time zone: America/Chicago
- Confirmation: Bookings are confirmed instantly.
- Payment: required, and collected on the booking page.
- Booking page: https://cal.com/jeffrey-long/consulting
- Event type id: 6480373

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=6480373&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": 6480373,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "guests": [
    "guest@example.com"
  ],
  "bookingFieldsResponses": {
    "notes": "…"
  }
}
```

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