TL;DR — what to build first
Hermes scored 12 candidate jobs across (a) revenue/value, (b) implementation cost in days, (c) suitability for local model. All 12 are local-model-suitable — your "zero token cost" thesis is well-supported.
Top 3 picks (highest revenue per implementation day, fast follow-on to the orchestration work that landed last night):
Sales Meeting Auto-Brief
Aspire DigitalLowest implementation cost, highest immediate ROI. Existing crawl4ai infra. Pure prompt-chaining pattern.
Daily Client-State Scanner
Aspire DigitalCompounding value across every existing client. n8n + Ollama routing. Zero token cost.
Multi-Client Overnight Content Batch
Aspire Digital96GB RAM handles batch generation at zero marginal cost. Blog/social/email drafts ready for review each morning.
📋 Full ranked menu — 12 Hermes jobs scored
| # | Job | Lane | Revenue / Value | Cost | Local? | Status |
|---|---|---|---|---|---|---|
| 1 | Daily Client-State Scanner | AD | HIGH ($300–$1.5k/mo/client) | MED (3–5d) | Y | |
| 2 | Sales Meeting Auto-Brief | AD | HIGH ($500–$2k/meeting) | LOW (1–2d) | Y | |
| 3 | Multi-Client Overnight Content Batch | AD | HIGH ($1k–$5k/mo) | MED (3–5d) | Y | |
| 4 | Personal-Brand Content Engine | Brand | HIGH (LinkedIn equity) | MED (2–3d) | Y | |
| 5 | Custom Client Knowledge Bases (RAG) | AD | HIGH ($2k–$10k/setup) | HIGH (5–10d) | Y | |
| 6 | Cross-Platform Lead-Radar | AD | HIGH ($1k–$3k/mo) | MED (3–5d) | Y | |
| 7 | SaaS Arbitrage / App-Rebuild | AD | HIGH (full SaaS margin) | MED (3–7d) | Y | |
| 8 | Domain/SEO Opportunity Radar | Ventures | MED ($300–$1k/mo) | LOW (1–2d) | Y | |
| 9 | YouTube Intel Pipeline | Ventures | MED (time saved) | LOW (1d) | Y | ✅ shipped 5/17 |
| 10 | Synthetic Data Generation for Client Fine-Tunes | Ventures | HIGH ($2k–$5k/project) | HIGH (5–10d) | Y | |
| 11 | Self-Improving Lead-Hunt Loop | AD | HIGH (compounds) | HIGH (5–10d) | Y | |
| 12 | Inbound Voice AI Receptionist | AD | HIGH ($500–$2k/mo) | HIGH (5–10d) | MED (latency) |
🛠️ What's actually shipping in 2026 (verified patterns)
Aider
↗ source15B tokens/week, 88% "singularity" (Aider writes most of its own code now)
Local-first AI pair-programming is the #1 confirmed revenue generator for technical solo operators in 2025–2026.
n8n + Ollama
↗ sourceStandard for 24/7 agent orchestration; replaces $25–$199/mo Zapier tiers
700+ app integrations, self-hosted, free. Small agencies use this to chain: calendar → GHL → LangChain → Slack.
Open WebUI
↗ source137k GitHub stars — most-deployed self-hosted chat UI for local LLMs
24/7 always-on agent dashboards. Plugins for agent customization. Native Ollama integration.
ComfyUI
↗ source100k+ stars; dominant visual AI workflow platform
Image/video generation pipelines for client deliverables. Zero API costs. Topher: this maps to Aspire Digital design work.
⚠️ 6 failure modes + standard fixes
Local model quality drift
Routing — fast models (7B) for simple, larger (27B+) for complex, frontier API only for the hardest. Never force one model across all complexity.
Context window exhaustion
Hierarchical context — fast "index model" filters docs, sends only relevant chunks to the reasoning model. Never dump raw docs into context.
Tool-use unreliability (small models)
Decompose tool use into sequential single-tool calls with validation gates between each. Anthropic's production data confirms.
Agent loops (infinite self-talk)
Hard step limits + output format validation gates + "give-up-and-escalate" pattern that sends stuck tasks to frontier API or human.
Observability gaps
Log every LLM call (full context/inputs/outputs) to SQLite. Simon Willison's pattern. Cheap, effective.
Mac thermal throttling
Schedule intensive batch processing during off-hours. 96GB RAM ≠ usable sustained throughput. Idle monitoring matters.
🍎 Apple Silicon state of the art — what the M3 Ultra actually unlocks
Three Apple-silicon inference frameworks worth knowing about in 2026:
| Framework | Strength | Best for |
|---|---|---|
| MLX (Apple) | Native Apple Silicon, dynamic memory across unified RAM, any model size that fits | Models that "fit in RAM" up to 96GB — M3 Ultra's killer feature |
| llama.cpp | Most mature, broadest model support, fastest inference, community-tested | Production serving, quantized models, speed-critical workloads |
| Ollama (current) | Easiest deploy, best model library, MCP integration; wraps llama.cpp | Default — what we run today. Move to MLX only when hitting performance limits |
The killer Apple-specific advantage
The M3 Ultra's 96GB unified RAM means any model that fits runs natively without VRAM concerns. The M3 handles 70B-parameter models that would otherwise require $10K+ NVIDIA hardware with CUDA VRAM. Plus: ~100W power draw vs. 300–800W for equivalent NVIDIA inference. Running 24/7, this is the unit economics.
📺 Channels worth tracking ongoing (beyond your current list)
Simon Willison
↗ linksimonwillison.net — top local-LLM voice, substantive analysis. More signal than Alex Finn.
Anthropic Engineering Blog
↗ linkProduction data on agent patterns — most authoritative source.
swyx
↗ linkAI workflow patterns + local-first dev. Practical essays.
r/LocalLLaMA
↗ linkCommunity benchmarks + production patterns. Qwen 3.6 / Llama 4 discourse lives here.
🚀 Next moves (decision-ready)
1. Build the Sales Meeting Auto-Brief first (#2 in the menu). Lowest cost, highest single-touch ROI, uses infrastructure that already exists. Aria can dispatch tonight if you approve.
2. Pick the second build from #1 (client-state scanner) or #3 (overnight content batch). Both are MED cost. Client-state scanner is more defensive (keeping existing clients hot); content batch is more offensive (creating leverage for sales).
3. Adopt the routing pattern across all new Hermes jobs — small model for triage, larger model for reasoning, frontier API only when stuck. This is the path to keeping the M3 humming without hitting model quality drift.
4. Add SQLite-based agent log to all Hermes jobs. Simon Willison's pattern. Makes debugging tractable; pays for itself the first time a job goes silent.
5. Consider Open WebUI as a second-machine UI for the M3 — gives you (and Jaime) a browser-based "talk to your home AI" surface without leaving CC behind.
📜 About this report
Generated by Hermes Agent v0.14.0 on the M3 Ultra, using qwen3.6:latest as the reasoning model + crawl4ai for source verification. 64 LLM API calls over ~68 minutes (00:25–01:33 EDT). Zero token cost.
All findings cite source URLs inline. Single-source items are flagged [unverified]. Raw report at ~/hermes/research/m3-agent-monetization-2026-05-17.md on M3 (kept as audit trail; this CC page is the canonical deliverable per the publishing rule).
Filed as part of OPS-49 — M3/Hermes orchestration meta-project.