Enterprise DNA

Instead of Conjointly

Stop renting Conjointly. Own your pricing research system.

We build your version around the studies you repeat, bring your exported Conjointly responses across and run the agreed system for you. Start with the research work your business needs to keep.

Conjointly Ultimate starts at US$10,000 a year. Professional costs US$2,895 per team per year.

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 Conjointly bill buys

Separate the research record from the wider package

Ultimate includes support and services alongside software. Compare the parts you use with the cost of owning your recurring analysis.

layers

An annual research package

Ultimate starts at US$10,000 a year. Its package includes more than access to saved responses.

groups

A lower-cost team licence

Professional is US$2,895 per team per year. This comparison targets the larger Ultimate commitment.

query_stats

Advanced research methods

Conjointly offers several methods. The free base here focuses on exported Van Westendorp price-sensitivity studies.

description

Research support

Ultimate adds research support, training and procurement onboarding. Scope the expertise your business needs alongside the software.

database

Respondent sourcing

Panel responses are separate from the licence. Owning the research record does not replace the work of finding suitable participants.

cloud

Your exported evidence

Conjointly documents raw-response exports. Keep that evidence available for the research work you want to run yourself.

The owned research desk

From price answers to a decision you can explain

Sample first

See exactly which answers count

Keep the original price answers and make the analysis exclusions visible.

  • check Reconcile imported, eligible and excluded response counts
  • check Keep incomplete responses separate from complete ones
  • check Flag price answers entered in an inconsistent order
  • check Record exclusion and reinstatement reasons without changing the original answers

Price perceptions

Read the range without inventing certainty

Calculate the price-perception curves from the eligible answers in the chosen study.

  • check Keep every study in its own currency and price unit
  • check Show all four price-perception intersections
  • check Preserve a range when the evidence does not give one unique point
  • check Withhold summary results below the agreed sample minimum

Buyer groups

Check the result against the people behind it

Compare the chosen groups with the same review rules, using the fields that matter to your business.

  • check Separate existing customers from new buyers when your export identifies them
  • check Show the eligible count for each group
  • check Apply the agreed minimum independently to every group
  • check Keep the whole-study result separate from a small subgroup

Decision evidence

Keep the reasoning after the meeting ends

Put a proposed price beside the analysis that supported it and the work that follows.

  • check Freeze the sample and analysis when recording a decision
  • check Keep a written rationale and evidence reference
  • check Assign follow-up with an owner and due date
  • check Produce branded study briefs and decision records

Make it yours

Design your own Conjointly replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Pricing Research for Claude Code

Connected to your own database

How many responses can we use for this study?

Harbour Coffee subscription

Currency
NZD
Price unit
monthly subscription
Imported
10
Eligible
8
Excluded
2
Min sample
6

Ask it anything

Questions your owned research desk answers

These queries run on the fictional demonstration below. Conjointly also provides research analysis. The difference here is ownership of the records, calculations and decision process.

chat_bubble How many responses actually support this study?
chat_bubble Which responses failed the review checks?
chat_bubble Which buyer groups are below our agreed minimum sample?
chat_bubble How does the too-expensive percentage change across observed prices?
chat_bubble Is the extreme-balance result a point or a range?
chat_bubble How do eligible counts differ between existing and new buyers?
chat_bubble Which research reviews and follow-up actions are overdue?
chat_bubble What evidence supported our proposed price before later exclusions?
chat_bubble Which source export and count produced these responses?
chat_bubble Who recorded each review, note and decision?

Switching

How to switch from Conjointly

A move like this usually involves exporting the Van Westendorp responses, mapping your study fields and rules, checking the import, and reviewing the records before you switch.

  1. 1

    Export your raw responses

    Export the raw responses for the Van Westendorp studies you want to bring across. If Conjointly gives you an Excel workbook, save its Respondents worksheet as UTF-8 CSV before import. Export what your account allows, and check with Conjointly if you cannot find the raw response export. Keep an independent source row count for each study.

  2. 2

    Test the import

    Start with a test run using the import preview before adding records. Map the respondent identifier, buyer group, completion status and four price answers from your export. These columns vary by study, so check the mapping against the source rows before confirming the import. Use your own file and mapping for real research.

  3. 3

    Review flagged responses

    Compare the import totals with your independent source count, then review responses marked incomplete or inconsistent. These answers stay visible in the research record but are excluded from calculations. Check the buyer groups and the study minimum you have chosen before interpreting results. Correct mapping problems before relying on the analysis.

  4. 4

    Run both side by side

    Keep Conjointly available during a short overlap while you check the imported studies in the new workflow. Compare the source responses, sample counts, buyer groups and price-perception evidence, and note differences for review. Use this period to confirm your records and rules. The replacement does not provide survey hosting, respondent sourcing or other specialist methods.

  5. 5

    Switch off Conjointly

    Before closing your Conjointly account, confirm you no longer need its survey collection, respondent sourcing, other methods or connections. Pricing Research for Claude Code covers imported Van Westendorp responses, sample review, price-perception analysis and decision evidence, not the whole Conjointly platform. Once the workflows you still need are covered and your records are checked, switch off Conjointly.

construction

Where the real effort goes

The main work is mapping your study fields, buyer groups, completion rules, four price answers and sample minimum, then deciding which history to bring across. You will also need to reconcile counts and review flagged answers. When Enterprise DNA installs and runs your version, they handle this mapping and setup work as part of the agreed scope.

Not ready for a call?

Get your Conjointly switch plan by email

We will send you the step-by-step plan for moving your business off Conjointly, 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 base or have your version built

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, install dependencies and run npm run demo
  2. 2 Open the folder in Claude Code, Codex, OpenCode or Cursor
  3. 3 Export Conjointly responses and map the columns for import conjointly
  4. 4 Set brand.json and render your study briefs and weekly view
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your research fields, buyer groups and review rules
  • check Your Conjointly exports mapped and reconciled
  • check Your collection workflow and additional analysis methods scoped and tested
  • check Your choice of screens, reports and database setup
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with agreed access, backups and record handling
  • check Your research reviews prepared from current evidence
  • check Your reports and connections maintained as the business changes
  • check Run through Omni by Enterprise DNA alongside your other work
Book a discovery call

Questions

Instead of Conjointly, answered

Does this replace the whole Conjointly platform? expand_more

The free version covers imported Van Westendorp responses, sample review, price-perception analysis and decision evidence. Conjointly also supplies survey collection, other methods and respondent sourcing. Enterprise DNA scopes the collection workflow, specialist methods and connections your version needs before you switch.

Can we bring our existing responses across? expand_more

Yes, for the supported price-sensitivity work. Export the raw responses and map the respondent identifier, buyer group, completion status and four price answers. A workbook can be saved as a text export first. We reconcile the source count, keep incomplete answers visible and check the mapping before using the analysis.

Will it tell us the price that makes the most money? expand_more

No. Price-sensitivity responses describe perceptions. They do not establish future demand or profit. The analysis shows its sample and the intersections between those perceptions. A proposed price needs your rationale and evidence, and the system does not change selling prices.

What happens when the sample is small or an answer looks wrong? expand_more

Incomplete or inconsistent answers remain in the research record but are excluded from calculations. You can record further exclusions with reasons. Summary intersections and new pricing decisions are withheld below the agreed sample minimum. That minimum is a research rule you choose, not a guarantee of a representative sample.

What do we pay Enterprise DNA, and who keeps the evidence? expand_more

There is one setup fee, then a retainer for agreed customisation and operation. Your records remain in a database you own. We review the methods you use, the current Conjointly bill and the work your version needs with Sam before agreeing the scope.

Put your Conjointly bill beside the research you repeat

30 minutes with Sam. Bring the current bill, a sample export and the decisions your team needs to explain. We identify what belongs in your owned system and what needs to be connected before the move.

Book a discovery call Get the free version

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

Done paying for Conjointly?

Get your version built