A team, not a chatbot
Seven specialists and a Team Leader, each responsible for a stage. Every response identifies the agent doing the work.
RPA STUDIO · BY ACSYSTEM
A team of RPA specialists,
inside your Claude or Codex.
Describe your everyday repetitive task. Six specialists, each with a distinct role, take it all the way to a ready, tested and running Python robot. You approve the stages without needing to code.
MCP connectionClaude Code and CodexNo per-robot licenseIndependent review
Building the brand
> Menu
🤖 RPA Studio · Team Leader · menu
Active project: Receipt issuance report (Portuguese Tax Portal).
The QA Analyst approved the tests. Next step: acceptance testing with you.
analysis ✓architecture ✓development ✓setup ✓qa ✓deployment …
> Run the project
🤖 RPA Studio · Deployment Engineer · deployment
Run complete: 42 receipts processed, 0 failures, 1 pending action
(MFA requested by the portal). Evidence and summary saved.
Would you like to choose how the robot will run?
No AI in productionthe robot follows the same rules every time
Independent reviewat every stage
Passwords stay in the vaultnever in chat or code
No duplicate actionsrerunning does not duplicate entries
WHY RPA STUDIO
AI speed. Software predictability.
AI works where it excels: understanding processes, writing code and testing it. In production, a Python robot follows the same rules every time, with no AI cost per run.
You decide at the right moments
Analysis, architecture, setup and final acceptance wait for your approval. The rest moves forward on its own.
Quality enforced in code
An independent reviewer checks each deliverable against evidence. Any criterion without proof counts as a failure.
Transparent costs
Each project shows its cost by stage and compares the time with Power Automate Desktop and UiPath.
WHAT IT AUTOMATES
If it repeats and follows rules, it can become a robot.
From simple tasks to complex workflows spanning multiple systems.
Portals and websites
Signs in with your access, searches, fills out forms and downloads documents. Example: monthly receipts from Portugal’s Tax Portal.
Windows applications
Operates programs installed on your computer, clicking and typing as a person would.
Spreadsheets and files
Reads, cross-checks and generates Excel files, PDFs and reports.
Systems with APIs
When a system has an API, the robot communicates directly with it: faster and more reliable than clicking on screen.
Work queues
Receives requests from a SharePoint list, spreadsheet or database and marks each as completed or failed.
Insurance
claims reporting · policy issuance
Finance and accounting
supplier invoices · bank reconciliation · receipts from Portugal’s Tax Portal
HR
employee onboarding · leave schedules
Operations
daily reports across systems
HOW IT WORKS
Six stages. One specialist for each.
Each agent works only from the previous stage’s deliverables, with a clean context. At marked stages, nothing moves forward without your approval.
Team Leader
It all starts with “Menu”.
The Team Leader talks with you, organizes the project, calls in the specialist for each stage and pauses where the decision is yours.
01You approve
Analysis
Documentation Analyst
- What it does
- Reads the documents, screenshots and spreadsheets you provide and defines what the robot must do, including the process flowchart. Anything missing becomes a question, never an assumption.
- You
- Provide documents, or simply describe the process.
- Deliverable
- Analysis, flowchart, sourced requirements and functional documentation.
After delivery · on request
Support Analyst
Has the robot stopped or failed? Type “Menu” and choose Support. The agent reads the execution logs, reproduces the issue, finds the cause, fixes it, tests it, validates it with you and documents the incident.
Evolution
Only what changes
An improvement reopens only the affected work. A new rule returns to analysis; a workflow change returns to architecture. The rest of the approved robot stays as it is.
MCP CONNECTION
The team joins the tool you already use.
MCP connects Claude Code or Codex to the RPA Studio methodology. The server guides each stage; the robot is built and run in your environment.
PRODUCT ARCHITECTURE Illustrative demonstration
Your assistant Claude Code / Codex
RPA Studio MCP server · 6 agents
Your robot Python · local execution
Your environment Files and local vault
01 / REQUESTThe RPA Studio server delivers instructions and templates; it does not access the customer’s disk. Content shared with Claude or Codex follows the relevant AI provider’s settings and policies.
Receive access
Arrange the demo and terms. ACSystem provides the address and personal token.
Connect your tool
Add the MCP server to Claude Code or Codex on your computer.
Confirm the connection
Check the available servers and approve the use of RPA Studio.
Type Menu
Open the robots folder. The Team Leader presents the projects and the next step.
GUIDED CONFIGURATION
One connection.
Six specialists.
After the demo, we confirm the solution and access terms with you. ACSystem provides the address and personal token.
Configuration examples. The server’s public address is still being prepared. Replace the placeholders only on your own computer after receiving access details.
Get help starting ↗[Environment]::SetEnvironmentVariable("ACSYSTEM_TOKEN", "<O_SEU_TOKEN>", "User")
# Close and reopen the terminal before continuing
codex mcp add acsystem-fabrica-rpa --url "<ENDEREÇO-DO-SERVIDOR>/mcp" --bearer-token-env-var ACSYSTEM_TOKEN
codex mcp listClose and reopen the terminal after setting the variable, before adding the server. Then open the robots folder, approve the connection and type Menu.
BUILT-IN QUALITY
Nobody reviews their own work.
Quality control is a process rule enforced in code, not in conversation.
Independent reviewer at every stage
Before you receive a deliverable, a reviewer who did not produce it checks it against a criteria list by opening files, screenshots and pages. Criteria without evidence fail.
QA verifies, the Developer fixes
QA rejects with evidence: stage, item, error type and source, screenshot and reproduction steps. The Developer fixes it with a clean context and returns it directly to QA.
Clean context between stages
Each specialist receives only the previous stage’s deliverables. Less noise, fewer errors and lower cost per response.
Learns from every project
Lessons from each system are saved and reused in future robots. Work is not repeated if the input document has not changed.
What QA verifies in every robot
- Simulation without side effects (dry run)
- Runs twice without duplicates
- Correct pause at MFA and CAPTCHA
- No personal data in logs
- Automated robot tests
- Acceptance criteria from analysis
Formal QA verdict
approvedwith reservationsinconclusiverejected
Reviewer decision in each round
approvedsent to you
reworkfix and review again
3rd roundyou decide
CONFIGURATION
A setup panel. You choose where it lives.
The robot never has passwords or fixed values in its code. Everything it needs is in a panel with a section per system, progress tracking and missing items. If setup is incomplete, the robot refuses to run and explains what is missing.
Only on this computer
Local database and passwords in the operating system vault. Nothing else to configure.
Excel spreadsheet
Tabs for parameters, work queues and encrypted secrets.
SharePoint list
Parameters, work queues and credentials in your company’s lists via Microsoft Graph. Sign in with your own account or certificate.
Company database
SQL Server, MySQL or Oracle, with tables created from the project itself.
Passwords are never shown again
In shared storage, secrets are encrypted with the team key, kept only on authorized machines. Anyone opening the list or table sees encrypted text only.
The structure comes from the project
One column per credential used by the process. Existing lists and tables are reused and extended only where needed, with a plan shown beforehand.
Connection guide
The Setup Specialist explains how to connect each destination, starts with the simplest route and points to official documentation.
DEPLOYMENT
Four ways to keep your robot running. The choice is yours.
After acceptance testing, the Deployment Engineer presents the options, recommends one and waits for your decision.
Scheduled in the assistant
Claude or Codex starts the robot on schedule and summarizes the result.
For those who prefer no extra setup. Uses plan credits per run.System scheduler
Windows Task Scheduler or Linux crontab, created with a command.
No per-run charge and no need to keep the app open.Single executable
An .exe with the browser included, opening setup in two clicks and scheduling itself.
For computers and servers without Python.On request
Ask to “run the project” whenever you need.
For occasional processes or those requiring MFA on every access.LOGGING AND SUPPORT
Every run leaves evidence of its work.
Each stage is logged with its duration and screen. If something fails, the robot saves where and why, a screenshot and a browser recording. This makes fixes faster.
Safe retries
Retries only temporary failures, such as network issues or slow screens. Denied access is escalated immediately: repeating a rejected login can lock the user out.
Personal data masked
Email, IBAN, NIF and CPF are masked in logs, including error messages.
Version in every summary
Every fix increments the robot version, and each run records which version ran and on which machine.
# robot/evidence/2026-09-29-0900/events.jsonl (example)
{"event":"stage","name":"Sign in","ms":4210}
{"event":"stage","name":"Get work items","ms":1830}
{"event":"retry","type":"network","attempt":2}
{"event":"error","type":"screen","stage":"Download PDF","source":"process.py:88","screenshot":"error-03-download-pdf.png"}
{"event":"end","processed":41,"failed":1,"version":"1.2.0"}networkscreenaccesssetupbusinesshuman action requiredcodeunknown
Errors are classified at each failure. Blue marks the ones the robot retries.
01 — Configuration adjustment02 — Quick fix03 — Refactoring or improvement
DOCUMENTATION AND COST
Everything documented. Every cost tracked.
Functional documentation
Generated after analysis and updated during architecture. An HTML file you can open in your browser.
- Overview, systems and screens
- Process flowchart
- Requirements with their sources
- Acceptance criteria, risks and questions
- Screenshots from system exploration
Technical documentation
Generated by QA once the robot is approved; Deployment and Support keep it up to date.
- Step-by-step guide with screenshots
- Robot workflow and business workflow
- How to run it, setup and file locations
- QA and support checklist
- Incident history
Cost of each project
The cost of each robot from start to finish, calculated from actual Claude and Codex usage.
€US$R$
- Cost per stage and hours of work
- Comparison with Power Automate Desktop and UiPath, with adjustable assumptions
Through QA = proof-of-concept cost · through deployment = complete project.
SECURITY
Rules that no request can change.
They apply to every robot, at every stage. No user preference weakens them.
Passwords only in the vault
Never in code, logs, configuration files, databases or chat. Enter it in the panel and it goes into the system vault.
Evidence of everything
Every run leaves logs, screenshots and a summary of what was done.
No duplicate actions
Rerunning skips completed work: no duplicate entries, downloads or submissions.
Personal data protected
Sensitive-data checks during QA and masking in logs. Documents and logs are handled in the customer’s environment. Content sent to the assistant follows the AI provider’s policies.
No AI in the production robot
In production, the robot is a deterministic Python program that follows the same rules. AI builds and tests it and, if you choose, starts it and summarizes results.
WHERE IT WORKS
In the tools your team already uses.
Claude Code and Codex
RPA Studio is an MCP server. Once the connection is configured, the conversation starts by typing Menu. The server provides instructions and templates to guide the agents.
Local or hosted
Runs on your computer or on a server with individual-token access. The server never reads your disk or executes anything on your machine: the assistant executes locally.
A professional structure
Each project has standard folders by stage, a living README, reusable components across robots (optionally in your private GitHub repository) and an interactive product map.
Claude CodeCodexWindowsLinuxSharePointExcelSQL ServerMySQLOracle
ONE SUBSCRIPTION. ALL YOUR PROJECTS.
Try it for a week.
Automate with unlimited projects.
Discover RPA Studio with 7 days free. Then continue for €25 per month.
7 days free
RPA Studio
Unlimited projects
€25/month
Monthly subscription · After your free week
Request free trialRequest access using the form. ACSystem helps with the initial setup.
Included in RPA Studio
- Unlimited projects
- 6 specialist agents
- Independent review
- Documentation and 3D workflows
- Connect to Claude Code or Codex
Access to the methodology follows your usage. You own the delivered robots, with no per-robot license.
Prices exclude VAT or local taxes. Claude Code or Codex subscriptions and usage are paid separately.
WHO IS BEHIND IT
Alexandre Moutinho
ACSystem Founder · Senior RPA Developer · Power Platform Specialist
More than seven years turning business processes into robust automations: architecture, development and support with Power Automate, UiPath, Python and enterprise integrations, including insurance. RPA Studio combines that methodology with a team of AI agents.
Power AutomatePower AppsUiPathPythonAI BuilderCopilot Studio
View LinkedIn profile ↗HOW WE START
Bring a process. Leave with a running robot.
We demonstrate RPA Studio with a real process from your company, from analysis to a scheduled robot.
Initial conversation
Tell us what task you want to automate. 30 minutes, no obligation.
Analysis
The team returns the flowchart and open questions.
POC
A robot built and approved by QA, with measured costs.
Deployment
The robot running in your chosen way.
FREQUENTLY ASKED QUESTIONS
Before we get started.
Do I need to know how to code?
No. Describe the process, provide any documents you have and approve the stages. The agent team writes, tests and deploys the robot.
Does the robot use AI while running?
No. In production it is a deterministic Python program that follows the same rules. AI is used to build and test it and, if you choose, to start it and summarize results.
What if the website or system changes?
Type “Menu” and choose Support. The agent reads the execution logs, reproduces the issue, finds the cause and fixes only what changed, testing and validating it with you before returning to production.
Where are my passwords stored?
In the operating system vault, or encrypted with your team key when setup is stored in a spreadsheet, SharePoint or a database. Never in code, logs or chat.
Can the robot get past MFA or CAPTCHA?
It never bypasses these protections. In assisted mode it pauses for your input; in automatic mode it stops and alerts you. For processes requiring MFA on every access, we recommend on-request execution.
Do I need a Claude or Codex license?
You need access to Claude Code or Codex, purchased separately. The RPA Studio plan does not include the AI provider’s subscription or usage. The delivered Python robot can run without these assistants using autonomous deployment options.
How much does RPA Studio cost?
Try it free for 7 days. After that, the monthly subscription costs €25 and includes unlimited projects. Claude Code or Codex subscriptions and usage are paid separately. Prices exclude VAT or local taxes.
Do you monitor the robot continuously?
The focus is taking the process to a running robot and providing support on request. Continuous monitoring dashboards, metrics and SLAs are not part of the product today.
Does my data leave the company?
The RPA Studio MCP server delivers instructions and templates without accessing your disk. The robot, documents, credentials and logs stay in the customer’s environment. Content shared with Claude Code or Codex follows the relevant AI provider’s settings and policies.
Do I pay a license for each robot?
No. RPA Studio costs €25 per month, with unlimited projects. You own the code of the delivered robots, with no per-robot licence. Infrastructure, external services and additional support depend on the project.
How do I receive the address and token?
ACSystem provides access details after confirming the solution and terms with you. Commands on this page are examples; the final public address is being prepared. Do not share the token in chats, repositories or forms.
Can I install it on company infrastructure?
Local or dedicated installation can be assessed with ACSystem, subject to the project’s technical and commercial conditions. The robot requires Python 3.10 or later; Windows application automation requires Windows.
FREE TRIAL · 7 DAYS
Which task takes up the most of your time?
Request access to the free trial. ACSystem will contact you to help you get started.