Enterprise DNA

Instead of Q Research Software

Stop renting Q Research Software. Own your survey analysis.

We map your Q exports and build the survey workflow around your team. Your questions, your review rules, your system to keep.

Q lists US$3,259 per standard user per year and US$9,777 per transferable licence per year.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The annual research software bill

Pay for the analysis your team actually needs

Q Research Software charges annually for its analyst licences. It also offers a broad statistical and reporting toolkit. Start by separating the repeatable survey work you need every week from the specialist methods a particular project needs.

paid

A licence for each analyst

The standard licence is US$3,259 per user, billed annually, for one computer. Review the seats used for recurring summaries and review papers.

devices

Sharing a licence has its own terms

The transferable licence is US$9,777 annually. Q describes installation on multiple computers with one user at a time.

calendar_month

An annual commitment

The published licences are billed by the year. Owning the workflow lets you retain your research process independently of an analyst licence renewal.

query_stats

Specialist methods beside routine work

Q offers advanced analysis as well as everyday survey summaries. Your version starts with weighted counts, percentages, means and comparisons between survey waves.

description

Reporting tied to the analysis workspace

Q supports Office and PDF exports. Here, an internal review paper keeps the source wave, analysis choices and saved result together in your business brand.

support_agent

Training and support in the package

Q includes upgrades, technical support and online training with its licences. With Enterprise DNA, support is agreed around your own research workflow and ongoing requirements.

Your research process, in your hands

From a survey export to a finding you can inspect

01 / BRING YOUR HISTORY

Reconcile every wave before analysis

Import the response records you choose to export from Q. Keep the original evidence beside the fields used for analysis.

  • check Match the actual export headings
  • check Retain the source date and original responses
  • check Reject duplicate respondent identifiers and invalid weights
  • check Check imported counts before accepting a wave

02 / ASK THE NEXT QUESTION

Read weighted results with their bases

Compare categories, segments and numeric responses while keeping the denominator visible.

  • check Show raw and weighted response bases
  • check Exclude missing answers from the relevant estimate
  • check Review how concentrated weights affect the effective base
  • check Flag groups below your chosen minimum base

03 / KEEP THE REASON

Know when a finding needs to be rerun

Save the analysis choices and result. When exclusions or study rules change, the earlier result is marked stale.

  • check Keep the reason for each exclusion
  • check Restore a respondent without losing the review history
  • check Track which saved findings use an older revision
  • check Refuse a fresh report draft from an out-of-date result

04 / RUN THE RESEARCH WEEK

Bring evidence gaps into the Monday review

Combine wave health, overdue research reviews and stale findings in one working pack.

  • check Name the research owner and study purpose
  • check Review accuracy and retention dates
  • check Record the operator and reason behind changes
  • check Generate study review papers in your business brand

Make it yours

Design your own Q Research Software replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Survey Tabulation for Claude Code

Connected to your own database

How does channel preference differ between North and South?

North

Category
Online
Percent
75
Base
8
Weighted base
8
Missing
0
Status
descriptive

North

Category
Store
Percent
25
Base
8
Weighted base
8
Missing
0
Status
descriptive

South

Category
Online
Percent
62.5
Base
8
Weighted base
16
Missing
0
Status
descriptive

South

Category
Store
Percent
37.5
Base
8
Weighted base
16
Missing
0
Status
descriptive

Ask it anything

Ten questions your own research desk can answer

These are working questions for the free version. Q also supports custom analysis. The difference offered here is ownership of your records and review process.

chat_bubble Which wave has the most missing ratings?
chat_bubble How does weighted channel preference differ by region?
chat_bubble How much do weights reduce the effective base?
chat_bubble Which saved findings became stale after an exclusion?
chat_bubble Which source exports are more than 30 days old?
chat_bubble Which studies lack purpose or review evidence?
chat_bubble What changed between waves with the same response definitions?
chat_bubble Which respondents were excluded and why?
chat_bubble What exact analysis choices produced this saved result?
chat_bubble Which zero-weight responses remain in the source count?

Switching

How to switch from Q Research Software

A move usually involves exporting response records, mapping your fields and rules, checking the imported data, and comparing results before you retire Q.

  1. 1

    Export response records

    Export response-level data from Q, including category labels where available. Q documents CSV export for this purpose. The export will not bring across every project formula, report layout or model, so list any of those you still rely on. Check with Q Research Software if you are unsure which export options your account supports.

  2. 2

    Map your study fields

    Match the headings in your export to the questions and variables you use in your studies. Include the weight field, categories and any exclusions or study rules that affect your results. Decide which waves and source records to bring across. Keep a record of the definitions you use so you can compare like with like.

  3. 3

    Preview, then load

    Start with the import preview before loading records. Review how the source headings have been matched and correct the mapping if needed. Load the data only after the preview makes sense and the source counts are understood. This gives you a chance to catch a mistaken field match before it affects your working data.

  4. 4

    Check and compare results

    Review anything the import flags, then reconcile respondent counts, missing answers and weights against the Q source. Compare accepted examples using the same inputs, exclusions, categories and calculation rules. Keep both systems running side by side for a short period, and retain Q until the required analyses and source reconciliation are accepted.

  5. 5

    Switch off Q

    Once you have accepted the comparisons and confirmed that the records and rules you need are in the new system, you can stop using Q for those studies. Keep any Q project material you still need for specialist modelling, reporting or other work that the new system does not cover. Do not retire Q before you have checked those requirements.

construction

Where the real effort goes

The main work is usually mapping your own question fields, weights, exclusions and calculation rules, then deciding how much history to bring across. A response export does not carry every formula, report layout or model, so those needs must be reviewed separately. If you have Enterprise DNA run the system, they map your studies and reporting requirements as part of the setup.

Not ready for a call?

Get your Q Research Software switch plan by email

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

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Export your Q responses to CSV, map the headings and test the import
  4. 4 Compare a known result before moving a study
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your questions, weight rules and minimum reporting bases
  • check Your Q exports mapped and reconciled against source counts
  • check Your research papers and review process
  • check A web workspace or a different technology stack where your team needs it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access and backups configured
  • check Your sources connected to the agreed research process
  • check Review packs prepared and the system maintained
  • check Operated through Omni by Enterprise DNA beside the rest of your business
Book a 30-minute research workflow review

Questions

Instead of Q Research Software, answered

Does this replace every part of Q Research Software? expand_more

The free version covers descriptive survey tabulation and the records behind it. Q also supplies specialist modelling and reporting features. We review the studies you run, agree the methods and reporting your version needs, and reconcile known results before a switch. Displayr is another option for teams evaluating a hosted research workspace.

Can we bring our existing Q studies across? expand_more

Q documents exporting response-level data to CSV, including an export with category labels. We map the actual headings and check respondent counts, missing answers and weights. A response export does not carry every project formula, report layout or model. Those requirements are scoped as part of your version.

Will the weighted results match our current reports? expand_more

They match only when the inputs, exclusions, categories and calculation rules match. The free version calculates descriptive weighted shares and means, shows the response base and flags small groups. We compare accepted examples before changing the research process. It does not present a difference as statistically significant.

How are respondent records and old findings handled? expand_more

You control the database and who can access it. Source records, review notes and saved findings stay together. Changed exclusions or study rules mark earlier findings stale. Accuracy and retention reminders identify missing review evidence. Small-base warnings are internal review aids, not a guarantee that a report is safe to disclose.

What does Enterprise DNA charge? expand_more

We agree one setup fee, then a retainer for ongoing work or operation. The scope follows your studies, data migration, research methods and reporting needs. There is no fixed Enterprise DNA price on this page.

Bring Sam one study and your Q renewal

In a 30-minute call, show Sam the survey work your team repeats, a report you trust and the parts you want to own. We will identify the first workflow to build and the evidence needed before switching.

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

Done paying for Q Research Software?

Get your version built