# Strategy — AI Marketing Department

Canonical page: https://aryehalgorithms.com/ai-marketing-department/strategy

Strategy is the function that writes the plan every other function works from: goals, audiences, positioning per segment, channels and the order of work. It starts with what your company already knows about who buys and why, and it ends with a written plan that is kept current on a fixed cadence as results come in. The vocabulary it sets is the vocabulary research, content, campaigns and outbound write in.

## What it does

- Strategy starts before anything is sent, published or built. In the first weeks it gathers what your company already knows: who buys, why they buy, what they compare you against, which channels have worked and which have not. From that it writes the plan: the goals for the period, the audiences by segment, how you are positioned for each, the channels to be used and the order in which the work will happen. The plan is written in plain language so your team can read it in one sitting.
- Once agreed, the plan becomes the reference for every other function. Research uses its segment definitions, content uses its positioning, campaigns and outbound use its channel choices and its vocabulary. On a fixed cadence, monthly by default, the plan is reviewed against what has come back: which segments responded, which messages held up, which channels took more attention than they returned. Changes are proposed in writing, agreed with your team, and the plan is versioned so that anyone can see what changed and why.
- Strategy does not decide alone, and it does not replace the judgment of the people who run your company. Its job is to keep one clear, current answer to the question of what the department is trying to do, for whom and in what order, so that every task, approval and report in your portal can be traced back to a reason your team agreed to.

## Automated

- Intake and baseline: Your website, CRM fields, past campaigns and existing positioning documents are read at the start of the engagement and summarized into a baseline: what is said, to whom, through which channels. Gaps are listed for the first working session.
- Segment definitions: Each audience segment is written up in a fixed format: who they are, the problem they carry, the trigger that makes them look and the words they use. The definitions are published to the portal for every other function to read.
- Plan assembly: The plan is assembled from the agreed inputs into one document with a fixed structure: goals, segments, positioning, channels, order of work. Any section without an agreed input is marked open rather than filled in.
- Results collection: On the review cadence, results from analytics, campaigns and outbound are pulled into a scorecard against the plan’s goals, segment by segment and channel by channel, so every review starts from the same figures.
- Change proposals: When a result crosses a threshold agreed in setup, a written change proposal is drafted: what moved, which part of the plan it affects and what the options are. The proposal waits for a person; nothing in the plan changes on its own.
- Plan versioning: Every agreed change produces a new version of the plan with a dated note on what changed and why. Functions that depend on the changed section are notified so their next cycle starts from the current version.

## Supervised by a person

- The first plan: The first version of the plan is written by a person on our team with your founder or revenue lead, in working sessions. The automation assembles the inputs; a person writes the positioning and chooses the order of work.
- Positioning decisions: How your company is described to each segment is a decision a person makes with your team and signs off in writing. Drafts help the conversation along; the choice itself is never delegated to a process.
- Review sessions: Each review is a conversation, not a report that arrives. A person on our team walks through the scorecard with your team, reads the proposals and agrees what changes before any new version is published.
- Trade-offs between functions: When two functions pull in different directions, for example content wants a segment that outbound finds hard to reach, a person decides the order of work. A rule can flag the conflict; it does not settle it.
- Pausing the plan: If something in your business changes, a launch slips or a market moves, a person pauses the review cadence and reopens the plan on your timetable rather than the scheduled one.

## A note from the CEO

Strategy is the part of the department I do not delegate. I write the first plan with you, I am in every review, and no positioning changes without my reading it. The automation keeps the plan honest against results; deciding what to do about them is my job and yours.

## What you receive

- Marketing plan (Versioned at each review): Goals, audiences, positioning per segment, channels and the order of work, in one document your whole team can read.
- Segment definitions (Updated as the plan changes): One page per segment: who they are, the problem, the buying trigger and the vocabulary every function writes in.
- Strategy scorecard (Monthly): Results by segment and channel set against the plan’s goals, with the open questions for the next review.
- Change proposals (As results warrant): What moved, which part of the plan it affects and the options on the table, waiting for a decision.
- Review notes (Monthly, after each review): What was decided in the review, what was left open and which functions change their next cycle.
- Strategy section of the weekly summary (Weekly): Where the department stands against the plan this week and anything that should change before the next review.

## Questions

### What should a company automate first?

The work that already has a written plan behind it. Automation runs a defined process well and a vague one badly, so before anything is automated, strategy writes down who you sell to, what you say to them and in which order the work happens. Once that exists, the first review shows which function has the clearest inputs and outputs, and that is where automation starts.

### Does the plan change, or is it written once?

It changes on a fixed cadence, in writing. Each review pulls results against the plan’s goals, a person on our team walks through them with your team, and any change is proposed, agreed and published as a new version with a note on what changed and why. Between reviews the plan is stable, so the other functions are not chasing a moving target.

### What if we already have a strategy?

Then it is the starting point. The intake reads your existing positioning, segment definitions and channel history and writes the baseline from them rather than around them. Where your plan is complete, the function’s job is to keep it current and make sure every other function writes in its vocabulary. Where it has gaps, those are listed for the first working session.

## Related

- [Research](https://aryehalgorithms.com/ai-marketing-department/research): Supplies the market and account facts the plan is written from.
- [Analytics](https://aryehalgorithms.com/ai-marketing-department/analytics): Reports results against the plan’s goals and feeds each review.
- [Campaigns](https://aryehalgorithms.com/ai-marketing-department/campaigns): Runs the channels in the order and the voice the plan sets.

Route: /ai-marketing-department/strategy