Content repurposing

This playbook defines how Pump Up's hosted agent adapts one approved source asset—such as a recorded webinar transcript, a technical whitepaper, or a customer case study—into channel-specific drafts for review and confirmed publication. One run governs exactly one authorized source document and its designated distribution briefs. The process extracts verified factual claims, maps verbatim quotes, constructs channel drafts adhering to specific audience constraints, submits drafts for editorial approval, stages drafts in destination tools such as Notion, Google Docs, Ghost, or Webflow, and verifies live publication or transmission. If a connection is unconfigured or unavailable, the agent exports formatted drafts to local files and notifies the channel owner for manual staging.

• Extract the primary source content, verify rights and attribution boundaries, and compile a verified claims ledger. Distinguish direct participant quotes, demonstrated product benchmarks, author opinions, and secondary references. If a statement makes a quantitative performance claim or quotes a third party without an explicit attribution clearance in the case file, isolate that statement and flag it as unverified rather than incorporating it into public copy.
• Retrieve the channel briefs associated with this run, identifying the target formats, audience contexts, length constraints, and destination platforms. Compare the core thesis of the source asset against each brief to select relevant angles, key takeaways, and tone requirements. Ensure that adapting an asset across channels preserves the substantive meaning and technical boundaries of the original text rather than flattening nuances into generic promotional blurbs.
• Draft channel-specific adaptations based strictly on the verified claims ledger and the constraints of each brief. For long-form newsletter editions or blog highlights, retain detailed technical context, source references, and methodology caveats. For concise updates or social sequences, focus on a single concrete takeaway supported by an exact source quote. Link every drafted paragraph or bullet directly to the corresponding timestamp or section in the primary source document.
• Information request. Present unverified, ambiguous, or contested source claims to the designated subject matter expert or content lead. Display the exact excerpt from the source asset, the proposed channel adaptation, the specific uncertainty or missing attribution, and the risk of misstatement. If the expert confirms the claim and provides supporting documentation, incorporate the verified wording into the draft; if the expert clarifies or narrows the assertion, update the draft to reflect the qualified scope; if the expert rejects the claim or does not respond within the agreed review window, remove the claim from all channel drafts and proceed with the remaining verified points.
• Approval. Submit the completed adaptation packet to the content editor and channel owners for line-by-line editorial sign-off. Present each channel draft alongside its target channel brief, source citations, proposed staging platform, and designated publishing owner. The channel editor may approve individual drafts, request specific copy revisions, reassign channel destinations, or decline a channel adaptation entirely. If an editor requests revisions, update the draft within the boundaries of the verified claims ledger and resubmit for approval; if an editor declines an adaptation, record the reason and mark that channel item as declined while advancing remaining approved channel drafts.
• Stage approved drafts in their respective destination platforms, such as Notion editorial databases, Google Docs workspaces, Ghost newsletter drafts, or Webflow CMS staging collections. Verify the creation of each draft by reading back the staged record ID, publication status, title, and body content from the destination system. Ensure that all staged items remain in draft or pending status and are not published live or broadcast publicly.
• Approval. Request final publishing authorization from the authorized publishing owner for each staged draft. Present the read-back confirmation, staging URL or record reference, scheduled release date, and target audience settings. The publishing owner authorizes the scheduled public release, directs the draft to remain held in staging pending a specific date, or cancels publication. If release is authorized, confirm the scheduling status in the publishing platform; if the owner directs a hold or cancellation, retain the staged draft in review status and record the owner's instructions.
• In a representative scenario, an enterprise software company repurposes an internal engineering talk about zero-downtime database migration into a technical blog post for Webflow and an executive summary for Ghost. During draft preparation, the agent identifies that the speaker casually mentioned a '99.999% availability guarantee' during the live Q&A, whereas the company's formal SLA commitment is 99.99%. Rather than propagating the five-nines figure into the blog draft, the agent isolates the claim and submits an information request to the lead infrastructure engineer. The engineer clarifies that the architecture achieved five nines internally during testing, but customer SLAs remain four nines. The agent revises the blog post to explicitly distinguish internal test benchmarks from customer SLA commitments, submits the revised drafts for editorial approval, receives sign-off from the technical editor, stages the blog item in Webflow as a draft, and confirms the staged record ID before requesting scheduling authorization from the VP of Marketing.
• Confirm case completion only when each authorized release is verified as actually published or sent, rather than resting on staging or scheduling records alone. For web publications, query the live URL or public CMS endpoint to confirm the approved text appeared live; for email broadcasts or social distributions, verify the successful send receipt or broadcast log from the sending platform; for manual distribution channels, obtain explicit confirmation of manual publication from the channel operator. If a channel adaptation was held, cancelled, or declined, preserve its explicit unresolved or declined disposition on the case timeline instead of counting it as published. If external platform APIs are unavailable or fail write operations, do not assume success; retry the write once after verifying system state, and if the write remains unconfirmed, export the finalized draft to a local markdown artifact, assign a manual handoff task to the content operations manager, and keep the case in pending manual confirmation until the operator verifies manual staging.