# 60-Min Strategic Consultation with Orchestrary | Chief Agent Architect | Jakub Bares

> 200 USD per hour Description: A deep working session where we map your department's workflows, identify the highest-ROI automation targets, and outline what an agent deployment would look like in your environment. This is not a demo — it's real analysis of your real operations. What we cover: Detailed walkthrough of your department's core processes and bottlenecks Identification of 3–5 workflows where autonomous agents replace manual steps Initial agent architecture — what each agent would see, decide, and do Rough ROI projection based on your team size, volume, and current costs Technology and security considerations specific to your infrastructure Who this is for: Decision-makers ready to move beyond exploration. You have a department in mind, a problem that costs real time and money, and you want a concrete deployment plan — not another slide deck.

- Host: Orchestrary | Chief Agent Architect | Jakub Bares
- Duration: 60 min
- Location: Cal Video
- Host time zone: Europe/Prague
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/orchestrary/1-hour-consultation
- Event type id: 5271603

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=5271603&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": 5271603,
  "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.
