The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Mar 27, 2026 2:36am

@cursor review

@greptile review

PR Summary

Medium Risk
Renames a submitted/demo-request payload field (userCount -> companySize) across UI validation and the API handler, which can break any external callers still sending the old field. Otherwise changes are limited to form options/labels and email/log output.

Overview
Updates the demo request flow to collect company size instead of number of users.

This renames the field throughout the UI schema/form state and the /api/demo-requests handler (userCount -> companySize), updates the selectable ranges (including new 1001_10000 and 10000_plus buckets), and adjusts validation messages plus the email/log formatting to reflect the new field.

^{Written by Cursor Bugbot for commit bf0389b. This will update automatically on new commits. Configure here.}

Greptile Summary

This PR renames the "Number of users" field in the demo-request modal to "Company size" and updates all related constants, types, and the API route consistently. It also refines the size buckets by splitting the old 1000_plus value into 1001_10000 and 10000_plus, and replaces hyphens with en-dashes in the option labels.

• consts.ts: Renames DEMO_REQUEST_USER_COUNT_* → DEMO_REQUEST_COMPANY_SIZE_*, adds new 1001_10000 / 10000_plus enum values, updates the Zod schema field (userCount → companySize), and renames the label helper function.
• demo-request-modal.tsx: Updates all form state, combobox bindings, and the visible FormField label.
• route.ts: Updates destructuring, logger metadata, and the email template line from "Users:" to "Company size:".

The rename is thorough and consistent — no stale references to the old userCount field were found in the demo-request feature code.

Confidence Score: 5/5

Safe to merge — small, well-scoped rename with no logic changes or regressions.

All three touched files are updated consistently; no database persistence of the old enum values was found, so the bucket rename (1000_plus → 1001_10000 + 10000_plus) carries no backward-compatibility risk. No unrelated code is affected.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    actor User
    participant Modal as DemoRequestModal
    participant API as /api/demo-requests
    participant Email as Email Service

    User->>Modal: Fills form (including Company size)
    Modal->>Modal: Validates with demoRequestSchema (companySize enum)
    Modal->>API: POST { ..., companySize, ... }
    API->>API: safeParse with demoRequestSchema
    API->>Email: Send email with getDemoRequestCompanySizeLabel(companySize)
    Email-->>API: Sent
    API-->>Modal: 200 OK
    Modal-->>User: "We'll be in touch soon!"

_{Reviews (2): Last reviewed commit: "Fix lint" | Re-trigger Greptile}