Supernal
Statement of Work for Heritage Strategies
← All proposals

Content Master AI Employee

Stephen

Produces and ships ongoing marketing content across Heritage's owned channels (the Heritage Strategies and Heritage AI websites, plus the email newsletter) on a monthly cadence and on demand.

01 / Overview

The brief

The Content Master AI Employee drafts blog articles and the email newsletter for both Heritage brands. It operates inside the editorial content management systems delivered under the Heritage Strategies and Heritage AI website SOWs. It drafts in the voice of the right brand, runs SEO research, and queues content for human approval before publication.

The Heritage team reviews, edits if needed, and approves. The Content Master AI Employee handles everything else.

02 / Objectives

What success looks like

  • Maintain a consistent publishing rhythm across blog articles and the newsletter without consuming Heritage staff time.
  • Build organic search authority around Heritage.
  • Convert site visitors into newsletter subscribers and discovery calls.
  • Produce auditable, on-brand drafts that Heritage approves in under 30 minutes per item.

03 / Scope

Scope of work

Stage 1 · Weeks 0 to 2

Voice profile and brand quality controls

Train Stephen on Heritage's source material so every future draft sounds like Heritage. Lock the guardrails before any content ships.

  • Voice profile trained from Heritage source materials (existing copy, founder transcripts, sample posts).
  • Style guide enforced on every draft: tone, do and don't list, banned phrases, citation rules.
  • Hallucination guardrails: factual claims must cite a source the Content Master can show in the CMS.
  • Two-pass review: Content Master self-edit pass, then human approval. No auto-publish.

Stage 2 · Weeks 2 to 4

Channel A · blog articles

Publish search-optimized, authority-building long-form articles to the Heritage Strategies and Heritage AI blogs, routing each piece to the brand whose audience it serves.

  • Format (recommendation, adjustable): 1,200 to 1,800 words, structured with H2/H3, table of contents, citations, internal links, hero image, CTA.
  • Topics: sourced from a content calendar (Content Master proposes; Heritage approves).
  • Process: Content Master runs keyword research for both SEO (Google) and GEO (ChatGPT and other AI search), proposes monthly topics, and Heritage approves. Content Master drafts and stages each article in the editorial CMS. Heritage reviews and approves. Content Master publishes on the agreed schedule.
  • Output: published blog article on the website plus a newsletter item.

Stage 3 · Weeks 4 to 6

Channel B · email newsletter

Stay front of mind with interested leads so they reach out when ready, branded to the audience it serves (Heritage Strategies or Heritage AI).

  • Format: one curated email per cycle: a feature story (linked to a recent blog), 2 to 3 short links, one CTA.
  • Process: Content Master drafts newsletter from the cycle's published content. Heritage approves in CMS. Content Master schedules send, monitors deliverability, captures open and click metrics.
  • Output: sent newsletter and performance summary in monthly report.

Stage 4 · Week 6+

Steady state and reporting

Recurring monthly cadence on both channels with continuous content tuning and a single monthly report to Heritage.

  • Content Master produces the monthly content report: what shipped, traffic, conversions, top performers, next month's plan.
  • Tone, topic mix, and channel cadence tuned continuously based on report findings.
  • Recurring monthly cadence at steady state.

04 / Out of scope

Out of scope

ItemStatus
Translation into other languagesNot in scope (English only at launch)
White papers, lead-magnet eBooks, gated long-formNot in scope

05 / Timeline

Six weeks of build, then steady state

PhaseDurationOutcome
Voice and calendar onboardingWeeks 0 to 2Voice profile trained; first content calendar approved.
Channel A build: blog articlesWeeks 2 to 4Blog AI Employee live in CMS; first article shipped.
Channel B build: email newsletterWeeks 4 to 6Newsletter AI Employee live in CMS; first newsletter shipped.
Hypercare: content and tone iterationsWeeks 6 to 8Tone, topic mix, and channel cadence tuned.
Steady stateWeek 8+Recurring monthly cadence.

06 / Required inputs

What Heritage provides

For the Content Master to start producing on day one, Heritage provides the following in week 0 to 2. Approval delays extend cadence day-for-day. Several items may already exist within Supernal's stack from prior Heritage work. We will inventory what is reusable in week 0 and only ask Heritage to provide the gaps.

6.1   Engagement and approvals

  • List of approvers with publishing authority.
  • Weekly 30-minute review call during build.

6.2   Voice and source material

  • 5 to 10 examples of existing Heritage copy in the desired voice (web copy, prior posts, founder writing).
  • 2 to 3 founder or team transcripts or recorded conversations to mine for tone and phrasing.
  • Style guide preferences: tone, do and don't list, banned phrases or topics.
  • Approved bios and headshots of any Heritage author bylines.

6.3   Topic and strategy inputs

  • Heritage's positioning, target personas, and primary keywords to defend or pursue.
  • List of reference publications to monitor.
  • Approved citation sources.
  • Editorial red lines: regulatory, legal, client-confidentiality.

6.4   Operational access

  • Editor-level credentials to the editorial CMS (/admin).

Investment

Pricing

$4,000 / month