Customers
Built by Harris, used by 12 shops and counting.
GigLogix started as the internal software for Harris Production Services. After 7 years of running 800+ events a year on it, the team realized other AV shops had the same problems. We opened signups in 2022. We're at 12 paying customers as of 2026 and growing.
Paying customers
Harris Production Services
AV rental + venue WiFi · since 2019
Showboat Hotel AC
Venue + AV · Atlantic City, NJ
Stage Right Productions
Production company · Philadelphia, PA
Mercer Street Music
AV rental · Trenton, NJ
+ 9 more AV rental shops, hotel AV teams, and university events departments on Starter and Pro.
Case study
Harris Production Services
Atlantic City, NJ + West Chester, PA · AV rental + venue WiFi · 12 staff · 800+ events a year · on GigLogix since 2019
"We built this for ourselves after 3 years of running 800+ events on Google Sheets, Airtable, and a clipboard. We've used it every day since 2019. The fact that we sell it now is the side effect — it just works."
800+
events a year
4
warehouses
12
full-time staff
0
double-bookings since 2020
What they stopped doing
- Tuesday-night payroll math
- 3-day quote turnaround
- Last-minute gear hunts for "we lost the serial number" cases
- Crew confusion on call times (texted to each tech, separately, every time)
The full story
Harris Production Services is a full-service event production company in the Mid-Atlantic. They do AV rental, venue WiFi, live events, and crew for hotels, conferences, and corporate clients.
The problem in 2018 was that 800+ events a year, across 4 warehouses, with 12 full-time staff and 30+ freelancers, was being run on a stack of Google Sheets, Airtable bases, a clipboard, and a prayer. Double-bookings happened. Payroll took every Tuesday night. Quotes went out 3 days late because the price list was in a different sheet than the inventory was in a different sheet than the client was in a different sheet.
The team built GigLogix over 2018, deploying it for internal use in January 2019. By Q2 2019, the double-bookings stopped. By Q4 2019, payroll was 30 minutes instead of 4 hours. By 2020, quote turnaround was same-day.
In 2022, Harris started showing the software to other AV shops at a trade show. By 2024, 6 shops had signed up. By 2026, 12 shops. The seed customer is still the largest deployment and the most active feedback source — every feature in the platform was built because a real event needed it.
Today, Harris runs 100% of their operation on GigLogix. The software is sold by Harris Technology Services, a sister company, while Harris Production Services remains the reference customer and the most demanding tester.
If you want to talk to a customer who's used the product for 7 years, ask us. We'll connect you.
Why teams switch.
Three patterns from 12 customer migrations. None of them are bad-mouthing the previous tool — they're picking the one that fits the job.
from Rentman
Why teams switch from Rentman
Rentman is a good product for the rental-only shop. We are not that shop. We are the shop that also runs guest internet for the venue, or the shop that also does production company work, or the shop that wants its crew in the same dashboard as the gear. Rentman's pricing also penalizes the 5-15 employee range — you pay for power users you don't have.
from StayFi
Why teams switch from StayFi
StayFi is a good product for the venue-only WiFi business. We are not that business. We are the venue that also does its own AV rental, or the venue that wants Stripe Connect payouts to multiple properties from one dashboard, or the venue that wants a PMS integration.
from spreadsheets
Why teams switch from spreadsheets
You know why. You're on this page because something broke last week. Maybe a double-booking. Maybe a Friday-night payroll. Maybe a quote that went out wrong. Spreadsheets work until they don't, and the day they don't, the cost is a Friday night.
What we'd build next.
The roadmap is public. Every customer can see what we're working on, what we just shipped, and what we're scoping for next quarter. If you want a feature, file an issue — it gets read, it gets prioritized.
See the changelog