# PipeGen - ScaleFast  (EN) with Alex JAGLALE

> Hi, The goal of this call is straightforward: quickly validate whether our Pipe Gen expertise can strengthen your acquisition strategy — and more importantly, deliver measurable results. To keep things focused and useful, here's the structure I propose: 1. Frame & expectations — introductions, aligning on the call's objective, and defining what "success" looks like for you 2. Your organization — how Sales & Marketing operate today, roles, priorities, constraints 3. Process & tools — your stack, rituals, how you track performance, friction points 4. Account strategy — business signals, segmentation, personalization, prioritization — how you decide "who to engage, when, and why" From there, we make a clear call. If we're not the right fit I'd rather be upfront: if I see we can't create real, net value — I'll say so. - We'll connect you with a partner better suited to your needs - We'll leave you with concrete recommendations to improve things internally - And we'll cut the call short to respect your time If we are a good fit Then I'll show you exactly how we secure execution: - Our methods, processes, tools (and our AI agents) - Client case studies: roadmap, results, ROI, what worked and why We'll close with a plan: - Aligned scope + objectives - Clear, actionable next steps and a clean working cadence My intention is for you to leave this call with two things: clarity, and the confidence that — if we move forward together — you're in very good hands. Looking forward to it,

- Host: Alex JAGLALE
- Duration: 30 min
- Location: Google Meet
- Host time zone: Europe/Paris
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/scalefastnow/pipegen-scalefast-en
- Event type id: 5639546

## Check availability

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

- Required fields: `name` (Your name), `email` (Email address), `companyname` (Company)
- Optional fields: `attendeePhoneNumber` (Phone number), `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.
