[ About ]
I came to software from operations.
Since then, my work closes the gap between the two. This is the short version.
-
Operations
I spent eight years in behavioral-health operations: utilization review, revenue cycle, and clinical documentation. Those functions decide whether a program gets payment and stays compliant. Each of them ran on manual work. I learned what breaks when a process depends on a person's memory.
-
Learning to build
The fixes that I needed all had the same shape: software that no company makes for an organization of our size. So in 2020, I started to build it myself. I used automation tools first, then real code when those tools hit their limit. I did not come to this from computer science. I came to it from a backlog.
-
Systems at scale
Today I run business systems and client platforms at Rise4, a digital marketing agency. That work includes the CRM architecture, the internal operations platform, the data and attribution pipelines, and an internal AI-agent layer. It is the same job at a different altitude. An attribution pipeline fails in the same way as a revenue cycle: a handoff that no person owns, or a status that lives in one person's head. I see that across many businesses at the same time, and that teaches the lesson faster than any single stack can.
-
On my own
On the side, I build for myself and publish what survives. NoCodeWorkflows is the venture. It publishes operator-level reviews of the tools that this work runs on: Airtable, n8n, GoHighLevel, Postgres, and MCP servers. It runs on a publishing pipeline that I built end to end. The systems behind it are on this site, and I measure them as I measure work that I ship for a client. I build for the operator because I was one.