Enterprise DNA

Instead of Clozd

Stop renting Clozd. Own your win-loss research.

We build your research workflow around your segments and review rules, bring the agreed Clozd deal records across and run your version for you.

Clozd pricing is quoted privately. Bring your software and interview-service costs so we can compare the work you need.

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

Review your Clozd bill

Separate the research service from the records you keep

Clozd offers software-only and managed programmes. Check the scope of your own quote before deciding which work to bring in-house.

inventory_2

The deal register

Clozd keeps deal records alongside feedback. An owned register gives you a place to start from your exported deal history.

event

Interview coordination

Clozd offers workflows for participant contact and responses. In your version, review the interview queue and assign the next step.

record_voice_over

Interview delivery

Live interview services are part of the Clozd offer. Decide who will conduct the research before comparing software costs.

description

Feedback preparation

Clozd offers transcription and summaries. Agree how your source material will be prepared and checked when moving your research.

label

Themes and evidence

Clozd groups and tags feedback. Keep your own reviewed themes attached to the buyer words and their source references.

hub

Connections and distribution

Clozd offers connections to other business tools. Include the connections your team uses in the scope of your own version.

Your research cycle

Move from a reason on a deal to a change someone owns

Coverage

Find the interviews you are missing

See the gaps before treating a handful of buyer conversations as the whole market.

  • check Closed deals grouped by segment and outcome
  • check Coverage counts distinct deals, even with several interviews
  • check Uninterviewed wins, losses and no-decisions stay visible
  • check A Monday review combines gaps, overdue work and different explanations

Buyer evidence

Keep the words behind the reason

Separate the sales explanation from a buyer theme, then show the evidence for both.

  • check Reviewed excerpts with a named reviewer
  • check Source references for each decision factor
  • check Negative themes beside the original sales reason
  • check Counts of distinct deals behind each theme, with no invented revenue attribution

Follow-through

Give every improvement an owner

Turn an observed issue into a dated action and keep the evidence available for review.

  • check Actions linked to a recorded finding
  • check Owner and due date on every action
  • check Completion evidence before an action closes
  • check Open actions flagged when their supporting research becomes restricted

Record care

Control which evidence is used

Keep collection notices, permission and retention review dates beside each interview.

  • check Permission and notice evidence before an interview is completed
  • check Withdrawn interviews excluded from research reports
  • check Overdue retention reviews remove evidence from current analysis
  • check Private interview briefs and action reviews in your business colours

Make it yours

Design your own Clozd replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Clozd 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 Clozd data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Three real runs on fictional demonstration records. Your own reports use your own evidence and research rules.

forum

Win-Loss Research for Claude Code

Connected to your own database

Which deal segments still need buyer evidence?

segment | outcome | deals | interviewed | missing | coverage_pct ---------------+-------------+-------+-------------+---------+------------- Enterprise | lost | 1 | 0 | 1 | 0.0 Midmarket | lost | 1 | 1 | 0 | 100.0 Midmarket | won | 1 | 1 | 0 | 100.0 Small business | no_decision | 1 | 0 | 1 | 0.0 Small business | won | 1 | 0 | 1 | 0.0

Ask it anything

Ten questions for your own research records

These analyses run on the included fictional records. They demonstrate your own workflow, without claiming that Clozd cannot produce equivalent reports.

chat_bubble Which segments have no eligible buyer interviews?
chat_bubble Where does a buyer theme differ from the reason sales recorded?
chat_bubble Which overdue interviews leave a gap in our coverage?
chat_bubble Which open actions rely on evidence that is now restricted?
chat_bubble How many distinct lost deals mention each negative theme?
chat_bubble Which buyer words support the implementation concern?
chat_bubble Which competitors appear in interviewed wins and losses?
chat_bubble Which collection notices or permissions need review?
chat_bubble How many deals have unknown values in each currency?
chat_bubble Who recorded an interview withdrawal or closed an action?

Switching

How to switch from Clozd

A move involves exporting your deal records, mapping your fields, checking the import and running both systems side by side before you switch off Clozd.

  1. 1

    Export your Clozd records

    Use Clozd's selectable-field CSV export for closed deal records, and download individual feedback separately where needed. Include only the history you have agreed to bring across. The deal import does not bring across interview recordings, PDFs or permission history. Check with Clozd what your account can export, then plan separate review and mapping for interview documents, permissions and prior themes.

  2. 2

    Map and test the import

    Match the headings in your actual deal export to the fields in the new system. Run the import preview first, without writing records, and check the counts against your Clozd export. Adjust the mapping if the fields or counts do not match. Only proceed with the import once you are satisfied that the preview reflects the records you intend to bring across.

  3. 3

    Review import issues

    Check the preview for errors and compare the imported counts with your source export. Changed source rows stop for reconciliation, and an import with an error rejects the whole batch. Resolve those differences before relying on the imported records. Review interview materials and other history separately, since they need their own review and mapping rather than coming across as deal records.

  4. 4

    Run both systems side by side

    Keep Clozd available while you use the new system for a short period. Compare deal counts and sample records, and review how your team handles buyer evidence and improvement actions in each system. Use this time to spot missing fields or history and agree how your team will handle interviews, recordings and transcription, which the new system does not replace.

  5. 5

    Switch off Clozd

    Once your team has checked the imported records and agreed how it will handle the research work, switch off Clozd. Before you do, confirm what records you need to retain and who is responsible for reviewing them. Copies, earlier reports and private exports still need authorised retention review, so switching systems does not remove those responsibilities.

construction

Where the real effort goes

The hands-on work is usually mapping your fields and research rules, then deciding which deal and interview history to bring across. Deal records can be imported after the export headings are mapped, but interview documents, recordings, permissions and prior themes need separate review. If you have Enterprise DNA install and run your version, they do this mapping and migration work with you as part of the agreed setup.

Not ready for a call?

Get your Clozd switch plan by email

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

Run your research your way

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 with Claude Code, Codex, OpenCode or Cursor and ask for the weekly review
  3. 3 Map your actual Clozd CSV headings, preview the import and check the deal counts
  4. 4 Set your research purpose, permission rules and access before using real records
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your segments, decision themes and review rules
  • check Your agreed Clozd records mapped and reconciled
  • check Your own reports and the connections your team needs
  • check A web front end or a different 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 with access and backup arrangements
  • check Research review packs and action follow-up prepared
  • check Kept working as your research process changes
  • check Operated through Omni by Enterprise DNA, alongside your business
Book a call with Sam

Questions

Instead of Clozd, answered

Will this replace our Clozd interview team? expand_more

The free version organises deal records, reviewed interview evidence and improvement actions. Interview delivery, recording and transcription need their own arrangements. We agree who does that work and which connections your version needs before recommending a switch.

How much does Clozd cost compared with this? expand_more

Clozd pricing is quoted privately. The free version has no software licence fee, while hosting, your coding assistant and research time are separate. Enterprise DNA builds and runs your version for a setup fee and then a retainer. Bring your actual invoice so we can compare the same scope.

Can we bring our existing deals and interviews across? expand_more

Clozd documents a selectable deal export and individual feedback downloads. The free version imports deal records after their headings are mapped and the counts checked. Interview documents, recordings, permissions and prior themes need separate review and mapping. That work is part of the agreed migration, with no promise that every record moves automatically.

How do we keep buyer evidence under control? expand_more

An interview needs permission, a collection-notice reference and a current retention review before its findings appear in research. Withdrawal removes those findings from current reports. Stored records, earlier reports and private exports still need an authorised retention review. We set up access and record-handling arrangements for your team.

Can our team have its own screens and reports? expand_more

Yes. The free version produces read-only research views, interview briefs and action reviews in your colours. We build the team screens and connections you need into your version. Findings still need a source and human review; a small selected sample is never presented as every buyer.

Bring your Clozd invoice and one research question

Spend 30 minutes with Sam. Bring your current bill, an example deal export and the question your team keeps asking. We will work through the records, interview services and connections your own version needs.

Book a 30-minute call with Sam Get the free version

Win-Loss Research for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Clozd?

Get your version built