Enterprise DNA

Instead of Aha! Roadmaps

Stop renting Aha! Roadmaps. Own your product planning system.

We build your version around how you choose priorities and approve releases, bring your Aha! records across and run it for you through Omni by Enterprise DNA.

Aha! Enterprise starts at US$99 per paid user per month on annual billing. Reviewers and viewers are free on that plan.

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

What the Aha! bill buys

Aha! sells a broad planning suite. Decide which parts your business needs before paying for the next year.

group

Paid planning roles

Enterprise charges workspace owners and contributors; reviewers and viewers do not add paid seats.

map

Roadmaps and priorities

Premium includes roadmaps, feature scoring and visual plans. Your priorities become records in your own version.

forum

Idea collection

Ideas Essentials is included. We map the feedback records you need into your own review process.

dashboard

Whiteboards and documents

The suite includes Whiteboards Essentials and Knowledge Essentials. Scope these collaboration needs before switching.

analytics

Higher-tier planning controls

Enterprise+ adds team capacity planning and automation rules. Your own version can use your own capacity and approval rules.

storage

A plan tied to licences

Enterprise starts at US$99 per paid user each month with annual billing. The free base carries no software seat licence.

Your own version

Run the product review from your records

Priorities

Choose work with an explicit rule

See why one request ranks above another and which high-priority items still have blockers.

  • check Reach, impact, confidence and effort in one review
  • check Estimated work grouped by owner
  • check A visible queue for unassigned features
  • check Your review policy combined with your own business records

Release decisions

Know what is ready to move

Compare remaining work with capacity and check whether approvals still match the current plan.

  • check A release date and capacity allowance for each delivery
  • check Blocked work stays blocked until dependencies ship
  • check Scope changes require a fresh approval
  • check Internal release briefs built from the current records

Feedback

Keep the reason for each request

Link customer feedback to a feature and give personal-information retention its own review.

  • check Customer organisation and feedback together
  • check An explicit purpose and next review date
  • check Legal holds stay visible for the responsible owner
  • check Retention flags explain the record that needs attention

Weekly review

Give the owner an answer they can act on

Bring priorities, release risks and stale decisions into one Monday review. Aha! also supports custom reports; here you own the calculations and review rules.

  • check Unreviewed work separated from current decisions
  • check Private read-only views in your business colours
  • check Decision records with the stated owner and reason
  • check The records export together when you need them elsewhere

Make it yours

Design your own Aha! Roadmaps replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Aha! Roadmaps 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 Aha! Roadmaps data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the fictional product studio supplied with the free version. Ask a question in plain language and review the records behind the answer.

forum

Product Planning for Claude Code

Connected to your own database

Which features rank highest, and what is blocking them?

HAR-102

Name
Usage consent review
Owner
Aroha
Status
planned
Priority_score
48.00
Effort_days
3
Feedback_count
1
Blockers
0
Release
Spring service release
Last_reviewed
2026-09-18

HAR-101

Name
Usage export
Owner
Mere
Status
In progress
Priority_score
38.40
Effort_days
5
Feedback_count
1
Blockers
1
Release
Spring service release
Last_reviewed
2026-10-04

HAR-104

Name
Account handover
Owner
Hemi
Status
backlog
Priority_score
15.00
Effort_days
2
Feedback_count
1
Blockers
0
Last_reviewed
2026-09-03

HAR-103

Name
Partner welcome pack
Status
planned
Priority_score
2.10
Effort_days
8
Feedback_count
0
Blockers
0
Release
Partner onboarding

Ask it anything

Ten questions for your product review

These are real questions the demo answers today. Aha! supports custom reports too. Here, you own the records, calculations and review rules.

chat_bubble Which open features rank highest under our scoring rule?
chat_bubble Which high-priority features still have blockers?
chat_bubble Which releases exceed their remaining capacity?
chat_bubble Which releases contain features without current approval?
chat_bubble Which owners carry the most estimated work?
chat_bubble Which owners have stale feature reviews?
chat_bubble Which overdue releases still have open features?
chat_bubble Which active features have no accountable owner?
chat_bubble Which feedback records need a retention review?
chat_bubble Which dependencies prevent a feature from shipping?

Switching

How to switch from Aha! Roadmaps

A move usually involves exporting the planning records you use, mapping any extra fields or history, checking the import, then running both systems side by side before switching.

  1. 1

    Export your planning records

    Start with the planning records your team actually uses. Aha! supports spreadsheet exports from list reports, so export a feature list with references, descriptions, owners, statuses and release dates. Use the export format your account allows, usually CSV or Excel, and check with Aha! if you are unsure. Decide separately which ideas, votes, attachments and historical decisions you need.

  2. 2

    Load the feature list

    Use a fresh database without fictional demo records for your real data. Load the prepared feature list through the Aha! import path. Start with the import’s test run, which checks the file without saving changes. This lets you see whether the records and references are understood before you write anything to the new database.

  3. 3

    Review what needs attention

    Review anything the test run flags. Resolve ambiguous references and reconcile any changed rows the import rejects. Review imported capacity and scores, since those need checking. Map ideas, votes, attachments, integrations and historical decisions separately if you need them. Bring only the history your team will use, rather than assuming every Aha! record transfers with the feature list.

  4. 4

    Run both systems side by side

    Keep Aha! Roadmaps available while you use the new database for a short period. Compare feature records, release readiness, dependencies, decisions and feedback against the work your team still does in Aha!. Check that your team can follow the review process and that the records you chose to bring support the decisions you need. Fix mapping or rule gaps before making the new system your source of truth.

  5. 5

    Switch off Aha! Roadmaps

    Once the new database has the records and rules your team needs, make it the place you use for product planning. Stop updating the same plans in Aha! Roadmaps, and switch off or close your Aha! use through the account process that applies to you. Keep any records you still need before ending access.

construction

Where the real effort goes

The import itself is only part of the work. Most effort usually goes into mapping your own fields and rules, then deciding which history to bring. The standard import covers a prepared feature list, while ideas, votes, attachments, integrations and historical decisions need separate mapping. When you have Enterprise DNA run it, they handle this mapping and reconciliation as part of the move.

Not ready for a call?

Get your Aha! Roadmaps switch plan by email

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

Use the free version or have yours built

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm run demo to try the fictional product studio
  3. 3 Open it with Claude Code, Codex, OpenCode or Cursor
  4. 4 Prepare your Aha! feature-list CSV and test the import before saving it
Get it on GitHub

Built around your business

We customise it

A setup fee, then a retainer for ongoing work

  • check Your scoring, ownership and release approval rules
  • check Your Aha! records mapped and reconciled
  • check A web front end, feedback intake or connections scoped around your team
  • check A different technical foundation where your business needs it
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 Connected to the agreed business systems
  • check Access controls, backups and recovery checks for your team
  • check A person to call when the way you plan changes
Book a call

Questions

Instead of Aha! Roadmaps, answered

Are we replacing everything in Aha!? expand_more

Start with the planning work your team actually uses. The free version covers feature records, dependencies, release readiness, decisions and feedback review. Enterprise DNA scopes your collaboration screens, feedback intake and connections as part of your version.

Will our existing records come across? expand_more

Aha! supports spreadsheet exports from list reports. The free version imports a prepared feature list with references, descriptions, owners, statuses and release dates. Ideas, votes, attachments and historical decisions need separate mapping. We reconcile the records you need before you switch.

Does Aha! charge for everyone who reads a plan? expand_more

No. Enterprise and Enterprise+ include free reviewers and viewers. Enterprise starts at US$99 per paid user per month on annual billing. Compare your paid planning roles and the features you use with the work your own version would cover.

Can we trust the release and privacy checks? expand_more

The checks flag missing owners, stale approvals, blockers and feedback retention reviews. They use the records you enter. A responsible person still verifies the decision and the retention purpose; a legal hold stays visible and no information is automatically erased.

Who runs it after the move? expand_more

You can operate the free version yourself. With Omni by Enterprise DNA, we install, connect and run your version for a setup fee and then a retainer. We agree the access, backups, support and ongoing changes with you.

Own the plan for what you build next

Spend 30 minutes with Sam. Bring your Aha! bill and a release your team is planning. We will work through the records, decisions and screens your version needs.

Book a discovery call Get the free version

Product Planning for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Aha! Roadmaps?

Get your version built