Agentic AI becomes useful when it supports 1 real workflow. It does not become useful because it can discuss all company data. Start with 1 repeated decision, 1 primary source, and action limits that people can check.
A digital spreadsheet is not always an integrated workflow. A team can still copy figures from stock to a quote, then from a quote to an invoice. The data is on screen, but the status, decision owner, and change rules remain separate.
This article gives an initial design for connecting data without forcing every system into 1 physical database. Read company readiness in Indonesia for the AGI discussion before you choose the initial workflow.
Digital data does not always work together
A spreadsheet can store customer lists, stock, and prices. It may not give sales, warehouse, and finance the same answer. 1 person can change an old copy without telling the primary data owner.
An integrated workflow defines an event, owner, status, and evidence for each step. It also defines which system is the primary source. If stock changes, an unapproved quote must know about that change before the team sends it.
Do not start with the instruction, “connect all our data.” Map 1 workflow that often causes repeat work. Record its sources, readers, writers, business rules, and actions that require approval.
Unify the business identity, not every database
A unified business identity means that systems recognise the same customer, product, order, and document with consistent IDs. It does not mean the company must move all data into 1 physical database. CRM, stock software, and accounting software can remain separate primary sources.
Use an API, a path that lets applications exchange data under clear rules. Define which system can change each data type. Store the update time and version so that a system can reject stale data.
Use RBAC so people and agents access data only for their tasks. Keep an audit log, a record of who took an action, when, with which input, and with which result. These controls help a team trace an error without guessing.
MCP, or Model Context Protocol, can provide a standard path between an agent and approved tools or data. MCP does not replace permissions, price rules, or tool-result checks. The application must still enforce those rules.
After the team maps primary sources, data owners, and action limits, use AI Agent Ops Install to install access controls, audit logs, and procedures. Do not give an agent operational access before those control needs are clear.
Use Rama Business OS when several modules need the same identity, approval, and audit log. Start with the narrowest module so that the team can check its behaviour.
Illustration: a distributor from sales to invoice
This is a Rama Digital design illustration. It is not a customer case. A salesperson receives a request for 200 product units.
The agent can read the customer profile from CRM, available stock from the warehouse system, and discount rules from the official catalogue.
- Sales enters the request and customer code.
- The system checks the customer ID, product, and price version.
- The agent reads stock and creates a quote draft.
- Code rules calculate the price, tax, and discount limit.
- A manager approves the quote when its value passes a limit.
- The system reads stock again when it makes the actual reservation after quote approval.
- The system creates an invoice draft from the approved order.
- Finance approves the invoice delivery.
The agent must not invent a price when the catalogue is incomplete. It must flag missing data and request a check. Price and payment rules must run in code, not only in a prompt.
Keep links between records. A quote must store the request ID, stock ID, price version, and approval ID. These links help the system detect duplicate requests and prevent an invoice for a cancelled order.
When quotes, follow-ups, invoices, and approval form 1 operations problem, review OS Module: CRM. Define the scope and decision owner before you connect production data.
Choose a work pattern from the decision limit
This table is an original Rama Digital operational comparison. Anthropic distinguishes workflows that follow a fixed path from agents that choose steps and tools dynamically. Use this distinction as a design choice.
Do not give choice freedom when rules and order are already certain. Use code for fixed rules and an agent for choices with clear limits.
| Attribute | Deterministic automation | AI assistant | Bounded agent |
|---|---|---|---|
| Work path | Code defines every step. | The user selects the task and judges the answer. | The agent selects steps inside defined limits. |
| Main input | Structured data and fixed rules. | User questions, documents, or instructions. | Task state, official data, approved tools, and policy. |
| Action | The system runs programmed actions. | The assistant usually gives an answer or draft. | The agent can read, draft, or request approval. |
| Control | Input validation, tests, and code rules. | User review before using the result. | RBAC, audit logs, tool limits, approval, and rollback. |
| Example | Calculate tax from valid values. | Summarise meeting notes into a follow-up draft. | Prepare a quote from official CRM and stock data. |
Use deterministic automation for prices, payments, tax, minimum stock, and rules that must always match. Use an AI assistant for summaries or drafts that people still check. Use a bounded agent when work order can change but the data and action space remain clear.
Increase authority in phases
Start with the read phase. The agent can retrieve official data, show its source, and explain status. Test whether it selects the correct customer, product, and document version.
Continue with the draft phase. The agent can prepare a quote, email, or action summary. Store the draft with a task ID.
Do not send it, change a balance, or update primary data in this phase.
Use the approved write phase only after that. An authorised person approves sensitive actions, including financial actions, HR changes, invoice delivery, and customer-data changes. The system then runs the limited change and saves its result in the audit log.
For documents with scattered versions, sources, and approvers, use Sistem Dokumen Perusahaan. Do not send document contents, credentials, or sensitive data through a public form.
Test failures before you give write access
An agent that looks smooth in a demo can fail in operations. Design test cases before you expand access. These cases test the system, not only the model answer.
- Duplicate request: send the same request 2 times. Idempotency means 1 request produces 1 action. The system uses an idempotency ID so it does not create 2 quotes or invoices.
- Stale stock: change stock after the agent creates a draft. The system must read stock again at approval and when it makes the reservation.
- Hallucinated price: remove or replace the catalogue. The agent must stop and flag insufficient data.
- Injected instruction: include a customer message that asks the agent to ignore policy. The system must treat the message as data, not as a rule.
- Tool timeout: make an API fail to respond. A timeout means the tool response time has ended. The system records it, prevents blind repetition, and provides recovery.
- Change recovery: simulate a write that partly succeeds. The system must know which change happened and safely reverse or escalate it.
Do not use a prompt as the only protection. Apply schema validation, value limits, idempotency, response-time limits, limited retries, and change recovery in the application. Human approval remains necessary for sensitive financial and HR actions.
When data must run in the company environment, review Local AI Server untuk Perusahaan. Choose this path from verifiable data, operations, and infrastructure needs.
Build an integration that the team can maintain
Start with a simple contract between systems: ID, status, update time, owner, and failure condition. Document who can call an API and which response proves an action succeeded. Avoid integrations that depend only on copy and paste or shared account access.
Use Web Application Development when current systems lack needed apps, APIs, dashboards, or roles. Define acceptance criteria before the team gives an agent production access.
A quickly made prototype also needs review before it touches real data. When an older prototype has unclear access, incomplete logs, or untestable changes, use Vibe Code Rescue for an initial audit and stabilisation.
Evidence limits and the next step
The International AI Safety Report 2026 says agent capabilities are increasing, but basic errors and reliability limits remain. Use this as a reason to test system limits. The report does not promise that a design will work in your company.
Google Cloud Indonesia describes Indonesia BerdAIa, a programme that links data readiness, skills, and business needs. This is a vendor programme. Use it as context, not as proof of results or a vendor recommendation for every company.
After 1 workflow is stable, set the 90-day order through a 90-day AI transformation plan. Measure source quality, review time, repeat work, and incidents before you increase agent authority.
Frequently asked questions
Must company data go into 1 database?
No. Use consistent IDs, clear primary sources, role-based access, and traceable data exchange. Keep systems separate when they remain the primary source for a data type.
When can an agent create an invoice?
Start with an invoice draft from an approved order. Give write access after the system checks price, payment, stock, idempotency ID, and required finance approval.
Can an agent replace business rules?
No. Keep fixed rules, such as prices, tax, discount limits, and payment rules, in code or an official system. Use the agent to read context, create drafts, and route work inside those limits.
