コンテンツファクトリー Dot
あなたの dot が Notion のコンテンツカレンダーを埋め続け、共有したインタビューをすべてパックにします。
出品者：GetKits
その違いをご覧ください
ポッドキャストの文字起こしから、Notion に下書き8本
ビフォー
木曜 13:00 のチェックイン。Google Drive の「Content sources」に新規：Lena Zhou がゲストの48分のポッドキャスト文字起こし。ファイルに公開日の記載なし。
アフター
「私が見てきたスコープの揉め事は、どれもクライアントがファイルを見つけられないところから始まった。」（31:12） 新しいパック 2026-W43-scope-creep の一番強い一文です：Notion のコンテンツカレンダーに下書き8本、レビュー待ち。マージン15%の主張はあなたの [要確認] 待ちです。 あなたの決定事項：エピソード公開まで、どの投稿からもリンクできるようパックを保留しますか？推奨：はい。
Voice memo too thin to pack
ビフォー
Tue 2026-11-03, 7:40 PM America/Toronto. Lena in ChatGPT: "pack this", with a voice memo transcript: "ok idea for next week. annual plans. people keep asking on calls if we do annual, we don't, and I think we should? maybe two months free, that's what everyone does. thing is a lot of our churn is around month 3 so annual would lock them in, but is that good. Jun said Lumen's annual went well. anyway something about pricing. also our pricing page has too many words, I counted like 400. ok that's it" Content calendar: 2026-W46 (Nov 9 to 15) has 0 rows. Next source run: Thu Nov 5, 1:00 PM.
アフター
Not enough here for a pack yet, so I have not drafted anything. The memo is 77 words, with one idea and no proof I can use: - Annual plans: your opinion ("I think we should"). Fernway has no annual plan yet, so there is no result to post. - "A lot of our churn is around month 3": no number. [confirm] before any piece uses it. - Lumen's annual plan "went well": Jun's result, secondhand. Usable only with his numbers and his OK [confirm permission]. - Pricing page "like 400" words: a second topic, and the count needs [confirm]. Three questions. Answer in one message, or record another memo: 1. What happened, with numbers? How many calls asked about annual plans, over what period, and what share of cancellations come in month 3? 2. What did you get wrong first? Anything on pricing you tried that did not work. 3. What would you tell another founder about annual plans, in one sentence? What I did: one Idea row, "Should Fernway offer an annual plan?", Pillar Running a small SaaS, Source "voice memo, Nov 3", no Publish date. No drafts. Decision for you: 2026-W46 has 0 of 9 slots filled. Options: A, answer the questions by Thursday 1:00 PM and the source run builds the pack from your answers; B, I fill W46 from unused ideas in recent SOURCE BRIEFs, marked Drafting; C, a light week of 4 pieces. Recommendation: A if you can answer by Thursday, otherwise B.
Monday calendar check finds the gaps
ビフォー
Calendar check, Mon 2026-10-12, 9:00 AM America/Toronto. Content calendar, next 14 days: - 2026-W42: 9 rows. 7 Approved. Newsletter section (Thu) and RED note (Fri) in Ready for review since Thu Oct 8. X thread (Tue) Approved with no publish time. - 2026-W43: 3 rows, all Idea. The scope-creep pack was held to 2026-W44 for the episode. Google Drive "Content sources": no new files. Lena's edits to W42 drafts: sentences shortened in 6 of 7 approved pieces.
アフター
PIPELINE UPDATE | Mon 2026-10-12, 9:00 AM | Calendar check New sources: none since Thursday Packs drafted: none Next 14 days: W42 9 of 9 filled (7 Approved, 2 Ready for review). W43 3 of 9 filled, all Idea. Gaps: - W43 has 6 open slots and no source. Thursday's source run has nothing to pack unless a file lands in Content sources. - Pillar Retention unused since 2026-W39. Stuck: - NEWSLETTER SECTION (Thu 10-15) and RED NOTE (Fri 10-16): Ready for review for 4 days. - X THREAD (Tue 10-13): Approved, no publish time. To confirm: the newsletter link line still says [confirm link]. It goes out Thursday. Voice: you shortened sentences in 6 of 7 approved W42 pieces. Suggest changing Rhythm in your VOICE PROFILE from 8 to 7 words average. Approve the profile edit? Decisions for you: 1. Tuesday thread time. Options: A, 9:00 AM, last thread's slot (depth 7.7 per 1k); B, another time. Recommendation: A. 2. Source for W43. Options: A, a Retention pack from the 3 unused ideas in the 2026-W41-chatbot SOURCE BRIEF; B, you drop a new source in Content sources by Wednesday; C, a light week of 4 pieces. Recommendation: A. It also fills the Retention gap. 3. Review the newsletter section and RED note today so Thursday's send is not blocked.
Asking before a post goes out
ビフォー
Tue 2026-10-13, 8:50 AM America/Toronto. Content calendar: X THREAD "We sent new agencies 7 onboarding emails on a timer", Approved, Publish date 9:00 AM, Pack ID 2026-W42-onboarding-emails. Custom rule: Post, schedule or quote-post on X = Ask before taking action.
アフター
Ready to post your X THREAD (2026-W42-onboarding-emails) at 9:00 AM America/Toronto. 7 posts, longest 235 characters. Post 7 now links the Fernway Notes signup page; you replaced the [confirm link] on Monday. No [confirm] left in the text. 1/ We sent new agencies 7 onboarding emails on a timer. 9% clicked. We cut it to 4, each sent when someone gets stuck. 31% clicked, and client invites in week one went from 22% to 38%. Below: what didn't work, then each email's one job. (posts 2 to 7 exactly as approved, published without the 1/ markers) Post it at 9:00 AM? Reply yes, give another time, or say you will post it yourself. Without a yes it stays in Notion. After posting I will add the URL to Notes and set Status to Published.
収録内容
- content-factory-dot-setup.md
この Kit について
Hand your ChatGPT dot the job of running your content pipeline. Drop an interview transcript or a long piece into a Google Drive folder, and by the next check-in it is a full content pack in your voice, written into your Notion content calendar as drafts. Twice a week your dot checks the next 14 days, flags gaps and stuck drafts, and brings you the publishing decisions with a recommendation. Setup takes about 12 minutes.
What you get
- A setup file for the dot you already have: which apps to connect and at what permission level, then three blocks to paste.
- The responsibility: sources to watch (Google Drive, Notion, X and anything you share in chat), what to keep current, which changes deserve your attention and where updates go.
- Working instructions: how to turn a source into a pack, the limits for every channel, the anti-AI pass, how to handle transcripts and guests, and how to fill gaps without filler.
- Nine custom rules, ready to add: draft edits happen without asking, posting and public replies need your yes, deletions are handed back to you.
- Two check-ins: a Monday calendar check and a Thursday source run, each ending in a PIPELINE UPDATE with numbered decisions.
- The same block names and Notion fields as the Content Factory Skill and Bot, so all three can work from one calendar.
Who it is for
- Podcast guests, hosts and speakers who produce long material every week and never get around to cutting it up.
- Founders and creators who already keep a Notion content calendar and want someone to keep it honest.
- Anyone with a ChatGPT dot who wants it to own a recurring job instead of waiting for prompts.
- Ghostwriters running a client's pipeline, where every public action needs the client's yes.
What it will not do
- Post, schedule or reply on X without asking you first, each time.
- Delete anything. Notion rows, Drive files and posts are handed back to you.
- Edit a row you approved. It tells you what should change and waits.
- Change your VOICE PROFILE without asking.
- Work from stale data. If Notion or Google Drive is unreachable at a check-in, it reports that and stops.
- Invent facts. Numbers it cannot trace to your source come back as
[confirm].
レビュー
まだレビューはありません。
