Content Engine
How Content Engine turns customer evidence into planned, organized, and publishable content.
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 switch between Saved ideas and Suggested tabs in one shared workspace, using the same search, metadata filters, and card/list view toggle across both. Suggested ideas are generated from topic/ICP heatmaps and coverage gaps, then can be saved into the library or sent directly to Studio; seeded ideas are added automatically when Genie saves them. The Saved 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, list rows show the creator when available, and ideas 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 and rows 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, create new images, run editorial review, improve metadata, run SEO/AEO research over live SERPs and ChatGPT citations, 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.
When you need a net-new visual, Studio Genie can generate an image, upload it to Cloudinary, and insert markdown with meaningful alt text or fill Open Graph image metadata for social previews. It can also use attached screenshots or reference images for edits and variations, such as blurring sensitive UI details. When you need an existing Content Library asset, reusable media/collateral, or approved image/video, Genie searches and fetches from the Content Library instead and only inserts embed-safe media URLs. If you attach a file and explicitly ask Genie to save it, Genie can upload that attachment into the Content Library.
Studio surfaces related assets in the bottom drawer beside Citations so teams can keep a blog, derivative social posts, enablement pieces, supporting assets, and saved ideas connected as a content package without leaving the canvas. Explicitly linked related assets appear before suggested matches, and the Add Related Asset button asks whether to link existing or create new, then asset or idea: users can create a related asset from an idea (Studio creates one linked draft and opens it with Genie already riffing on the idea), seed a new saved idea, link an existing saved idea from the Idea Library picker (searchable, with idea folders and the same filters as the Idea Lab), or link Content Studio content picked from the Asset Library. Linked LinkedIn ideas and social content can be sent to or opened in Studio.
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 flag explicitly linked related assets, Studio links open in a new tab, and linked LinkedIn/social derivatives appear behind an expand/collapse toggle under the main source content instead of cluttering the top-level list.
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 picker, which offers the same search, folders, and metadata filters as the Idea Lab. 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. Each content item also has a visible Content owner on the card and drawer; LinkedIn schedules default to the selected profile/page account owner, other items default to the content or idea author when available, and users can override the owner from the item modal. 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. A publishing can only be approved once its asset is approved, and moving an asset back out of approved un-approves its pending publishings. The calendar drawer's Publishing section shows a status banner that says either when and where the item will publish or exactly what still needs to be fixed (with a one-click action for each). The Ready to publish action approves the asset, calendar item, and scheduled destinations together; destinations whose publish time already passed are rescheduled at the new future time you pick.
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.