Fixed quote after a free call

Content repurposing automation and publish-ready metadata

We build a WordPress or Ghost automation that prepares each finished article for search and for other channels: headline and meta description options, alt text drafts, internal link suggestions from your archive, then newsletter, social and short video drafts in your own voice notes, each keeping its link back and any sponsor disclosure. Everything lands as an unpublished draft for an editor to approve. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why good articles stop at one channel

A strong article could reach readers as a newsletter feature, a social thread and a short video, but rewriting it for each channel by hand happens days later or not at all.

Metadata gets the same treatment. Titles, descriptions, alt text and internal links are added at the last minute, even though they decide how the piece appears in search and whether screen-reader users can follow it.

What we build

What our content repurposing automation includes

Headline and description options

A few title and meta description options within common length limits, for the editor to pick and edit.

Alt text drafts

Alt text for each image based on what it shows and why it is in the article, checked by a person.

Internal link suggestions

Older articles from your archive suggested as links, with the passage where each could fit.

Channel drafts

Newsletter, social and short video outline drafts following your tone notes, saved unpublished in your scheduling tools.

Disclosure carried over

Sponsor and affiliate disclosures from the original piece are kept in every repurposed version.

Missing-item check

Empty category, author, featured image or schema flagged before scheduling.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Article ready

    An edited post is marked ready in WordPress or Ghost.

  2. 02 Automated

    Metadata drafted

    Title, description, alt text and link suggestions are prepared.

  3. 03 Automated

    Channel drafts created

    Newsletter, social and video drafts appear unpublished in your tools.

  4. 04 Editor review

    Editor chooses

    The editor picks, edits or discards each suggestion and draft.

  5. 05 Editor or publisher decides

    Publication voice

    Nothing goes out under your name until the editor or creator approves it.

How it behaves

How repurposing drafts behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What readers see

  • Posts with clear titles, descriptions and accessible images
  • The same piece in the newsletter and on social, in your voice
  • Disclosures wherever sponsored content appears

What the editor sees

  • Metadata options and link suggestions beside each draft
  • Unpublished channel drafts ready to edit
  • A list of missing items before scheduling

What the automation does

  • Triggers on articles marked ready
  • Drafts metadata and channel versions
  • Keeps links back and disclosures intact

Edge cases and fallbacks

Article is sponsored
Every draft keeps the disclosure; drafts without it are blocked.
Image has no clear subject
Alt text left for the editor rather than guessed.
Suggested link points to an outdated post
Flagged so the editor can update or skip it.
AI provider outage
The article publishes as normal and drafts are prepared once the provider recovers.

Architecture

Repurposing one article for every channel at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Ready article WordPress or Ghost n8n Webhook trigger Draft writer Your tone notes Archive index Past articles Editor Picks and edits Unpublished drafts Social, newsletter
  • Input
  • Logic and services
  • AI step
  • Data
  • People
  • Output

How it flows

  1. 1 An article marked ready in the CMS triggers the workflow by webhook.
  2. 2 Metadata, alt text and channel drafts are prepared, and the archive index suggests internal links.
  3. 3 The editor picks and edits suggestions and applies them in the CMS.
  4. 4 Approved channel drafts are saved unpublished in the newsletter and scheduling tools.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Content repurposing & publish-ready metadata project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    CMS, channels, tone notes, metadata rules and archive size.

  2. 02

    Design

    2 to 3 days

    Draft formats per channel, length limits, link rules and approval steps.

  3. 03

    Build

    1 to 2 weeks

    CMS trigger, archive index, metadata and channel drafts.

  4. 04

    Shadow run

    About 1 week

    Drafts prepared for live posts while the editor compares with their own versions.

  5. 05

    Launch

    1 to 2 days

    Switch on for new posts.

  6. 06

    Support

    Ongoing

    Tone notes, new channels and prompt updates.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n WordPress REST API or Ghost Admin API webhooks Claude or OpenAI models Your newsletter platform YouTube Data API for video metadata Your social scheduling tool where it offers an API

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Channels, tone notes and metadata rules.

    $200 – $400

  • Build

    Trigger, archive index, metadata and channel drafts.

    $500 – $1,350

  • Integrations

    CMS, newsletter and scheduling tools.

    $150 – $350

  • Testing and shadow run

    QA and side-by-side drafts.

    $100 – $250

  • Launch and training

    Switch-on and editor walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. AI usage, CMS and scheduling tools are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • AI model usage: Billed by the provider per use; a few drafts per article is usually a small monthly amount.
  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter), billed annually.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: disclosures travel with the content

The FTC expects disclosures close to the endorsement in each place it appears, so repurposed versions keep the original disclosure.

Source: www.ftc.gov

EU: AI-generated text and editorial control

Article 50 of the EU AI Act exempts AI-assisted public-interest text from disclosure only where it has human review and editorial responsibility, which is how this workflow runs.

Source: artificialintelligenceact.eu

UK: affiliate content is advertising

Under the CAP Code an affiliate link makes the content advertising, so labels stay in every version.

Source: www.asa.org.uk

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Content repurposing automation questions questions, answered.

It turns one finished piece into drafts for other channels, such as a newsletter feature, social posts and a video outline, as soon as the original is ready. An editor approves each draft before it is scheduled.

Yes, usually. A WordPress or Ghost webhook starts an n8n workflow that drafts the metadata and channel versions. WordPress plugins can do parts of this; we use n8n when you want several tools connected.

They follow tone notes and approved samples you give us, and the editor rewrites anything that does not fit. Your voice is the reason readers follow you, so nothing posts without review.

It makes sure every piece leaves with a considered title, description, alt text and internal links. Google's guidance focuses on helpful, people-first content, so the article itself still matters most.

It saves drafts in your scheduling tool where that tool has an API. Posting stays a human decision.

Share of posts published with complete metadata, internal links added per post, repurposed versions published and time from publish to repurpose.

Free 20-minute call

Want this for your bloggers & publisher?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call