Flow is powerful when the design is deliberate. I build and untangle automations so they are bulk-safe, testable, and readable by the team that owns them.
Clicks where they fit
My early writing on duplicate prevention used Flow to move complex logic out of code. The principle still holds: use declarative tools when they make the system easier to own, and code when it creates a cleaner boundary.
Typical work
I can take on a single high-value workflow or a wider automation review.
- Record-triggered and screen flows
- Approval and case-routing workflows
- Fault handling, observability, and testing
- Consolidation of overlapping automation
Built for limits and change
Queries, loops, updates, and related-record operations are designed with platform limits in mind. Naming and documentation make future changes safer.