Delivering Software Engineering Rigor to NetSuite

Where standard
implementation ends, engineering begins.

iDev Systems applies software-engineering rigor — specification-driven development, TypeScript, SDF, CI/CD, and AI — to ERP problems that refuse to resolve through configuration.

~/idev/engagement.spec
# specification-driven development
$ idev scope spec.md
  ↳ requirements formalized
  ↳ acceptance criteria locked
$ sdf deploy --pipeline
  → validating TypeScript...... ok
  → running integration tests.. ok
  → deploying to production.... ok
build shipped · audit trail preserved
$ _
01 / Approach

Most ERP consultants configure.
I engineer.

The difference is structural. Every engagement is specification-driven: requirements formalized before development begins, implementations source-controlled and pipeline-deployed, every deliverable auditable by the next engineer who touches it — including future me.

// TypeScript + SuiteScript 2.1
Type-Safe Development
Compile-time error detection and IDE tooling in an environment where most developers still write vanilla JavaScript.
$ sdf deploy --pipeline
SDF & Source Control
All customizations version-controlled and deployable via pipeline. No undocumented production changes.
✓ CI / CD validated
Automated Deployment
Changes validated and tested before they reach production. Every time.
↳ SDLC Modernization
SDLC Modernization
TypeScript, SuiteCloud Development Framework, and Git-based version control applied to NetSuite — driving superior code quality and lowering Total Cost of Ownership.
02 / Services

Five engagement types.
One methodology.

Each service is defined by the problem it resolves and the engineering approach that separates the work from commodity consulting.

01 / NETSUITE
Custom NetSuite Development
SuiteScript 2.1 in TypeScript. SDF project architecture, CI/CD pipelines, and RESTlet / Suitelet / API integrations built to be maintained — not just to function at launch.
Details
02 / ARCHITECTURE
ERP Strategy & Architecture
Data models, workflow design, integration patterns. The structural decisions that determine whether a system supports the business three years from now — or becomes a liability.
Details
03 / INTEGRATIONS
Integrations & Automation
System integrations with defined failure behavior, retry logic, and observability. When an integration breaks — and they do — the behavior is predictable and diagnosable.
Details
04 / AI · R&D
AI & Decision Support
Algorithmic decision support on live ERP data. Demand forecasting, anomaly detection, process intelligence — at the operational layer, not the reporting layer.
Details
05 / ADVISORY
Consulting & Code Review
Architectural review and technical decision support for teams with internal capability that needs senior external perspective on a specific, defined problem.
Details
ALL FIVE
Same methodology.
Same engineering standard.
Different class of problem.
03 / Manifesto

Most ERP consultants operate as feature configurators. iDev Systems operates as a software engineering practice that happens to specialize in ERP — a distinction that determines what work can be taken on, how it is delivered, and reduces the Total Cost of Ownership of the platform long after an engagement closes.

Matthew Plant · Principal · CS degree · 10 years NetSuite
04 / Standards

The specific practices that
separate deliverables.

Language
SuiteScript 2.1
in TypeScript — not vanilla JavaScript
Deployment
SDF + CI/CD
source-controlled, pipeline-validated
Process
Spec-Driven
requirements before code, always
Capacity
Active R&D
tools, systems, and AI at the frontier
05 / Open Source

Proof of practice.
Not just claim.

The methodology is published, not marketed. SuiteTools is an open-source reference implementation of how modern software engineering is applied to the NetSuite platform — available to read, fork, and audit.

github.com/mattplant/SuiteTools

SuiteTools

A React-based single-page application built in TypeScript and deployed to NetSuite via SDF from a monorepo. A working reference for how NetSuite development looks when software engineering rigor is applied from the first commit.

View on GitHub
StackTypeScript · React · SDF
ArchitectureMonorepo · SPA
DeploymentSDF pipeline
LicenseOpen Source
06 / Engage

Facing a problem standard
implementation can't resolve?

iDev Systems engages at the boundary of what enterprise software currently supports. If you've hit a ceiling — architectural, algorithmic, or integrative — that's where this work begins.

Responsewithin 1 business day
Intakecontact form
Engineering refgithub.com/mattplant
PrincipalMatthew Plant