How to Set Up an AI Content Team, Step by Step
To set up an AI content team, hire a department rather than a single writer: an AI chief of staff who owns output and the brand line, team leads for images, long-form and video, and makers for blogs and landing pages. Then give it your website, products, voice and documents, decide who approves what, and start with small first asks. This guide walks through each step on Nagent with CREA, the AI Content Chief of Staff.
What does an AI content team need before it writes a word?
A content team, human or AI, writes well only when it knows four things: who you are, what you sell, how you sound and who signs off. Skip any of them and you get confident, generic copy that a person then rewrites line by line.
So the setup work is mostly about the material the team reads and the rules it works under:
Your own material. Your website, your products and services, the documents your team already uses, and who you sell to.
A confirmed voice. Not a guess read off your site, but a voice a person has read and accepted.
A byline and a publisher. Whose name goes on posts, and which people may press publish.
A budget. A daily cap, so a busy week can't run up a surprise bill.
Get these right once and every draft after it starts closer to finished.
Where does CREA sit in the team?
Nagent builds AI teams like a team you would hire. You can see the whole model on the team page. For Content, the line looks like this:
You and your people, who approve what publishes and decide how much each agent may do alone
CREA, AI Content Chief of Staff. Owns output and the brand line. A message to the Content room addressed to nobody reaches her.
RUPA, team lead for the image studio. Renders images with your brand kit attached.
FOLIO, team lead for long-form. Turns your documents into illustrated publications as PDF and DOCX, with six stage agents under it: Ingestor, Architect, Writer, Artist, Compositor and Publisher.
Alpha, team lead for the video studio. Its bench holds ADS, UGC and AVATAR.
Makers on CREA's team. LANDON builds landing pages, PAIGE makes decks and documents, the Blog Studio agents write blog posts, and NOVA writes newsletters.
A request moves down the line and back up it. You ask the department in one line, in its room. CREA decides who owns it and hands it to that maker or team lead. The lead breaks it down, puts tasks on the board and briefs its bench. Each sub-agent does its part and hands the result back to its lead, never sideways to another seat, and one message travels at most three hops. The work comes back to you as one piece, with anything that needs a person waiting on a card.
Other departments reach Content the same way. MIRA, the AI Marketing Chief of Staff, passes the writing and visuals to CREA's Content team. Anyone in another room can type @CREA and say what they need. That becomes a task on the Content board, marked with who asked and from where, and the result is posted back to the thread that asked.
How do you set up an AI content team on Nagent?
Work through these steps in order. Each one gives the next more to go on.
Step 1. Hire the Content department
Sign-up opens on Choose teams, under the line Hire your AI team. On the Content card, CREA sits at the top, the card reads Owns output and the brand line, and RUPA (image studio), FOLIO (long-form) and Alpha (video studio) are listed as Live team leads, each marked Reports to CREA. Press the card to take the whole department, or tick only the leads you want, then press Continue. The teams install the moment you first sign in.
Already signed up? Choose Add a team, then Choose a prebuilt team, and press Use this team on Content. That needs the settings write permission an Organisation admin holds; see the prebuilt teams guide.
Step 2. Set up with N and your chief of staff
Set-up runs in N · Setup, a chat with N, the head of your AI growth org (Beta), together with the AI chief of staff of a department you hired. The heading names the pair, for example N, with MIRA, your AI Marketing Chief of Staff. The huddle beside it lists the other chiefs, who pick up their own teams once that part is done; below, CREA waits there for Content.
Tell N about your business, typed or with voice on (Beta). N asks for one fact at a time, saves each answer where it belongs, and only asks you to sign in to your tools: that part is always yours. The Onboarding page tracks five steps, Onboarding, Connect tools, Website, Brand and N · Setup, so you can pause and resume. Content's part covers adding the Content team so other teams can ask it for work, connecting a place to file what it writes, and whether your developers will connect your site.
Prefer screens to chat? I'll set it up myself takes you to the same settings.
Step 3. Fill the Knowledge Hub, in this order
Every draft is grounded in what your workspace knows: what you sell from Products & Services, up to six Knowledge Hub passages that match the topic, your voice from the brand book, and your booking link. If the hub has nothing on a topic, the draft goes without rather than inventing detail.
The Knowledge Hub is grouped by the kind of work, and two groups matter most for content, Teach and Your business. Fill them in this order:
Website, under Teach. Give it your site's address so it reads your own pages.
ICP, under Your business. Describe who you sell to in a few sentences.
Products & Services, under Your business. Review the drafted offerings and make the right ones active. An offering reaches agents only once a person makes it active.
Brand, under Teach. Covered in the next step.
Documents, under Teach. Add what your site doesn't carry: decks, research, call notes. A document is readable once its status reads embedded.
Step 4. Confirm your brand voice
Open Brand under Teach. The page is your brand book, headed with your brand's name and in one book every agent reads, with Download brand book at the top.
Further down, the Brand voice section has Extract from website. Press it, read the draft, and press Confirm only if it sounds like you, or Reject it. Agents read the confirmed voice only, never the draft, and write in neutral copy until one is confirmed.
The brand book itself is generated in the background the first time your website is read after sign-up. If you have a published brand guideline, upload it on the same page; it outranks anything read off the site. Brand Lock covers the page in detail.
Step 5. Set the default blog author
Every post the team drafts carries one byline. Open Settings, find the Default blog author card, type the name readers should see (a person or a team), and click Save author. Drafting waits until an author is set, and a run without one stops before it spends anything.
Step 6. Decide who approves, and set the budget
Nothing the team writes goes live until a person approves it. Approving and publishing a post needs the content publish permission, which a workspace admin holds. When you invite colleagues, give at least one of them a role that can decide, so approvals never wait on you alone.
Then set the money. Blog Studio estimates about 36 credits per blog, and runs share a daily blog budget: set Daily blog spend cap in Settings, in credits, or keep the cap sized to your plan. When it is spent, new runs stop until the next day.
Step 7. Learn the Content room
In the Content room, the Inbox on the left lists everything waiting on a person, oldest first. In Messages, a message without an @ goes to CREA, and an @ with a name, such as @RUPA, addresses that lead or maker.
The Team surface tab lays out the work. Board shows a Waiting on you list and the roster. Beside it sit Overview and a tab for CREA and each lead and maker your workspace holds; below, that is RUPA, PAIGE, LANDON, NOVA, FOLIO and Alpha.
CREA's tab opens her page inside the room, with four columns: Plan (approved topics ranked by an AI score), Write (live bulk-write progress), Review (blogs the AI couldn't fix in three passes, each showing the check that failed) and Publish. FOLIO's tab lists your long-form books with their status and spend in credits.
Step 8. Connect your site, when you're ready
Posts are stored in your workspace, and your website reads them with a site key from the Site connection card (Beta) in Settings, Integrations. Your developers wire it once, as in Connect your site. Until then, View live points at the Nagent website.
What should your first asks be?
Start small, so you can judge the team on work you can check in minutes.
One blog post in Blog Studio. Open Blog Studio, type a topic, optionally add an angle (who it's for and what it must argue), and click Start the agent team. The run page shows a live agent feed and the draft so far. When the run reaches Approve, the title, meta description, slug and body open for editing.
Then choose Send back with feedback or Approve & Publish. A check runs before anything publishes: a lead paragraph of 40 to 90 words, most section headings as questions, a FAQ of three to five questions, your brand's voice, and links a reader can open. What it can't fix on its own holds the post, with one sentence per problem.
One brief in the room. Type a line like "Draft a post on why onboarding emails fail without a clear next step, for heads of lifecycle marketing" into the Content room. It becomes a task on the team's board, and the work comes back as a file to review.
One image. Ask @RUPA for a banner in the room, or open RUPA's studio. Describe an image, or start from a format such as a story cover. The brand kit comes from your brand book, the cost is shown before anything renders, and every render is written to the audit log. See RUPA, the image studio.
One small kit. Once single pieces look right, ask for several at once: "A launch kit for our spring offer: a ten-slide pitch, a landing page and a short teaser video, for heads of operations." CREA writes one plan that names each piece's maker, shown on one approval card with an estimate. Approving the plan sends each piece to its maker; each piece still passes its maker's own approval and budget.
One landing page. The Content room has a LANDON tab, which links to your landing pages. A person presses Publish; LANDON never does. See Decks and landing pages.
One long-form piece. Open FOLIO's tab in the room and press New book. FOLIO's studio opens: pick a kind of book, a chapter count and your sources, and see the price in credits before anything is written.
What does the AI content team not do yet?
Better to know these on day one:
It doesn't publish on a schedule for you. Scheduled publishing and the blog engine modes in Settings don't run for customer workspaces yet. Publish with Approve & Publish or Publish now.
It doesn't publish on its own at all. Nothing is published, scheduled or sent by CREA. The last step is a person's.
Video waits for a person. Alpha plans a video and quotes it in credits, and nothing renders until a person approves the storyboard and its quote.
Your site needs your developers. Until the site connection is wired, posts show on the Nagent website.
Frequently Asked Questions
What is an AI content team?
An AI content team is a group of AI agents organised like a content department: a chief of staff who owns output and routes work, team leads for images, long-form and video, and makers for posts, pages and decks. On Nagent, CREA leads it, and people approve what publishes.
How long does it take to set up an AI content team?
The department installs the first time you sign in, and the brand book is generated in the background about a minute after your website is first read. The rest depends on how quickly you confirm a voice, make offerings active and add your documents.
Does an AI content team publish without approval?
Not on Nagent. The team does every step up to the last one, and a person presses Approve & Publish. An editorial check runs at publish and holds a post if it finds a blocker.
Can I start with one content team lead instead of the whole department?
Yes. At sign-up, tick single team leads on the Content card instead of pressing the card for the whole department. RUPA, FOLIO and Alpha have no room of their own, so each works in the Content room with CREA, on its own tab of the Team surface.
Start with one department, then grow it
An AI content team pays off when it writes from your material, in your confirmed voice, under approvals you set. Hire the department, set up with N, fill the Knowledge Hub, confirm the voice, name the byline and approvers, then judge the team on small first asks. CREA and her team do the drafting; your people keep the last word. The CREA guide has every screen in detail.
Book a demo to see CREA's Content team set up in a workspace like yours.