Turn 3 blog posts into a gated mini-guide

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. 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. 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. Save the approved brief in Google Docs and record the source URLs, selection rationale, reviewer, and approval date at the top of the document.

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. Open Claude, start a new chat for source extraction, and paste the prompt below into the main chat composer. 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. 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.

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.

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. Open Claude, continue in the mini-guide project or start a new outline chat, and paste the prompt below into the main chat composer. 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. 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.

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.

Create a Google Docs drafting template with the approved outline, section owners, source IDs, verification notes, visual placeholders, and status fields for Draft, Review, Approved, and Designed. Draft one section at a time so each section can be reviewed against its purpose and source material before the full guide is assembled. Open Claude, use a separate chat or clearly labeled turn for the section being drafted, and paste the prompt below into the main chat composer. Include the approved outline, section purpose, assigned source excerpts, verified claims, brand voice, reader knowledge level, and practical takeaway as source inputs. Ask Claude to draft concise copy with useful transitions, examples, and a clear takeaway while marking any sentence that requires verification or editorial judgment. Copy the draft into the correct section of Google Docs and save the Claude output or conversation link in the section notes. Review each section for source fidelity, duplication, unsupported claims, generic filler, tonal consistency, and whether it moves the reader toward the promised outcome before advancing its status.

Draft one section of the approved mini-guide.

Source inputs:
- Approved outline: {{approved_outline}}
- Section name and reader purpose: {{section_name_and_purpose}}
- Assigned source excerpts with source IDs: {{section_source_material}}
- Verified claims and approved proof: {{verified_claims}}
- Brand voice and reading level: {{brand_voice}}
- Required example or visual placeholder: {{example_or_visual}}
- Practical takeaway for this section: {{practical_takeaway}}

Create:
1. Section heading and optional subhead
2. Concise section draft
3. Transition from the previous section
4. Example, framework, or evidence placement
5. Practical takeaway
6. Visual or callout note
7. Claims requiring human verification
8. Editorial questions or missing inputs

Do not invent statistics, customer examples, or product claims. Avoid generic blog-style introductions and keep the section focused on its stated reader purpose.

Choose the practical artifact promised in the outline and define the real decision or action it should help the reader complete. List the minimum fields, scoring logic, instructions, examples, and output the reader needs without turning the artifact into another long chapter. Open Claude, start a focused artifact-design chat, and paste the prompt below into the main chat composer. Include the guide promise, target persona, approved sections, reader outcome, artifact type, brand terminology, and any scoring or compliance constraints as source inputs. Ask Claude to create the artifact, completion instructions, a realistic filled example, and guidance for interpreting or using the result. Copy the artifact into a distinct Google Docs section and save an editable version or table layout that can later be recreated in Canva. Test the artifact with one person from the target audience or an internal proxy, then revise any field, instruction, or scoring rule they cannot understand or complete without explanation.

Create the practical artifact for this mini-guide.

Source inputs:
- Guide promise: {{guide_promise}}
- Target persona and context: {{target_persona}}
- Approved guide sections: {{approved_sections}}
- Reader outcome: {{reader_outcome}}
- Artifact type: {{artifact_type}}
- Brand terminology: {{brand_terminology}}
- Scoring, legal, or compliance constraints: {{constraints}}

Return:
1. Artifact title and purpose
2. Completion instructions
3. Fields, checklist items, or scoring criteria
4. Editable table or page structure
5. One realistic filled example
6. How to interpret the result
7. Recommended next action based on the output
8. Usability-test questions

Keep it simple enough to use immediately. Do not add scoring logic that cannot be explained or supported.

Run Grammarly across the complete Google Docs draft for grammar, clarity, sentence length, tone, and repeated language, but review every suggested rewrite before accepting it. Create a verification table listing each statistic, factual claim, customer reference, product statement, quotation, and external source with its original source, current verification URL, reviewer, and status. Re-check publication dates and replace outdated evidence with current approved sources or remove the claim if it cannot be supported. Complete a manual editorial pass for narrative flow, section transitions, consistency with the guide promise, CTA alignment, and whether the worksheet matches the surrounding content. Route customer, legal, regulatory, and product claims to the appropriate reviewer and record approval or required changes in Google Docs comments. Confirm that all source attributions, image permissions, screenshots, and customer names are approved for gated distribution. Lock the Approved Copy version only after all high-risk comments are resolved and the verification table contains no unexplained open items.

Create a Canva file using the approved brand kit and define the page system before laying out individual pages, including cover, table of contents, section opener, standard content page, callout, worksheet, and CTA page. Import only the locked Approved Copy and use visual placeholders from the draft to assign diagrams, screenshots, icons, pull quotes, and proof callouts. Keep body type, line length, spacing, color contrast, and heading hierarchy consistent so the guide remains readable on screen and when printed. Recreate the practical artifact as a usable page rather than shrinking a dense Google Docs table into the layout. Add page numbers, source notes, image credits, legal footers, and accessible link text where required. Export a review PDF and test it on desktop and mobile for clipping, broken links, low-resolution assets, inaccessible contrast, missing fonts, and awkward page breaks. Save the editable Canva source, final PDF, export date, version, and design approver in the campaign folder.

Prepare the final guide title, promise, audience, verified takeaways, preview image, form fields, privacy language, thank-you experience, CTA, and channel plan before writing launch copy. Open Claude, start a new launch-package chat, and paste the prompt below into the main chat composer. Include the approved guide summary, target audience, landing-page requirements, verified takeaways, brand voice, form strategy, CTA, distribution channels, and prohibited claims as source inputs. Ask Claude to create landing-page copy, thank-you-page copy, social variants, email blurbs, and a sales-sharing note that sell the reader outcome rather than the fact that blog posts were repurposed. Copy the approved page copy into Webflow and save the channel snippets in the campaign document with owner, status, tracking URL, and publish date. Configure the form, consent language, asset delivery, CRM campaign association, confirmation email, UTM rules, and conversion event, then test the full path with internal and external email addresses. Launch only after confirming that the PDF downloads correctly, attribution is captured, the thank-you experience works, mobile layout is clean, and the campaign owner has approved the final page.

Create the launch package for this gated mini-guide.

Source inputs:
- Approved guide title and summary: {{guide_summary}}
- Specific guide promise: {{guide_promise}}
- Target audience and funnel stage: {{target_audience}}
- Verified key takeaways: {{verified_takeaways}}
- Brand voice: {{brand_voice}}
- Landing-page and form requirements: {{landing_page_requirements}}
- CTA and thank-you experience: {{cta_and_thank_you}}
- Distribution channels: {{distribution_channels}}
- Prohibited or unsupported claims: {{prohibited_claims}}

Create:
1. Landing-page headline and subhead
2. Outcome-focused introduction
3. Three to five what-you-will-learn bullets
4. Form CTA and privacy reassurance
5. Thank-you-page copy and next step
6. Three LinkedIn post variants
7. Two email blurbs
8. Sales-sharing note
9. Meta title and meta description
10. QA checklist for message consistency across the funnel

Do not describe the asset as three blogs combined. Sell the specific reader outcome and use only verified claims.