How a solo B2B consultant scaled from 3 posts to 15 posts per week without hiring help

Industry: B2B SaaS consulting (cybersecurity & compliance)

Team size: 1 (solo creator)

Tools involved: LinkedIn, X/Twitter, Notion, NAVi

Problem: Manual content creation capped at 3 posts/week, missed breaking news windows

Outcome: 12-15 posts/week sustained for 8 weeks, 40% less research time

Timeframe: 2 days setup, 8 weeks execution

The situation

Former CISO running an independent compliance consulting practice. 8,500 LinkedIn followers. Revenue from retained advisory (60%) and project work (40%). New business came entirely through LinkedIn and X/Twitter visibility.

Posted 3x per week. Generated 2-3 inbound conversations per month. One new project every 6-8 weeks.

Client work consumed 25-30 hours/week. Content creation happened Sunday mornings and occasional evenings. Standard workflow: scan LinkedIn, Reddit, X/Twitter, and news sites (45-60 min), draft posts, schedule for Mon/Wed/Fri.

This broke in March 2024. Major CVE disclosure + SEC cybersecurity rule proposal created a time-sensitive content window. Consultant published about the SEC rules four days late. By then, 30+ voices had already covered it. Engagement was 60% below average.

Same week, turned down two project inquiries because client capacity was full. Revenue ceiling became visible.

What wasn't working

Research took 45-75 minutes per session. On a good week, this happened twice. They'd write 3-4 posts and call it done.

The problems:

1. No capacity for breaking news (research alone: 30-40 min)
2. Only covered major stories, missed secondary opportunities
3. Saw engagement opportunities 12-48 hours too late

Example: Target account VP posted about SOC 2 scope struggles. Consultant saw it 36 hours later, didn't comment. That VP hired a competitor two weeks later.

Failed fixes:

1. Wake at 6 AM to write before calls → lasted 11 days, killed focus during client work
2. VA to curate articles ($400/mo) → sent 8-12 links daily with no filtering, still required 30+ min review, canceled after 5 weeks
3. ChatGPT drafts → worked for generic content, failed for technical posts, engagement dropped 25%

The issue wasn't writing speed. Research, context-building, and relevance filtering ate all available time.

Why standard approaches didn't work

Content templates didn't help—the consultant knew how to write. The problem was having nothing to say because they hadn't seen the right inputs.

Outsourced research failed because VAs couldn't distinguish stories that mattered to compliance officers from generic cybersecurity news.

AI tools couldn't identify which stories were worth posting about in the first place.

Batching content 10-14 days ahead meant posts felt stale when they published.

Every solution addressed writing and scheduling (20% of work) while ignoring monitoring and filtering (80% of work).

What changed

Late June: configured NAVi to monitor 12 news sources, 8 regulatory bodies, 15 LinkedIn profiles, 4 subreddits, 3 YouTube channels. Setup took about 90 minutes.

The tool grouped posts with newsworthy level. When SEC published guidance, NAVi showed the official release, LinkedIn posts, Reddit threads, and YouTube breakdowns.

New routine: review feed twice daily (morning: 15 min, afternoon: 10 min). Flag stories worth posting about. Generate drafts, edit for voice (20-30 min total).

Research time dropped from 90-120 min/week to 25-35 min/week.

Workflow became:

1. Scan story threads (15 min)
2. Flag 2-3 topics
3. Edit drafts (20-30 min)
4. Publish

Fit in 45-minute blocks instead of 2-hour Sunday sessions.

How execution was verified

Week 1-2: Ran both systems in parallel. Checked LinkedIn and news sites manually while NAVi ran alongside.

Result: NAVi surfaced 11 of 12 stories found manually, plus 4 the consultant had missed.

Week 2: Stopped manual checking. NAVi became primary input.

Week 3: Tested new cadence—5 posts instead of 3. Time: 2h 10min (vs 3+ hours for 3 posts). Engagement held.

Week 4-5: Pushed to 7 posts. Editing: 8-12 min per post.

Week 6: Posted 12 times. Three were rapid responses (within 4 hours of news breaking). One got 140+ comments, two inbound calls.

Operating parameters established:

1. Research: under 40 min/week
2. Volume: 10-15 posts/week
3. Quality: avg 80+ engagements per post
4. Speed: breaking news within 6 hours

Results

Weeks 6-13 (8 weeks sustained): 12-15 posts/week

Volume: 102 posts (vs 24 in prior 8 weeks)

Time: 3-4 hours/week (vs 4-5 hours for less output)

Engagement: Avg per post: 87 (down from 95). Total weekly engagement: up 340%

Inbound: 6-8 conversations/month (vs 2-3). Three converted to projects.

Timeliness win: Published CISA emergency directive post 90 minutes after release. Best-performing post of quarter (340+ engagements, 4 calls, 1 contract).

By week 13, 12-14 posts/week became standard without increasing time investment.

Lessons for other teams

When this works:

1. Content already proven, just time-constrained
2. Creator has expertise, limited research capacity
3. Being early to stories has measurable value

What teams underestimate:

1. Research takes 3-4x longer than writing
2. Value of seeing full story context vs scattered posts
3. Shift from "write more" to "need better inputs"

Verify early:

1. Does monitoring catch what you'd find manually? Test 1-2 weeks in parallel
2. Can you trust filtering? Too much noise = back to manual
3. Is editing drafts faster than writing from scratch?
4. Can you sustain new pace when client work spikes?

The breakthrough: eliminating research bottleneck so posting more didn't require working more.