CrewChat
CrewChat
Impact worked as a network to get hired. The problem was everything that happened after the hire. CrewChat was built to close that gap and turn Impact into a full production tool that studios would pay for at scale.
The One Workflow Worth Solving
After getting hired through Impact, crew left the platform entirely — back to email, iMessage, and a 15-page PDF called the crew list. The PDF was the only consistent artifact on a production. Everyone had it. Everyone relied on it. And it was completely broken.
The bigger pain point wasn't crew. It was coordinators. Every personnel change meant rebuilding and resending the list to 200+ people. No version control. No single owner. Every update fell on one person.
Every other piece of the production workflow had a tool.
The crew list had nothing.
Every other piece of the production workflow had a tool. The crew list had nothing.
 Slack |  SetKeeper |  WhatsApp |  IMDb | |
|---|---|---|---|---|
| Communication | ||||
| 1:1 and group production messaging | ✓ | — | ✓ | — |
| Crew-wide announcement channel | — | — | ✓ | — |
| Separation between work and personal | ✓ | — | — | — |
| Built for temporary, rotating crews | — | — | — | — |
| Crew & Files | ||||
| Auto-updating digital crew list | — | — | — | — |
| File distribution + recall | — | ✓ | — | — |
| Per-recipient watermarking | — | — | — | — |
| Sides generation from script | — | ✓ | — | — |
| Talent | ||||
| Crew database with production credits | — | — | — | ✓ |
| Avail check any profile instantly | — | — | — | — |
We assumed it was a crew list problem.
The obvious starting point: replace the PDF with something searchable, department-organized, built for how film actually works.
Clear problem, tight enough to ship. What we didn't know yet — we were solving the right problem for the wrong user.
Three iterations before we landed. Each one taught us what the next had to solve.
The Personal Contact Directory
The first concept parsed the PDF into a digital contact directory. Two problems: it still sent people to their native phone to communicate, so the retention problem was untouched. And as crew added more shows, contacts collapsed across productions with no separation.
The Active Production Directory
Version 2 scoped lists by production and let anyone upload an updated crew list. It solved the crowding problem — but broke version control immediately. When anyone can upload, no one owns it. Same problem as the PDF, now inside the app.
We paused CrewChat and went back to users.
The finding was consistent: neither version had reduced coordinator workload. They were still building the crew list somewhere else. The app made consumption easier. It didn't touch production.
The through-line became obvious, with the two past iterations communication was still happening off the app. As long as that was true, we weren't essential — we were slightly more digital. If we wanted retention, we had to own the communication aspect.
Keeping Communication On Platform
A place to message people on set
Not a workaround in iMessage. Not a group chat with unknown numbers. A purpose-built communication layer where every contact is verified, role-tagged, and scoped to the production.
A place to have community on sets
Productions are their own ecosystems. Announcements, department threads, the social layer of a shoot — all of it was scattered. CrewChat needed to be where that community actually lived.
With the new north stars in place, the concept shifted entirely. Not a crew list feature — an on-set communication tool. Something crew couldn't do without on a 14-hour shoot day.
Coordinator-Owned. On-Set Communication.
Version 3 committed to messaging as a core surface, not an afterthought. One coordinator owns the list. Email invites go to the address already on file — no opt-in ambiguity. If you're on the crew list, you're in the app.
Department-first navigation
The structure matched the mental model crew already had.
Dark mode only — functional, not just aesthetic
Film sets are dark. Stages, night shoots, low-light environments.
The crew member row
Name at highest visual weight, role below it. Call and message icons on the right — findable without competing.
Department-first navigation
The structure matched the mental model crew already had.
Dark mode only — functional, not just aesthetic
Film sets are dark. Stages, night shoots, low-light environments.
The crew member row
Name at highest visual weight, role below it. Call and message icons on the right — findable without competing.
Redesigning CrewChat
The original drill-down required a back button between every department — real friction on a 14-hour shoot day. Field complaints flagged it, timed tests confirmed it.
The redesign: tap a caret, the department opens inline. Name becomes a sticky header. Next department appears at the bottom. No back button, no lost context.
Tracking User Behaviors That Led To Evolution
We hadn't designed file sharing into CrewChat — but crew were using the announcements channel to distribute production documents anyway. The chat couldn't handle it: phones lagged, size limits were hit, no watermarking, no access controls. The live product told us exactly what to build. When we built it, we built the right thing.
File Distribution — the feature the announcements channel had become, done properly.
Coordinator-owned, watermarked per recipient, organized into color-coded distro lists. Rich text, large file support, scoped access. This replaced the last piece of off-app workflow — email — and closed the full loop.
CrewChat didn't start here.
Network + Credibility
Profiles, search, availability, reputation signals. A network with real trust — not just a database of people who exist.
Hiring System
Avail Check, status tracking, coordinator workflow. Structure that fit how hiring already worked, without replacing it.
On Set Tools
Crew list, messaging, file distribution. The layer that kept crew inside Impact during the production itself — and closed the retention loop.
On Set, For Real
Ron Howard's EDEN was one of the first major productions to run fully on CrewChat.
Ground-level read on adoption from day one to wrap, not platform averages.
Messages sent across the production during the shoot.
Announcements broadcast production-wide, replacing email chains.
Phone calls made through the app — crew list as live contact directory. 200+ crew using the app daily at peak, across 15+ departments.
"I don't know how I or any other production could do without it now. It set a new standard."
"CrewChat became my first choice for getting information from production instead of email."
"The most streamlined way to get messages out to everyone on set immediately."
Important Milestones
Scenechronize was charging $30,000+ per production. Impact delivered comparable
capabilities at a fraction of that cost and the product sold itself into the studio layer
once productions were running inside it.
Driven by keeping crew in the platform long after the hire closed, driven by in-app communication.
New productions onboarded, from 30 to 500 crew members each, driven by top-down approach.
AMC, Skydance, Warner Bros, and Netflix signed through the platform, vertical product made it make sense.
It spread the way good tools spread
Half of all new productions came through referrals — crew carrying the tool from job to job.
That kind of adoption doesn't come from sales. It comes from people not wanting to go back.
It spread the way good tools spread
Half of all new productions came through referrals — crew carrying the tool from job to job. That kind of adoption doesn't come from sales. It comes from people not wanting to go back.
Of new productions came through referrals — crew carrying the tool from job to job.
Active productions in a rolling 30-day window.
Next Steps & Reflections
The pause was a product decision, not a delay
Stopping CrewChat gave us clarity we couldn't get by iterating in place. When we came back, we understood the retention problem differently — as a communication problem, not a directory problem.
The referral number told us something the DAU didn't
43% DAU increase showed crew were staying. 50% referral rate told us why — the product was solving a specific enough problem that people carried it between productions.
Cutting from MVP was the right call — every time
Call sheets and on-site status indicators were both designed and both cut. The live product validated every cut — shipping incomplete is a listening strategy.
Offline-first should have been a launch requirement
We knew signal was poor on soundstages and didn't prioritize aggressive caching. Given the constraint, offline-first should have been a launch requirement, not a retrofit.