CLAUDE LABJP
FORK — Claude Code 2.1.212 changes what /fork does: it copies your conversation into a new background session with its own row in claude agents, so you can keep working. The old in-session subagent is now /subtaskLIMITS — WebSearch calls are now capped at 200 per session by default, and subagent spawns get the same 200 ceiling, so a runaway search or delegation loop stops on its ownMCPBG — MCP tool calls running past two minutes now move to the background automatically, keeping the session usable. Tune the threshold with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MSPLANFIX — Fixed plan mode auto-running file-modifying Bash commands such as touch and rm without a permission prompt or an SDK canUseTool callbackSONNET5 — Claude Sonnet 5 is running on introductory pricing of $2 per million input tokens and $10 per million output. After August 31 it moves to $3 and $15IPO — Bankers are reportedly lining up investor meetings for Anthropic ahead of a possible public listing as soon as OctoberFORK — Claude Code 2.1.212 changes what /fork does: it copies your conversation into a new background session with its own row in claude agents, so you can keep working. The old in-session subagent is now /subtaskLIMITS — WebSearch calls are now capped at 200 per session by default, and subagent spawns get the same 200 ceiling, so a runaway search or delegation loop stops on its ownMCPBG — MCP tool calls running past two minutes now move to the background automatically, keeping the session usable. Tune the threshold with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MSPLANFIX — Fixed plan mode auto-running file-modifying Bash commands such as touch and rm without a permission prompt or an SDK canUseTool callbackSONNET5 — Claude Sonnet 5 is running on introductory pricing of $2 per million input tokens and $10 per million output. After August 31 it moves to $3 and $15IPO — Bankers are reportedly lining up investor meetings for Anthropic ahead of a possible public listing as soon as October
Articles/Cowork
Cowork/2026-03-16Intermediate

Automate note Content & Monetization with Cowork: Build a Subscription Business

Discover how to use Cowork and Claude in Chrome to automate note.com membership content creation, analytics, and grow passive income from your writing.

Cowork33note2Monetization9MembershipAutomation38Passive Income

Understanding note's Membership Revenue Model

What is note?

note is a Japanese content platform where creators can publish and monetize text, images, audio, and video. It's particularly popular in Japan for bloggers, writers, and independent creators seeking direct audience monetization.

note's Revenue Streams

FeatureDescriptionPrice Range
One-time ArticlesSell individual articles¥100–¥10,000
Support DonationsReaders donate any amount¥100–¥10,000
Membership (Subscription)Monthly recurring subscribers¥100–¥10,000/month

This guide focuses on Membership subscriptions, which provide the most predictable recurring revenue. By charging ¥300–¥1,000/month for exclusive member-only content, you build a sustainable subscriber-based income stream.

Revenue potential: 50 subscribers at ¥500/month = ¥25,000/month (~$170 USD)

Automating note Content with Cowork

Step 1: Access note Management Dashboard

Use Claude in Chrome to navigate the note platform and review current membership settings.

"Open the note management dashboard (https://note.com/my_page).
Retrieve:
- Current membership subscription price
- Total member count
- This month's revenue
- Membership page description and enrollment status"

Claude in Chrome provides a real-time snapshot of your membership performance.

Step 2: Trending Topic Analysis & Keyword Research

Automate the content idea generation process by analyzing trends and reader demand.

"Research and compile the following:
 
1. Google Trends: Top trending keywords in AI, tech, business, and productivity
   (past 30 days)
2. Twitter Trends: Identify trending topics in #tech and #business hashtags
3. My note Performance: Review past 60 days of article analytics
   - Which articles have highest views?
   - Which topics get most 'support' (donations)?
   - Which attract most subscribers?
4. Competitor Research: Review top 3 competing creators' popular articles
   - What topics appear most frequently?
   - What subscriber counts do similar creators have?
 
Based on this analysis, generate 3 article topic ideas for my membership audience.
For each idea, explain:
- Why it's trending
- Estimated reader interest
- How it differs from competitor content"

Example output from Claude:

  1. "How to Build a 6-Figure Income with Cowork Automation"

    • Trend Signal: Cowork-related searches increased 40% month-over-month
    • Competitor Gap: Few creators cover Cowork + monetization together
    • Subscriber Appeal: High (previous "automation income" article got 2.5K views)
  2. "Claude API Mastery: Prompt Engineering for Developers"

    • Trend Signal: Claude 3 release drove 200% increase in API-related queries
    • Subscriber Appeal: Developer audience actively seeks practical implementation guides
    • Competitor Gap: Most guides are too theoretical; practical tutorials are scarce
  3. "Personal Branding in the AI Age: 100K Follower Strategy"

    • Trend Signal: AI + personal brand = sustained trending topic
    • Competitor Gap: Existing content is generic; personal case studies perform well
    • Subscriber Appeal: Aligns with creator economy interests

Step 3: Auto-Generate Article Drafts

Once you've selected a topic, have Claude generate a complete first draft.

"Write a note membership article with these specifications:
 
**Title:** How to Build a 6-Figure Income with Cowork Automation
 
**Target:** note membership subscribers (creators and entrepreneurs)
**Word count:** 2,500–3,000 words
**Tone:** Helpful, personal, conversational (use 'you' and 'I')
 
**Structure:**
1. Hook (why Cowork automation matters now)
2. How I started + early mistakes (personal story, 300 words)
3. Three proven income strategies (each: 600 words, include real examples)
4. Real case studies (2 examples of client/project success)
5. Common questions FAQ
6. Call-to-action
 
**Include:**
- 1-2 actual code snippets or workflow diagrams
- Screenshots/UI references where helpful
- Keywords: 'Cowork', 'automation', 'side income' (each 3-5 times naturally)
- 2-3 internal links to related note articles
 
Format in Markdown. Ensure it's ready to paste into note editor."

Claude generates a complete, publication-ready draft. You can review and refine if needed, but it's typically 80-90% ready to publish.

Typical generation time: 2-3 minutes for a 2,500-word article

Step 4: Auto-Post to note

Once the draft is approved, use Claude in Chrome to input it into note's publishing system.

"Visit note.com and create a new article post:
 
**Article Details:**
- Title: [article title from draft]
- Body text: [paste the full Markdown draft, formatted for web]
 
**Publication Settings:**
- Mark as 'Membership Only' (not free access)
- Set price to 'Membership subscription access'
- Tags: ['Cowork', 'Automation', 'Income', 'Side Hustle']
- SEO Description: Generate a 120-character Google search preview
 
**Final step:** Save as draft (do not publish yet—I'll review before going live)"

Claude inputs the article into note's dashboard and saves it as a draft for your review.

Step 5: Announcement & Call-to-Action

Drive membership enrollment by announcing the new article to both members and non-members.

For existing members (email/direct message):

"Use note's 'Member Message' feature to send this announcement:
 
---
 
📄 **NEW EXCLUSIVE ARTICLE**
 
Just published for members only:
 
'How to Build a 6-Figure Income with Cowork Automation'
 
In this article, I'm sharing:
✅ The exact Cowork strategies I use for clients
✅ How I landed 10+ automation projects in 3 months
✅ Income breakdown (what actually pays well)
✅ Case studies: 2 real client projects worth $50K+ combined
 
This is the complete breakdown usually only my paid consulting clients see.
 
**Member-only link:** [auto-insert article link]
 
---"

For non-members (social promotion):

"Post on Twitter/X:
 
'Just shared a detailed breakdown of how I built a 6-figure automation income
using Cowork. Member-exclusive article.
 
The strategies inside have already generated $150K+ combined across my clients.
 
Not a member yet? Read the preview and join: [link]
 
#Cowork #Automation #Entrepreneurship'"

Member Engagement & Analytics

Step 6: Analyze Article Performance

After publishing, measure article success and member satisfaction.

"Check note analytics and retrieve:
 
**Article Metrics (past 7 days):**
- Views/reads
- 'Support' (donation) count and revenue
- Comments and their sentiment
- Read completion rate
- Time spent reading
 
**Membership Metrics:**
- New members joined
- Cancellations (churn)
- Most popular member articles
- Member comments/feedback themes
 
**Summary:** Is this article resonating? Should I write more like it?"

Sample output:

📊 Article Performance: "Cowork Automation Income"
├─ Views: 856
├─ Support (donations): 12 × ¥500 = ¥6,000
├─ Comments: 8 (mostly positive)
├─ Read completion: 64% (good—indicates strong engagement)
└─ Avg. time on page: 6 min 24 sec

💰 Membership Impact
├─ New members: 5 (+5)
├─ Cancellations: 0
├─ Current total: 48 members
├─ Monthly recurring revenue: ¥24,000 (5 new members × ¥500 + existing 43 × ¥500)

💡 Insight: This topic resonates. Next month, plan another automation/income-focused article."

Step 7: Respond to Member Feedback

Member comments reveal what subscribers value most, guiding your future content strategy.

"Review all member comments on the new article.
Identify:
1. Questions or requests for follow-up content
2. Specific topics members want covered next
3. Feedback on writing quality/clarity
4. Suggestions for case studies or examples
 
Based on this feedback, generate 2 new article ideas for next month."

Feedback insights might reveal:

  • "Can you write a detailed API implementation guide?"
  • "More real-world examples like the client case studies"
  • "A video walkthrough of your Cowork setup would help"

These become your next month's article topics, ensuring content stays aligned with subscriber needs.

Automated Publishing Schedule with Cowork

Step 8: Schedule Monthly Content Planning

Create a recurring Cowork task that automates your entire monthly publishing workflow.

Task Name: Monthly note Content Automation
Frequency: 1st of every month at 10:00 AM
Duration: Runs automatically every month

Task workflow:

"Execute the following monthly content pipeline:
 
### Phase 1: Trend Analysis (complete by 10th)
Gather:
- Google Trends top keywords (AI, business, productivity)
- Twitter trending topics (#tech, #business, #startup)
- My own note analytics (past 30 days)
- Competitor analysis (top 5 creators' recent articles)
- Member comment themes (what are they asking for?)
 
Output: Rank 5 potential article topics by interest + trend strength
 
### Phase 2: Draft Generation (complete by 15th)
- Select the top 2 topics
- Generate full 2,500-word drafts for each
- Check: SEO keywords, Markdown formatting, internal links
- Save drafts to Notion: [workspace link]
 
Deliverable: 2 publication-ready drafts with edit-ready formatting
 
### Phase 3: Publishing Prep (complete by 20th)
- Visit note.com and create 2 draft posts
- Input Article 1: [auto-fetch from Notion and paste]
- Input Article 2: [auto-fetch from Notion and paste]
- Set both to 'Membership Only'
- Add tags and metadata
- Preview for errors
 
Deliverable: 2 drafted posts ready for human review + go-live approval
 
### Phase 4: Member Engagement (complete by 25th)
- Review last month's analytics
- Identify top 3 most popular topics
- Generate 1 follow-up article idea for month 2
- Prepare member announcement text
- Run simple survey: 'What should I cover next?' (create 3-option poll)
 
Deliverable: Survey results + refined topic roadmap for Month 2
 
### Final Output: Monthly Report
Create Markdown report including:
- Topic rankings and trend analysis
- Draft preview (first 500 characters of each)
- Member feedback summary
- Revenue metrics (members, MRR, support donations)
- Recommendations for next month
 
Format: /reports/note-monthly-{date}.md"

This automation runs on the 1st of every month, handling 80% of the content planning and preparation work. By the 20th, you have articles ready to review and publish.

Revenue Optimization Best Practices

Membership Price Strategy

Choose a price that balances accessibility (higher enrollment) with revenue maximization.

PriceProsConsBest For
¥100–¥200/moEasy signup, high volumeLow per-member revenueBuilding audience first
¥300–¥500/moBest balance (recommended)N/AMost creators
¥1,000/moHigh per-member revenueVery small subscriber basePremium/expert content

Recommendation: Start at ¥300–¥500/month. After 50+ members, test increasing to ¥700/month if engagement is strong.

Publishing Cadence

Balance content quality and member satisfaction against your effort.

FrequencyMember SatisfactionWorkloadRecommendation
4+ posts/week⭐⭐⭐Very HighUnsustainable
2–3 posts/week⭐⭐⭐HighRequires a team
1 post/week⭐⭐⭐Medium✅ Ideal with automation
1–2 posts/month⭐⭐LowRisks member churn

With Cowork automation, publishing 1 article/week is highly sustainable.

Call-to-Action (CTA) Placement

Drive new subscriptions by placing compelling CTAs throughout your presence.

Article CTA example:

📚 This is a member-exclusive article.

New here? Join 45+ subscribers getting weekly insights on Cowork automation,
side income, and creator tools.

✅ Automation Income Strategies (guide)
✅ Claude API Implementation (code examples)
✅ Creator Business Models (case studies)

**+ New member-exclusive articles every week**

👉 Subscribe now: ¥500/month (or your custom price)
[Join button]

Optimal placements:

  1. Top of article (before full read)
  2. Middle (after 50% of content)
  3. End (call-to-action summary)

Real-World Revenue Projection

Goal: ¥30,000/month (¥500 × 60 members)

Month 1: Building Foundation

  • Members: 0 → 10
  • Articles: 4 (weekly)
  • Revenue: ¥5,000

Months 2–3: Growth Phase

  • Members: 10 → 35
  • Articles: 4 per month (total 8 new articles)
  • Revenue: ¥17,500

Months 4+: Stable Growth

  • Members: 35 → 60
  • Articles: 4 per month (recurring)
  • Revenue: ¥30,000 (sustainable)

Success factors:

  1. High-quality articles drive CTR on CTAs (20–30% conversion on visitors)
  2. Weekly consistency builds trust and reduces churn (<5% cancellation rate)
  3. Member engagement via comments/feedback increases retention
  4. Automation via Cowork makes weekly publishing sustainable for solo creators

Wrapping up

Using Cowork and Claude in Chrome for note automation:

Automate trend analysis and topic selectionGenerate publication-ready articles in minutesSchedule monthly publishing workflowsTrack member engagement and revenue metricsBuild sustainable ¥20K–50K/month passive income

Start with 1 article/week, build an audience of 30–50 members, then scale. The Cowork automation framework makes high-frequency publishing feasible even as a solo creator.

Ready to launch? Set up your note membership, create a Cowork scheduled task, and start automating your content empire today.

Share

Thank You for Reading

Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • Copy-paste ready implementation code
  • New advanced guides published daily
  • $5/mo or $10 for lifetime access
View Membership →

If you found this article helpful, a small tip ($1.50) would mean a lot to us. Your support helps keep this site ad-free and covers server and hosting costs.

Related Articles

Cowork2026-07-02
How Many Tasks Fire in the Same Minute — Flattening Cowork Scheduled-Task Collisions from Cron
When Cowork scheduled tasks bunch up at the same time and fight over shared resources, you can expand every cron expression into fire times, count collisions and true concurrency, and shave the peak with a greedy offset that never moves your premium slots. With working code and measured before/after numbers.
Cowork2026-07-01
Let the Downstream Task Verify the Upstream Actually Ran Today: A Completion Ledger and Dependency Barrier for Unattended Schedulers
Unattended schedulers have no notion of dependencies, so when a morning data-refresh task fails silently, the noon generation task keeps running on yesterday's leftovers. This is a design for recording upstream completion atomically and having downstream assert its preconditions before running, with working TypeScript and lessons from my own operations.
Cowork2026-06-29
Failing Loud on Stale Inputs: A Freshness Contract for Unattended Pipelines
How to stop a scheduled, unattended pipeline from silently shipping degraded work when its upstream data is empty or stale. We implement a freshness contract in bash that asserts recency, non-emptiness, and provenance, plus two real pitfalls I hit running Cowork scheduled tasks.
📚RECOMMENDED BOOKS
Build a Large Language Model (From Scratch)
Sebastian Raschka
LLM Dev
Prompt Engineering for LLMs
Berryman & Ziegler
Prompting
AI Engineering
Chip Huyen
AI Eng
* Contains affiliate links
See all →