# Ara finishes the work. Your team decides. > AI employee inside Slack, Teams and KakaoTalk. Ara takes each department's recurring work, returns finished files and waits for approval before anything leaves. Canonical: https://grinda.ai/en/products/ara Last updated: 2026-09-16 Hand over work in Slack, Teams or KakaoTalk and get the finished file back. Anything that leaves the company waits for a person to approve. Free consultation · Reply within one business day · No commitment Nothing new to learn. Invite Ara into the messenger you already use. Slack · Microsoft Teams · KakaoTalk · Naver Works · Telegram · Messenger · Instagram · WhatsApp · SMS · Google Chat · Discord · Dashboard · API · MCP ## AX is not a new tool. It is a new way of working. Chatbots give answers. Employees finish the work. That is why every employee has a chatbot and the company's work has not changed: taking the answer, moving it into a sheet, posting it and doing it again next week is still a person's job. ### Deliverables, not answers - Today: Copy the answer into a sheet, then post it in the messenger. - With Ara: The finished sheet, doc or PDF lands in the thread. ### The method stays when people move on - Today: Know-how lives in someone's head and leaves with them. - With Ara: How the job is done is kept as files, so the next run is more accurate. ### A record of who did what - Today: Nobody knows what the AI looked at or what it sent. - With Ara: What it read, what it did and what went out is recorded on every run. ## Here is how a week runs once Ara joins the team. Each department gets a colleague with its own brief, but all of them read the same company documents and the same way of working. Scheduled work runs on its own; anything that leaves the company stops in front of a person. *Example scenario* - **Mon 09:00 · Finance** — Last week's revenue and spend report posts to #finance. People only read it. (Scheduled, runs on its own) - **Mon 11:20 · Sales** — Follow-up drafts are ready for every account silent for over three weeks. Sending waits for the owner's approval. (Awaiting approval) - **Tue 08:30 · Support** — Overnight tickets are sorted, each with an answer draft based on our own documentation. (Draft) - **Wed 14:00 · Marketing** — Next month's content plan, built from customer search terms, lands in the thread with carousel drafts. (Draft) - **Thu 16:00 · IT** — Post-deploy error trends are checked and a customer-readable release note is written. Publishing waits for approval. (Awaiting approval) - **Fri 17:00 · Leadership** — A summary of what Ara read, did and sent this week arrives, run by run. (Scheduled, runs on its own) Why this counts as AX: - No new tool, the messenger you already use - One team, two or three jobs to start - People decide, Ara executes - Every run recorded, results in numbers ## Every department, starting with the weekly grind. No new process to design. Pick from the work you already do and hand it over. Anything that leaves the company, like sending or submitting, is always approved by a person. ### Sales — Quiet accounts get chased first - Follow-up drafts for accounts that went quiet - Company and contact brief before a meeting - A quote written to the terms from the call ### Finance · Operations — The Monday report posts itself - Receivables status and staged reminder letters - Monthly spend by category, as a sheet and a chart - The weekly report, every week, on time ### Marketing — Briefs and carousels arrive as drafts first - A month of content briefs built from what customers search - Carousels, banners and short intro videos - Watch for competitor price and page changes ### Support · Operations — Inbound tickets wait already sorted - Triage and reply drafts from your own documents - Briefs before meetings, decisions and owners after - Scheduled checks and reports ### People · Leadership — Only what a decision needs, laid out - Applications screened against the posting, decisions stay human - Market and competitor briefs with sources - Today's priorities from your calendar and inbox ### IT · Engineering — Screens without an API, worked like a person - Error trends after a deploy, with a verdict - Release notes a customer can read - Legacy ERP and supplier portals, worked on screen Connected apps: HubSpot · Salesforce · Gmail · Google Calendar · Google Drive · Notion · Google Sheets · GitHub · Linear — and the apps your team already uses. Which tools each app exposes is a switch you set. ## Only what you switch on. People approve what leaves. The wider the rollout, the more control matters over features. Ara was built in that order, and security review answers come from the actual configuration. ### Only the tools you switched on Every app has tool switches, and a tool that is off cannot be used by anyone. A colleague's tool list can only be trimmed, and the default is read-only. ### Scope set per department Each colleague is limited to drafts only, ask before acting, or act. A workspace admin can also require approval for every change in an app, or block the app outright. ### Only people approve Sending, deleting, paying or deploying stops with a preview and waits for the owner. Only a signed-in member can decide, and an API key can never approve its own request. ### Every run is an audit record What was read, what was done and how long it took is kept for every run, failures included. Access to personal data is logged with account, time and IP, purged on a retention schedule, and exportable as CSV. ### Access control on your terms IP allowlists, automatic disconnect after inactivity, password rules and API key expiry are set per workspace. Nothing can be loosened below the floor the deployment sets. ### Your data, your location Customer data is used only to handle the request and never to train a model. Each workspace runs in an isolated sandbox and tokens are stored encrypted. Choose our cloud, a dedicated tenant, on-premises or a fully air-gapped network. The subprocessor and cross-border transfer disclosure and the security checklist are generated from the deployment's own configuration, not written by hand. We answer your review form in the consultation. ## One team, two or three jobs to start. You do not have to decide on a company-wide rollout first. Start small, check the numbers, then widen. 1. **Diagnostic call** — In 30 minutes we go through the work your team repeats every week and the systems to connect. 2. **Pilot** — One team hands over two or three jobs. We build the skills and do the integrations. 3. **Rollout** — Add a specialist colleague per department and design approval rules and permissions for your organisation. 4. **Operations** — We review what ran with you every month. On-network and air-gapped deployments get a dedicated engineer. Korean SMEs can lower the upfront cost with government AX and data vouchers. [See the Grinda AI AX program](https://grinda.ai/en/ax) ## Questions asked before adopting ### Can we get security review material? Yes. Access logs, IP allowlists, idle disconnect, retention periods and password rules are set per workspace, and the processing and cross-border transfer disclosure and the security checklist are generated from the actual configuration. In the consultation we answer in your own questionnaire format. ### Does it work on our network or in an air-gapped environment? Yes. Choose between our cloud, a dedicated tenant, your network or a fully air-gapped environment. You can also dedicate one office PC to Ara so it works with the accounts signed in on that machine. ### Does it connect to our ERP and groupware? Apps like CRM, email, calendar, documents and code repositories work as soon as an account is connected; internal APIs and data warehouses are scoped in the consultation. Legacy screens with no API are worked by Ara signing in like a person, and it always asks before submitting. ### If someone gives a wrong instruction, can anything leave the company? Only what you switched on. Every app has tool switches, and a tool switched off cannot be used by anyone. Set sending, deleting and paying to review and they stop with a preview and wait for approval. Only a signed-in member can approve. ### Is our data used to train models? No. Runs happen in an isolated sandbox per workspace, tokens are encrypted at rest and never written into the sandbox, and every run is logged line by line. ### Which messengers work, and does it work in Korean? Slack, Microsoft Teams, KakaoTalk and Naver Works, as well as Telegram, Google Chat, Discord and others; if you would rather attach nothing to chat, use the dashboard alone. Ara answers in the language your team uses, and with a working language set, reports and approval cards follow it. ### How long does adoption take, and what does it cost? After the diagnostic call, one team starts a pilot. Pricing is quoted by the number of systems connected, the number of colleagues and the deployment model. There is no per-seat fee and monthly plans are the default; on-network deployment and SLAs are set by contract. Korean SMEs can combine it with government AX and data vouchers. ## Related - [Rinda](https://grinda.ai/en/products/rinda) - [See the Grinda AI AX program](https://grinda.ai/en/ax) - [Scenarios](https://grinda.ai/en/use-cases)