> ## Documentation Index
> Fetch the complete documentation index at: https://docs.marketer.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Next steps
> Turn one verified result into deeper analysis, creative work, a controlled campaign plan, or a repeatable workflow.
After your first verified result, expand one product flow at a time. Carry the accepted evidence forward, name the output you need, and keep the action boundary explicit.
## Continue from the result
Use this sequence:
Summarize the verified finding, source, account scope, dates, and important limitation. Keep the original result linked or continue in the same conversation when the next request depends on it.
Ask for a deeper analysis, brief, creative direction, campaign plan, report, alert, or workflow. Do not combine several deliverables into an approval request you cannot review clearly.
Say whether you want analysis, a draft, an approval-ready proposal, or execution under existing policy. A request cannot expand your role or bypass workspace controls.
Review visible steps and answer required input. If Marketer presents a proposal, inspect every step before you dismiss, edit, or approve it.
Open **Analytics**, **Briefs**, **Creatives**, **Campaigns**, **Workflow**, or another owning surface and confirm that the expected result or artifact exists in the correct workspace.
## Choose a product flow
Move from an account-level change to the channel, campaign, creative, product, or landing-page evidence behind it.
Turn a grounded finding into a reviewed brief, then continue through Studio or Assets when appropriate.
Define objective, source evidence, budget boundary, targeting, creative, destination, and approval state.
Make a report, alert, or other recurring process repeatable with explicit inputs, timing, and destination.
### Analysis path
Start with the verified result, then narrow one dimension at a time. Keep the same source and time window until you intentionally change them. Stop when the evidence no longer supports a more specific conclusion.
**Success:** the deeper result still identifies source, scope, dates, filters, and calculation, and it explains any change from the original measurement frame.
### Creative path
Ask for a brief before asking for final creative when the message, audience, offer, or evidence still needs agreement. Confirm that product claims and brand facts come from approved workspace context.
**Success:** the brief or creative exists in its owning surface and clearly shows what still needs human review.
### Campaign path
Keep the first campaign output as a draft or approval-ready proposal. Confirm provider account, campaign objective, budget, targeting, creative, destination, tracking, guardrails, and post-launch measurement before any publish action.
**Success:** the displayed proposal matches the reviewed scope, and any approved change is verified in **Campaigns** and the provider state.
### Workflow path
Turn a proven, stable procedure into recurring work. Define the trigger or schedule, data source, date window, output, destination, failure behavior, and decision point.
**Success:** a test run produces the expected output, and the workflow surface shows the intended configuration and status.
## Prepare the workspace for actions
Before you approve work that can publish, spend, or change a connected account:
1. Confirm member roles and who can approve or change workspace settings.
2. Set performance targets, spend caps, budget-change rules, and protected campaigns in **Guardrails**.
3. Review the workspace **Autonomy** level and default creative-brief behavior.
4. Keep the first campaign launch paused for review unless your documented policy requires another state.
5. Check **Awaiting action** for unresolved work and remove stale proposals.
6. Define where the resulting state will be verified after approval.
See [Approvals and autonomy](/essential-guidelines/approvals-and-autonomy) before enabling a path that can publish or spend.
## Make good work reusable
Reuse the right layer instead of copying an entire conversation:
| What should persist | Save it as |
| ------------------------------------------------------------------- | -------------------- |
| Stable company, product, audience, positioning, or operating fact | **Knowledge** |
| A repeatable set of instructions with clear inputs and review rules | **Skill** |
| Scheduled or event-driven work with a destination | **Workflow** |
| A request-specific hypothesis, window, or constraint | Keep it in that task |
Review suggested Knowledge and Skills before making them part of future workspace context. A useful one-off assumption should not become a durable company fact by accident.
## Track activation without rushing authority
Your workspace may show these activation milestones:
1. **Connect your ads account**
2. **Connect MCP**
3. **Chat with agent**
4. **Generate brief**
5. **Launch ad**
These are product milestones, not instructions to give every workspace the same autonomy. Complete **Generate brief** and **Launch ad** only when your team is ready to review creative and spend-related work.
For the full operating model, continue to [Working with Marketer](/working-with-marketer/overview). For a copyable flow, choose a [template and use case](/templates-use-cases/overview).
## Related topics
- [Chat and context](/working-with-marketer/chat-and-context.md)
- [Awaiting action](/working-with-marketer/awaiting-action.md)
- [Questions and approvals](/working-with-marketer/questions-and-approvals.md)
- [Specialists](/working-with-marketer/specialists.md)
- [Tasks and activity](/working-with-marketer/tasks-and-activity.md)