I build the systems layer for businesses without engineers.
By day, I run the systems for a digital marketing agency. On the side, I run NoCodeWorkflows, a review site and directory for no-code and AI-agent tools. This page shows the system underneath it.
See the systemsThe System That Builds the Systems
My personal OS.
None of it is client work. All three run every day. The boundary decides what my agents can see. The pipeline publishes NoCodeWorkflows. The knowledge base connects what I save, so I can ask it questions while I write.
-
Operating infrastructure
Two directories, never the whole vault
An agent reads whatever directory you open it in.
Each repo mounts a slice. No session ever bypassed the gate.
-
NoCodeWorkflows
A directory that regenerates
Most tool directories become stale when the maintenance stops.
nocodeworkflows.co runs on it. A saved bookmark ships an entry.
-
ClipBase retrieval eval
The fix worked and the score decreased
Most changes to a retrieval system ship, and no one measures whether they helped.
The fix ran on the live corpus. The eval says that it cost a rank slot.
NoCodeWorkflows
NoCodeWorkflows is my venture. It publishes operator-level reviews of no-code and AI-agent tools, a curated directory, and playbooks. The pipeline in the exhibit above publishes the site.
The Story
- I spent eight years in behavioral-health operations: utilization review, revenue cycle, clinical documentation.
- I learned to build in 2020. Automation came first, then real code.
- Now I do the same work at agency scale, and I build my own systems on the side.
Work With Me
info@mattbastar.comSend an email about your operation. An introduction from someone we both know also works.