Service Marketing Automation

The content pipeline behind our daily blog, built for you.

Research, drafting, fact-checking, a person's review and publishing, wired into one pipeline. We run ours every day across our own sites and will build yours the same way.

Free discovery call. NDA before the first call if you need one.
Pipeline run · draft 2,481 4 of 5 stages clear
Research
6 sources, 2 rejected as thin
Done
Draft
1,340 words, house style applied
Done
Fact-check
3 claims verified, 1 flagged
Done
Human approval
waiting on an editor, 11m
Held
Publish
WordPress, scheduled 14:00
Queued

The flagged claim is why the editor gate exists. A pipeline that cannot stop is not a pipeline you can publish from.

Why this matters

Most "AI content pipelines" produce content no one would publish.

The first version is exciting. The tenth is generic. By the hundredth, your blog reads like every other AI-generated blog. We build pipelines that keep your editorial voice, ground every claim in your real sources, and put humans in the loop where judgment matters. The result is content you actually want to publish, at a cadence your team could not hit by hand.

In flight today

Six stages. Articles moving through.

The pipeline view our editors check first thing each morning. Every article passes through draft, edit, image, audit, ready, then live. Each stage has SLA. Watch one article promote forward when you scroll into the section.

Content pipeline · this week auto 22 in flight · 12 shipped this week
Draft 5
community

AI search visibility for BuddyPress sites

v0.3 · 1,840 w
guides

Headless WP, year 2: what we changed

v0.1 · 920 w
Edit 3
products

Why we switched from JetEngine to ACF

v1.2 · 2,140 w moving →
technical

Cloudflare Workers Assets at scale

v1.0 · 2,560 w
Image 2
case

LMS migration from Teachable to LearnDash

og + 4 inline
Audit 4
community

BuddyPress activity throttling patterns

SEO 92 · A11y 98
how-to

Setting up Stripe Connect for marketplaces

SEO 88 · A11y 100
Ready 3
technical

Astro 6 + WP REST: what to know

scheduled · 09:00 IST
community

Moderation queue patterns we ship

scheduled · Mon
Live 5
case

How we rebuilt our store on Astro

3.4k views · 18 ref
guides

Pre-release smoke testing for WP plugins

1.8k views · 6 ref
Avg time draft → live 4d 6h This week's velocity +18% vs prev SEO median 90 / 100 A11y median 98 / 100
  • House style baked into prompts · same voice across every article
  • Fact-check step uses retrieval over your real sources
  • Human gate at audit · publishing never bypasses a person

What we build

A pipeline your editors will actually use.

Research grounded in your real sources. Drafts in your house style. Fact-check before review. Human approval at the right step. Publishing wired to your CMS. Analytics closing the loop.

01

Research that uses your real sources

The pipeline pulls from your existing knowledge base, brand voice docs, customer research, and approved external sources. The AI does not invent context, it composes from the context you already have.

Drafts feel on-brand from version one.

02

Drafts in your house style

Style guide encoded as a Claude skill. Tone, sentence rhythm, banned phrases, paragraph structure all enforced. Editors edit voice nuances, not basic style.

Drafts arrive close enough that editing is editing.

03

Fact-check before human review

Every claim cross-checked against the source documents. Hallucinated stats flagged before they hit your editor. Sources cited inline so verification is one click.

Fact-check failures caught before publish, not after.

04

Human approval where it matters

No content publishes without an editor approval step. The pipeline does not replace editorial judgment, it just removes the time you spend on draft generation and formatting.

Editorial team retains full control of voice.

05

WordPress, Ghost, MDX, all supported

Publishing adapter ships content to wherever you publish. WordPress via REST, Ghost via API, static MDX via PR. Featured images, internal links, schema, all wired.

No manual copy-paste between tools.

06

Analytics loop closes the cycle

Published post performance tracked in GA4 and Search Console. Underperformers flagged. Best-performing patterns reused in future drafts. The pipeline gets smarter monthly.

Top-quartile post rate climbs measurably each quarter.

Per post

model spend logged per published post, research through to metadata

Every call in the pipeline is costed and attributed, so the bill reads as a line per post instead of one number at the end of the month.

Proof we run this ourselves

The pipeline ships our blog every day.

We use this exact pipeline to publish on wbcomdesigns.com, vapvarun.com, attowp.com, and three other properties. Every workflow we ship to a customer is one we already run for ourselves.

Recent runs across 5 properties
wbcomdesigns.com
Today · 2 drafts
Published
buddyxtheme.com
Yesterday · 1 draft
Published
reigntheme.com
Yesterday · 1 draft
Held for review
tweakswp.com
2 days ago · 2 drafts
Published

A pipeline is judged on the days it does not run cleanly. The held run is the one worth looking at.

Process

How a content pipeline project runs.

01

Discovery

Two weeks. We capture your style guide as a Claude skill, ingest your source documents, design the workflow stages, and lock the editorial approval rules.

Fixed scope, fixed price.

02

Build

Four to six weeks. Pipeline ships in stages: research first, then draft, then fact-check, then publish. Editors review real output by week three. Iterate weekly.

First real published post by week six.

03

Launch + tune

Two weeks. Production rollout, weekly tuning sessions with your editorial lead, analytics dashboards live. Handoff includes the maintenance runbook.

Your team owns the pipeline at the end.

What it costs

Pipeline pricing follows the number of stages and destinations.

A draft generator for one site and a researched, fact-checked, human-approved pipeline publishing to several are the same sentence and very different projects. Here is what moves the number.

What moves the number

  • How many sources Pulling from your own docs and data is straightforward. Reconciling several sources of truth is the work.
  • How many stages Draft and publish is a short pipeline. Research, draft, fact-check, human approval and analytics feedback is a system.
  • Where it publishes One WordPress site is simple. Several sites, or several platforms, multiply the integration surface rather than the effort.
  • How much human review Full automation is rarely the right answer. Where a person approves, that step has to be fast enough that they actually do it.
  • What volume A pipeline running weekly and one running daily across several properties have different reliability requirements.

Small, well-defined work is usually better handled as an hourly block than scoped as a project, and we will say so rather than inflate it into one.

Rough idea to delivery

  1. You send the details What you want built, roughly, plus budget range and timing. The form asks for all of it
  2. Same day, Monday to Friday We read it and reply. Nothing is scheduled before we know what it is about
  3. Then the call Free discovery, booked once there is enough on the table to make it worth your hour
  4. Within 48 hours of the call A written fixed-price quote you approve before anything starts
Tell us about your project

Quick enquiry

Publishing bottlenecked on people?

Tell us what you publish, where it goes and which part is the bottleneck. If drafts are not the problem and review is, say so, because that changes what we build.

Prefer the full form? Tell us about your project

No drip sequences, no marketing list. We reply and that is it.

Common questions

Frequently asked

  1. Will this replace our content team?

    No, and we will warn you if you ask us to. The pipeline replaces the work editors should not be doing (formatting, image processing, internal link insertion, schema, scheduling). Editors keep doing what only editors can do (voice, judgment, the part the AI cannot fake). Done right, your team ships more without burning out.

  2. How long does a content pipeline take to build?

    Six to ten weeks for a full pipeline (idea queue, research, draft, fact-check, human review, publish, analytics). Two weeks discovery to capture your style guide and source documents, four to six weeks build, two weeks launch and tuning.

  3. Can it ship to multiple sites?

    Yes. We have built pipelines that ship to 5+ properties with per-site style guides, per-site source documents, and per-site approval rules. The pipeline scales horizontally without rebuilding the workflow.

  4. What about SEO?

    SEO is built into the pipeline. Keyword research informs the brief. Internal linking is mandatory and validated against your sitemap (no hallucinated URLs). Schema markup is generated. Featured images include alt text. Yoast or Rank Math fields are populated.

  5. How much do AI costs run?

    Production cost typically lands at $0.50 to $2 per published post, all in. Prompt caching, model routing, and source document caching keep it well below what manual generation through ChatGPT would cost.

  6. What does it cost?

    Pipeline work is estimated against scope rather than sold at a list price. A draft generator for one site and a fact-checked, human-approved pipeline publishing to several are very different projects. The section above sets out what moves the number.

What clients say

★★★★★
“Wbcom Designs was methodical, reliable, innovative, and knowledgeable. They communicated with us every step of the way and delivered on time and on budget.”
Upwork review, Forum setup, 2023
★★★★★
“A partner, very trustworthy, very reliable. Gets the job done.”
Upwork review, Site development, 2 years

Rated 4.8 out of 5 across 360+ Upwork jobs since 2010, on our company and founder profiles.See them on Upwork

Our plugin customers rate us 4.8 on Trustpilot (93 reviews).Read them

Ready to publish more without dropping your standards?

Tell us what you publish and how often.

Discovery call is free. Fixed-price quote within 48 hours. NDA on request.