Blog · October 5, 2026
How to choose your first process to automate
Before connecting tools, document a task, its rules and its exceptions. A practical way to assess effort, potential value and necessary oversight without promising savings that have not been measured.
San José · since 1996Published
October 5, 2026
A suitable automation candidate has an identifiable trigger, available data, repeatable steps and a result that can be checked. Before development, distinguish rules from decisions that need a person.
Describe one task from start to finish
Choose a specific process, such as receiving a request and assigning it to someone for review. Describe what triggers the task, what information arrives, who uses it and what should happen when it ends.
Include exceptions: missing information, duplicate requests, an absent team member or an unavailable tool. If everyone handles these situations differently today, agree on the rules first.
Measure the starting point
Record how often the task happens, how much manual work it requires and how often it needs correction. Separate execution time from time spent waiting for approval. Reducing manual copying does not itself remove the wait for a decision.
For an initial estimate, multiply task frequency by the manual time that might be avoided. Then subtract the reviews that will still be necessary and compare potential value with development, licenses, support and maintenance. This is a hypothesis to validate, not a savings guarantee.
Check access to the tools
List the systems involved and who administers each one. Confirm whether they allow the required data to be read and written, with which permissions and under which limits. Access to a screen does not necessarily mean an integration is available.
Decide where the authoritative information lives. When data changes, the workflow needs to know which system takes precedence and how to detect duplicates. Include error handling and a way to recover a task without sending it twice.
Start with a scope you can review
Test a limited workflow whose outcome can be compared with the current procedure. Keep human review for sensitive approvals and decide who gets an alert when something fails. A pilot needs success criteria, an owner and a way to return to the previous process.
If the data is unreliable, the process changes every day or the task rarely occurs, organizing the work may be a better first step. A procedural improvement can be valuable even when it requires no custom software.
What to bring to a first conversation
Prepare a description of the task, its participants, current tools, frequency and common exceptions. Share examples without confidential information. At Estudio Gráfico, we review the process and the feasibility of an integration or custom tool based on what each system allows.
For a real custom tool project, explore the ID Trips website and CMS. That case demonstrates content management; we do not present it as evidence of measured savings or operational automation.
Your project
Put these thirty years to work for your brand.
Tell us what you need: websites, systems, automation, branding, design or printing. We review the scope and prepare a proposal.