# Growth Strategy Consultation with Reece Gregory

> For operators who know something in their business is capping growth, and want to find out exactly what it is before they build around it. This is the first step of how we work: we map your operations, find the constraint that's actually limiting what you can ship, close, or deliver, and hand you a fixed-scope plan to break it — before any code is written. What we'll cover A walkthrough of your operations — ops, delivery, reporting, onboarding, content — to find the single bottleneck capping output, not just where things feel slow. A ranked shortlist of automation opportunities, scored by ROI and build complexity, so the highest-leverage constraint gets fixed first. A straight read on what we'd actually build to break it: an AI agent, document automation, a full-stack app, a content/video system, or an intelligence dashboard — whichever fits, not a generic framework. What you leave with A one-page build spec: fixed scope, fixed price, no surprises. If it's a fit, most builds ship in 2–6 weeks and you own the system on handover. This is for you if: Something in your operation is capping how much you can take on, ship, or close — and it's not more headcount that fixes it. You suspect a process is the real constraint on growth, not effort. You want a concrete, buildable plan to remove the bottleneck — not a strategy deck. No pitch, no deck. You leave with a clear picture either way.

- Host: Reece Gregory
- Duration: 30 min
- Location: Google Meet
- Host time zone: Europe/London
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/reece-gregory/growth-strategy-consultation
- Event type id: 6803052

## Check availability

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