Bil Arikan

Claude for Small Business is a one-click plugin that puts Claude inside the tools small business owners already use. In this post I want to look at two implications for the SMB software market : why your product almost has to be a first-class citizen inside tools like Claude to stay in the candidate set, and why being in that candidate set also puts you a step closer to being benchmarked, ranked, and eventually replaced by the platform itself. I also walk through the plugin-and-connector architecture behind the payroll workflow Anthropic uses in the launch video.

The first two posts in this series put Editframe through its paces on a hello-world clip and a 71-second product walkthrough. This third post zooms out. The question is no longer ‘does code-as-video work for L&D’ — the first two experiments answered that. It is which other frameworks belong in the picture, where they sit on a deterministic-to-generative spectrum, and what each tier can credibly contribute to a learning content development workflow.

The first experiment closed with a question : can an agent take structured product information and turn it into a short, repeatable video composition? This second experiment is the answer. The interesting part is not the seconds. It is what this workflow does to the way Learning Program Owners, Learning Designers, and Learning Developers traditionally split the work.

Can video production start to look more like a dev workflow, where the composition is code, the output is reproducible, and the agent can help move through the rough edges? Experiment 01 – a hello-world Editframe project, scaffolded, iterated, and rendered locally, with the failure points captured for the next pass.

Most AI rollouts stall not because people lack tools, but because nobody named the cliff between using AI and building with it. Here is the nine-level model AI Spark is using inside Sage, the seam at level six, and the nine moments from my own path that map onto it.

While creating a blog post with Claude Code, I noticed the changes were on GitHub but not visible in my local files. The reason was git worktrees – a Git feature that lets Claude work in isolation without touching your local working directory. Here is what happened and what the trade-offs are.

Building the same workflow in Claude takes an hour; in Copilot it means Power Automate and three to five hours. That gap is real — and it’s architectural. Here is how Claude’s skill system maps to M365 Copilot, and what the comparison reveals about where each system was designed to be used.

GitSync worked reliably for editing existing notes, but adding a new note triggered an index corruption error every time. This is a follow-up to my original vault sync post, documenting the switch to Termux and why the underlying architecture difference matters.

The ADK Dev UI supports camera but not screen sharing. In this post I build a custom client that swaps getUserMedia for getDisplayMedia, writes a 16kHz AudioWorklet from scratch, and sends 1 FPS JPEG screen snapshots to the same WebSocket endpoint. The agent now sees the application instead of the user’s face.