I build systems around the way the work actually happens.
I build and troubleshoot business systems, NetSuite customizations, web tools, data flows, and workstation environments. The common thread is practical technical work that has to keep working after the handoff.
Companies and teams I’ve supported.
Experience across NetSuite and business systems, software and web work, operational automation, and earlier database / IT support.
01TreveraCurrent role · systems / NetSuite
02Empire Auto PartsClient support · business systems
03ARYCS TechnologiesClient support · NetSuite / data
04ZeagerClient support · ERP / automation
06MulhollandEarlier technical support
07SIG SauerDatabase / IT support
08SRNADatabase / IT support
09SumitomoDatabase / IT support
10MagnaFlowDatabase / IT support
Company names identify organizations supported across different roles and types of work; they do not imply endorsement or that every engagement involved the same services. Public project details are intentionally limited to non-proprietary information.
Technical work tied directly to operations.
Open a service for a little more context. The detailed Services page goes deeper into scope, typical problems, and related project writing.
01NetSuite development & troubleshootingSuiteScript, SuiteQL, records, forms, transaction behavior, and debugging.
I build new NetSuite behavior when native configuration is not enough, but a large part of the work is investigative: tracing which script, workflow, form, permission, or configuration source is actually responsible for a bad result before changing anything.
View service details →02Approval systems & SuiteFlowMaintainable approval routing, exception handling, workflow state, and business-owned configuration.
I work on approval systems that have outgrown a simple supervisor chain, with an emphasis on making changing business values configurable and keeping routing behavior understandable enough to troubleshoot later.
View service details →03Data migration, imports & reconciliationCSV imports, record relationships, duplicate analysis, and Sandbox-to-Production mapping.
I treat imports as data-model work rather than spreadsheet formatting. That means validating parent/child relationships, references, destination IDs, record status constraints, and the actual post-import result.
View service details →04Integrations, SFTP & transaction outputREST/SOAP/SuiteTalk, file movement, payment formats, FreeMarker, and operational documents.
These projects start with the downstream consumer: what a bank, shipping team, customer, API, or file-processing system actually needs, then how NetSuite can produce it reliably and securely.
View service details →05PC systems, hardware & technical supportCustom builds, upgrades, workstation configuration, Windows setup, hardware diagnosis, and practical IT support.
I have built, upgraded, configured, and troubleshot PC systems for years. That includes matching parts to the actual workload, resolving hardware and driver issues, tuning thermals and stability, rebuilding Windows environments, and helping people avoid spending money on the wrong component.
View service details →06Web systems & internal toolsCustom WordPress development, account systems, permissions, security flows, and connected tools.
I am most interested in web work where the site is doing real operational work: authentication, role-aware experiences, custom plugins, account management, administration, or integration—not just brochure-site assembly.
View service details →Start with the process, not the script type.
I try to find the smallest durable fix. That means understanding the real workflow before deciding whether the answer is configuration, SuiteFlow, SuiteScript, data cleanup, an integration, or something outside NetSuite entirely.

- 01Trace the current process
Who touches the record, what triggers the next step, where the data comes from, and what people do manually today.
- 02Find the actual failure point
Separate configuration, permissions, workflow state, script logic, data, and integration behavior instead of patching the symptom.
- 03Choose the smallest durable fix
Use native behavior where it fits, workflow where it stays maintainable, and code where the requirement genuinely needs it.
- 04Test the ugly cases
Missing mappings, duplicates, environment differences, role restrictions, boundary values, and failure paths are part of the build.
- 05Leave it supportable
Keep changing business values outside deployed code where practical and document the pieces someone will need later.
Tell me what the system does today and what you need it to do instead.
You can use the quick project form without leaving the page, or open the full Contact page if you want to provide more context.