Answers, before the demo call.

Car show organizers, concours committees, cars & coffee hosts, regional event promoters, and clubs that run a calendar. Pitform fits events where tickets, vehicles, arrivals, voting, awards, and records all need to stay accurate.

Pitform is built around vehicles, not just tickets. Cars can have reusable profiles, display tickets can collect vehicle details, QR stickers open public vehicle pages, and voting and awards stay tied to the vehicle. Generic platforms usually stop at admission.

Those tools are built for sanctioned competition — timing, transponders, run groups, sanctioning bodies. Pitform is for shows: registration, check-in, voting, results, exports. If your event is a track day or autocross, Pitform is not the right fit.

No. Pitform is built for small shows, regional events, and club calendars. Free events can run without Pitform platform fees; larger or paid events go through a setup review before launch.

A first event setup covers ticket types, voting categories, public registration, check-in flow, staff access, imports when needed, and Stripe setup for paid sales. Returning participants can reuse saved vehicles instead of rebuilding the same car every show.

Pitform is web-based, so the check-in team needs an internet connection through venue WiFi, phones, hotspots, or cellular tablets. The event-day screens are designed for field use on devices with signal.

Event staff get focused screens for the work at the gate: scan a ticket, type a code, search a name, confirm an arrival, or hand off a display sticker. They do not need the full admin surface to work the line.

Each linked vehicle has a QR sticker that opens its public vehicle page. Attendees scan, vote by category, and keep walking. There is no app download or attendee sign-in, and voters can change or remove votes while voting is open.

Event staff can scan signed ticket QR links, type visible ticket codes, or look up tickets manually. Pitform blocks duplicate use, wrong-event tickets, and refunded or cancelled tickets before they become a gate problem.

Yes. Display registration supports multiple vehicles, and participants can save reusable vehicle profiles in My Account. Each event still keeps its own vehicle snapshot for check-in, QR linking, voting, photos, and award history.

Ticket confirmation emails include signed QR ticket links, and participants can sign in to My Account to access current and past event tickets tied to their email/account.

Yes. Vehicle photos and multi-photo galleries are part of the current product. Public vehicle pages and browsing surfaces can show the car, details, story, voting, and awards after results are published.

Free events can run with a $0 Pitform platform fee. Standard paid-event pricing is confirmed before setup based on event size, ticket mix, support needs, and whether fees are passed to buyers or absorbed by the organizer. Custom pricing applies to larger or support-heavy events.

Paid ticketing uses Stripe Connect Express. Paid ticket types require a connected Stripe account; free ticket types do not. Stripe processing is separate from the Pitform platform fee.

They stay with the event. Admin Orders supports full and partial refunds, per-ticket cancellation without refund, resend, ticket links, ticket status, check-in tools, and CSV export for the selected event.

No. Paid sales open after Stripe and event setup are confirmed. The launch review covers the connected account, ticket setup, checkout path, and the event-day operating pieces.

Support expectations are confirmed before launch. Paid and custom events can include event-day support, with coverage matched to the event size and operating plan.

You do. Every record you put in Pitform is yours, and you can pull it back out as CSV — participants, orders, tickets, results, payment records, and vehicle data.

Yes. CSV import for vehicle pre-registration is supported. The morning of an event is not the time to retype a list.

No. We do not have a marketing list. Your event's contacts are yours.

Pitform is multi-tenant. Each organizer operates under its own Pitform subdomain, tenant context is resolved before tenant routes run, and organization data stays scoped to that organization.