Enterprise DNA

Instead of Alteryx

Replace Alteryx prep. Own the rules.

We build your version around the files, checks and reports your business uses. Bring across your agreed Alteryx data, validate the preparation rules and have it run through Omni by Enterprise DNA.

Alteryx Starter lists US$250 per user per month, billed annually. That is US$3,000 per user a year. Professional and Enterprise pricing is quoted privately.

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

Compare the preparation work you repeat every week

Alteryx prices its editions around capabilities, user roles and automation capacity. Start with the recurring job your business needs, then agree what your replacement must do.

paid

A price for each Starter user

Starter lists US$250 per user per month billed annually. The edition supports one to ten seats. Compare that licence cost with the preparation jobs your team actually runs.

join

Cleaning and combining data

Starter includes blending, transformation, joining and aggregation. Your owned version saves the agreed preparation rules and the source records behind each result.

upload_file

File-based preparation

Starter connects to file sources. The free base brings across a complete CSV export with its column names and preserves each imported snapshot.

schedule

Scheduled work

Professional includes essential cloud scheduling. Enterprise adds more advanced scheduling and monitoring. We scope when and where your custom version should run.

hub

Connections beyond files

Professional lists more than a hundred data-source connections. We agree which live connections your version needs and validate their output against your existing process.

verified_user

Governance and deployment

Enterprise includes broader governance and private data handling. Your custom version needs access, hosting and data-handling controls matched to your business.

The version you own

From a source file to an answer you can explain

Source history

Keep the original evidence

Each imported file becomes a separate snapshot. New information does not rewrite the source of last month's report.

  • check Original field values retained as text
  • check Repeated identical files skipped
  • check Import count and source fingerprint recorded
  • check Source owner and purpose kept beside the records

Repeatable work

Run the rules your business agreed

Save the cleaning and preparation steps once, then apply them to the next complete export.

  • check Trim and standardise field values
  • check Filter, select and rename the fields you need
  • check Remove exact duplicates and reject conflicting keys
  • check Join a lookup and calculate exact decimal totals

Reconciliation

Explain why the count changed

Check the work before using the answer. A failed check remains visible with its reason.

  • check Input and output counts for each successful step
  • check Missing required values stop the run
  • check Source-record references attached to results
  • check New source imports flag old answers as outdated

Weekly review

Leave the next job with an owner

Keep source problems, review evidence and overdue work together with your preparation history.

  • check Stale sources and failed runs in the weekly view
  • check Personal-data purpose and retention review prompts
  • check A branded reconciliation document for each run
  • check Assigned actions closed with recorded evidence

Make it yours

Design your own Alteryx replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Data Preparation for Claude Code

Connected to your own database

Which sources need attention before we prepare this week's report?

BRANCHES

Owner
Ben
Row count
2
Freshness
stale

CONTACTS

Row count
0
Freshness
never imported

Ask it anything

Ten questions your version answers

These questions run against the working database. Alteryx also provides preparation and analysis tools. This version puts the agreed rules, evidence and changes under your control.

chat_bubble Which source has stopped arriving?
chat_bubble How many blanks and distinct values are in each column?
chat_bubble Which weekly preparation run failed, and why?
chat_bubble Did a new source file make the previous answer outdated?
chat_bubble How many rows did filtering and deduplication remove?
chat_bubble Which original rows contributed to this branch total?
chat_bubble What rules and source snapshot produced an old answer?
chat_bubble Who imported a file or changed a rule?
chat_bubble Which personal data needs a purpose or retention review?
chat_bubble Who owns the overdue mapping check?

Switching

How to switch from Alteryx

A move usually involves exporting complete data, mapping your preparation rules, and reconciling the new output against Alteryx before you stop the existing job.

  1. 1

    Export the agreed data

    Choose the datasets and history you need to bring across. Ask Alteryx which export options your account supports, usually CSV or Excel. The importer reads complete CSV data exports with column names, so make sure the data you agree to move is available as CSV. Saved Alteryx workflows need separate mapping and are not imported as working recipes.

  2. 2

    Load a test import

    Register each dataset and start with a test import before loading the full export. The importer checks the data structure, preserves the records and reports the imported count. Once the test looks right, load the complete CSV export. Repeated identical files are skipped. A changed file creates a new full snapshot, not an automatic append or merge.

  3. 3

    Review the import and rules

    Check any structure issues reported during import, then compare the imported count with Alteryx's full output. Next, map the preparation job's fields and rules, including any formulas, lookups and checks it needs. Run the new preparation job and review its findings. Missing required values and duplicate lookup keys, for example, stop a run and record the reason.

  4. 4

    Compare both jobs

    For a short period, run the existing Alteryx job and the replacement against the same agreed inputs. Compare their outputs and investigate differences before relying on the new result. Check that important records and totals match, and that you can trace successful results back to their source rows. Keep Alteryx working until the replacement passes the checks you agreed.

  5. 5

    Switch off the agreed job

    After the replacement passes reconciliation, stop using Alteryx for that agreed preparation job. Do not treat this as an automatic replacement for every Alteryx workflow. Other saved workflows, macros, schedules, connections and spatial models need separate implementation and reconciliation. Switch off only the processes covered by your checks, and keep any other Alteryx work in place until it has its own replacement plan.

construction

Where the real effort goes

The main work is usually mapping your own fields and preparation rules, then deciding which history to bring across. Saved workflows do not transfer as working recipes, so formulas, lookups and checks need to be mapped and reconciled for the jobs you are replacing. When you have Enterprise DNA run it for you, Enterprise DNA handles this setup and validation work within the agreed scope.

Not ready for a call?

Get your Alteryx switch plan by email

We will send you the step-by-step plan for moving your business off Alteryx, 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 how much of the work you want us to run

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 Import a complete Alteryx CSV data export and reconcile the count
  4. 4 Save the preparation recipe, run it and compare the output
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your fields, preparation rules and exception checks
  • check Your agreed Alteryx exports brought across and reconciled
  • check A web front end or different stack when your team needs one
  • check Your live connections and reporting requirements implemented
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Agreed source connections and run times kept working
  • check Backups and access arranged for your business
  • check Your preparation checks, documents and follow-up maintained
Book a call with Sam

Questions

Instead of Alteryx, answered

Can we bring our Alteryx history across? expand_more

Yes. The free importer reads complete CSV data exports with column names. It checks the structure, preserves the records and reports the imported count. Saved preparation workflows need separate mapping. We validate a sample and then reconcile the full result before replacing the agreed job.

Will our saved Alteryx workflows run unchanged? expand_more

The free version runs its own explicit preparation rules. We translate the jobs you need, including the required formulas, lookups and checks, then compare their results with the existing process. Keep the original process working until the replacement passes those checks.

What happens when a lookup or source file is wrong? expand_more

Duplicate lookup keys and missing required values stop the run and record the reason. Conflicting duplicate records also fail. Successful results retain their source references. Importing a newer source marks old answers as outdated so the team knows they need another run.

Can it run on a schedule and support our data controls? expand_more

We build the agreed schedules, connections, access controls and screens into your custom version. The free base operates on locally imported data and provides review prompts for source freshness, purpose and retention. Those checks support the responsible owner rather than certify compliance.

What does Enterprise DNA charge? expand_more

One setup fee, then a retainer for agreed ongoing work. We review your current Alteryx bill, preparation jobs, data volumes and operating requirements before agreeing the scope. The free base has no licence fee. Hosting and the tools used to operate it have their own costs.

Bring your Alteryx bill and the preparation job nobody wants to own

Spend 30 minutes with Sam. Show the export, the repeated cleaning steps and the result your team checks by hand. We map the preparation rules, history and operating work your version needs.

Book 30 minutes with Sam Get the free version

Data Preparation for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Alteryx?

Get your version built