# Executive LLM Exposure Debrief with Fabio Yocco

> A confidential, architect-led briefing examining how generative AI engines (ChatGPT, Claude, Perplexity, Gemini) evaluate, attribute, and recommend your enterprise. During this session, we review your organization's AI Discoverability diagnostic, identify active competitor attribution diversion, and examine your technical remediation roadmap. What we assess during the debrief: ✓ Actual AI Perception vs. Market Reality: How models currently interpret your products, leadership, and technical specifications. ✓ Competitor Diversion Analysis: Exactly where and why AI assistants recommend competitors instead of your domain during commercial buying queries. ✓ Attribution Leakage: Identifying proprietary innovations that AI currently credits to third-party aggregators or news blogs. ✓ Machine Readiness Architecture: Gaps in your server-side crawlability, JSON-LD Entity Graphs, and /llms.txt manifests. ✓ On-Chain Notarization: How sealing verified audit records on Ethereum provides tamper-proof provenance for autonomous AI agents. Who this is for: Founders, CEOs, CMOs, and Commercial Directors of technical, B2B, and high-growth industrial enterprises who want to protect their market share in AI-driven procurement. Session format: 30 to 45-Minute Private Briefing with Lead GEO Architect Fabio Yocco. No sales pitch. Concrete architectural intelligence and forensic findings.

- Host: Fabio Yocco
- Duration: 45 min
- Location: Cal Video
- Host time zone: America/Cordoba
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/fixgeo/geo-forensic-briefing
- Event type id: 5823686

## Check availability

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