Kumi by Maayins
Describe it.
Kumi builds it
in NetSuite.
Ask in plain words. Kumi reads your account, builds the scripts, records and fields you need, checks every change and deploys only after you approve.
Free plan, no credit card. Your first Health Check is read-only.
Request
▍
Kumi
How it works
From request to release.
You hold every gate.
Describe what you need
Brief Kumi the way you would brief a consultant. Attach a policy or spec if you have one.
“When a sales order over $50,000 is saved, email the finance controller.”
Kumi reads your account
Records, fields, forms and scripts involved, before anything is planned.
Nothing has changed in NetSuite.
Kumi builds a new version
Only what the request needs, as a version of its own. Live configuration is never overwritten.
Named the way your admins name things, so they can find it in NetSuite.
Automated checks
Structure, governance, conflicts and real situations, explained in plain words.
You approve, Kumi releases
Sandbox first. Production needs a second confirmation: the owner types the account ID.
Every change logged with before and after. Any version can be restored.
Platform
Your NetSuite team's work,
in one place.
Build
Built from a conversation
Scripts in SuiteScript 2.1, custom records and custom fields. Every build is a version you can follow from request to production.
- Every build is a version
- Never overwrites live configuration
- Moves 1.0 and 2.x scripts to 2.1
In progress
3
Live in sandbox
5
Live in production
12
| Build | What | Version | Status |
|---|---|---|---|
| Large order alert | Script, user event | 1 | Live in sandbox |
| Warranty end date | 2 custom fields | 1 | Waiting for approval |
| Credit hold check | Script, 1.0 to 2.1 | 2 | Live in production |
| Vendor bill PO rule | Script, user event | 3 | Reverted to 2 |
| Equipment register | Custom record | 1 | Building |
Check
Checked before it ships
Automated checks run on every change before it can reach NetSuite, including how it behaves in real situations.
- Structure, governance and naming
- Conflicts with your existing scripts
- Same behavior after a 2.1 move
Situations tested
- Order over $50,000Email sent to the controller
- Order under $50,000Nothing sent
- Order edited, still overNo second email
- Controller has no emailOrder saves, problem logged
Govern
Controls your auditors ask for
Approvals, a full audit trail and revert, on every plan. Nothing reaches NetSuite without the right person saying yes.
- The requester confirms the exact change
- Production needs the owner's confirmation
- Before and after for every write
Changes this month
18
Waiting for approval
2
Reverted
1
| Time | Who | What | Where |
|---|---|---|---|
| 16:05 | Owner | Confirmed production, typed account ID | Production |
| 14:32 | Kumi | Deployed Large order alert v1 | Sandbox |
| 14:20 | Controller | Approved Large order alert v1 | Sandbox |
| 11:47 | Admin | Reverted Vendor bill PO rule to v2 | Production |
| 09:12 | Admin | Asked for Warranty end date | Sandbox |
Health Check
Know what is wrong, read-only
A review of your configuration and scripts that changes nothing. Each finding explained, with a fix you can approve.
- Changes nothing in your account
- Fixed assets and scripts today
- Fixes go through the same checks
Findings
7
Needs a fix
2
Changes made
0
| Severity | Area | Finding | Next |
|---|---|---|---|
| Needs a fix | Fixed assets | 2 asset types have no accounting book | Fix proposed |
| Needs a fix | Scripts | 9 scripts on SuiteScript 1.0 | Move to 2.1 |
| Worth a look | Fixed assets | Disposal account shared with sales | Review |
| Worth a look | Scripts | 31 scripts on 2.0 or 2.x | Plan the move |
| Good to know | Scripts | 6 inactive scripts on 1.0 | Retire |
2028.2
NetSuite release
Scripts on 1.0, 2.0 and 2.x stop working.
Converting the code is the easy part. Kumi finds every script, rewrites it in 2.1 and checks that it still does what it did, before it goes live. Migration is included in every plan.
Scan my scripts freeGovernance
Safety is not a paid extra.
It holds on every plan.
Never touches money
Kumi never makes payments, approves or rejects transactions, or deletes records.
Recommends, you decide
On accounting and policy questions, Kumi lays out the options. Your controller makes the call.
Your keys stay locked
NetSuite tokens are encrypted per workspace and used only inside Kumi's gateway.
You see the exact change
Nothing is written until the person who asked confirms the exact change.
Pricing
Pay for jobs, not hours.
A job is one change that reaches NetSuite. Drafts, revisions and abandoned ideas are free.
Free
$0
Try Kumi on one account
- 5 jobs a month, one at a time
- 1 NetSuite account
- 1 user
- 2 Health Checks a month
- Bring your own AI key
- Email support
Without your own AI key, Health Checks run without explanations.
Starter
$499/mo
Companies with their own NetSuite admin
- Everything in Free
- 25 jobs a month, several at once
- 4 NetSuite accounts
- 5 users
- Scheduled Health Checks with alerts
- Kumi's AI included
- Email support, answered first
Extra jobs about $20 each.
Business
$999/mo
Replace part of a managed services contract
- Everything in Starter
- 100 jobs a month, several at once
- 8 NetSuite accounts
- 20 users
- Agreed response times
- Maayins experts at a preferred rate
Extra jobs about $20 each.
Enterprise
Custom
Large or multi-company groups
- Everything in Business
- Jobs agreed per contract
- Unlimited NetSuite accounts
- Unlimited users
- SSO
- Kumi's AI or your own
- Dedicated support
Every plan: automated checks on every change, the audit trail, revert, production confirmation and SuiteScript 2.1 migration.
FAQ
Questions, answered.
Your NetSuite backlog,
one conversation at a time.
Start with a free, read-only Health Check. Build when you are ready.
Start free