Enterprise DNA

Instead of LaunchNotes

Stop renting LaunchNotes. Own your release communications.

We build your version around how your team prepares and reviews a release. We map the agreed LaunchNotes records, connect the delivery tools you need and run the system for you.

LaunchNotes Growth: US$999 a month on monthly billing, or US$11,988 over a year. Annual billing is US$799 a month, equivalent to US$9,588 a year.

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 recurring bill

One release process. A subscription around it.

Growth includes one page and two users. Premium is quoted for a broader setup. Compare the work you need with the package you keep renewing.

banknotes

A monthly or annual commitment

Growth is US$999 on monthly billing or US$799 a month billed annually.

users

The core publishing team

Two users are included in Growth. A custom user count sits in Premium.

document-text

The product update page

Growth includes one LaunchNotes page. Premium supports multiple pages.

chat-bubble-left-right

The communication bundle

Announcements, roadmaps, feedback and an in-app widget come together in Growth.

adjustments-horizontal

More audience options

Advanced segmentation and full white-labeling sit in Premium.

shield-check

The enterprise arrangement

Premium adds SAML, dedicated account support and a custom service agreement. Agree the scope before comparing costs.

The owned version

Make the weekly release review work the way you do

Readiness

A decision tied to the current wording

See which release is prepared and which still has work attached.

  • check Name an owner and a review date
  • check Keep the announcement summary with the release
  • check List unfinished handover tasks
  • check Require a fresh approval when the wording or tasks change

Audience

Know why each address is included

Review preferences and evidence before any external delivery.

  • check Keep selected categories with each subscriber
  • check Record the source and date of consent evidence
  • check Keep blocked and unsubscribed addresses suppressed
  • check Explain missing evidence and category mismatches for a chosen release

Paperwork

The handover brief comes from the records

Prepare the working documents for the people who check the release.

  • check Draft the announcement in your business colours
  • check Produce a release brief with tasks and approval history
  • check Create an audience review for each product
  • check See overdue work in a read-only weekly report

Ownership

Keep a record you can inspect

Change the process without waiting for a vendor plan to fit.

  • check Keep the original imported subscriber fields
  • check Export your complete project record
  • check See the actor and values behind a recorded change
  • check Add your own fields, review rules and reports

Make it yours

Design your own LaunchNotes replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Release Communications for Claude Code

Connected to your own database

Which releases are ready for review?

R01

Revision
3
Open tasks
2
Current approval
false
Review ready
false

R03

Revision
1
Open tasks
0
Current approval
true
Review ready
true

R02

Revision
1
Open tasks
0
Current approval
false
Review ready
false

Ask it anything

Ten questions your release review can answer

Each question has a working answer in the demo. These are examples of the owned workflow, not claims that LaunchNotes lacks the same features.

chat_bubble Which release has overdue handover work?
chat_bubble Which release has complete tasks and a current approval?
chat_bubble Which approval became stale after the wording changed?
chat_bubble Who owns each unfinished readiness task?
chat_bubble Which confirmed subscribers lack recorded consent evidence?
chat_bubble Why is this address excluded from the announcement?
chat_bubble Which categories did each subscriber select?
chat_bubble Which access and retention reviews need attention?
chat_bubble Who changed the release and what changed?
chat_bubble What needs review before Monday’s announcement?

Switching

How to switch from LaunchNotes

The move involves exporting your subscriber list, mapping its fields, deciding which other history to bring, then checking the import before you make the new database your working record.

  1. 1

    Export your subscriber list

    Export the subscriber list from LaunchNotes using the documented subscriber export. The importer accepts a CSV or the documented saved exportSubscribers JSON response. Export the fields you want to carry over, including email, region, status, selected categories, source ID and confirmation date where available. CSV headers can vary, so check with LaunchNotes if your account's export differs.

  2. 2

    Load the records

    Create a project for your product, then have the subscriber export imported into it. Start with a test run that does not save changes. If your CSV uses different field headings, map them before saving the import. Back up the database first, since imported preferences replace recorded category links. The importer keeps the original source fields for review.

  3. 3

    Review the import results

    Check the test run before importing for real. Review any field mapping or record issues, and pay particular attention to subscribers with no selected categories, which are held for review rather than treated as eligible for every category. Confirmation dates remain source facts, not consent evidence. Suppressed addresses stay suppressed, and invalid records roll back the whole file.

  4. 4

    Run both systems briefly

    Keep LaunchNotes available while you check the imported records and try the release review work your team needs. The free base prepares internal drafts and reviews, but does not send announcements or publish a public changelog. If you need those parts, keep the current service until the agreed delivery connections or public pages work for your team.

  5. 5

    Switch off LaunchNotes

    Once your team has checked the records and confirmed that the replacement covers the work you agreed to move, stop using LaunchNotes as your working system. Arrange the account closure or subscription change with LaunchNotes. Keep any exports and database backups you need under your retention policy, and make sure you can restore the database backup.

construction

Where the real effort goes

The main work is usually mapping your own fields and review rules, then deciding how much history to bring. The documented importer covers subscriber records, but announcement content, roadmap history, feedback, attachments and delivery metrics need separate export and mapping work. If Enterprise DNA runs your version, they map the agreed LaunchNotes data as part of that work.

Not ready for a call?

Get your LaunchNotes switch plan by email

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

Choose your route

Three ways to own the release process

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run the demo with Claude Code, Codex, OpenCode or Cursor.
  2. 2 Create a project and import a LaunchNotes subscriber CSV or saved export response.
  3. 3 Review the mappings, consent evidence and category preferences.
  4. 4 Run the weekly review and generate private announcement drafts.
Get the free version

Built around your business

We customise it

Setup fee, then a retainer

  • check Your release fields, readiness checks and approval rules.
  • check Your agreed LaunchNotes records brought across and checked.
  • check A web front end or a different technology stack if you need one.
  • check Your paperwork and delivery connections built around your team.
Get your version built

Omni by Enterprise DNA

We run it for you

Setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA.
  • check Your product record connected to the agreed business systems.
  • check Backups, access and changes managed with your team.
  • check A working release process maintained as your products change.
Talk to Sam

Questions

Instead of LaunchNotes, answered

What will we pay instead of the LaunchNotes subscription? expand_more

The free base has no licence charge; hosting and agent usage have their own costs. Enterprise DNA builds and runs your version for a setup fee, then a retainer. We scope the records, public pages and delivery connections you need before agreeing the work.

Can we bring our subscriber history? expand_more

The free importer reads the documented subscriber export, carrying email, region, status and selected categories where present. It also keeps the original fields for review. Confirmation dates stay separate from consent evidence. Announcement content, feedback and delivery history need separate export and mapping work.

Will it send announcements or replace our public changelog? expand_more

The free base prepares internal drafts and release reviews. Enterprise DNA can build your public changelog, connect a delivery service and add the audience controls your product needs. Keep the current service until those agreed parts work for your team.

What happens when someone changes an approved release? expand_more

Changing the wording, owner, date or category starts a new revision. Task changes also invalidate the earlier approval. The next review sees that gap. An internal approval records readiness; it does not send the announcement.

Does a confirmed subscriber automatically qualify for an announcement? expand_more

No. The audience review also needs dated consent evidence and a matching category or an explicit all-category preference. Suppressed addresses remain excluded after import. These are checks of your recorded evidence, with cited rules, rather than a certificate of legal compliance.

Put your release process on the desk

30 minutes with Sam. Bring the LaunchNotes bill, one release review and a sample of the records you want to keep. We work through what your version needs, what comes across and what Enterprise DNA would run for you.

Book 30 minutes with Sam Get the free version

Release Communications for Claude Code is free and open source, published by Enterprise DNA.

Done paying for LaunchNotes?

Get your version built