# Marketing

Source: https://routineos.org/use-cases/marketing

> Weekly numbers and cited drafts, on your yes. Claude routines for marketing teams, built from two real templates. They start report-only.

Use case: marketing

# Marketing routines for Claude: weekly numbers and cited drafts, on your yes

Two templates cover the regular work in marketing. One compares this week's metrics with last week's and flags the big moves. The other drafts cited posts in your house style and publishes only the ones you approve. Both start report-only. Free (MIT). Needs a paid Claude plan.

[Get started](https://routineos.org/#start)[See weekly marketing report](https://routineos.org/templates/weekly-marketing-report)[See content calendar](https://routineos.org/templates/content-calendar)

weekly-marketing-report: unpilotedcontent-calendar: unpilotedexample scenario

The job

## The job: the weekly report and the content calendar

A marketer pulls numbers from several platforms every week, compares them with last week and checks a few key pages. Alongside that, someone keeps a calendar of posts moving from research to draft to published.

Both are regular, sourced work. The scenario below is an example built only from what the two templates do.

An example week

## An example week with both routines

This is an example built from the real templates, not a customer story. It carries no results, numbers or quotes. Say a small team connects its analytics and ad platforms, lists two topics and one source feed, and connects a publishing platform.

1. **Monday and Wednesday, 21:00 UTC: content calendar runs**It reads your feeds and searches each topic, keeping every source URL. It drafts posts in each format you chose (blog and LinkedIn by default) in your house style, with a marker per claim. A script checks every marker has a source.
2. **You approve, edit or decline**Drafts wait behind an email gate that times out after 72 hours. On a later run, only approved drafts are published, exactly as approved. The first run is report-only and publishes nothing.
3. **Sunday, 21:00 UTC: weekly marketing report runs**It reads this week's and last week's totals per source and metric. A script computes the change, so no figure is the model's arithmetic. It also opens the pages you list and notes visible issues.
4. **You read the Sunday report**Changes beyond 20 percent by default are flagged. Each number names its source, because platforms differ on time zones and attribution windows. You open the Desk and keep, edit or drop what you see. The routine learns from those choices and suggests setting changes. Nothing applies until you say yes.

Source: template READMEs and catalog schedules in the [RoutineOS repository](https://github.com/devkindhq/routineos). Schedules are the template defaults, in UTC.

Templates

## The marketing templates

 [

### Weekly marketing report

Each week, compares marketing metrics with the week before, audits a few key pages, and flags big moves.

unpilotedwatch
Open ](https://routineos.org/templates/weekly-marketing-report) [

### Content calendar

Drafts cited posts from your topics and sources in your house style, and publishes only what a person approves.

unpilotedapproval-gated
Open ](https://routineos.org/templates/content-calendar)

**Weekly report needs**An analytics and ad platform connector (read), web fetch optional

**Content calendar needs**Web search and web fetch; mail for approvals and a publishing platform are optional

**First run**Report-only

Maturity is from the catalog. Neither template has had a real run yet, so read the first report-only run before you rely on it.

Safety

## What it never does

These come from the template prompts. They are rules the prompt forbids and the checks around it. They are not a promise about every possible run.

- The prompt forbids changing a campaign, budget, bid or page in weekly marketing report.
- The prompt forbids publishing in content calendar until a person has approved that draft, and forbids editing or deleting a published post.
- Recommendations in the report are the model's suggestions, never a change to spend.
- A renamed metric can look like one metric gone and a new one at zero. Check before acting.

**Heads up**A model can misread a source, and a draft may copy a source too closely. Open the sources before you approve a draft. The Desk's approve-then-publish flow is not piloted end to end, so test it on your own machine first.

Next

## Where to go from here

Read the [weekly marketing report page](https://routineos.org/templates/weekly-marketing-report) for install steps and settings, or the [content calendar page](https://routineos.org/templates/content-calendar). See the other teams on [all use cases](https://routineos.org/use-cases), read how [approvals](https://routineos.org/concepts/approvals) and [learning](https://routineos.org/concepts/learning) work, or check the [honest limits](https://routineos.org/honest-limits).

## Install the weekly marketing report first

It only reads. Run it report-only, check a few numbers against the platforms, then add the content calendar.

[Get started](https://routineos.org/#start)[Install weekly marketing report](https://routineos.org/templates/weekly-marketing-report)