AI implementation that survives production.
Agents, pipelines, and LLM integrations built by senior systems engineers — from people who spent two years writing publicly about where AI fails, and are therefore very careful about where it goes. AI earns its place in your stack, or it doesn’t ship.
01 / 02
What we build
Production AI, wired into the systems you already run — ERP, payments, support, operations.
- ▸ LLM-backed workflow automation inside NetSuite, payment stacks, and internal tools
- ▸ Agents with real guardrails: bounded tools, audit trails, human-in-the-loop where money moves
- ▸ Retrieval and document pipelines over your actual data, with quality evals before launch
- ▸ Integration with Anthropic, OpenAI, and self-hosted models — chosen per task, not per hype cycle
- ▸ Evaluation harnesses so you know it works before your customers find out it doesn’t
02 / 02
How we decide what gets AI
The most valuable sentence in an AI engagement is “this part doesn’t need a model.”
- ▸ Task-by-task triage: deterministic code where possible, models where they genuinely win
- ▸ Cost ceilings designed in from day one — see our AI cost engineering practice
- ▸ Failure-mode analysis first: what happens when the model is wrong, and who notices
- ▸ No resume-driven architecture — the boring solution wins ties
FAQ
Specifics, in plain English.
What's the difference between a SuiteScript and a SuiteApp?
A SuiteScript is a single script (Suitelet, RESTlet, User Event, Scheduled, Map/Reduce, etc.) that runs inside NetSuite. A SuiteApp is a packaged bundle of SuiteScripts, custom records, custom forms, and configuration that can be installed across NetSuite accounts and — if certified — listed on SuiteApp.com as Built for NetSuite. We do both, and we know which one fits your problem.
What is Level II / Level III payment processing and why does it matter?
Level II and Level III commercial card processing means submitting line-item data — purchase order numbers, ship-to addresses, item descriptions, tax breakouts — alongside the transaction. Card networks return lower interchange rates for B2B and corporate-card transactions when this data is present. For B2B businesses processing significant volume, Level III alone can pay for the integration work in months.
Can you help us migrate from SuiteScript 1.0 to 2.x?
Yes. SuiteScript 1.0 is deprecated and the migration is non-trivial — APIs are different, the SuiteScript 2.x runtime is stricter, and any code with implicit type coercion or loose error handling will break. We've done these migrations end-to-end without disrupting the production NetSuite account.
Do you do PCI-DSS-compliant payment processing?
We architect to keep PCI scope minimized — typically by tokenizing cardholder data at the processor or hosted-iframe boundary so internal services never see PANs. Whether the resulting system needs SAQ A, SAQ A-EP, or full SAQ D depends on your specific architecture. We've shipped against all three; the first call usually settles which scope is right for you.
Can you build Apple Wallet or Google Wallet passes?
Yes. We've shipped PKPass generation (Apple Wallet) and Google Wallet pass APIs end-to-end — for tickets, IDs, loyalty cards, and payment cards. The signing, image dimensioning, pass updates, and HTTPS hosting requirements are exacting; we know what trips up production deployments.
Are you US-based? Do you outsource?
Yes, US-based. Our registered office is Canyon Country, California. The senior engineer on every engagement is the founder. We do not subcontract code to anonymous offshore teams — when you talk to us, you talk to the people writing the code.
Do you sign NDAs?
Yes. We sign mutual NDAs before anything sensitive is shared. If a confidentiality agreement is a precondition for the first conversation, just say so in your initial message.
Not sure which of these fits your problem?
That is normal. Most of our engagements start with a 30-minute call where we figure out what you need, who else might be a better fit, and whether we should keep talking.
Book a discovery call