# Intro Call — 30 minutes with Smartsales.ai

> A working conversation, not a sales pitch. This is the call where we figure out whether I'm the right operator for what you're facing. Thirty minutes, no slides, no discovery questionnaire. You describe the situation in your own words. I ask four or five specific questions. We both decide whether to go further. I do my best work with B2B SaaS founders and revenue leaders between $3M and $30M ARR who are facing one of these moments: - An AI pilot that spent real money and didn't move a real metric - A VP Sales or CRO transition where the new leader needs to inherit a working system, not a mess - An expansion from one region to two, where the GTM motion you built at home doesn't survive the geography - A forecast that keeps breaking, and you can no longer explain to the board why the variance keeps showing up in the same place - A founder still running sales personally, scaling past the point where that's possible, unsure what kind of first sales hire actually fits If one of these is your week — keep reading. If none of them is, I'm probably the wrong operator, and a thirty-minute call won't change that. What we cover in 30 minutes The first ten minutes: you describe the situation. Specifics, not generalities. What's broken, what you've tried, what's at stake on Monday. The next ten: I ask the questions that determine whether this is an architecture problem (my work) or a coaching problem (someone else's work) or a hiring problem (also someone else's). I'll be direct about which. The last ten: if there's a fit, we discuss what an engagement would look like — Audit, Rescue, or Fractional. If there isn't, I'll point you to operators I trust who are closer to your actual situation. Either outcome is useful. What you don't need to prepare No deck. No metrics package. No NDA in advance. Bring the honest version of what's not working, and we'll go from there. After the call If we move forward, the standard first engagement is a two-week Revenue Architecture Audit ($12K, fixed scope). If timing isn't right or fit isn't there, you'll leave with at least one piece of useful framing you didn't have before. I take this seriously even when I'm not the answer.

- Host: Smartsales.ai
- Duration: 30 min
- Location: Google Meet
- Host time zone: Europe/Madrid
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/roman-smartsales/30min
- Event type id: 1983018

## Check availability

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