# Stu AI - Your Content Studio & Team

> An AI content engine that drafts campaigns toward a goal you set and counts results only with evidence. Nothing is scheduled or published until a person approves it.

Set the goal. Studio drafts the work. Nothing goes out until you approve it.

Studio does not mark text inline in a draft: preflight runs when Review opens and shows its results as a list there. The sample draft on the how-it-works page is an illustration that places each result beside the words it is about.

Studio is made by Bolls in Nashville, Tennessee.

What this site does not claim: it names no customers, and it names no logos, testimonials or metrics. It publishes no citation numbers.

## Pages

- [Home](https://stu.now/): The product doing the work, the six steps a campaign runs, and what is checked before a draft reaches you.
- [How it works](https://stu.now/how-it-works): The four steps in full, with the screens: say it, it works, you decide, it counts.
- [Security](https://stu.now/security): How membership is checked, and what the product seals, records and caps, from the product's code, with no compliance claims.
- [Sign in](https://stu.now/signin): Where members sign in, with a link sent to their work email.

## Key facts

- Studio is described as a content team you run: it plans, researches, drafts and checks, and a person with the approver role decides what goes out.
- A campaign starts from a sentence: Studio restates it (name, outcome, audience, timing, pillar, first plan, goal), and nothing is created until a person starts it.
- A goal names a metric (mention, signup, demo, customer conversation, website conversion, or other), a target, a deadline and a lookback of 30, 60 or 90 days. AI citation goals are coming to design partners. Citation tracking is through Profound and Promptwatch.
- A campaign reads On track or Complete only from evidence; without it, it says so.
- Agents research and draft on their schedules. Nothing they make goes out without a person.
- Four checks run on every draft and are recorded with its approval: brand voice, sources and citations, product canon, and the answer-engine shape. Most results are a pass or a warning a person weighs. A structural problem fails, and a failed check cannot be overridden in the editor: the piece cannot be approved until it is fixed.
- Every agent run records when and why it ran and what it wrote, and each model call it makes is metered to that run. It also stores the workspace's Boundaries as it read them when it started.
- You stay in control. Today nothing is scheduled or published until a person approves it, articles need someone with the approver role, and each piece is approved on its own. Rules you trust that approve for you, and approving several pieces at once, are coming later, as an opt-in. Neither can be switched on today.
- Approving does what the approver chose: keep an approved draft and deploy nothing, stage a date, or let the piece go out.
- What waits for a person sits on each campaign's own page. There is no single screen that gathers every decision.
- If your site is built from a GitHub repository, Studio opens a pull request for each approved article. If you connect your Buffer account, a post goes through it once you approve that post. Both are coming for partners: early partners receive approved drafts to publish themselves.
- No connection changes who approves: a person still approves each piece, and a connection decides where an approved piece travels rather than whether it travels. A social post can also be copied, pasted and marked posted by hand, which needs no account connected anywhere.
- Outside agents connect over MCP with a scoped key; no scope can approve, generate, schedule or publish.
- There is no checkout, so every plan starts as a conversation. Contact: hello@stu.now.

## What is checked before a draft reaches you

| Check | What it looks at | Result it can record |
| --- | --- | --- |
| Brand voice | Generic voice rules: hype phrases, sales CTAs, exclamation marks, dash budget | pass or warn |
| Sources / citations | Complete source fields and footnote mapping, and whether a page states the figure it is cited for | pass, warn or fail; only a structural problem fails |
| Product canon | Whether a draft's claims match the workspace's product facts | pass or warn |
| AEO | Whether an answer engine can quote it: a direct answer, questions as headings, FAQs, a sourced statistic, structured data | pass or warn |

All four are recorded with the approval. A warning is yours to weigh. A failed check has to be fixed before this can be approved.

- Brand voice (pass): No hype, no sales CTAs. The voice rules are generic ones: hype phrases, sales calls to action, exclamation marks and the dash budget.
- Sources / citations (pass): Footnote 2 points at a listed source. Every footnote in this draft maps to one of its four sources.
- Sources / citations (warn): This page may not state this figure. Studio could not find "about a third" on Mid-Market Benchmark's survey page. Open the page, then fix the figure, change the source, or mark it checked.
- Sources / citations (fail): Sources have title, publisher, and URL. Incomplete source: #3 (missing url). Every source needs title, publisher, and URL.

The results above are the product's. Studio shows them as a list in Review and does not mark text inline; the sample draft on the how-it-works page places each one beside the words it is about.

## Security

- Membership is checked: Every request checks that the person signed in is a member of the workspace.
- Credentials stay sealed: The publishing tokens and model keys you connect are encrypted at rest, used only on the server, and shown back as their last four characters.
- Roles decide who approves: Only someone with the approver role can approve an article, and agents connected over MCP get no key that can approve, schedule or publish.
- Spending has a ceiling: Each workspace has a monthly model budget. When it is spent, the work stops and says so, instead of running up a bill.
- Everything is on the record: Runs, decisions and outcomes are written down as they happen, and a correction is a new row rather than an edit.

## FAQ

### What does Studio make?

Articles for your blog, posts for your social channels and the briefs behind them, organized into campaigns that each pursue one goal. Agents research and draft on their schedules. Nothing they make goes out without a person. Studio also watches your sources and the news for openings worth answering, and files them as ideas.

### Where does approved work go?

Coming for partners. If your site is built from a GitHub repository, Studio opens a pull request for each approved article, and if you connect your Buffer account, a post goes through it once you approve that post. Early partners receive approved drafts to publish themselves. Each article and each post is approved on its own.

### Does anything go out without a person?

Not today. You stay in control: nothing is scheduled or published until a person approves it, and each piece is approved on its own. Articles need someone with the approver role. Posts wait for a person too, and every agent run is recorded with what it did. Rules you trust that approve for you are coming later, as an opt-in.

### How is a goal measured?

A goal names a metric, a target, a deadline and a lookback of 30, 60 or 90 days. A result counts for every piece published within the lookback before it, until the deadline's day ends, and its credit is split across those pieces: each one's weight halves for every seven days between its publication and the result, and the shares add up to the whole result. A campaign says On track only when outcomes back it.

### Can it tell us whether AI answers cite us?

Coming to design partners. Studio tracks AI citations through Profound and Promptwatch. Every article is also checked before approval for what answer engines look for: a direct answer, questions as headings, FAQs, a sourced statistic and structured data.

### Can our own agents work with it?

Yes. An agent you run elsewhere can connect over MCP with a key you scope. It can file ideas and content plans, read your campaigns and an article's review, and record outcomes, which are always labeled attested. There is no key that can approve, generate, schedule or publish: your agents propose, and a person decides.

### What does it cost?

Free stays free. Starter is $149 a month, Growth is $399, Scale is $999. Enterprise is custom: talk to us. There is no checkout yet, so every plan still starts as a conversation.

## Optional

- [Every page in full](https://stu.now/llms-full.txt): The text of every page on this site, as one Markdown file.