NetSuite SDN partner · Peterborough, Ontario

NetSuite work that still has a paper trail.

I mainly take the difficult SuiteScript problems others cannot solve: SuiteScript 2.1, integrations, and AI that has to survive an audit. Not admin work! I am Lee Young, the developer of QSmap.

Start a conversation QSmap product site

Four things I actually take on.

NetSuite development

SuiteScript 2.1, SDF, and SuiteApps. Governance, concurrency, platform limits, and customizations that have already beaten a ticket queue. Written to the same bar as a Built for NetSuite review — even when it never leaves your account. Not admin work.

Integrations

REST, middleware, and event-driven sync. The interesting part is not the first successful payload. It is retries, idempotency, and what the integration does when NetSuite is slow or a record is locked.

AI consulting for NetSuite

Where AI belongs in the account, where it does not, and which data must never leave. Strategy first: assistants, RAG over NetSuite records, and SuiteScript that calls models without turning your ERP into a prompt dump.

AI audits & testing framework

A review of data flow, prompts, permissions, and failure modes — then a SuiteScript test framework so AI-touched customizations have a regression net. If it cannot be tested, it does not belong in production.

Audit, then build, then prove it.

AI in NetSuite is easy to demo and easy to get wrong. The sequence is the product: we do not skip to a chatbot on top of customer records.

01
Audit
Map customizations, data classification, and the actual job. Decide what AI should touch, what it must not see, and whether the existing SuiteScript can carry it.
02
Build
SuiteApps, scripts, integrations, and the AI-assisted workflows that survived the audit. Written in SuiteScript 2.1, deployed via SDF, by the person you hired — not a bench of juniors.
03
Test
Custom SuiteScript is unit tested outside the account — locally and in CI — then it lands via SDF. Change a prompt or a script and you find out before production, not in next month’s close.

I build QSmap.

QSmap is a native NetSuite SuiteApp — not a sidecar with a sync job. Sales and marketing plot customers, prospects, leads, and more on a map, draw territories, layer saved searches, and export lists without leaving the account.

It is certified Built for NetSuite. Product, trial, and pricing live on the QSmap site. This page is the consulting practice that wrote it.

Continue to qsmap.net

QSmap showing customers, prospects, and leads clustered on a map of North America

Lee Young

Principal · 10+ years on NetSuite

I am a self-taught developer. I have been writing code since BASIC was a thing. I started my career as a mechanical engineer and used VectorScript and Visual Basic to automate VectorWorks and SOLIDWORKS. I then moved on to PHP websites, then to add-ins I built and sold for SOLIDWORKS PDM. Full-time developer since 2010 — .NET, PHP, and integrations the whole way. AI automation and NetSuite is the work now.

I run a one-person practice on purpose. I mainly take the problems that sit well above admin work; the ones that have already bounced off a partner, an in-house team, or a generic SI. A SuiteApp, a brittle integration, AI that has to survive an audit. Building QSmap is the public record that I finish hard things inside the platform.

“If we’re talking, I’m the one writing the SuiteScript.”

Straight answers.

Are you a NetSuite implementation partner?: I am a SuiteCloud Developer Network (SDN) partner: I build SuiteApps and custom code. If you need a greenfield SuiteSuccess rollout with a full implementation team, that is a different kind of firm. I often sit beside those partners.
Do you take admin work — workflows, saved searches, configuration?: No. If the work is SuiteFlow, saved searches, or day-to-day admin, you already have people for that. I take the engineering problems those teams cannot close.
Do you write scripts in the account?: The custom SuiteScript I ship is unit tested locally and in CI, then deployed with SDF. The account is not an editor.
What does an AI audit actually produce?: A written finding: data that would leave the account, permissions that are too wide, prompts that can invent records, and a recommended test set. Then, if we continue, the build and the framework.
Is QSmap part of consulting, or a product?: QSmap is a native SuiteApp sold on its own site. It is here as proof I ship marketplace software, not as a consulting add-on. Product questions go to qsmap.net; project work comes here.
Do you only work in Canada?: Based in Peterborough, Ontario. NetSuite work is remote. Time zones in North America are straightforward; further out we plan around them.

Tell me what is broken, or what you want built.

A short note is enough: account context, the constraint, and whether this is development, AI, or QSmap. I answer myself.

Open the contact form