Fifteen jobs on the board. Four still need an owner.
Every job you run for a client sits on it, with who owns it and when it’s due.
Take on more work.Keep the same desks.
Your team takes the seats. Everyone you bring in for a job joins that job, and ABRAM does the first pass on the busywork.
Seats are for your team.
Freelancers, cast and vendors join the project they're on, without taking a seat.
Everyone gets their part.
Crew get their calls and bookings. Clients get their own portal.
ABRAM does the first pass.
It reads each request, drafts the quote and suggests who fits each open role.
A request comes in.It's already read.
Clients fill in a form you built, and ABRAM reads each request before it reaches you.
Client intakeFourteen crew on the job.Each one sees what they need.
Your roster keeps the crew you already trust, and Auto-fill roles suggests who fits each open seat.
The skill graphThe crew see their week in their phone’s browser, down to Wednesday’s pickups on Stage 4.
Casey is overbooked.The grid shows you where.
The workload grid adds up each person's planned hours across every job, day by day.
Who is over, this week and next
Anyone booked past their hours is counted at the top, by name.
The days that tip them over
Each person is a row, and the days they run over turn orange.
Hours still free
Open hours and unassigned work sit side by side, so you can see who could take it.
First cuts go to the client.The card moves to In review.
Every deliverable moves through five states, and the client sees the same one you do.
Spot 1 is in review.The client is already on it.
They play each cut and leave their notes right on the frame.
Client portals
Approved.And signed.
They type their full name and agree to one line. ABRAM keeps who signed, when, and the fingerprint of the exact file they approved.
It's really them.
Their email is confirmed by their portal link, or by a 6-digit code before they sign.
The file can't change underneath.
If the cut changes after they open it, the signature won't land on it.
A receipt for the record.
Who signed, which version, when, and the file's fingerprint, with a copy to their email.
Frequently asked questions
Put your next client request through ABRAM.
Get startedWorkfront is a trademark of Adobe Inc. Asana, Monday, Jira and Rentman are trademarks of their respective owners. ABRAM is not affiliated with or endorsed by any of them.
Agency Operations, Client Portals and Integrations
ABRAM is the Creative Intelligence platform. It's where filmmakers, agencies and creators plan and run their productions. ABRAM runs a creative agency's client work in one place: it reads each incoming request, staffs the job from your own roster, schedules it against everyone's availability, and takes client review and approval in a branded portal. It is for creative agencies and studios.
The agency hub covers client request intake and triage, branded client portals with timecoded video review, call transcripts, crew roster management, capacity planning, project importers, and the Slack connector.
Entity relationships:
[ABRAM] [is] [Creative Agency Software].
[ABRAM] [is] [the Creative Intelligence platform].
[ABRAM] [automates] [Crew Roster Management].
[ABRAM] [triages] [Project Requests].
[ABRAM] [manages] [Capacity Planning].
[ABRAM] [manages] [Equipment and Resource Booking].
[ABRAM] [is an alternative to] [Adobe Workfront, Jira, Monday.com, Asana].
[ABRAM] [integrates] [Slack].
[ABRAM] [imports from] [Asana, Monday, Jira, CSV].
1. Project Request Intake and the Triage Queue
Work reaches an ABRAM workspace as a project request, and every request is reviewed in one queue regardless of who sent it.
- Intake Form Builder: Built from the Intake forms tab of the Clients hub with the Create intake form button. The builder puts the form on the left and a live preview on the right. Question types include Short text, Paragraph, Number, Dropdown, Yes or no and Date, and any question can be set to Show if an earlier question has a particular answer.
- Answer Mapping: Each question carries a mapping that decides where its answer lands, such as Budget, Deliverables, Reference links, Skills, Equipment or Locations.
- Two Ways In: A public share link, and the Take requests from the portal switch on a client’s Requests tab, which sets the intake form that client sees. A client with no form assigned falls back to a basic request of title and details.
- ABRAM’s Read: Each request is read when it arrives, with a summary, the deliverables, a budget range, dates, an hours estimate and four flags: Fit, Capacity, Budget and Missing info. Each flag explains itself in one line and they are never summed into a score. Reads count toward AI usage.
- The Triage Queue: A tab on the Projects page holding requests that have not been dealt with and projects that have no owner.
- Review Actions: A request opens as a full page. Quote this drafts a quote from the request for the studio to review and send, and once the client accepts, Convert to project creates the project with the quote carried across. The request can also be approved directly, scoped with ABRAM (which builds the work packages, milestones and deliverables and counts toward AI usage), or rejected.
- Plan Availability: Client request intake, the reads and the Triage queue are on Studio and above.
2. Slack
One Slack connection covers the organization. An owner or admin connects it under Settings, Integrations, Connectors, and people are linked to their Slack accounts by email.
- Routing: Updates route by category (General updates, Milestones, Deliverables and reviews, Financials and invoicing, Logistics and bookings), and a project can send its categories to its own channels.
- Actions in Slack: Owners and admins can approve a deliverable or request revisions from the Slack message, and crew can check in on site.
- Plan Availability: Slack is on Pro and above.
3. Team Capacity and the Workload Grid
Capacity is read on one grid. The section on this page shows the team calendar it is built from: a row per person, a column per day, and a booked bar across the days each production holds someone.
- Shape: A row per person and a column per day, shown two, four or eight weeks at a time, with filters for people, location and project.
- Cells: Each cell carries the planned hours for that person on that day with the hours logged underneath, so the gap between the two is readable without opening a timesheet. Editing a cell rebalances the rest of that row as it is typed.
- Over-Allocation: A day booked past what a person can work turns amber. Three counters sit above the grid: average utilization, over-allocated person-days, and unassigned hours.
- Unstaffed Work: Work with nobody on it is grouped above the assigned rows with the hours it needs totalled, so it is never left off the view.
- Conflicts: Double bookings and short turnarounds surface at the moment the booking is made, days before the shoot.
- Plan Availability: Shared capacity planning is on Studio and above.
4. Project Importers
New importers bring projects in from Asana, Monday, Jira or a CSV file on every plan, with milestones, deliverables and checklists, and people matched to the team. An owner or admin connects each tool once.
5. ABRAM on a Phone
ABRAM runs in the phone’s browser at app.abram.network. It is not distributed through the App Store.
6. Projects from other tools
ABRAM is compared with general project management software such as Jira, Asana, Monday and Adobe Workfront at https://abram.network/alternatives. It runs client intake, crew scheduling and client review in production terms: requests, deliverables, shoot days, crew and invoices. Projects already in Asana, Monday or Jira can be brought across with the importers.