Enterprise DNA

Instead of DevResults

Stop renting DevResults. Own your programme reporting system.

We build your version around your indicators, partner returns and review rules, bring your DevResults records across and run the reporting desk for you.

DevResults lists US$28,000 a year for its entry programme band, before setup and training. Confirm the current quote for your organisation.

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 bill covers

The reporting record should outlast the subscription

DevResults prices by programme size. Its entry pricing band lists US$28,000 annually or US$2,800 monthly, with US$33,800 setup charged separately. Its FAQ example differs from the listed bands, so confirm current terms before comparing your renewal.

paid

A programme-sized subscription

The published annual bands rise to US$49,000, US$70,000 and US$91,000. Compare the band your organisation actually buys.

settings

Setup before reporting starts

Configuration is a separate purchase. In your own version, the measurement definitions and reporting calendar remain part of your owned record.

groups

Access for your reporting network

The subscription includes unlimited user licences. Compare partner access and review responsibilities when scoping the connected version.

database

Storage for programme history

Hosting and storage are included in the subscription. Your owned reporting history can be backed up and exported independently.

support_agent

Support and maintenance

Ongoing support and software updates form part of the vendor service. Include operating support when comparing the full replacement scope.

school

Training for the team

The vendor lists training separately. Agree who will operate the reporting desk and how partner returns will be checked.

Your reporting desk

Work from the evidence, with your own rules

Partner returns

Know exactly what is still missing

Register what each project owes for each period, then compare it with the returns actually received.

  • check Named owners for every expected return
  • check Due dates beside missing submissions
  • check Pending and rejected figures kept visible
  • check Your own follow-up work beside each reporting obligation

Measurement

Keep counts, rates and snapshots distinct

A good-looking total is useless if it combines the wrong things. Your definition governs the calculation.

  • check Separate definitions and units for each measure
  • check Rates weighted by the underlying assessment counts
  • check Unknown results kept separate from reported zero
  • check A new measure when the meaning changes, with old history retained

Evidence

See the reason behind a correction

A new figure gets a new version. The earlier record remains available for review.

  • check Source references and observation dates
  • check Accepted figures separated from unreviewed returns
  • check Correction history with a named operator and reason
  • check Your reporting evidence joined to your own review actions

Reporting

Prepare the review without rebuilding it each month

Read the period, the missing returns and the evidence gaps together before preparing the working papers.

  • check Period briefs in your organisation’s colours
  • check Indicator reference sheets with the calculation method
  • check Partner returns with targets and outstanding work
  • check Period closure held until registered returns and actions are complete

Make it yours

Design your own DevResults replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Programme Results for Claude Code

Connected to your own database

Which results are ready, and which are still unknown?

LEARN

Indicator
ATTEND
Period
CURRENT
Target
150
Actual
unknown
Accepted
1
Pending
1

LEARN

Indicator
PASS
Period
CURRENT
Target
80
Actual
54.44
Accepted
2
Pending
0

WATER

Indicator
WORKING
Period
CURRENT
Target
8
Actual
unknown
Accepted
0
Pending
0

Ask it anything

Ten questions your own reporting record can answer

These questions run against the demo today. Your version can combine them with the other records your organisation owns.

chat_bubble Which partners owe a return after the collection deadline?
chat_bubble Which reported figures still lack source evidence?
chat_bubble Which accepted results fall below their agreed targets?
chat_bubble What is the pass rate when sites have different assessment counts?
chat_bubble Which corrections changed an earlier reported figure?
chat_bubble Which locations have numbers waiting for review?
chat_bubble Which projects have gone fourteen days without a recorded note?
chat_bubble How does this period compare with the prior period using the same definition?
chat_bubble Which imported measures still need an approved calculation method?
chat_bubble Which follow-ups must finish before a period can close?

Switching

How to switch from DevResults

A move usually involves exporting reporting-period results, mapping your definitions and deciding which supporting records and history need separate migration work.

  1. 1

    Export reporting-period results

    Use DevResults' reporting-period export to take out the results you want to move. The import accepts the raw Excel worksheet or a CSV copy. Decide which reporting periods to bring across, and check with DevResults if you are unsure how to produce the export your account allows. Documents, narrative responses and records held in other services need separate migration work.

  2. 2

    Test the import

    Ask whoever is running the import to test the export first, then load it. The import keeps the original records and source rows, and imported results stay pending for review rather than becoming accepted automatically. If Enterprise DNA is running your version, they can handle the import as part of the move.

  3. 3

    Review flagged records

    Check the import's flags before relying on the results. Reconcile headings, measurement definitions, reporting periods and totals. Extra columns remain dimensions until someone maps them, and changed or overlapping cells are rejected rather than overwriting the working record. Confirm targets and source evidence too. Reviewers need to check whether groups overlap and whether the evidence supports each result.

  4. 4

    Run both systems briefly

    Keep DevResults and the new desk in use side by side for a short period. Compare the reporting periods, expected returns and results you rely on, and resolve differences before making the new desk your working record. Keep existing collection, mapping or partner services in place until their replacements are installed and tested.

  5. 5

    Switch off DevResults

    Cancel or switch off DevResults only after you have checked the imported results and tested any services you still need. The base does not reproduce DevResults' mapping, collection integrations, partner access or document storage. Plan replacement or continued use for each service before ending your subscription, and keep the records you need for your own history.

construction

Where the real effort goes

The main work is usually mapping your own fields and measurement rules, checking definitions and totals, and deciding which periods and history to bring across. Documents, narrative responses and other services need separate migration work. If Enterprise DNA runs your version, they bring over the records, reconcile the definitions and fields, and handle the import as part of the setup.

Not ready for a call?

Get your DevResults switch plan by email

We will send you the step-by-step plan for moving your business off DevResults, 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 and ask for the reporting desk
  3. 3 Import a DevResults reporting-period CSV or XLSX after a dry run
  4. 4 Reconcile definitions and evidence, then operate your own database
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your indicator definitions, fields and reporting rules
  • check Your DevResults records brought across and reconciled
  • check Staff screens and partner access built for your process
  • check Another technology stack and connections where you need them
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access controls and backups
  • check Partner follow-up and reporting reviews prepared
  • check Maintained as your programmes and commitments change
  • check Run through Omni by Enterprise DNA alongside your other systems
Book a reporting review

Questions

Instead of DevResults, answered

Will this replace everything we use DevResults for? expand_more

The free version runs the internal reporting desk. Enterprise DNA can build the staff screens and partner access you need and connect collection and mapping services. Keep existing services until the new connections are installed and tested.

Can we bring our existing results across? expand_more

Yes. DevResults provides a reporting-period export. The import accepts its raw Excel worksheet or a CSV copy, keeps the original records and holds results for review. We reconcile your headings, definitions, periods and totals. Documents, narrative responses and other services need separate migration work.

Can we trust the totals when partners report differently? expand_more

Only after the reporting definitions and coverage have been checked. The free version distinguishes counts, weighted rates and snapshots, preserves corrections and shows incomplete results as unknown. Your reviewer still checks overlapping groups, collection methods and the underlying evidence.

Does a clean evidence check mean our reporting is compliant? expand_more

No. It identifies missing definitions, dates, targets and source evidence, and holds period closure when registered returns remain incomplete. Your reporting professional decides which framework applies and reviews the final statement. Working papers do not provide an audit opinion or prove that a programme caused a change.

How should we compare the cost? expand_more

Use your actual DevResults renewal and the services it includes. The vendor pricing page lists US$28,000 for the entry annual subscription, with setup and training separate, while its FAQ example differs. The free version has no licence fee, but hosting and operating time still cost. Enterprise DNA builds and runs your version for one setup fee, then a retainer.

Bring the renewal and one reporting period

In 30 minutes with Sam, look at your DevResults bill, the returns you chase and the evidence behind one reporting period. Agree what your own version needs and what Enterprise DNA would build and run.

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

Programme Results for Claude Code is free and open source, published by Enterprise DNA.

Done paying for DevResults?

Get your version built