What does it take to run a business on systems?
Mostly it takes counting: the hours that go to rebuilding context nobody needed rebuilt, and the workflows that repeat every week and break quietly when nobody is watching. These posts take one question at a time, for founders and operators, with the systems OCTYN builds and runs as the evidence.
Custom AI systems4 min
No. 03: Build vs buy AI tools for operations: look for the side spreadsheet
On build vs buy AI tools for operations, buy wherever your workflow looks like everyone else's and build only the narrow part that is specific to how you work. The deciding cost arrives later, every day, in the workarounds a team invents when a bought tool cannot hold one of its steps.
No. 02: Should an AI agent send your emails? Ours did, once
No, an AI agent should not be the part that actually sends your emails. Let the model draft and sort, then pass each message to a small, boring service that sends on a schedule and confirms every delivery. We learned this after a model driven sender we built for a client reported a send that never happened.
Client context4 min
No. 01: How to stop rebuilding client context before every call
Stop rebuilding client context by giving each client one record that every channel writes into as things happen. WhatsApp threads, emails, call notes and CRM changes land in the same place, with dates and sources, so the history is already assembled when someone opens it. The coordinator reads one page and starts from the last promise made.
Topics
every post belongs to one of five5Custom AI systems · 1Client context · 1Automation that holds up · 1Founder operations · 0Growth systems · 0
Bring the version of this that is about your operation. Thirty minutes, with the people who would build it.
Book a call →