Quick Answer
Create a project with your product context, upload competitive intel and customer research, define AI roles for positioning/messaging/enablement, and generate launch-ready materials.
Create Your Product Marketing Project
Strong project description:
Target segment: Operations teams at mid-market companies (200-2000 employees) currently using manual processes or basic automation (Zapier level).
Product capabilities:
• Visual workflow builder (no code)
• 150+ pre-built templates
• Conditional logic and branching
• Integration with 50+ tools
• Audit trail and compliance logging
Competitive landscape:
• Monday.com (has automations, limited complexity)
• Asana (basic rules, not true workflows)
• Process Street (workflow-focused but standalone)
• Zapier/Make (powerful but separate tool, technical)
Key differentiator: Only solution that combines project management context WITH workflow automation in one place. No switching tools. No broken context.
Buyer personas:
• Primary: Operations Manager (evaluator and champion)
• Secondary: IT Director (security and integration approver)
• Economic: VP Operations or COO (budget holder)
Sales cycle: 45-60 days average, involves demo and trial
Messaging constraints: Don't bash competitors by name. Don't promise “no code” if edge cases need developer. Focus on time savings, not “AI” buzzwords.
Generate Project Instructions
OBJECTIVE:
Create positioning, messaging, and sales enablement materials that differentiate our product and arm sales with winning arguments.
BEFORE CREATING ANY DELIVERABLE:
1. Search project knowledge for product capabilities and limitations
2. Search project knowledge for competitive positioning
3. Search project knowledge for buyer persona details
4. Search project knowledge for approved proof points and case studies
5. Search project knowledge for messaging constraints
ANALYSIS FRAMEWORK:
1. Positioning Foundation
– What category do we compete in?
– Who is the target buyer (specific, not general)?
– What's the key differentiation (one thing)?
– What proof supports the claim?
2. Competitive Context
– How do competitors position this capability?
– What do they say about us?
– Where do we win? Where do we lose?
– What FUD do we need to counter?
3. Buyer Journey Alignment
– What triggers evaluation?
– What questions arise at each stage?
– What objections must we overcome?
– What proof points matter when?
DELIVERABLE TYPES:
Positioning Doc:
– For/Who/That/Unlike/Because framework
– Value pillars with proof points
– One-liner, elevator pitch, boilerplate
Messaging Framework:
– Headlines by audience
– Key messages (3-5)
– Proof points per message
– Objection handling
Battle Cards:
– Competitor overview (positioning, pricing)
– Where we win (talk tracks)
– Where we lose (honest assessment + pivot)
– Landmines (what they'll say about us)
– Knockout questions (questions that favor us)
Launch Materials:
– Announcement copy (blog, email, social)
– Demo script outline
– One-pager / sales sheet content
– Customer-facing FAQ
ALWAYS:
– Tie features to customer outcomes
– Include objection handling for every claim
– Provide talk tracks, not just bullet points
– Acknowledge limitations honestly (builds trust)
– Create versions for different personas
NEVER:
– Use internal jargon customers don't use
– Make claims without proof points
– Ignore competitor strengths
– Create materials sales won't actually use
– Assume one message works for all personas
OUTPUT FORMAT:
[Varies by deliverable type – always include:
– Who it's for
– How to use it
– What success looks like]
Define AI Roles
Upload Reference Documents
Product Context
- Product requirements doc / feature specifications
- Product limitations and known gaps (internal honest doc)
- Demo script or product tour flow
- Customer success stories / case studies
Competitive Intelligence
- Competitor feature comparison (your internal assessment)
- Competitor pricing (current)
- Competitor positioning (their words from their site)
- Win/loss analysis summary
- G2/Capterra comparison data
Customer Research
- Buyer persona documents
- Customer interview summaries
- Sales call recordings/transcripts (key quotes)
- Support ticket themes (objections and confusion)
Existing Materials
- Current positioning doc (to improve upon)
- Sales deck
- Website messaging
- Previous launch materials
Constraints
- Brand guidelines
- Legal/compliance review notes
- Messaging dos and don'ts
Generate Product Marketing Deliverables
Session 1: Positioning Foundation
Use the For/Who/That/Unlike/Because structure:
– FOR: [Target segment]
– WHO: [Key need or trigger]
– THAT: [Primary benefit]
– UNLIKE: [Alternative approaches]
– BECAUSE: [Key differentiator + proof]
Also provide:
– One-liner (under 10 words)
– Elevator pitch (30 seconds)
– Three value pillars with proof points
Session 2: Battle Card Creation
Include:
1. Competitor overview (their positioning, not our spin)
2. Head-to-head comparison (honest)
3. Where we win – with talk track
4. Where we lose – with pivot strategy
5. Landmines – what they'll say about us and response
6. Knockout questions – questions that favor us
7. Proof points to use in this comparison
Session 3: Launch Package
1. Blog post announcement (800 words)
2. Email to existing customers (200 words)
3. LinkedIn post (company page)
4. Sales notification with talk track
5. Customer-facing FAQ (top 10 questions)
6. One-pager content (not design, just copy)
Ensure consistent messaging across all touchpoints.
Knowledge Graph Compounds
Week 1
Generates materials based on uploaded context
Month 1
Knows your positioning pillars, remembers which competitive angles work, understands your sales team's language
Month 3
Maintains messaging consistency across multiple launches, connects new features to established positioning, anticipates objections based on past materials