# Scoping call with zulusec

> A working session to figure out what you actually need and what it costs. Free, 30 minutes, no obligation. By the end of the call you will have an agreed scope and a fixed-price quote in writing. No slides, no pitch deck. What we'll cover: 1. Your environment. What you run and where: cloud accounts, subscriptions or projects, on-prem sites, Kubernetes, and roughly how big each one is. 2. What's driving this. A customer questionnaire, a compliance requirement, a board question, an incident, or just wanting to know where you stand. This tells us where to dig deeper than the standard checklist. 3. Scope and price. We agree exactly what is in and out, then quote a fixed price for it. Fixed means fixed: the number we agree is the number you pay, and there is no hourly meter. 4. What happens next, if you want to proceed. A mutual NDA, an engagement agreement, and a written access authorization naming exactly which systems we may look at. You sign and pay before any work starts, and access is always read-only and least-privilege. Useful to have ready, though none of it is required: a rough list of the environments you would want covered, any compliance requirement or customer questionnaire driving this, and whether someone with admin rights can create read-only access later. Nothing is committed on this call. If we are not the right fit, we will say so and point you somewhere better. Questions beforehand: ops@zulusec.com

- Host: zulusec
- Duration: 30 min
- Location: Google Meet
- Host time zone: America/Chicago
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/zulusec/30min
- Event type id: 6659394

## Check availability

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