Fixed quote after a free call

Content calendar automation and editorial workflow for publishers

We build an editorial workflow that collects ideas from the inbox, notes and reader forms onto one calendar, drafts freelancer briefs from your house template and contributor guidelines, logs every commission with its due dates, reminds writers and editors before deadlines and sends the editor a Monday summary of what is publishing and what is at risk. It runs on the board you already use, such as Notion, Airtable or Trello, plus WordPress or Ghost for publish status. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why editorial calendars drift

An editorial calendar is only useful if it is current, and most are updated by hand after the fact. Ideas sit in notes apps and starred emails, assignments sit in private calendars, and writers ask the editor what is due.

Every freelancer brief repeats the same style notes, sourcing rules, word counts, link policy and disclosure requirements. When a brief is rushed, the draft comes back off target and the edit takes longer than the writing.

What we build

What our content calendar automation includes

One ideas list

Ideas tagged in the inbox, notes tool or a reader form land in one list with the source attached and possible duplicates of existing articles pointed out.

Briefs from your template

The editor fills a short form; a full brief is drafted from your house template and contributor guidelines for the editor to approve.

Commission log

Writer, fee, rights terms, draft due and publish date recorded once and shown on the calendar.

Deadline reminders

Polite reminders to contributors and editors ahead of each date, and overdue pieces highlighted.

Publish status from the CMS

Draft, scheduled and published states read from WordPress or Ghost so the calendar matches reality.

Monday summary

One email to the editor: what publishes this week, what is late and what needs a decision.

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

    Idea captured

    A tagged email, note or reader form adds an idea to the list with its source.

  2. 02 Automated

    Brief drafted

    From the editor's short form, a brief is drafted from the house template.

  3. 03 Automated

    Reminders sent

    Contributors and editors get reminders before each deadline.

  4. 04 Editor review

    Editor reviews

    The editor approves briefs, reviews drafts against them and moves pieces on.

  5. 05 Editor or publisher decides

    Editorial decisions

    What gets commissioned, when it runs and what is dropped is decided by the editor.

How it behaves

How the editorial workflow behaves

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

What contributors see

  • A complete brief with style, sourcing and disclosure notes
  • Friendly reminders before each deadline
  • One place to send drafts and invoices

What the editor sees

  • One calendar with every idea, commission and date
  • Overdue pieces highlighted
  • A Monday summary of the week ahead

What the automation does

  • Captures ideas and spots likely duplicates
  • Drafts briefs from the house template
  • Reads publish status from the CMS

Edge cases and fallbacks

Idea duplicates an existing article
Flagged with a link to the older piece so the editor can decide on an update instead.
Contributor misses a deadline
One reminder, then the editor is alerted; no repeated nagging.
Piece published outside the calendar
The CMS check adds it so the calendar stays accurate.
Board or CMS API unavailable
Reminders pause, the run retries and the editor gets an alert.

Architecture

An editorial workflow from idea to publish at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Ideas Inbox, notes, forms n8n Capture and remind Brief drafts House template Editorial board Notion or Airtable Editor Approves and edits CMS status WordPress or Ghost Monday summary Email to editor
  • Input
  • Logic and services
  • AI step
  • Data
  • People
  • Output

How it flows

  1. 1 Ideas arrive from tagged emails, notes and a reader suggestion form.
  2. 2 n8n adds them to the editorial board and drafts briefs from the house template when a piece is commissioned.
  3. 3 The editor approves briefs, contributors get reminders and drafts are reviewed against the brief.
  4. 4 Publish status is read back from the CMS and the editor gets a Monday summary.

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.

Editorial calendar & contributor workflow project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    How ideas, commissions and deadlines are tracked today, brief templates and contributor guidelines.

  2. 02

    Design

    2 to 3 days

    Board fields, brief template, reminder timing and summary format.

  3. 03

    Build

    1 to 2 weeks

    Idea capture, brief drafting, commission log, reminders and CMS status.

  4. 04

    Shadow run

    About 1 week

    The board runs beside your current calendar while the editor checks every entry.

  5. 05

    Launch

    1 to 2 days

    Switch over and brief contributors on the new reminders.

  6. 06

    Support

    Ongoing

    Template changes, new sections and new contributors.

What it runs on

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

n8n Notion API, Airtable or Trello WordPress REST API or Ghost Admin API Gmail or Microsoft 365 Claude or OpenAI for brief drafts Slack for reminders

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

    Board fields, templates, reminder rules and summary.

    $250 – $450

  • Build

    Capture, brief drafting, commission log and reminders.

    $450 – $1,250

  • Integrations

    Board, CMS, inbox and chat.

    $150 – $400

  • Testing and shadow run

    QA and a side-by-side run with your calendar.

    $100 – $250

  • Launch and training

    Switch-over and contributor note.

    $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. Board, CMS and n8n subscriptions 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.

  • Board or database: Your Notion, Airtable or Trello plan.
  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter), billed annually.
  • AI model usage: Billed by the provider per use; short brief drafts are usually a small monthly amount.

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: sponsored pieces carry disclosure from the brief

The FTC says each sponsored post needs its own clear disclosure close to the endorsement; a site-wide disclosure page is not enough. Briefs for sponsored pieces carry that requirement.

Source: www.ftc.gov

UK: ads must be obviously identifiable

Section 2 of the CAP Code requires marketing to be obviously identifiable, and the ASA prefers a clear label such as "Ad" up front.

Source: www.asa.org.uk

EU: AI-drafted public-interest text

Article 50 of the EU AI Act requires disclosure of AI-generated text published on matters of public interest unless it has had human review and editorial responsibility. Our briefs are drafts an editor approves.

Source: artificialintelligenceact.eu

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

Editorial calendar automation questions questions, answered.

It means the calendar fills and updates itself: ideas land in one list, commissions show their dates, publish status comes from the CMS and reminders go out without the editor chasing. The editor still decides what runs.

Yes. Your contributor guidelines, style notes, link policy and disclosure rules are part of the template, so every brief carries them. The editor approves each brief before it is sent.

Both views of the same data: an editorial calendar of commissions and deadlines, and a content calendar of what publishes where and when, including newsletter and social versions.

Yes. WordPress has a REST API for posts, and Ghost's Admin API covers posts, pages, members and webhooks, so the calendar can read draft and published status from either.

It can collect contributor invoices against each commission and pass them to your accounting tool. Paying them stays with you.

Pieces published against plan, average days late, briefs revised after first draft and time from commission to publish.

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