Core Concepts
Nuviro turns one thing worth announcing into a full marketing campaign, with a human reviewing the AI's work at two deliberate checkpoints along the way. Here's the whole path, in order.
Signal → Assessment → Campaign + Brief → Content → Review → Publish
Signal
The raw thing worth marketing — a shipped feature, a changelog entry, a competitor's move, or just a note. Signals live under a Product and don't do anything on their own; they're raw material.
Assessment
Before any campaign gets built, Nuviro assesses the signal: is this worth ignoring, a quick social post, a focused mini-campaign, or a full multi-channel launch? This is a strategy decision, kept deliberately separate from actually producing anything — assessing a signal never creates a campaign by itself.
Campaign
A campaign is anchored to one primary signal and has a scope (Social Only / Mini Campaign / Full Campaign) that controls how much review it needs later. Creating a campaign doesn't generate content yet — it first generates a brief.
Brief
The strategy and messaging for the campaign — objective, audience, primary message, key points, call to action — written before a single piece of actual content exists. This matters because the brief, not the raw signal, ends up driving the tone and emphasis of everything generated after it; the signal stays the source of facts.
Depending on your campaign's scope and your workspace's approval settings, a brief either auto-approves (small, low-risk campaigns) or needs a human decision first. A Full Campaign brief always needs a human to approve it — there's no auto-approve for those, regardless of settings.
Content generation
Once a brief is approved, Nuviro generates one asset per channel the brief calls for — written copy always, plus an image and/or a video script depending on that channel's settings. Every asset starts in draft, then moves to pending review once it's ready.
Text and images can be regenerated if the first result isn't right — see Generating Content and Generating Images.
Review
Every asset needs a human decision before it can go anywhere: Approve, Reject, or Request Changes. This is the second deliberate checkpoint — nothing reaches a real channel without someone looking at it first. See Reviewing & Approving.
Publishing
Publishing is always a separate, deliberate action — approving an asset never publishes it automatically. You choose when to send it live, and only to channels you've connected. See Publishing for which channels are live today.
Two checkpoints, on purpose
Nuviro is built around exactly two points where a human decides, not zero and not twenty:
- The brief — is this the right strategy before we spend effort writing content for it?
- The finished asset — is this specific piece of copy/image/script actually good enough to publish?
Everything in between is automated. This is what makes it possible to go from "we shipped a feature" to "a reviewed, on-brand campaign is ready to publish" in minutes instead of days, without losing the human judgment that actually matters.
Where locales/languages fit
A campaign can be written directly in your own language (see Content Language), and can be localized into other markets as a linked sibling campaign that adapts the same approved strategy for a new audience — see Localization.