About iDev Systems

An engineering firm
that happens to know ERP.

iDev Systems LLC is an engineering consultancy and R&D firm. The distinction from typical ERP consulting is methodological — and it determines the quality of everything delivered.

01 · The Firm

A software engineering firm
that happens to specialize in ERP.

iDev Systems provides professional consulting in enterprise infrastructure architecture, systems integration, and the development of custom software. The firm specializes in the design and implementation of AI systems for enterprise operational efficiency, data analysis, and decision support.

The practice also engages in scientific research and experimental development — resolving technical uncertainty in software systems and algorithmic workflows where standard implementation approaches are insufficient. This R&D capacity is not incidental; it is the reason iDev can engage on problems that other consultants have reached the boundary of.

Most ERP consultants operate as feature configurators. iDev Systems operates as a software engineering firm that happens to specialize in ERP. That distinction is structural: it determines what work can be taken on, how it is delivered, and what the output looks like twelve months after an engagement closes.

SuiteScript 2.1
in TypeScript — not vanilla JS
SDF + CI/CD
source-controlled deployments
Spec-driven
requirements before code
R&D capacity
active research at the frontier
02 · Methodology

How the work
is actually done.

The methodology is not a differentiator by claim — it is a differentiator by practice. These are the specific engineering decisions that separate iDev deliverables from commodity consulting output.

→ spec.md
Specification-Driven
Every engagement begins with a formal technical specification. What the system must do, edge-case behavior, and acceptance criteria — written down before any code is written. This is the document that prevents scope drift and enables objective delivery assessment.
// TypeScript
Type-Safe SuiteScript
SuiteScript 2.1 in TypeScript means compile-time error detection, IDE tooling, and a maintainable codebase. In an environment where most developers still write vanilla JS, this is a meaningful difference in code quality and future maintainability.
$ git log --oneline
Source Control via SDF
All customizations are managed through SuiteCloud Development Framework — version-controlled, deployable via pipeline, auditable. The system documents its own history. No undocumented production changes.
✓ pipeline validated
CI/CD Deployment
Changes are validated and tested before reaching production environments. Automated pipelines eliminate the manual deployment risks that are standard practice in most NetSuite implementations.
03 · The Contrast

Commodity consulting vs.
engineering practice.

The difference between consulting that delivers a working system and engineering that delivers a maintainable one. Both produce go-live. Only one survives the following three years.

Dimension
Commodity ERP consulting
iDev Systems
Requirements
Implicit, verbal, discovered during build
Formal specification before implementation begins
Language
Vanilla SuiteScript JavaScript
SuiteScript 2.1 in TypeScript — type-safe, tooled
Deployment
Manual changes made directly in production
SDF-managed, CI/CD-validated, source-controlled
Integrations
Scripts. Fail silently. Diagnosed by inspection
Systems. Defined failure behavior. Observable
Documentation
Generated from institutional memory
Architectural documents produced as deliverable
At month 18
Customizations are feared — not understood
Codebase is maintainable by whoever comes next
04 · R&D

Operating at the
boundary of what exists.

iDev Systems engages in active research and experimental development to resolve technical uncertainty in software systems and algorithmic workflows. This is not a service offering — it is a mode of operation.

When a standard implementation hits a wall — algorithmic complexity, broken integration architecture, data model limitations — the question becomes whether the solution exists and needs to be implemented, or whether the solution itself needs to be discovered. iDev Systems is structured to do both.

The R&D work is most visible in the AI & Decision Support service, where the specific approach to a business problem is often uncertain and requires a research engagement before implementation begins. It also surfaces in complex integration and data architecture problems where established patterns are insufficient.

Engineering reference · github.com/mattplant
// In practice, this means

iDev takes on engagements where the client has been told the problem is not solvable, or where prior consultants ran out of depth. The R&D capacity exists to address the class of problems that standard ERP consulting cannot.

↳ Engagement types include
  • Novel AI/ML integration patterns in ERP environments
  • Complex data model redesigns under live-system constraints
  • Integration architectures for systems with no documented API contract
  • Algorithmic decision support where spreadsheet models no longer scale
Engagement

Bring the hard problem.

If your NetSuite implementation has hit a ceiling — technically, architecturally, or algorithmically — describe it. That is where this work starts.