A custom pipeline that pulls live data, writes structured drafts and stages them in your CMS, so your team only does the part that needs a human: the final review. Built once, runs daily.
Pipeline: match preview, today 06:00
At an assumed €0.12–0.20 per word, a single 1,000-word article costs €120–200 from a decent freelancer, before briefing, revisions, and the two weeks of lead time. Publish 60 articles a month and you're spending the salary of a full-time hire on content that still arrives inconsistent in structure, tone, and SEO basics.
The uncomfortable part: most recurring content formats (match previews, product roundups, data-driven comparisons, local guides, news summaries) follow the same structure every single time. You're paying human rates for template work.
A pipeline is a fixed, quality-controlled assembly line. Five stages, every article, every time.
The pipeline pulls structured, verified data from APIs and feeds: odds, prices, specs, schedules, inventory. No data source, no article. That's the hallucination firewall.
A tuned system prompt turns that data into a draft matching your exact format: your headings, your tone, your internal linking rules, your schema. Identical structure, every time.
Automated checks before anything reaches you: fact consistency against the source data, length, forbidden claims, duplicate detection.
Drafts land in WordPress with title, meta, schema, and categories already set. Nothing auto-publishes without your sign-off unless you want it to.
A human reviews, adjusts a sentence if needed and hits publish: around 5 minutes with a clean setup. That's the whole manual workload.
What freelance content production costs you per month, compared with an automated pipeline where an editor reviews every article, around 5 minutes with a clean setup. Drag the sliders or type your numbers directly.
Runs entirely in your browser. Nothing you enter is sent anywhere.
Automated cost = around 5 minutes of editorial review with a clean setup, at your hourly rate. Assumes the pipeline replaces the per-word freelance fee. Engagement reference: €2,290. Estimates only.
Strong fits are recurring, data-driven formats: the content where you're currently paying human rates for template work.
Daily previews, odds movement, results coverage. Same structure, fresh data, every day.
Product comparisons, price updates, category texts that stay current without a content team.
Destination guides, seasonal updates, event calendars, refreshed automatically.
Spec pages, model comparisons, how-to content built from structured data.
Changelog posts, integration pages, programmatic landing pages at scale.
Market summaries, regulatory updates, weekly roundups, minutes after the data lands.
Not a fit: opinion pieces, brand storytelling, investigative content, anything without a reliable data source behind it. If your use case is in this bucket, I'll tell you in the first call. Sometimes no pipeline is the honest answer.
With the assumptions below: from €120–200 per freelance article to a few euros for review time and tokens. Run the numbers with your own figures.
React to events, price changes, and news same-day instead of next sprint.
Every article carries your structure, schema, and internal links. No more editing freelancers back on-brand.
60 or 600 articles a month is a config change, not a recruiting project.
Generation is grounded in your feeds, which is what keeps quality stable and hallucinations out.
Nothing publishes without human review unless you decide otherwise.
Paid per word, per article
€120–200 per 1,000-word article
Assumption: €0.12–0.20 per word. Enter your own rate in the calculator above.
Salaried content role
€140–275 per article at realistic capacity
Assumption for a mid-level content role in the DACH region, gross salary plus employer contributions. Your numbers may differ.
Custom build, human review
a few € per article: around 5 minutes of review with a clean setup, plus tokens
Excludes AI token costs, which run on your own accounts. The calculator above shows if and when the setup pays off with your numbers.
Individual quoted per scope
For brands producing across markets: one shared infrastructure, per-market output in every language you publish in.
from €2,290 one-time
A production content pipeline for one site, one language: from data source to reviewed draft in your CMS. Built by me, owned by you.
€1,890 /month · 3-mo minimum
Ongoing senior SEO oversight with automation built in. For sites where rankings directly drive revenue.
Setup prices exclude AI token costs. These run on your own API accounts for full cost control.
The complete build: workflow architecture, integration of your data sources (APIs, feeds), system prompt engineering based on your best existing article as the format template, automated quality gates, CMS integration with drafts staged in WordPress, an editorial review workflow, documentation, a handover session, and 30 days of post-launch adjustments. It is a one-time fee, and the pipeline belongs to you afterwards.
Token costs are the usage fees of the AI provider (e.g. OpenAI or Anthropic) for generating text. They run on your own API account so you have full cost control and no markup from me. How much they come to depends on the model and text length; compared with per-word freelance rates they usually matter little.
Google's published position is that it rewards helpful content regardless of how it is produced, and penalizes content created primarily to manipulate rankings, human-written spam included. That is why the pipeline is grounded in verified data sources, follows a fixed quality structure, and keeps a human review before publishing. Data-driven, useful, reviewed content is exactly what this builds.
Strong fits are recurring, data-driven formats: sports previews, product comparisons, price and spec pages, destination guides, market summaries, programmatic landing pages. Poor fits are opinion pieces, brand storytelling, and anything without a reliable data source behind it. If your use case is in the second bucket, I will tell you in the first call. Sometimes no pipeline is the honest answer.
A single-site, single-language pipeline is typically live within 2–4 weeks, depending on how quickly data source access and CMS credentials are available. The first week produces reviewable test articles; the remaining time goes into prompt refinement and quality gates.
Yes, deliberately. The pipeline stages drafts; a human approves them. Reviewing an article takes around 5 minutes with a clean setup, because structure, data, meta and schema are already handled. Full auto-publishing is technically possible and some clients use it for low-risk formats, but human sign-off is the default I recommend.
15 minutes, no pitch deck. Bring your current production costs and your data sources. I'll tell you straight whether a pipeline makes sense, what it would save, and what it would cost. If it doesn't fit, I'll say that too.
You talk to the person who builds it. Replies within 24h.