Here's your marketing context document, built for your specific stage and motion. Keep this as a living file — update it quarterly or whenever your positioning or ICP shifts materially.

---

Marketing Context: [Company Name]

Last updated: [Date] | Stage: Post-Series A | ARR: $2.8M

---

Company Snapshot

Attribute	Detail
Stage	Post-Series A
ARR	$2.8M
Revenue motion	Transitioning founder-led → marketing-led
Primary market	Mid-market B2B, 50–500 employees
Category	Workflow automation
Target buyer	Operations teams

---

Ideal Customer Profile (ICP)

Primary Buyer: Operations Lead

• Title: VP of Operations, Head of Operations, Operations Manager, COO (at 50-150 employee companies)
• Pain: Spends 30–40% of time on manual coordination tasks across systems that don't talk to each other; team uses a patchwork of Zapier, spreadsheets, and Slack to hold processes together
• Motivation: Build scalable ops infrastructure without growing headcount
• Success metric: Hours saved per week; reduction in cross-team errors; faster process cycle times

Secondary Buyer: IT / Technical Approver

• Title: IT Manager, Head of Engineering (in ops-adjacent role), CTO (at smaller end of range)
• Role in deal: Security review, integration feasibility, vendor risk assessment
• Concern: Data residency, SSO/SCIM support, API reliability, vendor stability

End User: Operations Analyst / Coordinator

• Title: Operations Analyst, Revenue Ops Associate, Business Analyst
• Role in deal: Product champion; drives internal adoption post-sale
• Concern: Ease of building automations without engineering help; quality of templates and documentation

---

Positioning Statement

For mid-market operations teams that are outgrowing duct-tape automation, [Product] is a workflow automation platform that lets non-technical ops professionals build and maintain complex multi-system automations — without depending on engineering. Unlike Zapier (consumer-grade, brittle at scale) and Make (powerful but technical), [Product] is purpose-built for ops team ownership at the 50–500 employee stage.

---

Competitive Landscape

Competitor	Strength	Weakness	How We Win
Zapier	Brand, ecosystem, ease of use	Brittle at scale, expensive at volume, consumer positioning	Reliability and ops-team ownership narrative
Make (Integromat)	Powerful, visual builder, affordable	Steep learning curve, no ops-team positioning	Ease of use for non-technical ops buyers
n8n	Open source, developer-friendly, self-hosted option	Requires technical setup, no enterprise support	Time-to-value, support, ops buyer fit

Competitive displacement motion: Most deals are rip-and-replace Zapier at scale. The trigger is usually a Zapier bill that has grown past $1K/month or a reliability incident that broke a critical workflow.

---

Messaging Pillars

1. Built for ops teams, not developers Operations professionals can build and own automations without engineering tickets. Your IT team approves it; your ops team runs it.

2. Reliable at scale Handles the volume, complexity, and error recovery that consumer automation tools can't. Built for workflows you depend on daily — not experiments.

3. Time-to-value at your stage Pre-built templates for common mid-market ops workflows (employee onboarding, contract routing, CRM hygiene). First automation live in a day.

---

Current Growth Constraints

• No repeatable top-of-funnel yet — growth has been founder outreach and referrals; marketing-led motion is being built now
• Category education burden — buyers often don't know they need workflow automation; they describe the pain (manual work, errors) not the solution
• Sales cycle length — mid-market deals run 30–60 days; IT/security review adds 2–4 weeks; deal velocity needs qualification discipline
• ICP definition still being validated — data suggests ops teams at 100–300 employees are highest close rate; below 50 employees churns faster

---

Tone and Voice

• Direct and practical — ops buyers are results-oriented; skip the abstraction
• Credible, not hype-driven — this buyer has been burned by tools that over-promised; lead with proof
• Peer-to-peer — write as if an experienced ops professional is talking to another ops professional
• Avoid: "AI-powered," "revolutionary," "game-changing" — they trigger skepticism in this audience

---

Key Metrics (for marketing context)

Metric	Current	Target
ARR	$2.8M	—
Primary CAC channel	(to be established)	—
Average deal size	—	—
Sales cycle	30–60 days	—
Logo churn	—	—

Fill in actuals and update quarterly.

---

Use this document as the opening context for any marketing session — positioning, content, campaigns, messaging, or ICP analysis.

Here's your marketing context document built around your PLG motion and free-to-paid conversion dynamics.

---

Marketing Context: [Product Name]

Last updated: [Date] | Stage: Seed/Early Growth | ARR: $500K | MRR: ~$42K

---

Company Snapshot

Attribute	Detail
ARR	$500K (achieved in 18 months)
Free users	8,000
Paid accounts	340
Free-to-paid conversion	~4.25%
Growth model	Product-led growth (PLG)
Category	Developer tooling

---

Buyer Personas

The Developer Champion (Free User)

• Who: Individual developer or small team; self-discovered the tool; self-onboarded
• Motivation: Solves a specific technical pain; wants to avoid writing boilerplate; finds tool through GitHub, HN, Reddit, or a blog post
• Behavior in PLG: Uses the free tier; builds something real; may or may not share with team
• Conversion trigger: Hits a usage limit, needs collaboration features, or wants to share results with their manager

The Budget Owner (Team Lead / Engineering Manager)

• Who: Engineering manager, tech lead, or VP Engineering approving $50–500/month spend
• Motivation: Reduce developer time on the problem the tool solves; sees evidence of team already using it
• Behavior in PLG: Receives a Slack message from a developer: "I've been using this, we should pay for it"
• Conversion blocker: Needs to understand security posture, data handling, and whether tool is production-ready

Secondary: Platform / Infra Buyer (Enterprise)

• Exists at larger accounts; requires SSO, audit logs, SLA
• Not your primary segment yet — flag for later

---

Positioning Statement

For development teams who [core pain point], [Product] is a [category] that [key capability], so developers can [outcome] without [current painful workaround]. Unlike [Alt 1] and [Alt 2], [Product] is [key differentiator — e.g., open-source, no-config, built for CI/CD].

Fill in the bracketed sections with your specific product details — this structure fits your PLG model.

---

PLG Metrics and KPIs

Metric	Definition	Current
Free → Paid conversion	Paid accounts / free signups	~4.25%
Time to first value	Time from signup to first meaningful action	—
Activation rate	% of signups completing activation milestone	—
PQL conversion rate	% of PQLs converting to paid	—
Expansion MRR	MRR from upgrades / total MRR	—
Net Revenue Retention	—	—

Establish baseline values for all metrics within 60 days.

---

Activation Milestone (PQL Definition)

A Product Qualified Lead (PQL) for your product is a free user who has:

1. Completed [core activation action — e.g., connected first integration, run first pipeline, generated first output]
2. Used the product on [N] separate days within the first [X] days
3. Reached [usage threshold — e.g., 80% of free tier limit, or 3+ collaborators invited]

PQL → paid conversion is your single most important marketing metric. Increasing this from 4.25% to 6% has greater revenue impact than doubling free signup volume.

---

Free-to-Paid Conversion Motion

Activation-first approach

Marketing's job in PLG is not generating leads — it's improving the activation rate of the 8,000 free users you already have. Content, onboarding emails, and in-product nudges should all drive toward the activation milestone.

Conversion triggers

• Usage limit hit — most common; ensure the upgrade prompt gives clear value context
• Collaboration feature locked — effective if team use cases are strong
• Manager-directed upgrade — comes from developer champion → budget owner hand-off; needs social proof and security documentation

Expansion signals

Users who have hit the free tier limit and not upgraded within 7 days are at risk of churning or switching. Users who have added a second collaborator within 14 days are 3× more likely to convert. Track both.

---

Developer Marketing Channels

Channel	Role	Priority
GitHub (README, discussions, stars)	Discovery and credibility signal	High
Hacker News (Show HN, Ask HN)	Early adopter acquisition	High
Developer-focused newsletters (TLDR, Bytes)	Paid reach at scale	Medium
Twitter/X — developer audience	Founder/brand voice, organic reach	Medium
Reddit (r/programming, r/devops, subreddit specific to your category)	Community discovery	Medium
Technical blog / SEO	Compounding organic traffic	High (long-term)
Community (Discord, Slack)	Retention and word-of-mouth	High

Developer marketing is content-first. Tutorials, benchmarks, and opinionated takes outperform feature announcements.

---

Community-Led Growth Levers

• Discord/Slack community: Already exists or should — developers help each other, reducing support burden and increasing stickiness
• Open-source component: If any part of the product is open-source, GitHub stars are a credibility signal for the budget owner conversation
• User-generated content: Encourage power users to write tutorials; amplify them
• Changelog communication: Developers follow changelogs — ship publicly and communicate clearly

---

Tone and Voice

• Direct and technical — developers see through marketing language; write as a practitioner, not a marketer
• Show don't tell — code examples, demos, benchmarks beat feature lists
• Honest about tradeoffs — acknowledging what the tool is not builds trust with a skeptical audience
• Avoid: "AI-powered" (overloaded), "best-in-class," vague ROI claims without data

---

Load this context at the start of any marketing session — content strategy, paid campaigns, onboarding email sequences, or PQL analysis.