Enterprise DNA

Instead of Dramatify

Stop renting your production office. Build your Dramatify alternative.

We build your version around your shoot days, cast, crew and approvals. We map the Dramatify records you need, check them with your production manager and run the system for you.

Dramatify Professional lists US$36 per paid editor per month, or US$27 with annual billing. Read-only cast and crew are included free.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Read the invoice first

Count the editors, then the work you use

Dramatify combines production records with creative and broadcast features. Compare your actual plan with the production-office work you want to own.

paid

Professional editor seats

Professional costs US$36 per paid editor per month on monthly billing, with a minimum of five paid seats.

event_repeat

An annual billing choice

Professional lists US$27 per paid editor per month with annual billing. Compare the commitment as well as the monthly figure.

groups

Viewers are already included

Read-only cast and crew access is free. Count people who need editing access when reviewing your bill.

movie

Different production packages

Fiction Standard starts at US$13 per paid editor per month with annual billing and a five-seat minimum.

calendar_month

Scheduling and production records

The office still needs its scene order, calls and working-hours history when a production finishes.

inventory_2

A move needs more than one export

Dramatify documents daily hours exports. Bringing schedules, breakdowns and other project records across needs separate mapping and checking.

The office you own

Start with the records behind the next shoot

Shoot planning

See what is ready before the unit moves

Keep each scene attached to its production, location and shoot day. Ask about the unresolved work before drafting the calls.

  • check Scenes in page eighths, with the planned duration
  • check Unshot scenes whose shoot date has passed
  • check Scenes that still have no date
  • check Day-specific permission and safety-record checks

Cast and crew

Find the booking that breaks tomorrow

Review the whole office schedule together, including people booked on more than one production.

  • check Confirmed and tentative calls side by side
  • check Cast without cover for the full shoot day
  • check Overlapping crew calls, including overnight bookings
  • check Two units using the same location at the same time

Wrap and review

Keep the recorded day and the planned day together

Review what was shot and what still needs a correction. Missing hours stay visible until someone supplies the source.

  • check Completed scenes and page eighths by production
  • check Missing wrap times and absent working-hours records
  • check Long days against your agreed office policy
  • check Short recorded rest intervals across productions

Your paperwork

Draft the day from the same records

Create the paperwork with your business name and keep the open decisions on it. Your production manager reviews each draft.

  • check Call sheets with scenes, calls and outstanding checks
  • check Daily production reports with scene progress
  • check Risk registers with controls, owners and review dates
  • check A weekly review from the coming shoots and unresolved work

Make it yours

Design your own Dramatify replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Dramatify. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Dramatify replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Dramatify data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Screen Production for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Screen Production for Claude Code

Connected to your own database

What are we shooting in the next seven days?

D-102

Oduction sh
P-101
Oot date un
2026-11-12
It lo
Main
Cation sc
Wharf Warehouse
Enes pl
1
Anned minutes co
180
Nfirmed people
1

D-103

Oduction sh
P-102
Oot date un
2026-11-12
It lo
Main
Cation sc
Studio Two
Enes pl
1
Anned minutes co
60
Nfirmed people
1

Ask it anything

Ten questions to ask your production records

Each question below has a working answer in the demo. Your own policies and records make the answers yours.

chat_bubble Which scenes have cast without confirmed cover for the whole day?
chat_bubble Who is double-booked across our productions, including overnight work?
chat_bubble Which locations have overlapping unit bookings?
chat_bubble Which shoot days are missing safety contacts or daily briefing records?
chat_bubble Which permissions expire before the planned shoot?
chat_bubble Which risk controls are still open or due for review?
chat_bubble Which scenes missed their shoot date and which have no date?
chat_bubble How many page eighths have we shot on each production?
chat_bubble Which daily hours are missing a wrap or exceed our own long-day policy?
chat_bubble Who has less than our agreed rest interval between recorded shifts?

Switching

How to switch from Dramatify

A move usually means exporting daily working hours, mapping the records you want to keep, and checking them against Dramatify before your team changes over.

  1. 1

    Export the records you need

    Start by exporting the daily working hours you want to bring across, since that is the supported Dramatify import path. Gather the other production records you need, such as productions, scenes, schedules, cast, crew, budgets and attachments. The material does not specify a full Dramatify export process, so export what your account allows, usually CSV or Excel, and check with Dramatify about available exports.

  2. 2

    Map and test the hours

    Match the exported headings to the working-hours fields and match each person to the roster in the new database. Start with a test run, which checks the file without applying it. The built-in import covers daily working hours only. Other records, including schedules and breakdowns, need their own mapping before you load or recreate them.

  3. 3

    Review the import checks

    Read the test results before applying the hours. Review each flagged problem against your source records and correct it before testing again. The import checks the whole file before changing anything, so a problem prevents a partial load. After applying it, repeated imports update the same person, production and date rather than creating duplicates.

  4. 4

    Run both systems briefly

    Keep Dramatify available while your team uses the new database for a short period. Compare the imported working hours and the records you mapped, then check the reports and draft paperwork your production office relies on. Ask the team to confirm that the records are usable and that the important workflows are covered. Keep Dramatify as the source until your team accepts the result.

  5. 5

    Switch off Dramatify

    Once your team accepts the new records and workflows, make the new database the place your production office works from. Confirm that you have kept any Dramatify records your team still needs, including history you chose not to import. Then stop relying on Dramatify for the production office work you have moved. If a workflow is still missing, resolve it before switching off.

construction

Where the real effort goes

The import itself is the smaller part. Most effort goes into matching your own fields and production rules, deciding which history to bring, and mapping records the working-hours import does not cover. The more schedules, breakdowns, budgets and attachments you want to carry over, the more review that takes. Enterprise DNA handles this mapping and review when you have them run the switch.

Not ready for a call?

Get your Dramatify switch plan by email

We will send you the step-by-step plan for moving your business off Dramatify, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose how much you want us to handle

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and ask for /attention
  3. 3 Match your roster, map a daily Dramatify hours export and run a test import
  4. 4 Render your call sheets and views, then adapt the remaining production records
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your scene fields, unit structure and agreed office policies
  • check Your Dramatify exports mapped and reconciled against the originals
  • check A team screen or mobile access built around your actual workflow
  • check A different technical foundation if your production needs it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Access, backups and day-to-day operation set up for your office
  • check The connections your production manager needs
  • check Changes and report maintenance as productions change
  • check Run through Omni by Enterprise DNA alongside the rest of your business
Talk to Sam

Questions

Instead of Dramatify, answered

Will this replace everything we use in Dramatify? expand_more

The free version covers production-office records: scenes, shoot days, cast, crew, hours and draft paperwork. If you need script editing, live broadcast timing, media handling or a crew portal, we scope those parts of your custom version before you switch. Bring the workflows your team uses to the call.

Can we bring our existing production history across? expand_more

The built-in import handles a daily working-hours export after your roster and the export headings have been matched. It checks the whole file before applying it and repeat imports update the same records. Schedules, breakdowns, budgets and attachments need separate mapping. We include that work in the switch plan and check the counts with you.

Does it send call sheets or approve a shoot? expand_more

It creates drafts and shows missing safety contacts, permissions and review records. Your production manager and safety adviser make the decisions. Nothing sends from the free version. We can build your chosen approval and distribution process into your version.

Does every crew member need a paid account? expand_more

The free software has no per-person licence charge. It starts with a trusted production office operating the records. Your agent subscription, hosting and support are separate costs. Individual crew access and permissions are part of a custom setup. Dramatify already includes free read-only cast and crew, so compare paid editors fairly.

How do we know the move is worth doing? expand_more

Bring your invoice, editor count and the reports the office relies on. We compare those with your import and customisation needs before recommending a switch. Start with a copied production, check the records and paperwork, and keep the source until your team accepts the result.

Bring the production-office bill to Sam

Spend 30 minutes with Sam. Bring your Dramatify invoice, a daily hours export and the call sheet your manager actually uses. We will work through the records to keep, the parts to build and what it takes to run your version.

Book a 30-minute call Get the free version

Screen Production for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Dramatify?

Get your version built