Explain a software product from its positioning brief in Claude
Give Claude the audience, approved positioning and supported product facts. Review ngram’s plan, then create a concise explanation of how the product’s main concepts fit together.
See what you can make
A Blueprint explanation created through Claude from a positioning brief supported by Linear’s official product pages. Labeled diagrams explain issues, projects, initiatives, cycles and roadmaps.
Prompt
Use the connected ngram tools to explain Linear from this source-backed positioning brief. The audience is product managers and software teams who want a concise introduction to how the product organizes work. Positioning brief: Linear connects product planning with day-to-day execution. Projects bring related issues, documents and updates together. Initiatives organize larger product efforts, while cycles help teams plan time-boxed work. Roadmaps provide a visual view of the product plan. Explain these relationships without adding performance guarantees, customer results, pricing or endorsement claims. Sources: https://linear.app/features, https://linear.app/plan and https://linear.app/build. Use this narration: “Product plans and daily work need a shared structure. Linear brings issues, projects and larger initiatives into one product-development system. A project gathers related work and documents. Initiatives connect projects to bigger product efforts. Cycles help teams plan time-boxed work, while roadmaps show the plan visually. Start with the product work your team needs to organize, then explore how these pieces fit together.” Create a 40-second, 16:9 Blueprint video with clear English narration and quiet background music. Use labeled diagrams to introduce “Issues”, “Projects”, “Initiatives”, “Cycles” and “Roadmaps”, keeping the relationships consistent with the brief. Show a project containing issues and documents, an initiative grouping projects, and a separate cycle timeline. Treat these as explanatory diagrams. Use plain text “Linear” and do not simulate clicks or invent product interface screens. Finish on “Explore your product workflow” with “linear.app/features” held fully visible for at least five seconds after narration. Include readable source credit “linear.app/plan · linear.app/build”. Prepare the video for review and download. Show selected settings and the total estimate before creation. After I confirm, create the plan and return the narration and complete scene sequence for review. Wait for approval before production. Continue the same video when I ask for progress. Leave scheduled tasks off. Return the preview, ngram project and available MP4 export when ready. If the ngram connector is not connected, read https://www.ngram.com/markdown/docs/connect-ngram-to-claude.md?view=1 and help me connect ngram to Claude. Wait for me to complete sign-in and approve access, then resume this workflow.
Selected style
Blueprint
Read the video transcript
Product plans and daily work need a shared structure. Linear brings issues, projects and larger initiatives into one product-development system. A project gathers related work and documents. Initiatives connect projects to bigger product efforts. Cycles help teams plan time-boxed work, while roadmaps show the plan visually. Start with the product work your team needs to organize, then explore how these pieces fit together.
How it works
One source. A repeatable workflow.
Start with
An approved positioning brief and current product sources
Create in
Claude
Make
A source-backed software explanation with clear labeled visuals
Supply the approved positioning
Open Claude with ngram enabled. Provide the audience, product purpose, supported capabilities and current source pages.
Review the concept relationships
Confirm the selected settings and estimate with plan review. Check the narration, diagram labels and relationships against the approved brief.
Watch the complete explanation
Ask Claude for progress on the same video. Check that the visuals explain the intended concepts and that the source credit and next action remain readable.
Place it beside the product information
Choose appropriate viewing permissions or an available MP4 export. Include the current product destination where viewers can learn more.
Watch the workflow
Explain software positioning through Claude
Follow the product brief and sources in the actual Claude conversation. Review the diagram revision, approve the plan and download the MP4, then watch the complete software explanation.
Read the walkthrough transcript
The request supplies an audience, positioning brief, official source pages and narration. The plan is revised to keep cycles and roadmaps separate from the issue, project and initiative hierarchy. The revised plan is approved, and Claude returns the MP4 and ngram project. The complete explanation plays with this narration. Product plans and daily work need a shared structure. Linear brings issues, projects and larger initiatives into one product-development system. A project gathers related work and documents. Initiatives connect projects to bigger product efforts. Cycles help teams plan time-boxed work, while roadmaps show the plan visually. Start with the product work your team needs to organize, then explore how these pieces fit together.
Your starting point
Start with the prompt.
Prepare the audience and approved software brief in Claude, then review ngram’s explanation and concept diagrams.
Review. Then deliver.
Claude returns the software explanation and ngram project. Check the product facts and visual relationships before sharing.
While your video is being made
Ask Claude for the existing video’s status and review any pending plan or question.
Share a link
Choose the intended viewers and include the relevant product destination with the explanation.
Download the video
Ask Claude for an MP4 using an option available to the ngram account. Download in the ngram project requires an eligible paid plan. Review the saved explanation before placing it on the product page or presentation.
If the workflow needs attention
Ask Claude to inspect the existing attempt and identify the source or creation issue. Continue with the same video ID and project link.
- The diagram implies an unsupported relationship
- Identify the affected connection and provide the correct product description. Ask Claude to revise the diagram and matching narration.
- The explanation adds a product claim
- Quote the added line and supply the approved source wording. Review the full revision before sharing.
- The positioning changes
- Update the audience, product brief and closing action together. Ask Claude to revise the affected scenes and review the complete story.
Keep the workflow. Change the story.
- 01
Explain the product to another audience
Change the assumed knowledge, vocabulary and relevant capabilities while preserving supported product facts.
- 02
Refresh the story when the product changes
Provide the updated positioning and current source pages. Review the concept relationships and next action before replacing the video.
Examples
Explore ways to explain software concepts
Compare the structure and visual language for the intended audience.
SaaS explanations
Introduce the product’s purpose and supported capabilities.
See the exampleFounder product explanations
Explain the product to viewers encountering it for the first time.
See the exampleDeveloper explanations
Clarify technical relationships with the right level of detail.
See the exampleMarketing explanations
Connect the product story with the audience’s stated task.
See the exampleSecurity explanations
Use a separate reviewed brief for security-related concepts.
See the exampleExplainer examples
Compare ways to sequence an unfamiliar idea.
See the exampleTemplates
Start with the approved product story
Choose the explanation format that fits the audience.
SaaS explainer
Explain the product’s purpose and main concepts.
Use this templateGeneral explainer
Structure a focused explanation from approved facts.
Use this templateSoftware pitch
Introduce a broader product proposition to a new audience.
Use this templateSecurity explainer
Use a separately reviewed source brief for a security capability.
Use this templateProduct demonstration
Use genuine interface material when the next brief requires a walkthrough.
Use this templateSaaS demonstration
Show a current product task in a separate screen-led video.
Use this templateFeatures
Keep the explanation grounded in the source
Review the labels, narration and concept relationships together.
Script preparation
Draft the explanation from the approved positioning and product facts.
Explore featureMotion graphics
Show how the product concepts relate through labeled diagrams.
Explore featureAI voiceover
Check product names and domain terms in the narration.
Explore featureCaptions and subtitles
Keep the explanation readable with sound muted.
Explore featureVideo editing
Revise a label, relationship or narration line after review.
Explore featureBrand Kit
Apply the product’s approved identity when the brief calls for it.
Explore featureSolutions
Create for the team explaining the product
Adapt the depth and vocabulary to the intended viewers.
SaaS companies
Explain the supported product structure to prospective users.
See the solutionProduct marketers
Keep the explanation aligned with the approved positioning.
See the solutionFounders
Introduce the product clearly to a new audience.
See the solutionSales teams
Give buyers a reusable explanation of the main capabilities.
See the solutionMarketing partners
Work from the client’s reviewed product brief.
See the solutionGrowth marketers
Prepare an audience-specific version of the product story.
See the solutionUse cases
Choose the product explanation needed
Keep one audience and conceptual task in focus.
Software product explainer
Explain the product’s purpose and main relationships.
Explore use caseSaaS explainer
Introduce the approved product facts to a prospective user.
Explore use caseProduct explanation
Connect the supported capabilities with the audience’s task.
Explore use caseStartup explanation
Introduce a new product with a clear source-backed story.
Explore use caseConcept explanation
Make an unfamiliar product idea easier to follow.
Explore use caseFounder explanation
Present the product direction in the founder’s approved language.
Explore use caseConverters
Bring the approved product source
Use the format that contains the current positioning and facts.
Positioning brief to video
Paste the audience, product facts and explanation direction.
Start convertingProduct document to video
Start from a reviewed positioning or messaging document.
Start convertingProduct documentation to video
Support the explanation with the current capability descriptions.
Start convertingProduct website to video
Use the product’s own published information as a source.
Start convertingSource page to video
Provide the exact pages supporting the brief.
Start convertingScript to video
Preserve the narration reviewed by the product team.
Start convertingTools
Prepare the next software explanation
Choose the tool that fits the source and audience.
SaaS video maker
Create the explanation from the current software brief.
Open toolExplainer video maker
Build a clear sequence around one product concept.
Open toolMarketing video maker
Adapt the approved message to the intended viewers.
Open toolVideo script generator
Draft the explanation without adding unsupported claims.
Open toolVideo editor
Refine a diagram or narration line after review.
Open toolAdd subtitles
Caption the approved product terms and explanation.
Open toolIntegrations
Create where the product brief is maintained
Choose a connection that fits the source and review process.
Claude
Review the positioning source and ngram plan in one conversation.
Explore integrationChatGPT
Use the approved product brief with the ngram connection.
Explore integrationMCP Server
Use ngram’s creation tools from another compatible assistant.
Explore integrationNotion
Start from product notes shared with the integration.
Explore integrationZapier
Map a reviewed product brief into a configured creation flow.
Explore integrationn8n
Connect the approved source with a configured video workflow.
Explore integrationRelated workflows
Continue with a more specific product communication
Choose another workflow when the audience or source changes.
Demonstrate a product task
Use genuine interface material to show the current workflow.
Explore workflowAnswer a product question
Create a two-speaker exchange from approved questions and answers.
Explore workflowExplain a release
Use the shipped-change brief for a focused product update.
Explore workflowTeach the first task
Create a source-backed introduction for a new customer.
Explore workflowIntroduce the product deck
Present the broader product overview from reviewed slides.
Explore workflowExplain a buyer comparison
Use supported comparison facts in a separate buyer explanation.
Explore workflow