01
SuiteScript 2.1 Development
User Event, Client, Scheduled, Map/Reduce, RESTlet, and Suitelet scripts, designed around NetSuite's governance model so they keep working as your data grows.
I have been writing software professionally since 2016. Before NetSuite, I worked in backend and full-stack development: PHP and Laravel for web applications, Kafka for event-driven data pipelines, and microservice architecture for distributed systems. Designing systems that have to be reliable, auditable, and maintainable is the same job whether the platform is NetSuite or anything else.
Most NetSuite partners are strongest on the functional side: implementation, configuration, process design. The SuiteScript layer, with its custom logic, integrations, and automation, is a different discipline. It is software engineering, and it carries the same demands for testing, error handling, and maintainability as any other production system.
I set Ryzoa up as a specialist practice because this layer rewards depth. Most companies do not need a SuiteScript developer every day, but when they do, they need someone who does this work all the time rather than as a sideline.
Technical layer only
SuiteScript, integrations, and custom logic. Not functional implementation, not system administration.
Why it matters that this is a solo practice
One developer, start to finish.
In a consultancy, the person you speak to in the sales call is rarely the person who writes the code. Your problem gets translated through an account manager, passed to a project manager, and eventually reaches a developer who has never spoken to you and is working from a specification written by someone else.
With a solo specialist practice, none of that exists. I take the brief, diagnose the problem, write the code, and do the handover. If anything is unclear, you raise it with me directly. The person accountable for the outcome is the same person doing the work.
This also means I am careful about what I take on. I work with a small number of clients at any one time. If I do not think I can deliver the outcome you need, because the scope is wrong, the timing is wrong, or it is genuinely outside my area, I will tell you that during the first call.
Technical capabilities
What the technical layer work covers
These are the areas where I work. If your problem sits outside them, I will say so.
02
Integration Design and Build
RESTlets, SuiteTalk SOAP, REST Web Services, and third-party connectors. Error handling, idempotency, and audit trails are part of the design rather than an afterthought.
03
SuiteScript 1.0 → 2.1 Migration
A systematic audit and migration of legacy SuiteScript, including documentation of business logic that was never written down. Pattern by pattern, not a bulk rewrite.
04
Upgrade Safety and Governance
Finding and removing deprecated API usage, unsafe patterns, and hardcoded assumptions that break at NetSuite release time, then setting standards your team can follow afterwards.
Who I work with
Honest filtering
Not every NetSuite problem requires a specialist. This practice is the right fit for a specific situation.
Right fit
- 01You run NetSuite and need automation, integrations, or workflows built, with no SuiteScript developer in-house
- 02NetSuite needs to exchange data reliably with the systems around it
- 03Customisations have built up over the years and need an owner
- 04A requirement has landed that goes beyond what configuration alone can handle
- 05You want the technical layer owned by someone who works in it every day
Not a fit
- 01You need functional implementation support: requirements gathering, module selection, or process design
- 02The project is configuration-only with no SuiteScript or integration work
- 03You need a general NetSuite admin or day-to-day system support retainer
- 04You need someone available full-time, embedded in your operations team
Next step
Sounds like a fit?
Book a 30-minute technical review. Bring whatever you're planning to build, or whatever's misbehaving. I'll tell you whether I can help and what that would look like.