Operational agents for casting
Move the preparation forward. Keep the casting judgment human.
A casting brief can trigger research across old lists, open sources, inboxes, and project records before a director can shape the field. Aran connects that preparation while keeping selection, permission, and client trust with the people responsible.
One workflow first · existing tools · documented permissions and checkpoints
- Starting point
- A real recurring brief
- System role
- Prepare the field
- Director role
- Shape the recommendation
The operating loop
The same preparation returns with every new brief.
The useful automation target is not casting taste. It is the repeatable work that has to happen before and around that taste.
Ownership model
The boundary follows consequence, not technical difficulty.
Research preparation can be technically complex and still belong with the system. A simple approval can be consequential and still belong with a person.
Aran can carry
- Brief requirement extraction from an approved input.
- Existing-database search before gap research.
- Source-linked enrichment, tagging, and deduplication.
- Shortlist preparation and outreach drafting for review.
- Project record organisation around the agreed workflow.
People continue to own
- The reading of culture, context, character, and client intent.
- Exceptions that cannot be reduced to a standing rule.
- Who belongs on a shortlist and who should be contacted.
- Consent, relationship management, and outreach approval.
- The recommendation and every final casting decision.
A casting pilot
Start with the point where preparation becomes a bottleneck.
A pilot maps one operating loop with the people who run it. The first deployment is shaped around the current tools, the records already in use, and the approvals the practice needs to keep visible.
A useful first scope has a real input, a reviewable output, a named owner, and an observable success signal.
Good first scope
- One recurring research or records workflow.
- A defined brief, source policy, and output shape.
- Named checkpoints for selection and outreach.
- A team member available to map exceptions and review output.
Not the pilot
- An automated replacement for a casting director.
- Unbounded collection from any available source.
- Automatic outreach without review or permission.
- A platform migration before the workflow is understood.
Proof and next steps