Enterprise DNA

Instead of ReqView

Stop renting ReqView. Own your requirements system.

We build your version around your engineering reviews, bring across the agreed ReqView records and run it for you. See which changes need fresh evidence before the next design review.

ReqView lists PRO at €440 per user per year, TEAM at €600, and ENTERPRISE at €1,800 per floating client per year, with a €5,400 annual minimum.

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

Compare the bill

What your ReqView licence covers

ReqView offers named-user and concurrent licensing. Count the people who edit at the same time before comparing your renewal with an owned system.

paid

Annual named-user plans

PRO and TEAM charge for each licensed user each year. Your editing team and plan determine the renewal.

groups

Concurrent licensing

ENTERPRISE licences are shared through floating clients. The minimum covers three concurrent clients.

visibility

Readers can already be free

ReqView provides read-only access through its free plan. A reader is not automatically another paid editor.

dashboard

TEAM collaboration features

The TEAM tier includes dashboards, linked projects and shared export configurations.

description

Your existing records

ReqView documents CSV export and an open project format. The comparison is about how you want to operate and customise those records.

history

Your own review process

An owned version lets you change the evidence rules, approval steps and paperwork around your business. Scope those changes against what you use today.

Your version

From a changed requirement to a clear review decision

Evidence

Know when a passing result is out of date

A changed requirement needs evidence for its current revision. See the gap before it reaches the review meeting.

  • check Requirements and verification procedures with revision numbers
  • check Test results linked to the revisions they checked
  • check Changed links marked for review
  • check Current passes separated from old passes and latest failures

Reviews

Prepare the weekly engineering review

Bring open decisions, overdue reviews and missing evidence into one discussion.

  • check An owner and due date for each review
  • check Source references and verification methods
  • check Approval with the reviewer and decision evidence
  • check Readiness held until all linked active procedures have current passing evidence

Traceability

Follow the impact of a proposed change

Follow the recorded relationships from a changed requirement to the dependent work.

  • check Requirement dependencies and verification relationships
  • check Dependent requirements and procedures traced across several steps
  • check A saved design-review snapshot
  • check A comparison of records and relationships changed since that review

Paperwork

Produce the review records in your name

Generate documents from the same records used to prepare the meeting.

  • check Requirements specifications with source references
  • check Verification matrices with the recorded evidence
  • check Review records with approval and change history
  • check Your business name, logo and colours across the documents

Make it yours

Design your own ReqView replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Requirements for Claude Code

Connected to your own database

Which requirements changed after their tests passed?

SRS:1

Heading
Buffer readings
Owner
Mara Chen
Linked_tests
1
Current_passes
0
Latest_failures
0
Stale_results
1

SRS:2

Heading
Restore transmission
Owner
Mara Chen
Linked_tests
1
Current_passes
0
Latest_failures
1
Stale_results
0

SRS:3

Heading
Operator access
Linked_tests
0
Current_passes
0
Latest_failures
0
Stale_results
0

SRS:4

Heading
Cabinet label
Owner
Ari Patel
Linked_tests
1
Current_passes
1
Latest_failures
0
Stale_results
0

Ask it anything

Ten questions your version answers

These are working questions supported by the free version. They are not claims that ReqView lacks equivalent reporting.

chat_bubble Which passing tests refer to an older requirement revision?
chat_bubble Which links need review after either endpoint changed?
chat_bubble Which requirements have no linked test procedure?
chat_bubble Which approved requirements still lack current passing evidence?
chat_bubble What else is affected if we change the buffer requirement?
chat_bubble Who has the largest overdue review queue?
chat_bubble Which requirements have no source reference?
chat_bubble What changed since our recorded design review?
chat_bubble Which personal-information records need a purpose review?
chat_bubble Who changed a record and what did it say before?

Switching

How to switch from ReqView

A move usually involves exporting your documents, mapping your fields and rules, and deciding which history to bring across before you cut over.

  1. 1

    Export your ReqView documents

    Export each ReqView document as a CSV using ReqView’s documented export path. Keep the original columns, including link references, in the files you hand over. Confirm the export covers the records you intend to move, and check with ReqView if your account or document setup does not allow that export.

  2. 2

    Test the import first

    Create a matching destination document for each ReqView document you plan to move. Load one document at a time, starting with a test run that does not save changes. Review the test result before running the import for real. This lets you check what would be brought across without changing the database.

  3. 3

    Review flagged records and links

    Check the import report for records that need attention. Repeated identical rows are treated as unchanged, while changed rows need an explicit update. Original link columns are retained, but their relationships need reviewed mapping before they become active links. Agree separately how to handle attachments, formatting and historical decisions, then reconcile the imported records.

  4. 4

    Run both systems side by side

    Keep ReqView available while your team checks the imported records and follows its review process in the replacement. Compare key records, links and evidence, and have your reviewers confirm the result before relying on it. The free version has no application front end, so check that your team can work with the agreed setup before you cut over.

  5. 5

    Switch off ReqView

    Once you have reconciled the records and your reviewers accept the result, make the replacement the working system. Confirm that the history you agreed to bring is available and that your team knows where to record new work. Then stop maintaining ReqView, following your organisation’s own retention and access requirements.

construction

Where the real effort goes

Most of the work is usually in mapping your own fields and review rules, then deciding how much history to bring. Link references need reviewed mapping, and attachments, formatting and historical decisions are separate migration work. If you have Enterprise DNA run the system, Enterprise DNA handles the agreed data migration and checks the result with you.

Not ready for a call?

Get your ReqView switch plan by email

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

Start with the free version or have yours built

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo to review the fictional engineering project
  3. 3 Open the folder in Claude Code, Codex, OpenCode or Cursor
  4. 4 Export each ReqView document, dry-run its import, then review and map the links
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your terminology, fields, review rules and decision evidence
  • check Your agreed ReqView exports mapped and reconciled
  • check Your specifications, verification matrices and review documents
  • check A web front end or a different technology stack when your team needs one
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 Backups, access and evidence storage configured for your business
  • check Your review pack prepared from the current records
  • check Ongoing changes as your products and engineering process evolve
Book a call

Questions

Instead of ReqView, answered

Will this replace every part of ReqView? expand_more

The free version covers requirements records, verification procedures, links, revision checks and review documents. We scope the authoring experience, integrations and approval controls your team needs before building your version. Engineering acceptance stays with your reviewers.

What happens to our history and traceability? expand_more

ReqView exports each document as a spreadsheet file. The import keeps the original columns, including link references. Those relationships need reviewed mapping before they become active links. We agree how to move attachments, formatting and historical decisions, then reconcile the result with you.

Can an old passing test make a changed requirement look ready? expand_more

The free version records the requirement and procedure revisions behind each result. A change makes earlier evidence stale. Readiness requires approval and current passing evidence for every linked active procedure. Reviewing a relationship does not rewrite an old test result.

Do our read-only users need paid ReqView licences today? expand_more

ReqView already offers a free reader option. Compare your actual editing and concurrent-use needs when checking the licence bill. We build your owned version around who reviews, who changes records and who approves them.

How much does Enterprise DNA charge? expand_more

One setup fee, then a retainer. We agree the data migration, review process, interface and ongoing operation with you. The open-source version is free to use yourself; hosting and agent usage have their own costs.

Bring your renewal and one requirements document

Book 30 minutes with Sam. We look at what you pay ReqView for, how your team reviews changes, and what your own version needs to do. Leave with a clear scope for the records, evidence and paperwork you want to own.

Book 30 minutes with Sam Get the free version

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

Done paying for ReqView?

Get your version built