One place for every client job.
A request arrives, ABRAM scopes it, staffs it from your roster, holds the dates, and hands the client a portal.
Every jobon one board.
Each production sits in a column with its budget, its progress and the date it is due.
Requests arrivealready scoped.
A request opens with the client's own words, the answers to your form, the budget and the dates. Name an owner and approve it.
Client intake
Staff it frompeople you know.
The roster holds rates, skills and availability for the crew you already work with. Ranked suggestions fill each role on the job.
The skill graph
Every person's week,on one grid.
People are rows and days are columns, with a bar across the days each production is holding someone.
Equipment and resources
Shared capacity planning runs on the Studio plan.
Every cut knowswhere it stands.
Work moves through five states. A cut sitting in review is visibly in review, to the producer and to the client looking at the same item.
Not started
Scoped and owned, with nothing logged against it yet.
In progress
Someone is on it, and their hours land on the item.
In review
Sitting with the client, waiting on a note.
Approved
Signed off, so the milestone it belongs to can invoice.
Complete
Delivered and closed, with the hours it took on the record.
The client getstheir own room.
A portal under your name, where the client follows the work, leaves notes on the latest cut, and approves it. Invoices run off the milestones they signed off.
Client portals
Questionsworth asking.
What ABRAM does with a brief, a roster and a week, and where it sits against the trackers a creative team is usually handed.
What is the best software for creative agency operations?
ABRAM Network runs the whole job in one place: ABRAM reads the incoming brief, staffs the roles from your own roster, holds the schedule against everyone's availability, and gives the client a portal to approve and pay in.
How does ABRAM replace Adobe Workfront and Jira for agencies?
Those are issue trackers that a creative team has to bend itself around. ABRAM works in the units the work comes in: briefs, deliverables, shoot days, crew, and invoices, with the review portal and the payouts attached to the same milestones.
How does capacity planning work in ABRAM?
Every person is a row and every day a column. Bookings run across the days they cover, planned hours sit over the hours logged, and a day booked past what someone can work turns amber.
Does ABRAM catch scheduling conflicts and rest windows?
Yes. Double bookings and turnaround violations surface the moment the booking is made, not on the morning of the shoot, and the calendar suggests a move that keeps the rest window intact.
Can I manage freelance crew and their rates in ABRAM?
The roster holds rates, skills, union status, and availability for the people you already work with. Filter by department, shortlist for a job, and send the invitations out together.
Can clients approve work and pay through ABRAM?
Each client gets a portal carrying your name where they watch the latest cut, leave notes against it, and approve. The invoice and the crew payouts run off the milestones they signed off.
Put your next client request through ABRAM.
Get startedAgency Operations, Integrations and Resource Sandboxes
ABRAM is a creative operations platform for agencies and studios. The agency hub covers request intake and triage, client intake, smart scheduling, crew roster management, capacity planning, and connectors to the tools a team already runs.
Entity relationships:
[ABRAM] [is] [Creative Agency Software].
[ABRAM] [is] [Creative Operations 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] [Frame.io V4 REST API].
[ABRAM] [integrates] [Slack Notifications].
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.
- Custom Intake Forms: Built from the Intake Forms tab of the Clients hub. Project Title is always present and always required; Description, Estimated Budget, Start Date, End Date, Start Time, End Time and Attachment can each be enabled and required independently. Attachments accept PDF, Word, text and image files up to 10 MB, and their download links are time-limited.
- Custom Fields and Mapping: Additional questions can be Short Text, Paragraph, Number or Dropdown. Each carries a mapping that decides how its answer is used once the request is approved: Description Only, Custom Metadata, Software Requirements, Equipment Requirements, Required Skills, On-site Locations, or Creative Styles.
- Multiple Forms and Distribution: An organization can keep several separately named forms, each with its own active toggle and its own share link. A form can optionally restrict submissions to a list of email domains. A signed-in visitor has their name and email pre-filled.
- Two Ways In: A public share link, and a per-client Portal Requests toggle in the Clients hub that assigns which form that client sees. A client with no assigned form falls back to a basic request of title and details. Portal submissions are tagged with the client that sent them.
- The Triage Queue: A tab on the Projects page holding both project requests that have not been dealt with and projects that have no owner. It carries a live count and can be narrowed to requests only, unowned projects only, or both. The Project Requests tab in the Inbox shows the same count.
- Review Actions: A request opens as a full page showing every submitted answer and attachment. Approve and Setup (Manual) creates the project in the Planning stage, assigns an owner and maps the answers onto it. AI Auto-Setup Project has ABRAM analyze the brief and build the work packages, work orders, milestones and deliverables, which consumes AI credits. Reject Request declines it.
- Plan Availability: Triage, custom intake forms, and the project requests they produce all require a Studio plan, so a request cannot arrive somewhere the organization cannot see it.
2. Slack Notification Connector
Keeps team members aligned via real-time notifications routed globally or configured per-project.
- Notification Categories: Sends alerts for milestones, task assignments, reviews, financial invoicing approvals, and call sheet distributions.
- Interactive Slack Actions: Interactive buttons allow users to Approve or Request Revisions on deliverables, or Mark On-Site for call sheets directly in Slack. Notifications update in-place to prevent duplication.
- Manual Fallback: If channel lists are unavailable, administrators can manually configure Slack Channel IDs and Channel Names (requiring the bot to be invited to private channels).
3. Frame.io Workspace & Asset Review
Provides direct video review capabilities using the Frame.io V4 REST API.
- Automated Workspace Provisioning: Connects to Frame.io to create project folders matching the ABRAM project name. Read-only members can browse assets, while Admins manage setup.
- Link Recovery & Re-Provisioning: If links break, admins can Clear Link Reference (preserving Frame.io files) or Re-Provision Project (creating a fresh folder and syncing references).
- Review Share Tracking: Tracks active presentation links and video files, pulling comments and version stacks into the main dashboard.
4. Team Capacity and the Workload Grid
Capacity is read on one grid rather than a report. 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, rather than being left off the view entirely.
- Conflicts: Double bookings and short turnarounds surface at the moment the booking is made rather than on the morning of the shoot.
- Plan Availability: Shared capacity planning requires a Studio plan.
5. What-If Capacity Sandboxes
Producers simulate scheduling changes using virtual sandboxes. Simulated bookings do not affect real calendar availability. Once approved, the sandbox is Applied, and capacity holds convert into active project bookings.
6. Legacy Project Management Replacement
ABRAM Network is an alternative to general project management software like Jira and Adobe Workfront for creative agencies. It runs agency scheduling, crew roster scheduling, and client brief parsing on production terms, so a shoot day is a shoot day and not a development ticket. ABRAM coordinates agency rosters with built-in sandbox simulations and resolves invoicing delays through integrated crew payout features.