Skip to content
Stu AI

How it works

From a sentence to a campaign that counts.

Studio takes what you want a campaign to achieve, does the work in the open, waits for your decisions, and keeps the score against a target you set.

One campaign, start to finish

Meridian · Own the ops conversation this quarter

Illustration · sample content

  1. #01IdeaTurned on with you

    You type one line.

    Quick start

    Category POV this quarter: why ops leaders are rewriting their stack.

  2. #02PlanTurned on with you

    The Strategist hands back a plan to confirm.

    Mandate
    Become the default voice for modern ops teams
    Primary goal
    50 newsletter signups by Jun 30
    Voice
    Jordan Hale, founder and CEO

    6 pieces over 4 weeksConfirm

  3. #03Long-formIn every workspace

    The Researcher and Writer make one article.

    Explainer · v3

    Why ops leaders are ripping out their stack (and what they keep)

    4 sources, each checked against the page it cites

  4. #04SocialIn every workspace

    The Writer cuts posts from that article.

    • 4 LinkedIn posts
    • 1 X post
    • The three tools every ops team keeps
    • What we ripped out of our own stack last year

    Same voice, same campaign.

  1. #05Waiting on youIn every workspace

    Every piece stops at your desk.

    Waiting on you3

    • Article

      Why ops leaders are ripping out their stack (and what they keep)

      4 of 4 checks passing

      OpenApprove

    • LinkedIn post

      The three tools every ops team keeps

      1 check needs you: a claim has no source

      OpenCan't approve: 1 failed check

    1 more piece is waiting on you. One piece, one decision. Approving several at once is coming.

  2. #06CountedTurned on with you

    The Analyst counts results, with evidence.

    31 of 50

    Newsletter signups

    from 6 attested outcomes and 25 outcomes reported by integrations

    A campaign reads On track only when outcomes back it.

  3. #07ImproveComing

    The next campaign starts from what worked.

    The posts that opened with Jordan's own story carried most of the signups in this window.

    Coming

    Illustration. Reading results back into the next plan is not built: today you decide what carries over.

Studio drafts the work: a plan line stays a plan until somebody starts that piece. Nothing goes out until a person approves it, and approving does not schedule it.

  • In every workspace
  • Turned on with you
  • Coming

01Say it

Say what the campaign should accomplish.

Type it the way you would say it to a colleague. Studio restates it as a campaign for you to confirm: a name, the outcome, the audience, the timing, the pillar it belongs to, a first plan and a goal.

  • Nothing is created until you start it, and pressing Start twice still starts one campaign.
  • Change something before you start, or cancel, and nothing is left behind.
  • Start from a typed sentence, from a Radar opportunity, or by growing an existing article or post into a campaign. Every start goes through the same restatement.

Studio

/ Campaigns · Meridian

Illustration · mocked UI, sample content

Meridian/ Campaigns

Campaigns

What should Studio accomplish?

Category POV this quarter: why ops leaders are rewriting their stack.New campaign

Studio restatesFrom your request

Here's how I understand the campaign.

Name
Own the ops conversation this quarter
Outcome
Ops leaders weighing a consolidation read Meridian's point of view and subscribe to the newsletter.
Audience
VP Ops and Head of Ops at mid-market companies
Voice
Jordan Hale, founder and CEO
Timing
Apr 6 to Jun 30
Part of
Become the default voice for modern ops teams
Initial plan
  • An article: Why ops leaders are ripping out their stack (and what they keep)
  • LinkedIn: the three tools every ops team keeps
  • LinkedIn: what we ripped out of our own stack last year
  • LinkedIn: why your ops team is drowning in handoffs
  • LinkedIn: an ops leader asked what to consolidate first. Here is the answer.
  • X: ops teams are not buying more tools this year. Here is what they want.
Goal
Signups: 50 by Jun 30, counting results up to 60 days after each publish

Nothing is created until you start it.

Start campaignChange somethingCancel

Illustration: a made-up workspace. The screens and their words are Studio's own.

02It works

It does the work, on the record.

Agents research and draft on their schedules. Studio watches your sources and the news for openings worth answering, drafts articles and posts in your voice with their sources, and proposes dates for the work. Nothing they make goes out without a person.

  • Agents you set up on News Radar watch the topics and pillars you choose, and each one's work is recorded run by run.
  • Drafts follow your own guides. Channel and persona voices are coming.
  • Every source a draft cites stays on record, with a check of whether the page really says what it is credited with.

Studio

/ News Radar · Meridian

Illustration · mocked UI, sample content

Meridian/ News Radar

News Radar

Ops conversation watch

Tool consolidation and ops hiring, from the operations press and Meridian's own pages

Generation autonomyDraft for reviewPublishing autonomyApproval required

Hide runs ▴

  • RunningToday, 9:00 AM, still runningOn its schedule

    Wrote nothing · No model calls

    Publishing: Approval required. Agents research and draft on their schedules.

  • SucceededYesterday, 9:00 AM, 52sOn its schedule

    Wrote 1 promotion run, 2 pieces of campaign work · $0.0418 · 6 model calls · 18,240 tokens

    Publishing: Approval required. Agents research and draft on their schedules.

    Three new signals on tool consolidation; two became ideas, one fed a campaign.

  • Succeeded2 days ago, 4:31 PM, 3sThrough MCP

    Wrote 1 piece of campaign work · No model calls

    Publishing: Approval required. Agents research and draft on their schedules.

  • Failed2 days ago, 9:00 AM, 14sStarted by a person

    Wrote nothing · $0.0031 · 1 model call · 1,920 tokens

    Publishing: Approval required. Agents research and draft on their schedules.

    A source did not answer in time.

Illustration: a made-up workspace. The screens and their words are Studio's own.

03You decide

You decide what goes out.

A campaign's page shows what waits for you: drafts in review, posts awaiting approval and recommendations to decide, the most urgent first.

  • An article goes out only after someone with the approver role approves it on its Approval tab, and the approver can keep it as a draft.
  • Coming for partners: if your site is built from a GitHub repository, Studio opens a pull request for it, and a post goes through Buffer once that post is approved, if you connect your account. Early partners receive approved drafts to publish themselves.
  • Each article is approved on its own. Each post is approved on its own, by a person.
  • A recommendation's changes apply once. If the work moved on since, the change is not applied and the card says why, and published work is never rewritten behind your back.

Studio

/ Campaigns · Meridian

Illustration · mocked UI, sample content

Meridian/ Campaigns

Campaigns › Own the ops conversation this quarter

Own the ops conversation this quarter

Waiting on approval

Part of Become the default voice for modern ops teams

Ops leaders weighing a consolidation read Meridian's point of view and subscribe to the newsletter.

Origin · your request: “Category POV this quarter: why ops leaders are rewriting their stack.”Started Apr 6 by a teammate6 pieces of work

PauseCancel campaign…Archive…

Primary issue · Waiting on approval

Why ops leaders are ripping out their stack (and what they keep) is waiting for review.

Open it

Recommendations · 1

Recommendation

Should the article open with our own audit, not the trend?

Campaign reviewOpen with what we ripped out, then the pattern behind it

The posts that opened with the founder's own story carried most of this campaign's signups. Leading with the audit puts the proof where readers already stop.

  • TitleWhy ops leaders are ripping out their stack (and what they keep)What we ripped out of our stack, and what every ops team keeps
  • Content angleThe trend first, then what teams keepOur own audit first, the pattern behind it second
  • AudienceAlready says this
Use recommendationReview individually

Also needs attention · 1

  • 1 post in this campaign was held for a person: a claim has no source.Needs judgmentOpen
Next
Review the article
Watching
Newsletter signups, through the outcome webhook
Work
6 pieces of work

Studio

/ Review · Why ops leaders are ripping out their stack (and what they keep)

Illustration · mocked UI, sample content

Approve & publish

Human approval is required before this article goes out. Review the gates, set the byline, choose publishing behavior, and approve.

v3 failed on a source with no URL. The URL was added, the checks ran again, and this is the version that passed.

Title
Why ops leaders are ripping out their stack (and what they keep)
Type · category
Explainer · Become the default voice for modern ops teams
Version
v4
  • AEOpass
  • Brand voicepass
  • Sources / citationspass
  • Product canonwarn

Publishing behavior

Draft onlySaves an approved draft. Nothing deploys.
Publish immediatelyApproving will publish this article after deploy.
ScheduledApproving will stage this article and publish at the chosen date and time.
Approve

Illustration: a made-up workspace. The screens and their words are Studio's own.

04It counts

It counts what happened, against your goal.

A goal names a metric, a target, a deadline and a lookback of 30, 60 or 90 days. Publishing opens the window, and the campaign reads Measuring while it runs.

  • A result counts when it lands within the lookback after one of the campaign's pieces is published, until the deadline's day ends.
  • A result's credit is split across the pieces it counts for. Each piece is weighted by how long before the result it was published, halving for every seven days, and the shares add up to the whole result. A piece published more than once counts from its publication closest before the result. There is no data-driven attribution.
  • On track and Complete come only from evidence. Without it, a campaign says so and tells you how to add some: connect a source, or attest an outcome, which is always labeled attested.
Goal, optional: what the campaign counts, and by when
Goal metricSignups
Goal target50
DeadlineJun 30
Lookback60 days30 days60 days90 days

A result counts toward the goal when it comes within the lookback after one of the campaign's pieces is published, until the deadline's day ends.

How credit is shared

One signups, booked inside the 60-day lookback of three pieces.

  • ArticlePublished 31 days before

  • LinkedIn postPublished 14 days before

  • ArticlePublished 3 days before

Less creditMore credit

Illustration: a made-up workspace. The screens and their words are Studio's own.

States

What a campaign tells you

One state leads, and everything else that needs a person stays listed beneath it.

Needs attention
Something failed to publish.
Needs judgment
An agent held a post for a person.
At risk
The month's model budget is spent while work is unfinished.
Waiting on approval
An article or posts are waiting for review.
Measuring
Its work is published and the goal's window is open.
On track
Outcomes back it, and it says which.
Complete
The window closed, with evidence.
Ended, not measured
The window closed without evidence, and it says so.

On the record

What every run records.

Each time an agent works, the run is written down, whether it was started on a schedule, by a person, or by your own agent over MCP.

When, and why
Its start, how long it took, and what started it: its schedule, a person, or MCP.
What it wrote
The opportunities, promotion runs and campaign work it produced, each linked back to the run.
What it spent
Each model call it made, metered to the run and the agent, with its tokens and its dollars.
The Boundaries it read
The workspace's Boundaries as the run read them when it started. Agents research and draft on their schedules, and nothing they make goes out without a person.

Publishing waits for a person today.

Agents research and draft on their schedules. Nothing they make goes out without a person. Claim changes are coming later, as an opt-in.

Settings · Boundaries

  • ResearchOn its schedule
  • DraftingOn its schedule
  • Claim changesComing later (opt-in)
  • PublishingApproval required

Illustration: a made-up workspace. The screens and their words are Studio's own.

Checked before anyone approves

Every draft is checked, and names what needs you.

Open a draft in Review and Studio runs its checks: voice rules, the sources behind each figure, and your product facts. Each is a pass, a warning or a fail, and a fail keeps the piece on your desk until it is fixed. The marks on this draft illustrate those results.

  • Your voice, then a voice check

    Studio writes from your brand voice guide, then checks the draft for the things good brand writing avoids: hype phrases, sales calls to action, exclamation marks and too many dashes. These are warnings for you to weigh, not blocks.

  • Every figure, against the page it came from

    Each figure should cite a page that states it. When Studio has read the page and cannot find the figure, the check says which one, so a person can open the page and fix the figure or the source.

  • Claims, against your product facts

    Claims are checked against your product facts, and a claim that does not match them is flagged for you rather than quietly left in.

  • A fail you cannot approve past

    Some checks are structural: a source missing its URL, or a footnote with nothing behind it. Those fail, and the piece stays with you until they are fixed. A warning is the other kind, and you can approve past one.

Studio

/ Why ops leaders are ripping out their stack (and what they keep) · Checks on the draft

Illustration · mocked UI, sample content

EditorWaiting on your approval

Why ops leaders are ripping out their stack (and what they keep)

Explainer · Become the default voice for modern ops teams · v3

Illustration. In the app, checks appear as a list in Review.

Ops leaders are not ripping out their stack because the tools failed. They are doing it because every tool added a handoff nobody owns Brand voice · No hype, no sales CTAs, and the work now lives in the gaps between them.1

Teams that audit before they buy cut their tool count by about a third4 Sources / citations · This page may not state this figure, and the tools they keep are the ones the whole team already opens every morning.

Sources / citationswarnChecked against 1 source

No cited page is known to omit its figure

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.

The test that settles most of these arguments is simple: count the handoffs a tool removes, not the features it adds2 Sources / citations · Footnote 2 points at a listed source.

Teams that publish their own audits are worth reading before you quote a benchmark, because a company of forty does not consolidate the way a company of four hundred does.3

Sources / citationsfail

Sources have title, publisher, and URL

Incomplete source: #3 (missing url). Every source needs title, publisher, and URL.

Can't approve: 1 failed check

Waiting on your approval

Nothing happens to this piece until you decide.

A warning is yours to weigh. A failed check has to be fixed before this can be approved.

Illustration: a made-up workspace. In the app, checks appear as a list in Review; here each result sits beside the words it is about. The check names and their results are the product's own.

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

Talk to us