Autofill is how the agent enters software. Ultimate Yearly is the workforce on those systems — Auto-Fill, worker, HITL, connectors — not a new SIEM, ERP, bank, or warehouse. AI Workforce is the expansion core. The other six are where that workforce is sold.
01Don't be a SIEM
Cybersecurity
SSO/SCIM, dual control, block card/SSN, fill receipts, security pack, VPC request. Org IAM. Zero Trust for the agent — who may fill, which fields are forbidden, sandbox. Field-level DLP. Audit export to the customer's SIEM. Edge controls (JWT, ACL, mTLS into VPC) for the path the agent uses to enter systems — security the org cannot skip on that path.
Never. Not an endpoint agent vs CrowdStrike. Not cloud CSPM. Not a 24/7 SOC. Not CyberArk-class PAM. Not a replacement for the rest of the security stack.
02The expansion core — priced against labor
AI Workforce
Digital operators on software you already run: worker jobs, connectors, generate pipeline, exception / HITL queue, hours-saved. Each record walks ingest → enter software → rules → act → review → report, with retries and resume after HITL. Fills on a licensed customer device — not a Ranasi-hosted browser farm. Priced against FTE replaced, not another SaaS seat.
Never. Not a chatbot that only answers. Not a billing engine. Customer-service and finance skills are actions on the customer's portal (refund, subscription, invoice post) — Ranasi does not become the system of record.
03Connect. Do not create.
ERP / core systems
The operating layer on the ERP you cannot rip out. First live skill: invoice → match PO → tax check → fraud signal → open HITL if it does not match → a licensed device posts on the customer SAP / NetSuite / Odoo screen. Live records: csv_upload, webhook, or erp_feed from the customer's iPaaS. SAP/NetSuite/Odoo kinds stay mapping-at-kickoff — Ranasi does not ship those vendor APIs.
Never. No accounting, inventory, payroll, or general ledger. We do not replace SAP, NetSuite, or Odoo.
04Recommend, then act — not a data lake
Decision intelligence
Hours-saved, portal drift, fill evidence (hashes only). GET /v1/org/intel recommends from those counts; POST /v1/org/intel/act enqueues a worker job for drifted portals or sends you to HITL. Pixels and typed values stay on the device. Not a separate intel product.
Never. Not a customer data lake. Not Palantir. Not a dashboard that cannot execute.
05Playbooks on the portals you already file in
Compliance / RegTech
The closest market after AI Workforce. KYC, IT-access, and security-incident templates already ship. Yearly adds vault + generate pipeline + evidence pack — an audit trail that survives examination. Playbooks on the regulator and carrier portals you already file in.
Never. Not Onfido, not ComplyAdvantage, not the bank's core KYC/AML engine. We are the layer people fill and review on supervised portals.
06A skill — not a processor
Financial infrastructure
Invoice-to-ERP, reconciliation-shaped jobs, fraud signals from abnormal fill patterns, billing ops on the customer's own portal. If we take a share of money movement, it is a fee per job the agent completes (for example per invoice posted) — not interchange.
Never. Not a payment processor. Not 0.1% × volume. Not credit, treasury core, or a bank. Those require a financial institution.
07Same as ERP: the operating layer
Supply chain / industrial
Agents on ASN, customs, vendor-onboarding, and 3PL portals — portal by portal, the same operating-layer model as ERP.
Never. Not MES. Not WMS. Not PLC. We do not run the factory or the warehouse.
These seven markets are the sell. Ranasi is the operating layer for an AI workforce on them — not a new SIEM, SAP, Palantir, Stripe, or warehouse. Switching cost stays with the system of record. We hook it.