Enterprise DNA

Instead of Centercode

Stop renting Centercode. Own your beta programme desk.

We build your version around your participant rules, weekly testing and exit decisions. We map your Centercode exports, bring the agreed records across and run the system for you.

Centercode quotes its paid plans privately. Compare your actual renewal quote with the beta work your team needs.

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

What the subscription covers

A hosted testing platform, when your daily decisions depend on records

Centercode offers Starter, Pro, Team and Enterprise plans. Paid pricing is by quotation. Separate the hosted participant experience from the evidence your operator reviews each week.

groups

A tester audience

Audience allowances vary by plan. Your own desk keeps participant groups, device details and eligibility records.

task_alt

Test planning and activities

The platform organises testing work. Your operator needs clear assignments, deadlines and recorded outcomes.

forum

Feedback handling

Issues, ideas and praise become records to review. You need owners, severity and evidence of what changed.

verified_user

Agreement records

Pro includes digital agreements. In your own desk, acceptance evidence is checked against the current programme agreement.

query_stats

Reports across projects

Centercode documents a reporting limit when projects, feedback dimensions and a date range are combined. Its guide describes export as a workaround.

settings

Hosted collection and delivery

Collection screens and build distribution belong in the switching plan. Enterprise DNA can build the connections and participant experience your version needs.

Your own operating record

The five decisions behind a well-run beta

Participants

Know who is ready to take part

Bring agreement evidence, notice references, retention reviews and assigned work into one review.

  • check Record the agreement version each participant accepted
  • check Block new assignments when the evidence is incomplete
  • check Spot people who have gone quiet while work is overdue
  • check Record withdrawal and keep it visible for review

Feedback

Keep the original report and the response together

Triage feedback without losing the source record or mixing programmes.

  • check Preserve every supplied export field
  • check Give an issue an owner and severity
  • check Link duplicate reports to the original in the same programme
  • check Compare project, issue severity and reporting dates together

Verification

A fix needs evidence from the current build

A passing result from an older build cannot close a revised fix.

  • check Request a retest against the recorded fix version
  • check Capture the tester, result and evidence reference
  • check Show overdue tests and failed current fixes
  • check Close an issue only after the latest result passes and pending tests finish

Exit decisions

Show the reasons to proceed or hold

The exit review combines the current blockers. A recorded decision remains a dated snapshot.

  • check Check high-severity issues and unfinished activities
  • check Flag activities that have never been assigned
  • check Produce a test plan, triage brief and exit review in your brand
  • check Keep decision history as new evidence changes readiness

Make it yours

Design your own Centercode replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Beta Programmes for Claude Code

Connected to your own database

What needs attention before the next beta decision?

BETA-1

Record
ACT-1
Reason
Activity overdue: P-02

BETA-1

Record
FB-01
Reason
High severity issue open

BETA-1

Record
FB-02
Reason
Retest overdue

BETA-1

Record
P-02
Reason
No activity in 14 days

Ask it anything

Ten questions the desk answers today

The first two combine projects, feedback and a date window. The others use your current participant, activity and verification evidence.

chat_bubble Which programmes have high severity issues reported in this date window?
chat_bubble Which tester platforms produced those unresolved issues?
chat_bubble Which participants have overdue activities and no recent activity?
chat_bubble Which fixes are waiting on an overdue retest?
chat_bubble Which current fixes failed their latest retest?
chat_bubble Which programmes have participants whose agreement or privacy records need attention?
chat_bubble Which unresolved issues still have no owner?
chat_bubble Which programmes have finished activities but still have release blockers?
chat_bubble Which programmes are ready for an exit decision under our recorded rules?
chat_bubble Which feedback is marked as duplicate and what original does it refer to?

Switching

How to switch from Centercode

A move usually involves exporting and mapping each feedback form, then checking the imported records against Centercode before you switch.

  1. 1

    Export your records

    Export each Centercode feedback form as a CSV, since forms can have different, configurable columns. Keep a private copy of each export. Decide which other records you want to bring, such as participants, attachments, survey answers and discussion history. Those need separate handling, so check what your Centercode account allows and agree what is in scope before you start.

  2. 2

    Map and test the import

    Inspect the column names in each feedback export and map them to the fields in the new desk. Start with the import's test run before loading records. The import handles one configured feedback export at a time, so prepare a map for each form you plan to bring. Keep the original exports available so you can compare them during the move.

  3. 3

    Review the import findings

    Check the test run findings and reconcile the rows and counts before loading the data. Stable source identifiers help prevent duplicate records on a repeat import. Changed rows stop the batch for review, and imported feedback starts as new without a participant link, regardless of its Centercode status. Confirm that these differences and any separate handling for other records are understood.

  4. 4

    Run both desks briefly

    After loading, keep Centercode available while you use the new desk for a short period. Compare the feedback and operational records you brought across, and check that your team can handle its beta work in the new desk. Use this time to resolve mismatches and confirm any workflows that need agreed custom work before you rely on the new desk.

  5. 5

    Switch off Centercode

    When you have reconciled the imported records and confirmed the new desk is ready for your agreed workflows, move your team to it and stop using Centercode for active beta work. Keep the private source exports and decide how to retain any Centercode records that were outside the migration scope. The new desk does not reproduce Centercode's hosted service.

construction

Where the real effort goes

The main work is usually mapping your own Centercode fields to the new desk and deciding which history to bring. Feedback forms can have different columns, while participants, attachments, survey answers and discussion history need separate handling. Your team also needs to agree its rules and any workflows that need custom work. If Enterprise DNA installs and runs your version, it handles the mapping and migration work with you as part of the agreed scope.

Not ready for a call?

Get your Centercode switch plan by email

We will send you the step-by-step plan for moving your business off Centercode, 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 who builds and runs your version

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Map your Centercode CSV headers, preview the import and reconcile each form
  4. 4 Ask for the beta week, retest queue and exit review
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your participant fields, agreement rules and exit criteria
  • check Your Centercode exports mapped and checked
  • check A web front end or different stack if you want one
  • check Participant intake and build delivery connections scoped to your process
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 Your database, backups and agreed connections maintained
  • check Weekly reviews adapted as your programme changes
  • check A team responsible for keeping your system running
Book a discovery call

Questions

Instead of Centercode, answered

Does this replace the whole Centercode service? expand_more

The free version runs the internal beta desk: participants, activities, feedback, retests and exit reviews. We build the participant screens, collection steps and delivery connections your version needs as agreed work. We compare those requirements before you switch.

What happens to our existing feedback? expand_more

Export each Centercode feedback form as a spreadsheet. After its columns are mapped, the free version loads the supplied feedback and preserves its original fields. Participants, attachments, survey answers and discussion history need separate handling. We check those exports and agree the migration scope with you.

Can we trust a passed exit review? expand_more

It confirms that the recorded checks pass at that moment. It does not certify product safety or release anything. A new issue or changed participant record can change readiness. The decision history keeps what was known when the decision was made.

How are participant privacy and agreements handled? expand_more

The desk flags missing notice references, overdue retention reviews and agreement evidence that does not match the current programme. Your operator reviews the evidence and retention purpose. We configure access and your own rules for the installed version.

What will our version cost? expand_more

The free version has an MIT licence. Enterprise DNA agrees one setup fee, then a retainer for customisation and operation. Centercode publishes no numeric paid-plan price on its current pricing page, so bring your renewal quote and the workflows your team uses.

Bring your renewal quote and the next beta decision

Spend 30 minutes with Sam. We look at your Centercode bill, the records you need to keep and how testers submit their findings. You leave with a clear scope for your own version and the work needed to switch.

Book a discovery call Get the free version

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

Done paying for Centercode?

Get your version built