Enterprise DNA

Instead of Specright

Stop renting Specright. Own your packaging system.

We build your version around how you review packaging, bring your Specright records across and run it for you. Your materials, suppliers and evidence stay connected in a database you own.

Specright quotes Foundations, Plus and Enterprise privately. Bring your annual contract and compare it with the packaging work your team actually uses.

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 contract behind the specifications

Separate the packaging work from the platform bill

Specright sells a wider specification and product-development platform. Start with the records and weekly decisions your packaging team needs.

paid

A privately quoted plan

Foundations, Plus and Enterprise each require a quote. Your contract is the starting point for a cost comparison.

group

Additional licence bundles

Specright says more licences can be purchased when the included allocation does not cover your team.

inventory_2

Packaging specifications

Material details, weights, intended uses and supplier references are business records your team maintains.

history

Version and review control

Specright offers versioning and approval traceability. Keep those review records central when scoping your own system.

query_stats

Packaging analysis

Specright provides comparison and reporting features. Decide which questions your own weekly review must answer.

sync_alt

Implementation and connections

Its pricing page describes discovery-led implementation and migration. Scope those steps against your actual records and systems.

Your packaging desk

Review the component. See the affected products.

Specifications

Keep the source beside the revision

Each change gets a new version, its own source and a named editor. Previous evidence stays with the version it supported.

  • check Material, component weight and intended-use records.
  • check Review dates and packaging owners.
  • check A new review after a specification changes.
  • check Every product using the changed component.

Supplier evidence

Know which evidence needs chasing

Bring missing references and overdue decisions into one review. Record why supplier evidence covers the intended use.

  • check Food-contact evidence attached to the exact revision.
  • check Support for recorded recycled-content claims.
  • check Expired references separated from current evidence.
  • check Supplier request drafts prepared for a person to review.

Product impact

Answer your own packaging questions

Combine your component records, local review rules and product usage in one place. These are questions the free version answers today.

  • check Shared components across different products.
  • check Packs with an unapproved component.
  • check Nominal packaging weight per finished pack.
  • check Overdue supplier evidence alongside the products it affects.

Review packs

Keep the decision as it was made

Save the specifications and evidence considered in an internal review. Later changes leave that saved record intact.

  • check Specification sheets in your business colours.
  • check Current product review documents.
  • check Saved internal review records with their supporting evidence.
  • check Your own fields and review rules added as the business changes.

Make it yours

Design your own Specright replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Packaging Specs for Claude Code

Connected to your own database

Which suppliers owe us current packaging evidence?

CAP-28

Supplier
Harbour Packaging
Owner
Aroha
Rule
FOOD
Issue
Food-contact suitability evidence missing or expired

BOX-06

Supplier
Tasman Fibre
Owner
Mia
Rule
RECYCLED
Issue
Recycled-content claim evidence missing or expired

Ask it anything

Ten questions across your packaging records

These questions run against the demo today. Specright also offers configurable analysis. Your own version connects the records and review rules your business chooses.

chat_bubble Which specifications have overdue reviews?
chat_bubble Which food-contact components lack current suitability evidence?
chat_bubble Which recycled-content claims lack current evidence?
chat_bubble Which products use a component awaiting approval?
chat_bubble Which components are shared by more than one product?
chat_bubble What is the nominal packaging mass of each pack?
chat_bubble Which suppliers owe evidence for multiple components?
chat_bubble Which owners have overdue actions?
chat_bubble Which specifications have no product usage?
chat_bubble Which products have no current evidence findings?

Switching

How to switch from Specright

A move usually involves exporting the fields you use, mapping them to the new database, and reviewing which supplier evidence, product links and history to bring across.

  1. 1

    Export the fields you use

    Specright documents CSV export from its configurable specification grid. Export the specification fields your team uses, including the codes, weights and intended uses you need to check after loading. If the export options in your account do not match, check with Specright. Supplier names come across with current specifications, but evidence documents, product links and previous versions need separate migration work.

  2. 2

    Map fields and test the import

    Match your Specright column headings to the fields in the new database, and normalise units to grams. The import brings in current specifications and supplier names. Run its test pass before loading records for real, then review any issues it reports. Blank values remain errors, so resolve missing information rather than relying on an assumed default.

  3. 3

    Reconcile the imported records

    Compare the imported codes, record counts, weights and intended uses with your Specright export. Review every issue the import flags and correct the source or mapping before trying again. Check that the records you need are present and accurate. Imported specifications are drafts, not approved records, so arrange the required reviews before treating them as ready for use.

  4. 4

    Run both systems briefly

    Keep Specright available while your team checks the new database against its day-to-day packaging work. Compare current specifications and review decisions, and confirm that the evidence and product links you need have been mapped and reviewed separately. Do not assume previous approvals carry over. Use this short period to identify anything missing before your team relies on the new records.

  5. 5

    Switch off Specright

    Once your team has checked the current specifications and decided what evidence, product links and previous versions to retain, move the packaging workflow to the new database and Claude Code. Keep the exports and source documents you need under your normal controls. Stop relying on Specright for this work only after the records and review process you need are in place.

construction

Where the real effort goes

The main work is mapping your own fields and rules, normalising units, and choosing how much history to bring. The basic import covers current specifications and supplier names. Evidence documents, product links and previous versions need separate mapping and review. If you have Enterprise DNA run it, they do this migration work as part of fitting the system to your operation.

Not ready for a call?

Get your Specright switch plan by email

We will send you the step-by-step plan for moving your business off Specright, 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 work you want us to handle

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, npm test and npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Export your Specright specification grid as CSV and map the actual column headings.
  4. 4 Preview the import, reconcile the records and add evidence before approving specifications.
Get it on GitHub

Built around your business

We customise it

A setup fee, then a retainer

  • check Your packaging fields, review rules and business documents.
  • check Your Specright records mapped and reconciled against the source.
  • check A web front end and supplier access if your operation needs them.
  • check Your choice of technology and connections to existing systems.
Build our version

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 agreed packaging review and supplier follow-up process.
  • check Team access, hosting and backups set around your business.
  • check Ongoing changes as your products and evidence requirements change.
Get your version built

Questions

Instead of Specright, answered

Is this a replacement for everything in Specright? expand_more

Start with the packaging work you use: specifications, supplier evidence, review decisions and product impact. Specright also covers wider product development. We scope your version against your real workflow, including supplier access, artwork handling and system connections where needed.

Can you bring our existing specifications across? expand_more

Yes. Specright documents exports from its configurable specification grid. We map your actual headings and units, then reconcile the records. The free version imports current specifications and supplier names. Evidence documents, product links and previous versions need separate mapping and review.

Does a clear evidence check mean our packaging is safe? expand_more

The checks identify missing references, expired evidence and outstanding reviews. Your responsible reviewer checks material suitability and the underlying supplier documents. Saved review records are internal evidence, not a safety certificate or authority to manufacture.

What happens when a component changes? expand_more

A new version starts without the previous evidence or approval. You can see the products using that component, collect current support and record a fresh review. Saved internal review records retain the earlier version and evidence.

What do we pay Enterprise DNA? expand_more

A setup fee, then a retainer for the agreed work. The free version is open source. On the call, we compare your current Specright contract, the records to bring across and the work you want us to build and run.

Bring your packaging contract and one real specification

Spend 30 minutes with Sam. We look at your Specright bill, the evidence your team chases and the products affected when a component changes. Then we scope the version Enterprise DNA builds and runs for you.

Get your version built Get the free version

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

Done paying for Specright?

Get your version built