Enterprise DNA

Instead of Parse.ly

Stop renting Parse.ly reports. Own your editorial review system.

We build your version around your publications, bring your Parse.ly exports across and connect the continuing measurement your team needs. Your story history and editorial follow-up stay in a database you own.

Parse.ly’s WordPress demo page lists plans from $3,000 a month, or $36,000 over twelve months. The page does not specify the dollar currency. Its main pricing page asks you to discuss your requirements.

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

The subscription behind the review

Compare the reporting you use with the platform you pay for

Parse.ly packages measurement, reporting and audience analysis into plans. Review which parts your publication needs before deciding what to replace.

paid

A published monthly starting price

The WordPress demo advertises $3,000 a month. Twelve months at that rate is $36,000. Confirm the currency and your own quote with Parse.ly.

analytics

The Content Performance plan

The pricing page includes audience metrics, real-time analytics and campaign tracking in its entry plan.

history

A defined historical window

Content Performance lists thirteen months of historical data. Your exported periods can also become a record you retain yourself.

conversion_path

Conversion analysis in Content Value

The next plan adds conversion reporting, attribution and audience segmentation. Decide whether those services are part of your replacement scope.

public

Site allowances differ by plan

The published plan comparison lists one, two and three tracked sites across its three tiers.

manage_accounts

Further capabilities in Content Advocacy

Geographic segmentation, video tracking and single sign-on appear in the higher plan. Your own version starts with the editorial work you actually need.

Your editorial desk

Connect the numbers to the work they create

Morning review

Read the story results with their context

Bring aggregate story results into an owned record and keep the reporting period visible.

  • check Views and recorded reading minutes beside each story
  • check Author credits and sections kept with each period
  • check Partial exports labelled as partial throughout
  • check Open editorial actions beside the latest story results

Evergreen work

Give declining stories an editorial owner

Compare like periods, then decide which older stories deserve attention.

  • check Declines only between comparable adjacent periods
  • check Missing stories kept separate from zero traffic
  • check Older stories with meaningful current readership
  • check Refresh work with a named editor and agreed date

Weekly meeting

Bring a finished review to the desk

Produce branded review papers from the same records the team uses.

  • check An editorial brief for each story
  • check A publication action register with completion evidence
  • check Section and byline summaries for the current period
  • check A weekly review joining performance, due work and record checks

Ownership

Keep the evidence behind each decision

Retain the imported record and the follow-up it prompted in one place.

  • check Original export files and their reporting settings
  • check Notes and a history of recorded changes
  • check Prompts for retention and access reviews
  • check Your editorial rules and paperwork adapted as the business changes

Make it yours

Design your own Parse.ly replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Content Performance for Claude Code

Connected to your own database

Which older stories lost views and already have follow-up?

DEMO

Title
Coastal freight guide
Previous_views
2400
Views
1200
Change_pct
-50.00
Open_actions
1
Previous_start
2026-10-29
Start_on
2026-11-05
End_on
2026-11-11
Coverage
partial

Ask it anything

Questions for your editorial review

These questions join imported story results to your own editorial actions and review records. Each is answered by the working demo.

chat_bubble Which declining story already has an editor assigned?
chat_bubble Which older stories still earn views but have no refresh action?
chat_bubble Which evergreen stories fell by at least twenty percent?
chat_bubble Which high-view story has little recorded reading time per view?
chat_bubble Which section has the most open work beside its current views?
chat_bubble Which byline groups have the most views and outstanding actions?
chat_bubble Which editor owns overdue follow-up?
chat_bubble What evidence closed a refresh task?
chat_bubble Which publication lacks a current export or a comparable prior week?
chat_bubble Which source file and reporting period supplied these story results?

Switching

How to switch from Parse.ly

The move involves exporting your story results, mapping and checking the records, then running both systems side by side before you switch off Parse.ly.

  1. 1

    Export your story results

    Export your history from Parse.ly’s Posts view and Top Performers reports, covering the reporting periods you want to keep. Include the aggregate story results you use for editorial review. Parse.ly documents CSV exports for Top Performers. Check with Parse.ly if you are unsure which formats or records your account allows, and note any limited coverage so it is not mistaken for a complete history.

  2. 2

    Load a test export

    Start with a test run of one export. The import can check the records without writing them to the database. You will need to supply the dates, timezone, audience scope and coverage for the reporting period. Use the test to confirm that the export’s columns can be mapped to the story fields before loading your history.

  3. 3

    Review and reconcile the results

    Check what the import flags before loading the rest. A malformed row stops the batch, and the import reports the row count so you can compare it with your export. Confirm that the dates and reporting settings match the source, and label limited exports as partial. Missing stories are not treated as zero views, so check coverage before comparing periods.

  4. 4

    Run both systems side by side

    Keep Parse.ly running while you bring in the periods you need and review results in the new database. Compare the loaded counts with your exports and check that the same reporting windows, timezone, scope and coverage are being used. The free version works from imported aggregate results, so keep your current measurement source until any replacement feed your publication needs has been connected and checked.

  5. 5

    Switch off Parse.ly

    Turn off Parse.ly only after you have checked the imported history and confirmed that your ongoing measurement needs are covered. The free version does not install a website tracker or provide live measurement. If you need continuing reporting, have Enterprise DNA connect and check the replacement feed as part of your version before you stop relying on Parse.ly.

construction

Where the real effort goes

The import itself is only part of the work. Most effort usually goes into mapping your story fields, agreeing on reporting dates, timezone, scope and coverage, and deciding how much history to bring across. Saved experiments, permissions and attribution settings need separate migration work. If you have Enterprise DNA install and run your version, they handle the mapping and setup as part of the agreed scope.

Not ready for a call?

Get your Parse.ly switch plan by email

We will send you the step-by-step plan for moving your business off Parse.ly, 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

Run it yourself, customise it, or have us run it

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm test
  2. 2 Run npm run demo with Claude Code, Codex, OpenCode or Cursor
  3. 3 Export Parse.ly posts as CSV, map your columns and test the import
  4. 4 Arrange a continuing measurement source and keep the records backed up
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your publications, editorial fields and review rules
  • check Your Parse.ly exports mapped and checked against the source
  • check A continuing measurement connection designed for your publication
  • check Your own web view or a different underlying system if required
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with controlled access and tested backups
  • check Regular imports and editorial review papers prepared
  • check Connections and reports kept working as the publication changes
  • check Operated through Omni by Enterprise DNA
Book a 30-minute call

Questions

Instead of Parse.ly, answered

Does the free version keep measuring our website? expand_more

It works from imported aggregate results. Continuing measurement is a separate part of the switch. Keep your current source until Enterprise DNA has connected and checked the replacement feed your publication needs. We scope live reporting and other required capabilities into your version.

Can we bring our Parse.ly history across? expand_more

Yes. Parse.ly documents exports from its Posts view and Top Performers reports. We map the story fields, record the dates and reporting settings, and compare the loaded counts with your export. A limited export is labelled as partial. Saved experiments, permissions and attribution settings need separate migration work.

Are these figures directly comparable with Parse.ly? expand_more

Imported views and reading minutes preserve the supplied values. The free version also calculates reading seconds per view, which differs from an average per visitor. It never adds unique visitors across stories, and it only compares adjacent periods with matching duration, audience scope and timezone.

What does it cost to have our version built and run? expand_more

Enterprise DNA agrees one setup fee, then a retainer for the work you need. We review your publications, reporting sources and editorial process before setting the scope. The free version is available if you want to operate it yourself.

What happens to our records if we change providers? expand_more

Your database, source exports, editorial notes and action history stay under your control. You can export the full record. We set up access and backups around your publication, and the record checks flag overdue reviews without pretending to certify legal compliance.

Bring the bill and one editorial review

Spend 30 minutes with Sam looking at your Parse.ly bill, the reports your editors use and the work those reports create. We will map the version your publication needs and the measurement that must continue behind it.

Book a 30-minute call Get the free version

Content Performance for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Parse.ly?

Get your version built