Intake.
Before you commit to the work, figure out what you’re actually committing to.
REQUEST → DEPENDENCIES → TEAM → DECISIONCreative requests rarely arrive with all their dependencies neatly attached.
Change the deliverables and you may change the team. Add review rounds and the schedule moves. The right artist isn’t available, so staffing changes, which changes cost. An asset you thought was approved isn’t, and suddenly there’s another step nobody planned for.
Most of this is knowable before the project starts. You just have to ask the right questions.
I built Intake to surface those dependencies early and streamline the producer work that comes next.
A launch brief arrives.
Six social videos. Motion titles and cutdowns. Four weeks. $10,000. More variants, maybe.
Questions before commitment.
The answers change the plan.
Intake starts with the request, then asks the questions that affect what happens downstream: scope, assets, channels, reviews, deadline and budget.
The answers aren’t just recorded. They change the plan.
Edit the request, structure it, then move through scope, staffing, schedule and the decision. The numbers update as you go.
The request arrives.
What do we know?
The best match is more than who’s free.
On an art team of 50+ people, staffing isn’t just finding someone who’s free.
A producer is looking for the best match across creative fit, availability, workload, timeline and cost. Change one variable and you may need to solve the puzzle again.
Intake does that comparison across the team, then builds a proposed staff, schedule and budget.
It doesn’t replace the producer’s decision. It gets the producer to the useful part of the decision faster.
I didn’t need another intake form.
I wanted the request, staffing, schedule and budget to behave like what they actually are: dependencies.
Change one and you should be able to see what happens to everything downstream, before you promise anyone anything.