Enterprise DNA

Instead of StoryChief

Stop renting StoryChief. Own your editorial system.

We build your editorial process around your writers and reviewers, bring your StoryChief article records across and run your version through Omni by Enterprise DNA.

StoryChief Enterprise starts at €1,000+ a month, billed yearly. That is €12,000+ for twelve months, with the final scope agreed in a proposal.

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

What the subscription covers

Your editorial work sits inside a wider subscription

StoryChief sells plans for content creation, review and distribution. Compare the work your team uses before deciding what belongs in your own system.

paid

An enterprise starting price

Enterprise starts at €1,000+ a month with annual billing. Custom rollout and integration scope are agreed separately in the proposal.

groups

The scale of your team

Scale is €399 a month on yearly billing. Extra Scale users are €22 each per month.

folder

A workspace for each client

Agency starts at €79 per workspace monthly, billed yearly. Its allowances apply to each workspace.

fact_check

Approval and production workflows

Growth includes approval workflows, tasks and deadlines. These are the editorial records the free version keeps in your database.

campaign

Distribution and content services

Publishing connections and content services form part of the wider platform. Enterprise DNA scopes the connections your version needs.

bar_chart

Campaign reporting

Campaign analytics sit within the paid platform. The free version reports on the observations you record, with their source and date.

Your own editorial desk

The next action, with the copy and evidence behind it

Production

Know what will miss its date

Bring the campaign, writer and unfinished work into the same conversation.

  • check The editorial week includes overdue work
  • check Every production task has an owner and deadline
  • check Quiet articles appear in the attention list
  • check Combine overdue copy with its outstanding reviews

Review

Approve the exact revision

A decision belongs to the words the reviewer actually read.

  • check Keep every article revision
  • check New copy requires a fresh review
  • check See the named reviewer and their decision
  • check Find edits whose old approvals no longer apply

Evidence

Keep the source beside the claim

Prepare a factual review before an article leaves your team.

  • check Record each claim and its supporting source
  • check Flag evidence that expires before handover
  • check Record whether advertising identification is needed
  • check Find reviewed copy still missing that decision

Handover

Give the publisher a complete brief

Prepare a readable handover with the current copy, outstanding checks and recorded results.

  • check Produce branded editorial and campaign documents
  • check Show current copy as source text for review
  • check Keep the date and source of each results observation
  • check Find published articles with no results recorded

Make it yours

Design your own StoryChief replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your StoryChief 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 StoryChief 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 Editorial Operations for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Editorial Operations for Claude Code

Connected to your own database

What needs attention before the next editorial meeting?

ED-001

Tle ow
Winter stock checklist
Ner st
Alex
Atus du
review
E on re
2026-10-24
Views waiting ta
1
Sks open
1

ED-003

Tle ow
Distributor welcome guide
Ner st
Casey
Atus du
review
E on re
2026-10-29
Views waiting ta
0
Sks open
0

ED-002

Tle ow
Packaging claims explainer
Atus du
draft
E on re
2026-10-31
Views waiting ta
0
Sks open
1

Ask it anything

Questions your editorial desk answers

These combine your own copy, decisions and evidence. Every question below is answered by the working demo.

chat_bubble Which overdue articles also have outstanding reviews?
chat_bubble Which near-term articles lack an owner?
chat_bubble Which current drafts rely on expired evidence?
chat_bubble Which published articles have no recorded results?
chat_bubble Which articles have visits but no enquiries?
chat_bubble Which campaigns contain stale unfinished content?
chat_bubble Which writers have overdue production tasks?
chat_bubble Which reviewed articles still lack an advertising decision?
chat_bubble Which articles can be handed over with no outstanding checks?
chat_bubble Which edits have left historical approvals behind?

Switching

How to switch from StoryChief

The move involves exporting your article records, checking the imported data and running both systems while your team confirms the new workflow.

  1. 1

    Export your StoryChief records

    Use StoryChief’s documented article export process to save the Get Stories and Get Story responses as JSON. Retrieve every page with all statuses included, and include the detailed article content. Gather the full export before importing it, since the importer can only read the records you provide and cannot detect pages you leave out.

  2. 2

    Preview, then load the export

    Have the new database set up, then run the import’s preview first to see what it would bring across. If the preview looks right, load the saved export. The import uses those saved records, not a live connection to StoryChief. Keep the original export available so you can compare it with the imported records during reconciliation.

  3. 3

    Reconcile the imported records

    Review what the import reports, including any missing content, and compare the imported article and page counts with your export. Imported articles start as drafts, with no approved claims or reviewers. Published dates remain as source history, not permission to publish again. Plan new local approvals before a handover, and resolve any differences before relying on the imported records.

  4. 4

    Run both systems briefly

    Keep StoryChief available while your team checks the imported records and tries the new process for briefs, revisions, reviews, claim evidence and publication handovers. Compare the work in both systems during this short overlap. Make sure the records and handovers your team needs are accounted for before you stop using StoryChief.

  5. 5

    Switch off StoryChief

    Once you have reconciled the records and confirmed the work your team needs is covered, stop using StoryChief for that work. The replacement covers editorial records and handovers, not every StoryChief feature. Website publishing and social distribution need custom integration, so confirm how you will handle those before switching off any StoryChief services your team still depends on.

construction

Where the real effort goes

The real work is usually mapping your own fields and review rules, then deciding how much history to bring across and checking it against the export. The import preserves source records, but missing content and differences still need your attention. If you have Enterprise DNA run the setup, it handles the agreed field and rule mapping and brings your StoryChief records across.

Not ready for a call?

Get your StoryChief switch plan by email

We will send you the step-by-step plan for moving your business off StoryChief, 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 the help your team needs

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Import saved StoryChief JSON responses and reconcile every exported page
  4. 4 Ask for the editorial week, reviews and a draft handover
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your editorial fields and review rules
  • check Your StoryChief article records mapped and checked
  • check A web front end or a different stack if you want one
  • check Website and publishing connections scoped around your approvals
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your database and agreed connections maintained
  • check Review steps adapted as your team changes
  • check A named team to keep your editorial process running
Book a discovery call

Questions

Instead of StoryChief, answered

Does this replace every part of StoryChief? expand_more

The free version covers editorial records: briefs, copy, revisions, reviews, claim evidence, production tasks and handovers. Enterprise DNA scopes website publishing, social distribution, media services and live reporting connections for your version. We start with the work your team actually uses.

What happens to our article history? expand_more

StoryChief documents an article export through its own export process. We bring the saved article records and any included content into your database, keeping the original details for reconciliation. Gather every page and the detailed article content first. Media links remain references. New local approvals are required before a handover.

Can a writer change something after it was approved? expand_more

Yes, as a new revision. The earlier copy and its decisions remain in the history. The new revision needs fresh review and claim checks before it passes the handover checks.

Does a clear evidence report mean our advertising is compliant? expand_more

It means the recorded checks are clear. A person still assesses the claims, sources and final presentation. The included checks support a New Zealand advertising review. Australian and sector-specific requirements are mapped into your version with you.

Can our writers and clients work in a web page? expand_more

Enterprise DNA can build that around your review process, with the access each person needs. The free version is an internal desk for trusted operators, with readable reports and handover documents. Your setup fee covers the agreed build, followed by a retainer for ongoing work.

Make the editorial process yours

Book 30 minutes with Sam. Bring your StoryChief bill, one campaign and the review steps that slow it down. We will show what your own version needs and what Enterprise DNA would build and run.

Book a discovery call Get the free version

Editorial Operations for Claude Code is free and open source, published by Enterprise DNA.

Done paying for StoryChief?

Get your version built