The Solo Stack Weekly — April 09, 2026
From the Desk
This past week was one of those rare ones where a long-running build suddenly becomes a running system.
The marketing assistant — the AI-driven content pipeline I've been building to run stephenbogner.com's marketing — crossed a threshold: it's now operational end-to-end. Content gets generated on a schedule, routes to a review queue, I approve or reject, and it publishes. The newsletter you're reading right now is the first output produced by that system.
I shipped a lot to get here: scheduled publish times, a calendar UI you can actually edit, a newsletter archive, and a deployment skill that pushes the website automatically. Under the hood: an orchestrator managing the whole pipeline with budget caps, kill switches, and completion callbacks. It's not glamorous engineering — it's the plumbing that makes everything else reliable.
Below I've broken down the three most significant commits from this week, plus a few links worth reading if you're thinking about building your own solo AI stack.
Product Updates
Scheduled Publish Times, Calendar UI & Newsletter Archive
Three things shipped in a single commit: scheduled publish times on content items, an interactive calendar edit UI, and the newsletter archive going live at stephenbogner.com/newsletter.
The calendar edit UI is the piece I'd been putting off. Previously the calendar was read-only — you could see what was scheduled but couldn't move things around without editing the database directly. Now you can drag-edit from the browser. The newsletter archive was a dependency for the newsletter creator skill to have somewhere to post issues. And scheduled publish times close the last gap in the approval workflow — you can now approve a post and say "publish this Thursday at 9am" rather than immediately.
Full Operational Pipeline — Generation to Subscribers
The full content pipeline is now wired: generation → review queue → approval → publishing → subscriber delivery. Each step hands off to the next automatically. Your job as operator is to approve or reject; the system handles the rest.
The key design decision here was keeping humans in the loop at the approval gate rather than running fully autonomous. That's a deliberate choice — not a technical limitation. Fully autonomous is one setting away, but I'd rather review content before it goes out until the quality metrics justify removing that gate.
Orchestrator Integration, Dashboard Fixes & Budget Management
The orchestrator now drives the full pipeline end-to-end with proper kill-switch guards and completion callbacks. Budget management was added so you can set a monthly AI spend cap — once you hit it, the orchestrator stops generating new content.
Budget management is underrated as a feature. Running an AI pipeline without spend caps is how you end up with a surprise invoice. Having a hard cap per month is a baseline requirement for anything you're going to leave running autonomously.
Links Worth Reading
The One-Person Billion-Dollar Company Is Here
PYMNTS covers what happens when AI tools remove the traditional scaling constraints on solo founders. In 2026, 84% of developers use AI tools that now write 41% of all code. The piece is worth reading not for the headline examples but for the underlying structural argument about what's actually changed for solo operators.
Developer Productivity Stats With AI Tools
Useful reference numbers from multiple sources: businesses implementing AI expect 25-55% productivity gains; the full solopreneur AI stack runs $75-150/month vs $600-1,000/month for a part-time VA. The cost comparison alone is worth bookmarking.
Privacy-First Local AI Apps in 2026
If you handle sensitive client data and have been hesitant to pipe it through cloud AI services, local models are now a real option. Tools like Ollama, Jan, and Msty Studio run fully on-device — no telemetry, no cloud sync, no accounts. Worth evaluating if data residency matters to you.
— Stephen
The Solo Stack Weekly is published weekly by Stephen Bogner, P.Eng. If someone forwarded this to you, subscribe here.