# AIelsen · End-to-End Marketing Agent Workbook

Purpose: connect requirements, verified facts, strategy, content and feedback throughout a product launch.
This template distils practical working methods. It contains no client materials, project data or proprietary creative work.

## 1. Before you start: establish a working baseline

| Field | What to record |
| --- | --- |
| Business objective | Whose decision should this work influence, and how? |
| Audience and task | Go beyond demographic labels: describe the specific task people need to complete. |
| Launch stage | Preparation / pre-launch / live / ongoing operations |
| Confirmed facts | Product capabilities, conditions of use and approved commercial information |
| Open questions | The exact question, evidence needed and person responsible for confirmation |
| Existing materials | Files, versions, scope of use and permission to share externally |
| Human and Agent responsibilities | Who supplies facts, researches, makes decisions and executes? |
| Definition of done | Which assets, audiences and questions must the work cover? |

Check: do not turn unconfirmed specifications, prices, performance or safety information into public promises.

## 2. Research and competitor matrix

Define common comparison dimensions for the category before evaluating individual products. Avoid selecting only the measures that favour your own product.

| Dimension | Our product | Alternative | Source and applicable conditions | Meaningful difference | To confirm |
| --- | --- | --- | --- | --- | --- |
| Core task and output | | | | | |
| Inputs and operating workflow | | | | | |
| Performance and quality conditions | | | | | |
| Materials and compatibility limits | | | | | |
| Maintenance and cost of use | | | | | |
| Configurations, accessories and service | | | | | |

Prioritise complete official specifications, user manuals and tests with clearly stated conditions. Search snippets help locate material; they do not replace checking important facts.

## 3. FAB: translate facts into specific customer value

| F: feature fact | A: advantage it enables | B: benefit, and for whom | Evidence required | Relevant channel | What not to promise |
| --- | --- | --- | --- | --- | --- |
| | | | | | |

Ask of every row: is the benefit specific? Is the audience clear? Does the evidence exist? Have we presented a possible outcome as a guaranteed result?

## 4. Content plan and channel responsibilities

| Touchpoint | The audience's question at that moment | Job of the content | Core message | Evidence or asset | Owner | Dependencies and status |
| --- | --- | --- | --- | --- | --- | --- |
| Search and advertising | | | | | | |
| Main landing page | | | | | | |
| FAQ | | | | | | |
| Reviews and demonstrations | | | | | | |
| Livestream | | | | | | |
| Hero film and short-form assets | | | | | | |
| Email and community | | | | | | |

Do not ask one film to explain everything. Give each touchpoint the question it is best placed to answer.

## 5. TVC and script review

| Selling point | What the existing draft says | Status | Barrier to understanding | Proposed change | Visual or evidence needed | Priority | Decision record |
| --- | --- | --- | --- | --- | --- | --- | --- |
| | | Clear / unclear / implied / missing | | | | | |

Review sequence:

1. Identify what the original draft already does well and who created it.
2. Check whether the product's key limits and customer benefits are clear.
3. Find jargon, unexplained specifications and visual implications the audience may not understand.
4. Turn every recommendation into an actionable shot, caption, voiceover or structural change.
5. Check runtime, production constraints and available evidence before assigning priorities.

## 6. Concept and feedback worksheet

| Scenario | Target audience | Benefit to communicate | People and action | Shot or composition | What already exists | This round's contribution | Team feedback |
| --- | --- | --- | --- | --- | --- | --- | --- |
| | | | | | | | |

For each revision, retain the original feedback, the specific change, reasons for declining a suggestion and questions still awaiting confirmation.
Translate requests such as “more premium” or “more impressive” into features that everyone can observe and revise.
Concept images communicate creative direction. They must not be presented as completed product photography or final client results.

## 7. After launch: turn questions into the next brief

| Question theme | Summary of the original question | Decision affected | Missing evidence | Suitable content | Owner | Check after the update |
| --- | --- | --- | --- | --- | --- | --- |
| Operating workflow | | | | Demonstration / tutorial | | |
| Cost of use | | | | Explanation with stated conditions / FAQ | | |
| Compatibility and limits | | | | Scenario explanation / FAQ | | |
| Maintenance | | | | Demonstration / instructions | | |
| Trust | | | | Test / review / project update | | |

## 8. Version control, privacy and release review

- [ ] Confirmed assets have not been lost during the visual redesign.
- [ ] Key facts match the latest approved product information.
- [ ] Headlines, images and voiceover match the substance of the content.
- [ ] Unconfirmed information has not become a definite promise.
- [ ] Attribution distinguishes original work, the initial draft, the Agent's contribution and the team's final production.
- [ ] Client names, internal identifiers, prices, data, file paths and links are handled within the permissions granted.
- [ ] Images are physically cropped or covered with solid masks; hiding parts with webpage overlays is not enough.
- [ ] Original assets and private verification materials stay outside the public release directory.
- [ ] Versions, approvers and questions to revisit are recorded.

Measure whether the work supports the next action, keeps facts consistent, answers real questions and makes handoff complete.
Do not substitute output volume or unverified adoption percentages for business judgement, or attribute sales results to a single tool.