Multi-stepPublishing
Your agent has the context. Give everyone the right picture.
Turn the research, files, and decisions your local agent has gathered into a detailed brief, client presentation, or public guide. Choose the audience and keep refining the same link.
A complete worked example
A week of investigation. One clear decision brief.
Maya's local agent has read the Acorn launch notes, compared three onboarding approaches, and inspected the support export. The next job is helping other people make a decision.
Fictional project and sample data. This preview does not submit, publish, or change access.
Choose an example edition
Each edition is a separate document with its own content and access.Project team · illustrative result
Make the first step unmistakable.
Start with a guided checklist. It addresses the most frequent first-use question while leaving account migration for a later phase.
- Evidence
- 18 of 40 requests asked what to do first
- Recommendation
- Pilot a guided checklist
- Decision needed
- Confirm scope and a pilot owner
| Approach | Effort estimate | Tradeoff |
|---|---|---|
| Refresh the guide | 3 days | Fast; still requires readers to find it |
| Guided checklist | 8 days | Clearer sequence; needs a pilot |
| Full migration | 4 weeks | Broader change and more dependencies |
Why this recommendation
The support export contains 18 navigation questions, 12 access questions, and 10 account questions. Four of six interviewees hesitated at the first step. A checklist targets that friction; it does not establish that retention will improve.
What to do next
Run the checklist with five new readers. Record where they pause, revise the labels, and ask the project lead to confirm the next phase. Source references: support-summary.csv and research-notes.md; raw transcripts remain private.
What the recipient can access
Restricted to authorized project teammates. Detailed comparison and anonymized evidence included.
Kept out of this handoff
Raw interviews and identifiable support records stay private.
How it runs
- Start with the contextPoint your connected agent to the relevant files, research, and tool results. Name the decision or idea the audience needs to understand.
- Ask for the right editionHave the agent build and upload a brief, presentation, guide, or interactive report. Select the source detail to include and the Fermium access setting before sharing.
- Keep the conversation goingAsk for a clearer explanation, another chart, or a revised recommendation. Update the existing document so its intended readers keep the same link.
- You getAn audience-appropriate page with a clear takeaway, supporting evidence, and a stable URL for future revisions.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Turn what we have learned about [project] into a clear, detailed page for [audience]. Lead with the takeaway, explain the tradeoffs, and include permitted supporting evidence. Leave out [private material]. Publish it in Fermium under [access setting], give me the link, and update that same page when I ask for revisions.
What this workflow needs
The connected agent needs access to the selected sources and permission to publish. Review what is included for each audience. A restricted team page, a password-protected client edition, and a public summary can be separate documents; linked sources retain their own permissions.
Does everyone need to use my agent or read its conversation?
No. Your agent compiles the material into a page people can open in a browser. Fermium controls access to the published document. You can keep improving that document without sending readers into the agent session or replacing their link.