Workflow guide · AI employees
Run Your First Campaign with AI Employees
Plan a small campaign with Morgan, hand approved work to Luca and Miles, and review the editable outputs before publishing. Includes a reusable brief.
Start with one offer, a short brief, and two deliverables. Have Morgan prepare the plan, review it, then give Luca the graphic assignment and Miles the video assignment. Review the finished files before publishing. This practice campaign expands the Morgan → Luca → Miles story in the AI Employees product illustration; it is a hypothetical exercise, not a recorded customer result.
What you need before starting
AI Employees is a self-hosted source-code product. You need a deployed installation, working credentials for your chosen supported model and media providers, and access to the source assets used in the campaign. Follow the deployment documentation supplied with your package for installation details.
Morgan, Luca, and Miles are part of the Core creative team. Both packages include the workflow builder and approval capabilities. Set your own task budget; provider usage and infrastructure are separate operating costs, and this guide does not assume a fixed cost per campaign.
Prepare the approved offer details, brand guidance, logo, destination URL, source footage, and one named reviewer. A missing date or unapproved claim should become a question for that reviewer, rather than a detail the employee invents.
1. Choose one small campaign
For this hypothetical exercise, promote a workshop using one square graphic and one short vertical video cut from footage you supply. The target audience is existing subscribers who have not registered. The campaign’s next action is visiting the registration page.
Keep the first assignment limited to preparing the creative. Publishing can follow after you review the exact files and destination. This gives you a complete production task to evaluate before adding more channels or deliverables.
2. Copy and complete the campaign brief
Replace each bracketed item with your verified information. This is a suggested brief for the exercise, not the original prompt behind the product illustration.
- Goal: Prepare a workshop campaign that directs [audience] to [verified registration URL].
- Offer facts: [workshop name], [date and time zone], [price or free registration], [what attendees receive]. Use only these approved facts.
- Inputs: [brand guide version], [logo file], [source footage], [approved transcript or captions], and [reference creative].
- Deliverables: One 1080 × 1080 graphic and one 1080 × 1920 video of approximately 20 seconds, plus their editable source projects.
- Message: Lead with [specific attendee problem] and explain [verified workshop outcome]. Do not add testimonials, scarcity, or results that are absent from the inputs.
- Budget: [your limit]. Ask before expanding scope or using an unapproved provider.
- Review: [reviewer] approves the plan and final files. Return questions when a required input is missing.
- Completion: Supply previews, export files, editable projects, unresolved issues, and the run record. Hold publishing until the final files and destination are approved.
3. Have Morgan turn the brief into assignments
Ask Morgan to identify the required inputs, propose the production steps, and spell out what each employee should return. Review the plan for scope, facts, dependencies, and the approval points before creative work starts.
A useful handoff gives the specialist an objective and the exact approved inputs. “Make the video match the graphic” is incomplete if the graphic has not been reviewed yet. If Miles needs Luca’s artwork, make the approved artwork a dependency; if the two tasks share only approved offer facts, they can be planned independently.
| Owner | Input | Expected handoff |
|---|---|---|
| Morgan | Completed brief and source assets | Plan, questions, employee assignments, and review points. |
| Human reviewer | Proposed plan | Approved scope and resolved offer facts. |
| Luca | Approved message, brand guidance, and logo | Graphic preview, export, and editable project. |
| Miles | Approved message, footage, and any required approved artwork | Video preview, export, and editable project. |
| Human reviewer | Both creative outputs and the run record | Specific revisions or approval of the exact final versions. |
4. Give Luca and Miles measurable finish conditions
For Luca, ask for a readable headline, the approved workshop details, and a clear next action at the requested square size. Review the result at a realistic viewing size. If the date is technically present but too small to read, the assignment is not finished.
For Miles, identify the source footage and the idea the viewer should understand. Ask for the requested vertical export, readable captions where speech is used, and a closing next action that matches the graphic. Play the full exported clip with sound; a thumbnail cannot show a bad cut or missing audio.
Open each editable project and make a small reversible text change. Verify that the project and export correspond to the same approved version. This is a practical acceptance check for the editable output, rather than accepting the employee’s completion message as proof.
5. Review the campaign as one set
Compare both outputs with the original brief. Check the date, time zone, price, spelling, destination, and stated outcome. A graphic and video can each look polished while advertising different versions of the offer.
Give revision feedback against a named file or version. For example: “In graphic version 2, increase the date size and keep the approved headline. In video version 1, replace the closing date with the date from the brief.” Recheck the changed files before approving them.
| Review question | Evidence to inspect |
|---|---|
| Are the offer facts correct? | Compare the files with the approved brief. |
| Can the audience understand the next action? | Read the graphic and watch the full video at the intended size. |
| Do the files work? | Open the exports and editable projects. |
| Did the work stay within scope? | Compare delivered assets and recorded work with the approved plan. |
| Is anything blocked or unresolved? | Review the run record, questions, and outstanding revisions. |
6. Record what happened before running it again
Inspect the run receipt and task history for the work performed, approvals, artifacts, and any blocked or failed steps. Keep your own short acceptance note beside the approved versions: what you accepted, what you corrected, and what still needs a decision.
For the next practice run, remove one required input and check that the workflow requests clarification. Then try a revision to one output and check that dependent work uses the approved replacement. These are suggested tests, not results claimed by this guide.
Reuse the workflow after those checks, updating the offer facts and asset versions for each campaign. Record review time and provider costs from actual runs if you want to evaluate the workflow’s value. Do not infer savings or campaign performance from the product illustration.
Can the first campaign publish automatically?
For this exercise, finish with approved creative and a separate publishing decision. If you later connect publishing through supported tools, specify the destination, exact approved files, and required authorization in the workflow. Preparing an asset and releasing it to an audience are separate actions.
What should you have at the end?
An approved brief, a reviewed plan, a graphic and video you have opened, their editable projects, and a record of the work and decisions. That is enough to evaluate the first workflow and identify the next improvement without expanding into an entire marketing operation at once.