Your engineer, from first conversation to handover
I'm Daniel Parsons. I build workflow automation and system integrations in n8n, Make and custom code, for businesses that need them to keep working after the person who built them stops watching.
Where this comes from
I spent 25 years as an electrical engineer before I did any of this. Embedded systems and FPGA firmware for defense, avionics and RF, including a display system carried all the way through DO-254 certification, plus calibration and verification firmware for automated semiconductor test equipment.
That work has a specific discipline attached to it. You do not get to say a design works because it worked once on your bench. You have to show what happens when the input is malformed, when a device stops responding, when the data arrives twice. Certification means someone else checks.
Business systems need that care too. A supplier may send an unexpected tracking number, an API may go offline, or an order may arrive twice. Those cases belong in the design and testing.
My goal is a useful system your team can understand, with clear records, sensible safeguards, and a proper handover.
Expertise & Skills
Automation & Integration
- n8n
- Make
- Zapier
- API integration (including services with no connector)
AI & LLM
- AI agents and routing
- Document and data processing
- Claude Code and Codex assisted development
Engineering
- Embedded systems and FPGA firmware
- Test and measurement automation
- DO-254 certified avionics software
- Failure analysis and verification
Who I work with
- E-commerce and multi-store operations
- Professional services firms
- Software and technology teams
- Operations teams drowning in manual steps
My Approach
How I work, and what you can expect me to do before I write a single node
Find the real bottleneck first
Most automation requests name a symptom. Before I build anything I want to see where the time actually goes, because it is frequently not where you think.
Build for the data you have not seen yet
Real inputs are messy. Duplicates, partial records, values pasted with stray whitespace, the same order arriving twice. A workflow that only handles clean data will skip things silently. Mine log what they could not handle and tell you.
Hand it over properly
You get documentation your team can follow, not a black box that only I understand. If you want to take it in-house later, you can.
Say what will not work
If the thing you are asking for is a bad idea, or a cheaper tool would do it, I would rather tell you before you pay me than after.
Have something that keeps breaking?
Or a process eating hours a week that shouldn't be. Tell me what you are trying to accomplish and I will tell you honestly whether it is a good fit.