# GTM Assessment with Levi Yosef

> A 45-minute GTM Assessment of your sales motion: where time is lost, what an AI-native GTM system changes for you. To prepare: Where is my B2B deal actually stuck? https://www.usecosa.ai/resources/where-is-my-b2b-deal-stuck How we read a deal stakeholder by stakeholder, before we talk about solutions. When should a technical founder hire a sales leader? https://www.usecosa.ai/resources/founder-led-sales-when-to-agentify What breaks first in founder-led sales and how you tell that a process is proven. Why do B2B pilots stall after the buyer says yes? https://www.usecosa.ai/resources/why-b2b-pilots-stall-after-yes If pilots or proofs of concept are stuck on your side, the cause is usually the order of steps, not the buyer. Our methodology: https://www.usecosa.ai/en/methodology How we work, from the assessment to the handover, so you know what the work looks like afterwards. Please bring one or two deals that are stuck right now. Please confirm the call beforehand. If we do not hear from you, we assume it was booked by accident and release the slot. Privacy: we use your details to arrange and prepare the call. Details: privacy policy at usecosa.ai, section 7. https://www.usecosa.ai/en/privacy

- Host: Levi Yosef
- Duration: 45 min
- Location: Google Meet
- Host time zone: Europe/Berlin
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/usecosa/gtm-assessment-en
- Event type id: 7807239

## Check availability

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

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