About iDev Systems

An engineering firm
that happens to know ERP.

iDev Systems LLC is my software engineering practice. I bring the methods of modern software development to NetSuite.

01 · The Practice

Software engineering,
applied to NetSuite.

I'm Matt Plant, founder and principal engineer. I design and build complete NetSuite solutions: the custom software, the integrations around it, and the architecture that holds it together.

A decade in NetSuite across manufacturing (MRP, WIP, BOMs), supply chain (3PL, procurement), order-to-cash and procure-to-pay, and retail and omnichannel eCommerce.

Configuration takes NetSuite a long way. My work starts where it runs out, and it's built so whoever comes next can maintain it.

A decade
in NetSuite
CS degree
computer science
Remote
US Pacific time
Open source
SuiteTools, the method in working code
02 · Methodology

How the work
is done.

Four practices, on every engagement.

→ spec.md
Specification-Driven
Every engagement starts with a written specification: what the system must do, its edge cases, and how to tell it's done. It keeps scope fixed and delivery measurable.
// TypeScript
Type-Safe SuiteScript
SuiteScript 2.1 written in TypeScript: errors caught at compile time, full editor support, and code the next developer can read.
$ git log --oneline
Source Control via SDF
Every customization lives in source control and deploys through SDF. The history is the documentation, and nothing changes in production by hand.
✓ pipeline validated
CI/CD Deployment
Every change is validated and tested automatically before it reaches production.
03 · The Contrast

Commodity consulting vs.
engineering practice.

Both reach go-live. Only one is still easy to change three years later.

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
Three years later
Customizations nobody dares touch
Codebase is maintainable by whoever comes next
04 · R&D

When the answer
isn't known yet.

Some problems don't have a known solution. Before committing to a full build, I run a scoped proof of concept that answers the technical question first. The full solution is then built on what it proved, not on a guess.

// For example
  • Complex data model redesigns under live-system constraints
  • Integration architectures for systems with no documented API contract
Engagement

Bring the hard problem.

If your NetSuite system has hit a limit configuration can't fix, describe it.