Content Engine

Content Engine helps marketing and RevOps teams turn sales and customer conversations into content briefs, drafts, reusable assets, and publishing plans.

Content Intelligence

Content Intelligence surfaces topic demand, objection heatmaps, rising objections, objection sentiment, objection stage mix, content coverage gaps, customer questions, competitor mentions, and the Content Idea Lab. In the Idea Lab, teams can review suggested ideas generated from topic/ICP heatmaps and coverage gaps, then organize suggested, seeded, and manual ideas in the shared Saved content ideas area. The Saved content ideas Add idea button opens a choice modal where teams can either manually save a rough idea or talk to Genie about a rough idea, campaign theme, or content type so Genie can shape the angle, check for duplicates, and save the best ideas. Saved content ideas show who saved each idea and use first-class folder navigation with All ideas, No folder, and nested folder paths. Teams can move cards between folders, use an expanding search control, and apply compact metadata filter pills for tags, saved-by user, best-fit ICP, topic, objection, content type category, priority, and roadmap status; tag, ICP, topic, and objection filters support multi-select dropdowns. Genie can also set those Saved content ideas folders and filters from chat. Genie checks existing saved ideas and existing Content Library/Studio assets before suggesting or saving new ideas so teams avoid duplicates. Clicking topic/ICP or objection grid selections carries those filters into the Idea Lab so teams can generate ideas from the exact demand signal they are reviewing. Explicit format requests such as articles, LinkedIn posts, battlecards, FAQs, whitepapers, or one-pagers constrain the generated recommendations to those formats. Saved idea cards store and expose editable best-fit ICP/topic metadata, with visible pipeline-fit, evidence, and specificity heuristic scores based on linked opportunity, objection, account, evidence, quote, SEO, outline, and angle metadata. The Plan action opens the Content Calendar schedule dialog with that idea selected so the user can choose when it should ship; the idea is converted into a Studio asset only after the user adds it to the calendar. Studio opens drafts directly with metadata and score context preserved.

Content Studio

Content Studio is the writing workspace for one saved content asset at a time. Studio Genie can edit the draft, generate evidence-backed briefs, run editorial review, improve metadata, and attach supporting sources to the asset.

Studio Genie is content-type aware. It does not force social posts, FAQs, battlecards, legal docs, decks, one-pagers, whitepapers, or internal enablement into a blog format. It requires evidence for factual claims, quotes, stats, competitor claims, and customer-specific statements, but can help with lower-risk structure, tone, headlines, and social copy when evidence is thin.

Studio also surfaces related assets below the canvas so teams can keep a blog, derivative social posts, enablement pieces, and supporting assets connected as a content package. Explicitly linked related assets appear before suggested matches, and users can manually link/unlink suggested assets or create one or many related draft assets directly from the source asset.

When Genie leaves [VERIFY: ...] or [EVIDENCE GAP: ...] markers in a draft, Studio highlights them as clickable pulsing badges. Users can remove a resolved marker or ask Genie to inspect the exact tag, nearby draft context, and available sources before replacing it or explaining what evidence is still missing.

Content Library

Content Library is the inventory for uploaded source collateral, reusable media, Content Studio assets, generated outputs, templates, and external assets. Users can search from an expanding header control, add compact metadata filters for content type, library kind, audience, allowed use, author, and related-asset packages, and browse folders as first-class navigation. The Create Asset button lets users start from an existing saved idea in the Content Idea Lab or create a new Studio draft from scratch. Library rows also flag related assets when the current result set has shared tags, audience, or content type overlap, and Studio-linked library assets can jump straight into related-asset creation.

Folders are represented as asset folder tags, support nested paths, and appear when assets or ideas are assigned to them. Asset details expose content type, audience, allowed uses, visibility, status, folder, and tags as first-class editable fields.

Content Calendar

Content Calendar plans when ideas, drafts, approved assets, and scheduled Campaign Engine sends should ship. It opens in a weekday-focused Week view by default, hides weekends until users turn on the Show weekends toggle, and uses a full-width, full-day scrollable time grid with hour labels, horizontal time lines, a current-time line, and a 30-minute hover highlight in Week and Day views. Status and asset type filters live in one compact filter menu. Month, Week, and Day views each have an inline editable period theme that autosaves on blur and guides the calendar plan; Calendar Genie can set visible month themes, week sub-themes, and daily subthemes from chat and sees the active theme hierarchy, prior items, Topic × Persona hotspots, Objection × Persona hotspots, rising topics, rising objections, objection gaps, competitor overlap, backlog assets, ready recommendations, saved ideas, and social assets when helping seed the calendar. Clicking an open calendar slot opens a scheduling dialog with two paths: use existing content from the Content Library picker, or use a saved idea from the idea library. Saved ideas stay ideas while selected and are converted into Studio assets only when the user confirms Add selected to calendar. The dialog keeps the scheduled time and destination adjustable, shows the selected asset author and publishing destination, and stores the linked Studio asset id on the calendar item. Existing content cards are rescheduled from their edit modal, and publishing uses the same scheduled calendar time rather than a separate publish-time field. Scheduled newsletter campaign sends appear as read-only campaign cards using the campaign-level send time, with recipient counts and links back to the scheduled campaign. The single Ask Genie to plan from theme action opens Genie with the current theme, or asks for a theme first, then asks Genie to propose a plan using existing content, social posts from users, saved ideas, ready recommendations, and Content Intelligence hotspots/gaps. If the idea library is thin, Genie suggests going to Content Idea Lab to seed more ideas before scheduling.

Calendar items can also have publishings. Each destination gets its own publishing row so LinkedIn and CMS delivery succeed or fail independently. Scheduled publishing pins the asset version/content hash and only publishes approved publishings. The calendar drawer has a Ready to publish action that approves the asset, calendar item, and scheduled destinations together.

Current publish destinations:

• LinkedIn — publish through the user's connected profile, a shared profile, or an allowed company page.
• Connected CMS — publish through the existing Sanity CMS publisher.

If a scheduled publish fails, the calendar drawer shows the failure reason and supports retry or cancel actions.