Writing17 posts · page 2 of 2
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. Each post takes one question at a time, with the systems OCTYN builds and runs as the evidence.
Build or buy5 min
No. 05: How to scope an AI project so it ships: write down what it will never do
To scope an AI project so it ships, tie it to one piece of work your team repeats every week, with your weekly hours on it, and then write down what the first version will never do. Feature lists grow with every meeting. The stated limits keep it small enough to finish and safe enough to leave running.
Founder operations4 min
No. 04: What should a founder automate first? Start with the catching up
The first thing a founder should automate is the step where someone rebuilds context by hand before acting, reading back through WhatsApp and email to see where a client stands. Count it before building anything. Clients times touchpoints times minutes spent catching up gives a weekly figure, and that figure decides what gets built.
Build or buy4 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 product 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. OCTYN learned this after a model driven sender 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.
Every post belongs to one topic.
- Build or buyBuild or buy, what it costs, and what to ask before anyone builds you anything. (4)
- Client contextThe work of reassembling who a client is before every next touchpoint, and how to stop doing it. (5)
- Automation that holds upSilent failures, gates, rollbacks and the checks that keep a running system honest. (2)
- Founder operationsCounting the hours that never needed a human, and deciding what to hand to a system first. (3)
- Growth systemsContent and outbound that keep running when the founder is busy, and still sound like the company. (1)
- Operations systemsIntake, handoffs and status carried by one system, so the team keeps the judgement calls. (1)
- Product systemsA model inside a product: speed, fallbacks, keys, and what running it costs after launch. (1)
Bring the version of this that is about your company.
The first conversation is with the people who would build it. If there is a fit, the Consult comes next.