Enterprise Platforms
The systems of record I design against, integrate, and hold to account.
NetSuite (ERP, primary) · Salesforce (CRM) · Coupa · Oracle EBS · Avalara · Vertex · Stripe · Workday · Paycor · Zip · Rocketlane
Multi-agent finance intelligence for NetSuite
A production-grade system of specialized AI agents that lets people ask their ERP real questions, in plain language, in real time.
The problem
An ERP already holds the answer to almost every question a finance team asks. What it lacks is the interface. Getting from "which invoices are about to age past 60 days" to an actual number means saved searches, report builders, and someone who knows exactly where to look.
The harder questions are worse, because they cross subledgers. Collections exposure touches receivables and reporting; a clean quarter summary touches AR, AP, and revenue at once. No single report answers them. A person does, slowly, by stitching modules together.
The system
This system puts a natural-language chat interface on NetSuite, built in Python on the Model Context Protocol (MCP). One orchestrator agent reads each query, routes it to the specialists that own the answer, coordinates them, and synthesizes a single response, including cross-functional answers no individual agent could produce alone.
Each specialist agent is scoped to one financial domain and reaches NetSuite only through MCP tool contracts, so every capability the system has is explicit, typed, and enumerable. Queries resolve against live ERP data, not an export.
| Agent | Domain | Answers for |
|---|---|---|
| Orchestrator Agent | Coordination | Routes queries, coordinates the specialist agents, and synthesizes cross-functional answers. |
| AR Agent | Accounts Receivable | Invoices, customer payments, aging, and collections insights. |
| AP Agent | Accounts Payable | Vendor bills, expenses, and payment status. |
| Revenue Agent | Revenue Recognition | Revenue recognition, deferred revenue, and ARR/MRR breakdowns. |
| Procurement Agent | Procure to Pay | Purchase orders, vendor records, and approval workflows. |
| Reporting Agent | Analytics | Financial summaries and ad-hoc analytics. |
Guardrails
The design rule behind it is the same thesis as the rest of my work: the deterministic 80% stays deterministic. The LLM is reserved for what actually needs language (understanding the question, routing it, and synthesizing the answer) while the data access underneath stays scoped, observable, and auditable per agent. Guardrails are the architecture, not a feature flag.
Python · Model Context Protocol (MCP) · NetSuite (live ERP data) · Multi-agent orchestration · LLM-backed routing & synthesis
What I architect
ERP Domain
The full ledger lifecycle (order to cash to close) treated as one architecture, not separate projects.
Order to Cash (O2C) · Procure to Pay (P2P) · Record to Report (R2R) · Revenue Recognition (ASC 606) · Billing & Subscription Management
Integration & Middleware
Pipelines built to fail loudly, retry safely, and leave a trail.
Celigo (iPaaS) · REST / SOAP APIs · Middleware design · AWS pipelines (S3, Transfer Family, SFTP) · CI/CD · Retry frameworks · Observability tooling
Engineering
Enough depth to build what I design, and to know what shouldn't be built.
SuiteScript 1.0 / 2.x · TypeScript · JavaScript · Python · React · Backbone.js · SuiteCommerce Advanced
Data & Analytics
High-volume financial data made queryable, reconcilable, and fast.
SQL · SuiteQL · SuiteAnalytics · High-volume Map/Reduce processing
AI & ML
Agentic systems with guardrails first: the 20% that actually needs an LLM.
Agentic systems · Model Context Protocol (MCP) · LangGraph · LangChain · LangSmith · CrewAI · RAG & embeddings · AI observability · LLM-backed routing & synthesis · Python
Governance & Quality
Controls designed in from day one, not bolted on for the audit.
SOX controls · Audit processes · Role-based access · SIT / UAT / regression · API & integration testing · Data reconciliation & validation
Certifications
| No. | Credential | Issuer | Year | Featured |
|---|---|---|---|---|
| 3100 | NetSuite Certified Application Developer | Oracle NetSuite | 2023 | Featured |
| 3200 | NetSuite Certified Web Services Developer | Oracle NetSuite | 2023 | Featured |
| 3300 | NetSuite Certified SuiteCloud Developer | Oracle NetSuite | 2023 | Featured |
| 3400 | NetSuite Certified SuiteCommerce Developer | Oracle NetSuite | 2018 | Featured |
| 3500 | NetSuite Certified SuiteFoundation | Oracle NetSuite | 2022 | Featured |
| 3600 | NetSuite Certified AI Foundations Associate | Oracle NetSuite | 2025 | Featured |
| 3700 | Claude 101 | Anthropic | 2026 | Featured |
| 3800 | Claude Code 101 | Anthropic | 2026 | Featured |
Writing
Your first LLM API call on Groq's free tier
Make your first LLM API call in about ten minutes on Groq's free tier. Step-by-step tutorial with curl and Python, API key setup, and common error fixes.
Groq · LLM · API
2026-07-12
The real cost of an LLM in production: a working ledger
Token pricing is the smallest line item. A cost model for agentic workloads (context windows, retries, caching, evaluation) built the way finance would build it.
LLM · Cost · Agentic Systems
2026-07-17
About & contact
Twelve years ago I started automating the unglamorous middle of the enterprise: orders, invoices, ledgers, the systems that have to be right. Since then I have designed and scaled back-office platforms for high-growth businesses: API-driven architectures, financial and operational workflows, and SOX-compliant systems that pass audits without heroics.
That work now converges somewhere specific: AI-driven financial automation. Not chatbots bolted onto an ERP, but agentic systems with guardrails, observability, and reconciliation designed in from day one, so the people who actually run the business can ask their systems real questions and trust the answers.
On file- Hyderabad, India
ASK-000 ready: pure keyword routing over the site's content layer. Try “flagship”, “writing”, “github”, or “help”.