# ProductFlo Demo with ProductFlo.io

> Most hardware teams don’t struggle with design. They struggle with organization, context, and coordination. CAD lives in one place. Firmware in another. BOMs in spreadsheets. Decisions buried in Slack. ProductFlo.io is the most important software for hardware teams. We give your team a single workspace for building physical products. Think GitHub for Hardware Engineers. Because Hardware engineering deserves better tools and better hardware starts with better software. This call is a short working session to see if it fits how your team actually builds. What We'll Cover 1. Quick Context (5 min) Tell us about what you're building. We’ll quickly understand: Your product (device, machine, hardware product, etc.) Current tools (CAD, firmware repo, spreadsheets, docs) Team size and development stage The biggest bottleneck slowing you down today 2. See ProductFlo in Action (10 min) We’ll show how teams structure real hardware projects inside ProductFlo. Examples include: Organizing product → assemblies → parts Connecting CAD, firmware, documentation, and BOM Tracking engineering decisions and design changes Keeping the whole team aligned on the product We’ll focus on one problem you currently face. 3. Map Your Workflow (10 min) We’ll walk through a piece of your current process: Where context gets lost Where work gets duplicated Where engineering time is wasted Then we’ll show how ProductFlo can structure that workflow. 4. What Happens Next (5 min) If ProductFlo fits your workflow: We’ll help you set up your first product workspace Import or structure your first product architecture Show how your team can start using it immediately No pressure timeline. Use it when it actually helps your team move faster. Who This Is For ProductFlo is built for teams building real physical products: Hardware startups Robotics and IoT teams Teams at Product Design Studio and Engineering Firm Product Page: https://www.productflo.io Demo Video: https://youtu.be/kjrhHj5O6Cg

- Host: ProductFlo.io
- Duration: 60 min
- Location: Google Meet
- Host time zone: America/New_York
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/productflo/productflo-demo
- Event type id: 1055219

## Check availability

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

- Required fields: `name` (Your name), `email` (Email address), `title` (Company Description), `notes` (How big is your engineering team?), `Mcad` (What is your current mechanical CAD software?), `Ecad` (What is your current electrical CAD software?), `Code-Version` (What is your current Code Version software?), `PLM` (What is your current PLM software?)
- Optional fields: `attendeePhoneNumber` (Phone number), `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.