Last updated:
Quick answer
Install the six roles in the order below. Give the editor desk your reader and send day, choose an idea with sources, check the facts, then get a draft and a pressure test. The sponsor role is optional. You approve every outside action.
At a glance
All outcome figures are estimates from cited sources, not independent verification by us.
- What it is allowed to do
- Drafts for you
Writes drafts (emails, posts, plans, replies). You review and send. Nothing goes out without you.
- Time saved (estimate)
- Not measured yet
- Money saved (estimate)
- Not stated.
- Difficulty
- Beginner
- Tools needed
- Typical cost
- Not stated in sources. Check the plans of the tools and connections you use.
Basis (estimate): Time saved in daily use has not been measured. Setup duration is listed separately in the FAQ.
What does this guide cover?
Install the newsletter team in order, try one clearly labeled example, and stop before anything is sent.
Who is it for?
Anyone writing a weekly or monthly newsletter who wants ideas, checks and a first draft ready, and still writes the final issue.
What does the first run look like?
Example only, made up for this guide: "The next issue is Friday. The reader is a first-time vegetable gardener. Find five real questions about watering, keep the source links, and draft only after the facts are checked." You choose one idea, review its sources, edit the draft and decide when to send.
Where do you stop?
Nothing is scheduled, sent, posted or pitched without your yes. No stat goes in without a source. Public templates are starting points, not a claim that this complete team has been tested. Review each template and its permissions before connecting accounts.
How do you run it step by step?
Tools
- Google Sheets (idea tracker) and Google Docs or Notion (drafts).
- X read access for the scout; your newsletter platform in read-only; Canva for graphics.
Steps
- Install the editor desk first. Paste its first message from the team page and give it your niche, reader and send day.
- Install the idea scout. Make the idea sheet and ask for five ideas with source links. Pick one.
- Install the fact checker. Give it the outline's claims and source links; read its checked, unclear or wrong labels yourself.
- Install the issue drafter. Give it the brief, checked facts and examples of your voice. Ask for a draft and three subject lines.
- Install the pressure-test editor. Read its strongest objection and one tighter version before revising.
- Add the sponsor scout only if you need it. Its short list and pitch are drafts, not outreach.
- Stop. Edit the issue yourself. Nothing is scheduled, sent, posted or pitched without your yes.
Newsletter
Get the free starter pack
Free starter pack with five beginner copy-paste prompts after you confirm, plus one researched setup in your inbox each week. Unsubscribe anytime.
What usually goes wrong?
Where agents tend to stall on this job. More patterns in Where AI gets stuck.
- Starting every role before defining the priority or reader. Give the coordinator that context first.
- Treating a draft as approved. Read it yourself before any outside action.
- Missing a connection. Stop and name the missing connection rather than guessing from incomplete data.
Common questions
- How long does setup take?
- About 30 minutes (estimate), not timed. This is an estimate, not a timed test.
- Does the team send anything?
- Nothing is scheduled, sent, posted or pitched without your yes. No stat goes in without a source.
- Has the whole team been tested?
- No. This is a researched setup built from public template references and existing setup pages, not a tested-team receipt.
What tips make it smoother?
- Install in the listed order so each handoff has somewhere to go.
- Keep the approval fence in the first message.
- Try one priority or one issue before expanding the routine.
Where do the claims come from?
Summaries use linked sources, not independent verification. This guide is not legal advice. How we pick setups.
- Read original on x.ai
Built on a public template by @farzyness. Master. Link only; role text is original.
- Read original on x.ai
Built on a public template by @teeRex247. Source Check. Link only; role text is original.
- Read original on x.ai
Built on a public template by @HeroHobby97191. Chief of Staff. Link only; role text is original.
- Read original on x.ai
Built on a public template by @aitrainingwork. Sponsor Scout. Link only; role text is original.
- Read original on x.ai
Built on a public template by @ArthurMacwaters. Research Bot; additional fact-checking reference, link only.