Enterprise DNA

Instead of Wildnote

Reviewing your Wildnote bill? Own your ecological survey review system.

We build your version around how your ecologists collect, check and report evidence. We map your Wildnote exports, agree the field tools you need and run the system for you.

Wildnote lists a starting price of $675 per user per year, with a two-user minimum and custom rates. Its published monthly equivalent is $56.25 per user, billed annually.

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

The Wildnote comparison

Separate the field tools from the review work

Wildnote includes mobile collection and reporting in its subscription. Compare what your team uses with the office records you want to own, then scope any field tools into your version.

groups

A price for each user

The published starting price is $675 per user per year. Your team size and agreed custom rate determine your bill.

smartphone

Mobile collection

Wildnote includes an offline mobile app. Agree the collection workflow your team needs before replacing it.

assignment

Project forms

Its subscription includes projects and forms. Your own version can use the fields and review rules your ecologists agree.

photo_library

Photographs with field records

Wildnote includes photo and data integration. Your evidence archive and its access rules belong in the migration scope.

description

Reports and exports

Wildnote offers standard and custom compliance exports. Compare those outputs with the survey papers and field briefs you need.

support_agent

Onboarding and support

Wildnote includes onboarding and support. Enterprise DNA can take responsibility for setting up and running your owned version.

Your own review desk

From a field visit to a defensible working record

REVIEW

See what changed after review

A review stays attached to the evidence version the reviewer actually checked.

  • check Survey edits trigger a new review requirement
  • check Observation changes invalidate the previous review
  • check Old reviews remain available with their evidence
  • check Open follow-ups prevent a review being recorded

EVIDENCE

Put missing evidence on the work list

Check the record before relying on the report.

  • check Find surveys missing location or effort
  • check Find missing field archive references
  • check Keep provisional identifications visible
  • check Assign each follow-up to a person and date

PERMISSIONS

Keep permission evidence beside the survey

The responsible ecologist records what permission applies. The system checks the recorded reference, scope and dates.

  • check Document why permission is or is not needed
  • check Compare survey dates with recorded permission dates
  • check Keep unresolved evidence in the review queue
  • check Retain the ecologist’s review without claiming statutory approval

REPORTING

Ask across projects and original answers

Bring the source answers and current review state into the same working picture.

  • check Read species observations by project and identification status
  • check Compare recorded effort by survey method
  • check Trace a survey back to its original exported answers
  • check Create branded survey papers and field return briefs

Make it yours

Design your own Wildnote replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Ecological Surveys for Claude Code

Connected to your own database

Which surveys still need review?

DUNE-01

Project
DEMO-DUNE
Site
Dune quadrat A
Observer
Aroha Bell
Review due
2026-10-13
Revision
2
Open actions
0
Check count
0

EST-02

Project
DEMO-ESTUARY
Site
Estuary south sampling
Observer
Tane Morgan
Review due
2026-11-11
Revision
4
Open actions
2
Check count
5

Ask it anything

Ten questions your review desk answers

These run on the fictional demo today. Adapt the checks to your practice and keep professional judgment with your ecologists.

chat_bubble Which surveys have changed since their last review?
chat_bubble Which permission references fail to cover the survey date?
chat_bubble Which field visits are missing coordinates, effort or evidence?
chat_bubble Which species identifications still need confirmation?
chat_bubble Which follow-ups are overdue, and who owns them?
chat_bubble Which projects have observations marked sensitive?
chat_bubble Which taxa were observed on each project, by confirmation status?
chat_bubble Which surveys are over thirty days old and still unreviewed?
chat_bubble How much recorded effort went into each survey method?
chat_bubble Which original answers and source export supplied a survey?

Switching

How to switch from Wildnote

A move involves exporting Pivot Report workbooks, mapping your form questions, testing the import, and checking the replacement alongside Wildnote before you stop using it.

  1. 1

    Export your surveys

    In Wildnote, use the documented Pivot Report Excel export. It provides one survey per row. Export the surveys and source answers you need to bring across, and keep the original workbooks. Photos need a separate archive and migration check, so account for them separately rather than assuming the survey export includes them. Contact Wildnote if you need help accessing the export.

  2. 2

    Test the import

    Use the documented import for the Pivot Report workbook and review the field mapping against your own question labels. Run the offered test before it writes any records. Confirm that the mapping reflects your forms, since question labels differ between teams. Dynamic species questions stay in source fields unless you explicitly map them into observations.

  3. 3

    Review flagged items

    Review anything the test flags before you commit the import. Pay particular attention to questions whose mapping is unclear, and decide which dynamic species answers should become observations. The original workbook and source answers are retained, so you can check imported records against what Wildnote exported. Do not treat unconverted source answers as confirmed species observations.

  4. 4

    Run both side by side

    Keep Wildnote running for a short period while you check the replacement against the source records and try the office review work with your team. Confirm the imported evidence and observations look right, and that people can handle reviews and follow-ups. Phone and offline collection are not part of the free base, so keep that field workflow in Wildnote until replacement requirements have been checked.

  5. 5

    Switch off Wildnote

    Once the imported records and chosen history have been checked, your team is using the replacement for office review work, and photographs are accounted for in your controlled archive, you can stop using Wildnote. Keep the original export workbooks and follow the agreed backup and access process for the new database. Do not switch off the field workflow before collection needs are covered.

construction

Where the real effort goes

The work is usually less about moving rows and more about mapping your form questions, deciding which answers become structured observations, and choosing which past records and photos to bring across. Your review rules and reporting needs also need checking against the replacement. If Enterprise DNA installs and runs it for you, they handle this mapping and setup with you.

Not ready for a call?

Get your Wildnote switch plan by email

We will send you the step-by-step plan for moving your business off Wildnote, 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, run npm install and npm run demo
  2. 2 Use Claude Code, Codex, OpenCode or Cursor with the included commands
  3. 3 Map your Wildnote Pivot Report Excel columns and test the import
  4. 4 Check the source evidence, configure your brand and run the reviews
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your survey fields, review rules and reporting formats
  • check Your Wildnote answers mapped across and checked
  • check Mobile collection, maps or a web screen scoped around your actual work
  • check Your preferred technology and evidence archive connected
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access, backups and your archive agreed
  • check Weekly evidence reviews and follow-up papers prepared
  • check Maintained as your team, forms and obligations change
  • check Run through Omni by Enterprise DNA beside the rest of your business
Book a 30-minute review

Questions

Instead of Wildnote, answered

What does Wildnote cost? expand_more

Its pricing page lists $675 per user per year as a starting point, with a two-user minimum and custom rates. The monthly equivalent is $56.25 per user, billed annually. Confirm current terms for your team. The free version has no licence fee. Enterprise DNA agrees one setup fee, then a retainer to customise and run your version.

Can we bring our existing surveys across? expand_more

Yes, through the documented Pivot Report Excel export after its question labels have been mapped. The free version retains the original workbook and every source answer. It does not automatically turn custom species questions into confirmed observations. Photographs need their own archive and migration check.

Can the team still collect data on phones? expand_more

Wildnote includes mobile and offline collection. The free version here handles office evidence review. Enterprise DNA can scope phone collection, maps, photo capture and offline requirements into your own version. Keep the current field workflow until the replacement has been checked in use.

Does a passing check mean the survey is legally compliant? expand_more

No. The checks expose missing records and compare recorded permission dates. Your ecologist decides which permissions and conditions apply, verifies the evidence and reviews the findings. The base includes a New Zealand marine reserve permission example. Other activities and jurisdictions need their own assessed rules.

What happens to sensitive locations and our review history? expand_more

The records stay in your database with original source answers, changes and previous reviews. Sensitive observations are marked for internal handling. That marker is not an access restriction. Enterprise DNA agrees the access rules and backup process with you before your team starts using the system.

Bring your Wildnote bill and one survey to Sam

Spend 30 minutes with Sam. Bring your invoice, a sample export and the report your ecologists actually deliver. We will compare the field tools you use, the review work you want to own and what your version needs.

Book a 30-minute review Get the free version

Ecological Surveys for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Wildnote?

Get your version built