Best for
- B2B teams with useful blog content that is not converting into leads
- Content marketers who need a lead magnet without starting from zero
- Demand gen teams building campaign assets from existing content
Convert related blog posts into a concise gated guide with a stronger narrative, designed PDF, landing page copy, and promotion assets.
Create a gated mini-guide package from existing blog content, including outline, rewritten guide copy, PDF design notes, landing page copy, and launch snippets.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
5 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Most teams have useful blog posts that never become campaign assets. A mini-guide gives existing content a stronger narrative, clearer audience, and gated conversion path. This workflow repackages what already exists while adding enough structure, editing, and design to make it feel like a real asset.
Expected results
Gated asset created
1 mini-guide
The workflow turns existing posts into a coherent downloadable guide with a clear promise.
Source reuse
3 posts repurposed
The guide uses existing content but restructures it into a new asset rather than combining posts unchanged.
Launch package
Landing page plus promo copy
The guide is packaged with page copy, social posts, email blurbs, and sales sharing notes.
Time saved
6-10 hours
Starting from existing blog posts reduces research and writing time while still requiring editing, design, and QA.
Step-by-step workflow
The first 3 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
45-60 min
45-60 min
Set up: In Google Docs, create a mini-guide brief with the three candidate blog URLs, publication dates, current traffic or engagement, target persona, funnel stage, conversion goal, and intended CTA. Confirm that all three posts address different parts of one reader problem rather than merely sharing a category tag or keyword.
Build: Write a one-sentence guide promise using the format: after reading this guide, {{persona}} will be able to {{specific_outcome}} without {{common_obstacle}}. Add a source-coverage table showing what each post contributes, where the posts overlap, which sections appear outdated, and what is missing from the combined narrative.
Scope: Define the approval owner, due date, desired page range, brand voice, required proof, and any product or legal claims that need review. Reject or replace any post that does not clearly support the promise, contains mostly promotional material, or targets a different audience.
Output: Save the approved brief in Google Docs and record the source URLs, selection rationale, reviewer, and approval date at the top of the document.
An approved mini-guide brief with aligned source posts, one audience promise, content gaps, CTA, scope, and review ownership.
Use the source-coverage table to spot a weak third post early. It is cheaper to replace a source before extraction than to force irrelevant material into the final guide.
60-90 min
60-90 min
Capture: Copy the full text of each approved blog post into a source section in Google Docs and retain the URL, author, publication date, and last-updated date above each post. Mark statistics, customer examples, screenshots, product claims, and external references that may require re-verification before they are reused.
Set up: Open Claude, start a new chat for source extraction, and paste the prompt below into the main chat composer.
Action: Include the approved guide brief, all three blog posts, source metadata, brand guidance, and known outdated sections as source inputs. Ask Claude to separate reusable ideas, examples, frameworks, visuals, and proof from SEO filler, duplicated explanations, tangents, and unsupported claims.
Output: Copy the structured extraction into a Source Inventory section in Google Docs and save the Claude response or conversation link with the working files. QA the inventory by tracing every retained idea back to a source passage and flagging any claim, statistic, or customer reference that lacks a current verification source.
A traceable source inventory containing reusable ideas, evidence, visuals, exclusions, and verification flags from all three posts.
45-60 min
45-60 min
QA: Review the Source Inventory and decide the reader journey from current problem to the promised outcome before asking for an outline. Define the approximate page budget, number of core sections, required proof, and one practical artifact such as a checklist, worksheet, scorecard, or template.
Set up: Open Claude, continue in the mini-guide project or start a new outline chat, and paste the prompt below into the main chat composer.
Action: Include the approved guide brief, cleaned Source Inventory, content gaps, page constraints, CTA, brand voice, and required practical artifact as source inputs. Ask Claude to create a new narrative sequence rather than preserving the order of the original blog posts, with each section stating its reader purpose, source material, proof, and visual opportunity.
Output: Copy the selected outline into Google Docs and save rejected structures or open questions in an Editorial Decisions section. QA the outline by confirming that every section advances the guide promise, no major idea is repeated, every factual section has source coverage, and the CTA follows naturally from the reader outcome.
An approved, source-linked mini-guide outline with a new narrative, section purpose, proof plan, visual opportunities, practical artifact, and CTA.
Pro workflow preview
Previewing 3 of 8 steps
Get the remaining 5 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Keep source IDs beside every extracted item. That makes later fact checking and editorial review much faster than searching across three original posts.
Extract only the source material that supports this gated mini-guide.
Source inputs:
- Approved guide brief and promise: {{guide_brief}}
- Target audience and funnel stage: {{target_audience}}
- Blog post 1 with URL and date: {{blog_post_1}}
- Blog post 2 with URL and date: {{blog_post_2}}
- Blog post 3 with URL and date: {{blog_post_3}}
- Brand and editorial guidance: {{brand_guidance}}
- Known outdated or prohibited material: {{known_exclusions}}
For each post, return:
1. Reusable ideas tied to the guide promise
2. Examples, frameworks, and step-by-step material
3. Statistics, claims, and customer references requiring verification
4. Screenshots, diagrams, or visual concepts worth reusing
5. Repetitive, outdated, promotional, or SEO-oriented sections to remove
6. Source ID and source passage for every retained item
7. Gaps the three posts do not cover
8. Recommendation to keep, rewrite, combine, or exclude each major section
Do not draft the guide. Preserve traceability to the original sources and do not strengthen claims beyond what the posts support.Add a reader-purpose sentence to every section. If two sections serve the same purpose, combine them before drafting.
Create a coherent gated mini-guide outline from the approved source inventory.
Source inputs:
- Approved guide brief and promise: {{guide_brief}}
- Cleaned source inventory with source IDs: {{source_inventory}}
- Content gaps to address: {{content_gaps}}
- Target page range and section constraints: {{page_constraints}}
- Required practical artifact: {{practical_artifact}}
- Brand voice: {{brand_voice}}
- Final CTA and conversion goal: {{cta}}
Return:
1. Working title and subtitle
2. Introduction purpose and opening angle
3. Three to five core sections in a new narrative order
4. Reader purpose for each section
5. Source IDs and proof assigned to each section
6. Examples and visuals to include
7. Practical worksheet, checklist, scorecard, or template placement
8. Transition logic between sections
9. Conclusion and CTA section
10. Gaps that still require research or SME input
Do not preserve the original blog-post order. Avoid duplicated sections and do not introduce unsupported claims.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
Produce a polished 8-12 page white paper with source-backed arguments, executive-ready structure, visuals, and a downloadable PDF.
Create a gated white paper draft, supporting research notes, designed sections, and promotion copy from an existing webinar deck.
Create a benchmark report package from survey data, including cleaned data, segment analysis, charts, report copy, landing page copy, and promotion assets.