Automate a recurring process
An inbox, an approval, a document, a tracker, and several reminders can often become one visible workflow—with a clear place for exceptions.
Power Automate · Power Apps · Dataverse · Microsoft 365Available for select weekend projects
Hi, I’m Elier.
I’m an automation engineer in Florida. I build workflows, internal tools, integrations, and data processes that make repetitive operational work less repetitive.
Most of the useful systems I’ve built live inside my employer, so I can’t turn them into public case studies. This site is an honest description of the problems I know, the tradeoffs I make, and where my experience may be useful.
Automation engineer
What I do
I’m useful when a task has become normal enough that nobody questions how awkward it is.
Make an Excel process repeatable
If the same exports are cleaned, joined, checked, and reformatted every week, a focused VBA or Power Query solution may be better than building an application.
Excel · VBA · Power Query · Power BIGive a small workflow a proper home
When a spreadsheet or email chain has outgrown itself, I can build a modest internal tool or integration without pretending it needs to become a software platform.
SvelteKit · JavaScript / TypeScript · REST APIs · CloudflareAI & judgment
Where I fit alongside AI
AI is very good at getting from nothing to a plausible first draft. I use it for that. But most businesses do not have a first-draft problem. They have a last-mile problem.
The real process includes the rule somebody forgot to mention, the credential that expires, the duplicate record, the spreadsheet with one strange column, and the person who needs to know what happened when a run fails.
What I bring is an understanding of the work, judgment about the tradeoffs, attention to the uncomfortable cases, and responsibility for the result.
The parts I take responsibility for
- Requirements
- What actually happens, who owns each decision, and which exceptions matter.
- Fit
- Whether this should be Power Automate, VBA, a web app—or not automated at all.
- Failure
- Retries, validation, visible errors, useful logging, and a person to notify.
- Handoff
- Clear limitations, test examples, operating notes, and something your team can understand.
A sample
What “done” means to me
Here is a fictional invoice-intake example using sample data. It is not employer or client work; it shows the questions I would expect a real build to answer.
Example 01
A PDF arrives by email
The obvious automation
Read the attachment, extract the total, and update a record.
The questions that make it real
- What if the attachment is not a PDF?
- What if a required value is missing or ambiguous?
- How is a duplicate detected?
- Whose account owns the connection?
- Where can someone see failed runs?
- What should retry automatically, and what needs review?
The handoff
A process map, an exception list, approved test examples, ownership notes, known limitations, and a short walkthrough—not just a flow that worked once.
Fictional demonstration · Sample data · No performance claims
Availability
I’m available for the right small project.
I work full-time during the week and keep a limited amount of weekend time open. The work that fits naturally is one repeatable workflow, one fragile workbook, one small integration, or one existing automation that needs to be made more dependable.
I prefer to understand what happens today, where judgment is required, which systems and permissions are involved, and what a useful outcome would look like. If it makes sense to continue, I’ll outline the boundary and estimate first.
- 1
You describe the task. Plain language is fine; you do not need to choose the technology.
- 2
I map the boundary. Inputs, decisions, exceptions, ownership, and what “done” means.
- 3
I build and hand it back. Tested examples, visible failure behavior, notes, and a walkthrough.
Three opinions
Things experience has made me particular about
- The exception path is the real workflow.The happy path is usually the easy part.
- Complexity needs to earn its place.Sometimes the honest answer is 40 lines of VBA.
- A handoff should explain itself.Status, ownership, errors, and the next action should be visible.
About
I work between business operations and software engineering.
My experience covers Power Platform, Excel and VBA data workflows, programming, custom web applications, integrations, and cloud technologies. That range helps me choose a tool based on the work instead of forcing every problem into the same platform.
I’m based in Florida and employed full-time Monday through Friday. Outside work, I’m interested in small systems that remove disproportionate amounts of friction.
Contact
I’m easy to reach.
If you have a repetitive task or small operational problem in mind, send me a short note with what happens today, the tools involved, and where it gets awkward. I’m available for select weekend work, and I’m always happy to hear about an interesting process.
A short, informal message is enough.