
Lesson 1: The Minimum Viable Workflow
Here's the workflow that produces sustainable cross-platform output in roughly 1 hour per week of your effort, plus 10-15 minutes per day of approvals.
The components
- A running ideas document. Captured continuously, not weekly.
- A weekly idea-processing session (30-45 minutes).
- A daily approval window (10-15 minutes).
- A weekly review (15 minutes).
That's it. 1 hour 15 minutes total per week of dedicated time, plus daily approvals during normal phone-checking.
Component 1 — Running ideas document
A simple list. Add to it whenever something hits:
- A pattern you noticed
- A customer question you got
- An observation about your work
- A pushback or disagreement
- A piece of news + your take
Don't draft. Just capture. Aim for 5-10 ideas per week added.
Component 2 — Weekly idea-processing session
Once a week (Monday or Sunday work for most people):
- Open your ideas document. Pick the 3-5 strongest ideas.
- For each, decide: which platforms fit? Use the format-decision tree from earlier lessons.
- Brief Bolta on each idea — what's the idea, what platforms, what register, what format.
- Hype-Man drafts the platform-specific versions for the week.
- You skim and approve in batch.
Total: 30-45 minutes for a week of content across multiple platforms.
Component 3 — Daily approval window
Each morning during coffee:
- Open Telegram. Approve or edit queued posts for the day.
- Skim Hunter's reply suggestions. Approve the strongest ones.
- Edit lightly when needed. Don't rewrite.
10-15 minutes per day. Spread across phone-checking moments.
Component 4 — Weekly review
Once a week, 15 minutes:
- Read Analyst's weekly summary.
- Note one win, one issue.
- Adjust persona or cadence if needed.
That's the whole workflow. Sustainable for years.
Lesson 2: Where Bolta Does the Heavy Lifting
Without Bolta, the same output would take 8-10 hours per week. Bolta absorbs the mechanical work.
What Bolta handles
- Platform adaptation. Hype-Man translates your idea into platform-specific versions.
- Scheduling. Posts go out at the right times without your involvement.
- Hashtag selection. Bolta picks from your curated pool.
- Reply opportunity discovery. Hunter surfaces what to engage with.
- Content warning decisions on Mastodon.
- Performance tracking. Analyst surfaces patterns weekly.
- Cross-posting with adaptation. Same idea, different platforms, no manual rewriting.
- Engagement. Engager handles routine comments and DMs.
That's roughly 70% of the work that used to take human time.
What Bolta doesn't handle
- Idea generation. You still capture ideas; Bolta processes them.
- Editorial taste. You still approve, edit, and redirect.
- High-stakes responses. Engager handles routine; you handle the important conversations.
- Strategic decisions. Which platforms, which cadence, which audience to target.
- Drift detection. Weekly skim is still on you.
The split: Bolta does the work; you provide the taste.
The "automate, don't abdicate" principle
The risk in any automation: handing over so much that you lose touch with what's happening. Bolta's design avoids this:
- Approvals stay human. Even at high autonomy, you skim.
- Drafts get reviewed. You see what's posting in your name.
- Drift detection requires you. Algorithms can't fully self-audit.
The 1-hour-per-week workflow only works if you stay in the loop on those things. Skip them, and the system drifts.
Lesson 3: The Discipline That Makes It Work
The workflow looks simple. The discipline that makes it actually happen is the hard part.
Discipline 1 — Capture daily
You won't generate 5 ideas per week if you don't have a habit of capturing. Set a phone widget, a daily journal prompt, a Slack channel — whatever works. The discipline isn't generating ideas; it's writing them down.
Discipline 2 — Weekly session non-negotiable
The 30-45 minute weekly idea-processing session is the linchpin. Skip it once and the week's content is reactive, scrambled, or absent.
Calendar it. Same time every week. Treat it like a meeting you can't skip.
Discipline 3 — Daily approval rhythm
10-15 minutes daily. Not "when I have time" — at the same window each day. Morning coffee is the most common rhythm.
If you skip approvals for a few days, the queue piles up; you start skimming instead of engaging; quality drops.
Discipline 4 — Weekly review actually weekly
The 15-minute weekly review feels skippable. It isn't. Drift detection happens here; performance signals get acted on here.
Set it for the same time each week. Many founders do it Friday afternoon as the last work activity.
Discipline 5 — Honest portfolio review quarterly
Every 90 days, ask:
- Which platforms are earning their effort?
- Which agents are performing?
- What's drifting that I haven't fixed?
- Where should I invest more next quarter?
This is the highest-leverage activity in the entire workflow. 60-90 minutes once a quarter.
When the workflow breaks
The 1-hour-per-week workflow breaks when:
- Capture stops. Without ideas, the weekly session has nothing to process.
- Approvals get skipped. Queue overwhelms; quality drops.
- Persona drifts unnoticed. Weekly review skipped; the agents drift unchecked.
- You stop trusting Bolta. Output gets edited heavily; the time savings disappear.
Each is recoverable. None should be ignored.
Common myths
- "1 hour a week is too aspirational." It's achievable for sustained cross-platform output, with the right setup.
- "Once it's working, I never need to touch it." You always need to touch it. The 1-hour minimum is the minimum, not the ceiling.
- "Bolta replaces strategy." It doesn't. Strategy is your work. Execution is Bolta's.
Action Steps
- Set up your ideas document today. Add the first idea before you close this lesson.
- Schedule your weekly idea-processing session — same time every week. Block 45 minutes.
- Schedule your daily approval window. Match it to a habit you already have (morning coffee, lunch, evening wind-down).
- Schedule your weekly review. 15 minutes, same time each week.
The discipline isn't glamorous. It's what makes the system run for years instead of weeks. You finished the cross-platform repurposing course. Now go capture an idea and ship something thoughtful — across as many platforms as your taste allows.