# Build-With-Me Session with Sharon Custer

> You have seen what AI can do with finance data. You cannot get it to work on yours. That is usually not one problem. It is three, and they arrive looking like one. The tool problem. Getting the AI to actually produce the thing, and getting the dashboard to sit somewhere people will look at it. The data problem. Pulling from systems that disagree, and cleaning them so the join is honest rather than just tidy. The finance problem. Which number belongs there, how it is built, and what it is supposed to tell whoever reads it. 90 mins, 1 on 1, with your own data and problem you want to solve. We work out what is actually blocking you, put them together in the right order, and build the part that matters while you watch. You leave with it working, and with the shape of the workflow, so the next one you build yourself. Private. Nothing you show me goes anywhere. Payment is taken at booking. Reschedule or cancel up to 24 hours before at no charge.

- Host: Sharon Custer
- Duration: 90 min
- Location: Cal Video
- Host time zone: America/Guatemala
- Confirmation: Bookings are confirmed instantly.
- Payment: required, and collected on the booking page.
- Booking page: https://cal.com/inventoryoptimizationpro/session
- Event type id: 7150609

## Check availability

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

- Required fields: `name` (Your name), `email` (Email address), `title` (What is this meeting about?)
- Optional fields: `attendeePhoneNumber` (Phone number), `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.
