Press and media

Company

Company facts.

Everything here can be quoted without checking back with us. Where a figure has a caveat, the caveat is part of the fact.

Legal entity

Nead, LLC, an Arkansas limited liability company doing business as DEV.co. Notice address 1425 Broadway 22689, Seattle, WA 98112. erp.io is a product of that company.

Funding

Bootstrapped. No venture capital, no outside investment, and no debt financing. Revenue comes from customers only — no vendor referral fees, affiliate arrangements, or sponsored content.

What the product does

An AI ERP platform and integration practice for US mid-market companies, roughly $5M to $150M in revenue. Financial core, projects, procurement, and agentic automation.

What it does not do

No manufacturing, MRP, or bills of material. No warehouse management. US-centric statutory coverage. Cloud only. These are published on our own comparison pages.

Published accuracy

Straight-through processing rates by workflow, from 94% on purchase order matching down to 66% on multi-line allocation, with the interquartile spread published. n = 23 customers.

Certifications

No SOC 2 Type I or Type II report held as of August 2026, and no ISO 27001. GDPR-compliant as a processor. We state this rather than describing controls as though they were certified.

Research available for citation

All of it is primary — measured from data we had access to rather than licensed or surveyed. Every paper states its sample size in the first paragraph and names the bias in its sample. Please cite with a date, because we revise on evidence and note corrections rather than applying them silently.

Agent benchmarks — straight-through rates by workflow with interquartile spread. n = 23 customers, 2025–2026.
Why ERP projects stall — primary cause analysis. n = 41 stalled or failed deployments. Requirements 31%, data quality 24%, decision authority 19%, software incapability 4%.
What we find in your data — n = 74 diagnostics. Median 8.4% vendor duplicate rate; 31% of companies had a closed period that did not balance; 64% had an account untied for over a year.
ERP pricing study — n = 63 real quotes. Median implementation 1.4× first-year licence; 2.1× spread between quotes for comparable scope; median +27% variance to original quote.
Close benchmarks — n = 38 finance teams timed at step level. Median 11 working days; 62% of elapsed time is waiting rather than working.
The 70% figure examined — citation analysis of 11 frequently quoted ERP failure statistics. Three had no traceable primary source.

Every sample we publish is small and we say how small in the first paragraph. A stated n = 23 is more useful to a reader than an unstated one.

What we will say on the record

Specific things about our own limitations, our pricing, our accuracy including the bad numbers, and where competitors are better than us. We rank fourth on our own ERP directory and we will explain why on the record.

We will also comment on category dynamics — the partner channel, undisclosed referral fees in selection advisory, the gap between announced and generally available AI functionality, and why nobody in this market publishes pricing.

What we will not do

Embargoed announcements or exclusives. We are not big enough for a news cycle and pretending otherwise wastes your time.
Customer names without permission. Ever, including in background conversation.
Comment on a named competitor’s security or financial position. We will discuss published product capabilities and nothing beyond that.
Growth or revenue figures. We are private and bootstrapped, and selective disclosure of favourable metrics is how misleading stories get written.
Anonymous quotes. If we say it, we will attach a name to it.

Fact-checking

Send us the passage and we will confirm or correct it before publication, quickly and without asking to review the rest of the piece. If we have something wrong on our own site, tell us and we will fix it and note the correction with a date.

Assets and usage

The name is written erp.io— lower case “erp”, and it is a product of Nead, LLC (d/b/a DEV.co). For logo files or screenshots, write to us and say what you need. There is no press kit download because a small company producing one is mostly producing it for itself.

Our own bias, for the record

We sell a product in the category we publish research about, which is a structural conflict a method statement does not remove. Our editorial policysets out the specific rules we hold ourselves to and the specific opinions encoded in our scoring weights. Please read it before citing us as a neutral source, because we are not one.

Questions

Common follow-ups.

Can we cite your research?

Yes, with attribution and a date. Every paper states its sample size and names its bias, and we note corrections rather than applying them silently.

Will you comment on competitors?

On published product capabilities, yes, including where they are better than us. Not on their security posture or financial position.

Do you share customer names?

Only with written permission, and never in background conversation. Several customers have consented to a factual listing and that is the extent of it.

Will you share growth figures?

No. We are private and bootstrapped, and selective disclosure of favourable metrics is how misleading stories get written.

How quickly do you respond?

One business day. If you are on a tighter deadline, say so in the subject line and we will do what we can.