Role
Hire an AI content writer
Briefs go in as tasks, drafts come back as versioned docs you can comment on line by line, and your voice rules live in a file rather than in one person's head.
What this worker is
An AI content writer in Polaris is a worker you hire to produce written drafts: articles, landing copy, release notes, newsletters. It drafts inside a versioned Polaris doc, applies the voice and structure rules stored in its editable skill file, cites anything factual it looked up, and posts the draft as a comment. An editor comments, the worker revises, a person publishes.
- Typical output
- Versioned draft in Docs
- Core connections
- Web search, Notion, Google Drive
- Illustrative task
- 2.8 human-hours, $5.60
What this worker is great at
Producing the first eighty per cent of a piece against a real brief, in a place your editor can actually work. The draft arrives as a Polaris doc with version history and inline comments, not as a block of chat text somebody has to copy into a document before it can be edited.
The interesting part is the voice rules. Every team has them and almost no team writes them down: no exclamation marks, never say solution, always open on the reader's problem rather than the company, British spelling, one em dash per page at most. In Polaris those rules go in the worker's skill file, which means the ninth draft obeys them as reliably as the first and nobody has to give the same feedback twice.
It is also good at the writing nobody volunteers for. Release notes from a list of merged changes, the FAQ page nobody has updated since launch, forty product descriptions with a consistent structure and no two openings alike.
What to connect it to
Four connections from the fixed catalog cover most writing work.
| Connection | Why this role needs it |
|---|---|
| Web search | Checking a claim before it goes in a draft, and citing the source next to it |
| Notion | Working from the brand guide and the existing wiki instead of guessing at house style |
| Google Drive | Where finished copy has to land when the rest of the team already lives in Drive |
| Slack | Turning a request in a channel into a prefilled writing task you approve with one click |
A realistic first week
- 1
Monday: one article against a real brief
Give it the audience, the angle, the three points it must make and the two things it must never claim. Checklist items become the acceptance criteria.
- 2
Tuesday: write the voice rules down
Read the draft, mark what grated, and paste those rules into the skill file. This is the hour that pays for the rest of the week.
- 3
Wednesday: release notes
Hand it the merged changes and ask for user-facing notes that say what changed and who should care.
- 4
Friday: a second pass
Comment on Monday's doc with your edits. The latest human comment is the brief for the next run, so the revision answers your notes rather than rewriting from scratch.
Where the human stays in charge
The brief
Audience, angle and the claims that are off limits are yours to set. A vague brief produces a vague draft faster than a person would produce one.
The edit
The worker revises against comments; the editor decides when the piece is finished.
Publication
Nothing is published by a worker. The draft sits in a doc until a person moves it.
The rating
You close the task and rate the delivery, and that rating is the worker's performance review.
Work this role picks up
A content calendar that maintains itself between meetings
The calendar stops rotting the moment somebody other than you is responsible for updating it every week.
SEO content production, briefed once and delivered as a file
The difference between usable drafts and filler is the brief, and the brief belongs in a file the worker actually reads.
You shipped twenty-three things and announced four
A draft built from what actually merged, plus a list of the changes nobody described.
Battle cards that are still true this quarter
Enablement content is written once, used constantly, and updated never. The updating is the assignable part.
Questions people ask
+Where does the AI content writer put the draft?
In a Polaris doc, filed under the page whose topic fits, with version history and inline comments. The delivery comment on the task links to the doc, so the review happens in a document rather than in chat scrollback.
+How do I stop it writing like every other AI?
Write your banned words and structural rules into the worker's SKILL.md. A short list of forbidden phrases, a required opening move and a sentence-length instruction change the output more than any amount of prompting inside individual tasks.
+Can it write in more than one voice?
Hire one worker per voice. Two workers with different skill files, one for the product blog and one for the sales deck, cost nothing extra because there are no per-worker fees, and the briefs stay clean.
+What does a 1,100-word article cost?
As an illustrative example computed from the published formula, roughly 2.8 human-equivalent hours, which is $5.60 at $2 per human-hour. The line appears on the work log with the effort it was derived from, and you can challenge it there.
Related
Hire an AI SEO specialist
It looks at what is actually ranking today, then writes the brief that says what your page has to do differently to deserve the spot.
Hire an AI technical writer
The documentation debt on your team is not a writing problem, it is a nobody-has-two-free-hours problem, and this is the worker for those two hours.
Hire an AI social media manager
A month of posts planned, written and filed by Tuesday, so the only decision left is which ones you actually publish.
A content calendar that maintains itself between meetings
The calendar stops rotting the moment somebody other than you is responsible for updating it every week.
SEO content production, briefed once and delivered as a file
The difference between usable drafts and filler is the brief, and the brief belongs in a file the worker actually reads.
You shipped twenty-three things and announced four
A draft built from what actually merged, plus a list of the changes nobody described.
Connect Notion to Polaris
Notion decides what Polaris can see, page by page, because an internal integration only reaches what you explicitly share with it.
Skill file
The capability an agent has, written down where a person can read and edit it.