Skip to content
pm-skills

Storevine: Follow the Product

Series A, ~70 employees, ~15,000 merchants. Building Campaigns: native email marketing.

Prompt style: Organized: structured context, references prior work, clear scope boundaries.

Phase: Foundation

Section titled “Phase: Foundation”

Build Risk Review

Section titled “Build Risk Review”

Storevine B2B ecommerce catalog platform - whether to build a native bulk price-update tool requested by mid-market merchants

Full output: Build Risk Review

Build Risk Review: native bulk price-update tool

Section titled “Build Risk Review: native bulk price-update tool”

Mode: Feature-change | Date: 2026-06-22

Lean Canvas

Section titled “Lean Canvas”

Storevine Campaigns lean canvas for framing the built-in email / SMS re-engagement feature as an embedded alternative to Klaviyo for SMB merchants

Full output: Lean Canvas

Lean Canvas: Storevine Campaigns

Section titled “Lean Canvas: Storevine Campaigns”

Created: 2026-04-15 Author: Storevine Campaigns PM Mode: content Overall confidence: Medium Purpose: New feature thesis. Pre-PRD strategic review for leadership.

Meeting Agenda

Section titled “Meeting Agenda”

campaigns-kickoff

Full output: Meeting Agenda 
---
artifact_type: meeting-agenda
version: 1.0
generated_at: 2026-04-17T13:00:00Z
generated_by_skill: foundation-meeting-agenda


meeting_title: "Campaigns Feature Launch Kickoff"
meeting_date: 2026-04-17
meeting_start_time: "14:00 EST"
meeting_type: project-kickoff
meeting_duration_minutes: 60


project: campaigns
topics:
  - scope
  - capacity
  - launch-target


attendees:
  - name: jonathan
    role: decision-maker
  - name: maria
    role: contributor
  - name: alex
    role: contributor
  - name: sam
    role: contributor


desired_outcomes:
  - "Scope committed: feature set in/out for v1 launch"
  - "Engineering capacity confirmed for Q2 (sprint-weeks committed)"
  - "Launch-target date set with explicit dependencies"


related_brief: null
input_quality: high
confidence: high
visibility: team
status: draft
---


# Campaigns Feature Launch Kickoff


</details>


---


### Meeting Brief


*campaigns-exec-briefing*


:::note[Prompt]

foundation-meeting-brief “Tomorrow 9am exec briefing, 30 min with priya-ceo and rachel-vp. Campaigns Q2 commitment. Priya pushed back on capacity in Q1 exec review (I have the recap). Rachel privately supports.”

:::


<details>
<summary>Full output: Meeting Brief</summary>


```markdown
---
artifact_type: meeting-brief
version: 1.0
generated_at: 2026-04-16T17:00:00Z
generated_by_skill: foundation-meeting-brief


meeting_title: "Campaigns Q2 Exec Briefing"
meeting_date: 2026-04-17
meeting_start_time: "09:00 EST"
meeting_type: exec-briefing


project: campaigns
topics:
  - q2-commitment
  - capacity-context


attendees:
  - name: jonathan-pm
    role: contributor
  - name: priya-ceo
    role: decision-maker
  - name: rachel-vp
    role: contributor


stakeholders:
  - name: priya-ceo
    position: "cost-sensitive; pushed back on Q1 capacity; wants to hold line on Q2"
  - name: rachel-vp
    position: "private supporter; wants Campaigns in Q2; will back scope discipline"


primary_ask: "CEO greenlight for Campaigns Q2 launch with explicit capacity discipline mechanism"


related_agenda: null


input_quality: high
confidence: medium
visibility: private
status: draft
---


# Meeting brief: Campaigns Q2 Exec Briefing


</details>


---


### Meeting Recap


*campaigns-pricing-decision*


:::note[Prompt]

foundation-meeting-recap @campaigns-pricing-decision-transcript.txt @jonathan-live-notes.md

:::


<details>
<summary>Full output: Meeting Recap</summary>


```markdown
---
artifact_type: meeting-recap
version: 1.0
generated_at: 2026-04-24T19:30:00Z
generated_by_skill: foundation-meeting-recap


meeting_title: "Campaigns Pricing Decision"
meeting_date: 2026-04-24
meeting_start_time: "13:00 EST"
meeting_type: decision-making


project: campaigns
topics:
  - tier-structure
  - grandfathering
  - rollout-date


attendees:
  - name: jonathan-pm
    role: decision-maker
  - name: maria-eng
    role: contributor
  - name: alex-marketing
    role: contributor
  - name: sam-data
    role: contributor
attendees_absent: []


related_agenda: 2026-04-24_13-00EST_campaigns-pricing-decision_agenda.md
related_brief: null


agenda_reconciliation:
  topics_planned: [tier-structure, grandfathering, rollout-date]
  topics_hit: [tier-structure, grandfathering, rollout-date]
  topics_skipped: []
  topics_emerged: [comms-plan-ownership]


meeting_quality:
  outcomes_achieved: "3/3"
  started_on_time: true
  ended_on_time: false
  key_attendees_present: true


meeting_type_source: explicit
unassigned_action_ratio: 0.0


input_quality: high
confidence: high
visibility: team
status: draft
---


# Meeting recap: Campaigns Pricing Decision


</details>


---


### Meeting Synthesize


*q1-campaigns-retro*


:::note[Prompt]

foundation-meeting-synthesize —format=retro-input —quarter=2026-Q1 @recap*.md

:::


<details>
<summary>Full output: Meeting Synthesize</summary>


```markdown
---
artifact_type: meeting-synthesis
version: 1.0
generated_at: 2026-04-01T10:00:00Z
generated_by_skill: foundation-meeting-synthesize


project: campaigns
topics:
  - research
  - scoping
  - capacity


time_range:
  start: 2026-01-01
  end: 2026-03-31


scope_filter: "project=campaigns, format=retro-input"


source_meetings:
  - 2026-01-14_14-00EST_campaigns-research-kickoff_recap.md
  - 2026-02-04_14-00EST_campaigns-user-interview-debrief_recap.md
  - 2026-02-25_14-00EST_campaigns-scope-workshop_recap.md
  - 2026-03-11_14-00EST_campaigns-capacity-review_recap.md
  - 2026-03-25_14-00EST_campaigns-q1-close-out_recap.md


input_quality: high
confidence: high
visibility: team
status: draft
---


# Meeting synthesis: Q1 Campaigns Retrospective Input


</details>


---


### OKR Writer


*Storevine B2B ecommerce platform. Campaigns team Q3 2026 OKR set following the May 2026 Campaigns GA and the validated guided first-campaign flow.*


:::note[Prompt]

foundation-okr-writer

Scope: Campaigns team, Storevine Cycle: Q3 2026 (July 1 to September 30) Level: team OKR type: aspirational

Strategic context:

  • Company objective: reduce 12-month merchant churn from 18% to 14% [fictional] by year-end 2026.
  • Campaigns team owns email marketing for Storevine merchants.
  • Guided first-campaign flow shipped May 2026; validated June 27 with strong results.

Empowerment signal: empowered team. Leadership picks problems, team picks bets and KRs.

Draft objective: “Make Campaigns the email tool merchants use weekly.”

Candidate KRs (rough):

  • More merchants sending recurring campaigns
  • Higher campaign engagement (CTR or conversion)
  • Don’t break merchant satisfaction

Constraints:

  • Engineering capacity: 4 engineers, 1 designer
  • No new platform dependencies
  • Cannot influence pricing or top-of-funnel acquisition (other teams)

Source of truth: company OKR doc in Confluence at go/okrs-q3-2026-campaigns

---
:::


<details>
<summary>Full output: OKR Writer</summary>


```markdown
# OKR Set: Storevine Campaigns Team, Q3 2026


</details>


---


### Persona (Marketing Brief)


*Storevine Campaigns marketing persona for self-serve SMB merchant acquisition and competitive positioning against Shopify plus Klaviyo*


:::note[Prompt]
```text
foundation-persona marketing brief


Quick marketing persona for Storevine Campaigns SMB acquisition.


Context:
- We're targeting Shopify + Klaviyo merchants who might consolidate
- Win-loss: 6/14 wins cited "too many tools"; 4/9 losses said "Klaviyo is good enough" [fictional]
- Need this for competitive landing page and acquisition email sequence
- Self-serve purchase, no committee, individual merchant decision


Prior work:
- Competitive analysis (Feb 2026): Shopify Email is template-first, Klaviyo is automation-first
- Interview synthesis: merchants describe "tool juggling tax" as real operational cost


Keep it brief, focused on acquisition messaging and objection handling.

:::

Full output: Persona (Marketing Brief)

Persona Dossier: Priya Sharma, The Merchant Who Pays the Tool-Juggling Tax (Marketing, Brief)

Section titled “Persona Dossier: Priya Sharma, The Merchant Who Pays the Tool-Juggling Tax (Marketing, Brief)”

Persona (Marketing Detailed)

Section titled “Persona (Marketing Detailed)”

Storevine Campaigns committee-buying marketing persona for launch and enablement planning

Full output: Persona (Marketing Detailed)

Persona Dossier: Daniel Ng, The Internal Dealmaker (Marketing)

Section titled “Persona Dossier: Daniel Ng, The Internal Dealmaker (Marketing)”

Persona (Product Brief)

Section titled “Persona (Product Brief)”

Storevine Campaigns product persona for guided first-send onboarding and merchant activation

Full output: Persona (Product Brief)

Persona Dossier: Luisa Moreno, The One-Woman Marketing Department (Product, Brief)

Section titled “Persona Dossier: Luisa Moreno, The One-Woman Marketing Department (Product, Brief)”

Persona (Product Detailed)

Section titled “Persona (Product Detailed)”

Storevine Campaigns product persona for multi-location merchant campaign management and audience segmentation

Full output: Persona (Product Detailed)

Persona Dossier: Carlos Medina, The Multi-Store Operator Who Runs Marketing from a Spreadsheet (Product)

Section titled “Persona Dossier: Carlos Medina, The Multi-Store Operator Who Runs Marketing from a Spreadsheet (Product)”

Prioritized Action Plan

Section titled “Prioritized Action Plan”

Storevine B2B ecommerce platform. Campaigns GA’d May 2026; the first-campaign rate is healthy but the second-campaign rate is stalling, and the growth PM needs a ranked next-action plan before spending the quarter’s eng capacity.

Full output: Prioritized Action Plan

Step 0: Source ledger

Section titled “Step 0: Source ledger”
S1: "the second-campaign rate is stalling at 22.8% [fictional] and flattening" (origin: pasted prompt, Situation)
S2: "Merchants send one campaign, see modest results, and don't return" (origin: pasted prompt, Situation)
S3: "Support sees ~6 tickets/week asking "why did my campaign underperform" with no clear next step in-product" (origin: pasted prompt, Situation)
S4: "Sales flags two mid-market deals where the buyer asked about "campaign automation / sequences" which we don't have" (origin: pasted prompt, Situation)
S5: "Eng has ~4 weeks of Campaigns capacity this quarter" (origin: pasted prompt, Situation)
S6: "cut 12-month merchant churn 18% to 14% [fictional]" (origin: pasted prompt, OKR)
S7: "First-campaign rate is healthy (31.7% [fictional] after the guided-flow A/B)" (origin: pasted prompt, Situation)

Section 0. Executive summary

Section titled “Section 0. Executive summary”
  • Situation classification: Complicated (Cynefin). The stall is diagnosable from data and support signal, not emergent.
  • The binding constraint: the missing post-first-campaign path. After the first send, the product offers no clear next step (S3) and no automation (S4), so repeat usage decays (S2).
  • The critical next effort (P1): diagnose where and why second campaigns stall before building anything, so the 4-week window funds the right fix.
  • Overall plan confidence: Medium-High. Well-sourced; residual risk is that diagnosis splits between a guidance gap and a results-quality problem.
  • Time-to-value: about one week to a diagnosis that points the build.

Section 1. Input mirror - what I understand

Section titled “Section 1. Input mirror - what I understand”
  • What you gave me: Campaigns activates merchants well on the first send (S7) but does not retain them into a second (S1, S2); support sees confusion with no in-product next step (S3); sales hears demand for automation/sequences (S4); you have a 4-week eng window (S5) and a churn OKR that Campaigns engagement feeds (S6).
  • What you appear to be trying to accomplish: turn Campaigns from a one-time action into a sustained channel that moves the churn metric. Confidence: High (intent is explicit).
  • Adjacent intents I noticed but did not assume: building automation/sequences (S4), and improving campaign results quality. Neither is assumed to be the answer yet.

Section 2. Situation classification (Cynefin)

Section titled “Section 2. Situation classification (Cynefin)”

Domain: Complicated. Source: S1, S2, S3.

Cause and effect are knowable with analysis. You already have the shape of the problem (a sharp first-to-second-send drop, S1) and converging signal about why (no in-product next step, S3). This is not Complex: the outcome is not unpredictable, it is a diagnosable funnel with a likely mechanism. Posture: analyze the drop-off, then commit. Confidence ceiling: Medium-High.

Section 3. The binding constraint (Theory of Constraints)

Section titled “Section 3. The binding constraint (Theory of Constraints)”
  • System and goal: make Campaigns a repeated behavior so it moves merchant retention.
  • The constraint: the post-first-campaign path. Nothing in the product tells a merchant what to do after their first send (S3), and there is no automation to carry them forward (S4), so they send once and stop (S2).
  • Source: S2, S3, S4.
  • Candidate constraints considered: (1) Results quality (“modest results”, S2). Real, but subordinate: even strong results decay without a next step. (2) The automation feature gap (S4). That is a candidate solution, not the constraint, until the diagnosis confirms automation is what lifts repeat sends.
  • Why P1 lifts it: diagnosing exactly where the second send is lost converts a guess into a targeted fix for the binding path.

Section 4. Prioritized questions, gaps, and open decisions

Section titled “Section 4. Prioritized questions, gaps, and open decisions”
RankQuestion / gapWhy it mattersDecision required?How to resolve
Q1Where exactly do merchants drop between send 1 and send 2? (S1)Determines whether the fix is guidance, results, or automationYes, blocks P1Funnel analysis of first-send merchants
Q2Do the “underperform” tickets share a root cause? (S3)Tells us if a results problem masquerades as a guidance gapNo, resolve by P1Tag and cluster the ~6/week tickets
Q3Is automation/sequences what merchants want, or a sales artifact? (S4)Avoids building a heavy feature on two dealsNoCheck demand against the broader merchant base in P1
Q4What second-send rate moves the churn OKR? (S6)Sets the success bar for the quarterYesPM and growth agree a target

Section 5. The prioritized action plan

Section titled “Section 5. The prioritized action plan”

P1. Diagnose the second-send drop-off

Section titled “P1. Diagnose the second-send drop-off”
  • Why: lifts the binding constraint by locating exactly where merchants stop (S1, S2). The 4-week window (S5) must not be spent guessing.
  • What: a one-page diagnosis of the first-to-second-send funnel with the dominant drop point and reason.
  • How: (1) Build the funnel from first send to second send. (2) Tag and cluster the support tickets (S3). (3) Cross-check automation demand (S4) against the full base.
  • Confidence: Medium-High. Respects the Complicated ceiling.
  • Source: S1, S2, S3.
  • Expected outcome / success signal: a named drop point and reason that picks the P2 fix.
  • Estimated effort: about 1 week.
  • Dependencies: none.

P2. Close the post-send “what now” gap

Section titled “P2. Close the post-send “what now” gap”
  • Why: the most likely diagnosis is the missing in-product next step (S3); a lightweight guidance fix is far cheaper than automation and tests the constraint directly.
  • What: an in-product post-send state that shows results plainly and offers the obvious next action.
  • How: (1) Add a post-send results-and-next-step view. (2) Prompt a relevant second campaign. (3) Measure the second-send rate against baseline (S1).
  • Confidence: Medium. Depends on P1.
  • Source: S3, S2.
  • Expected outcome / success signal: second-send rate climbs off 22.8% [fictional].
  • Estimated effort: about 2 weeks of the window (S5).
  • Dependencies: P1.

P3. Scope automation/sequences only if P1 supports it

Section titled “P3. Scope automation/sequences only if P1 supports it”
  • Why: automation (S4) is the heaviest option and is currently evidenced by two deals; build it only if P1 shows repeat sending is genuinely demand-limited, not guidance-limited.
  • What: a scoped decision on whether a basic sequence ships this quarter or is deferred.
  • How: (1) Weigh P1 demand evidence. (2) If justified, scope the smallest useful sequence. (3) Otherwise defer and revisit next quarter.
  • Confidence: Low-Medium. Contingent on P1.
  • Source: S4, S5.
  • Expected outcome / success signal: a defensible build-or-defer call that fits the 4-week window.
  • Estimated effort: the remaining window if built; near-zero if deferred.
  • Dependencies: P1, P2.

Sequencing (Now / Next / Later)

NowNextLater
P1P2P3 (conditional)

What to defer / what NOT to do

  • Do not build automation/sequences (S4) before P1; two deals are not a mandate.
  • Do not spend the 4-week window (S5) until the drop point is named.
  • Do not treat “modest results” as the cause without ticket evidence.

Section 6. Risks and pre-mortem

Section titled “Section 6. Risks and pre-mortem”
RiskLikelihoodImpactEarly signalMitigationSource
The real issue is results quality, not guidanceMHP1 tickets cluster on deliverability/targetingPivot P2 toward results, not a next-step nudgeS2, S3
Automation gets prioritized on sales pressureMHRoadmap fills with sequences before P1 readsGate P3 on P1 demand evidenceS4
4-week window slips on a guidance-then-automation pivotLMP2 scope creeps toward sequencesHold P2 to the lightweight next-step fixS5
Section titled “Section 7. Recommended pm-skill prompts (copy/paste ready)”

To execute P1: diagnose the drop-off

Section titled “To execute P1: diagnose the drop-off”

Skill: measure-experiment-results Why this skill: P1 is a funnel diagnosis that benefits from a disciplined readout of where and why the second send is lost. Source: S1, S2

Prompt:

Analyze the Storevine Campaigns first-to-second-send funnel. First-send rate is 31.7% [fictional]; second-send rate is stalling at 22.8% [fictional] and flattening. Merchants send once, see modest results, and do not return; support sees ~6 tickets/week asking why a campaign underperformed with no clear in-product next step. Identify the dominant drop point between send 1 and send 2 and the most likely cause, separating a guidance gap from a results-quality problem, and flag where evidence is thin.

To execute P2: spec the post-send fix

Section titled “To execute P2: spec the post-send fix”

Skill: deliver-prd Why this skill: once P1 names the drop point, P2 needs an eng-ready spec scoped to the 4-week window. Source: S3, S5

Prompt:

Write a PRD for an in-product post-campaign state in Storevine Campaigns that shows results plainly and offers the obvious next action to drive a second send. Scope to roughly two weeks of eng capacity, exclude automation/sequences, and tie success to lifting the second-send rate off 22.8% [fictional]. Assume the drop-point diagnosis from discovery is settled.

Section 8. Evidence and source map

Section titled “Section 8. Evidence and source map”
Claim / recommendationSource IDExact quote
Second send is stallingS1”the second-campaign rate is stalling at 22.8% [fictional] and flattening”
Merchants send once and stopS2”Merchants send one campaign, see modest results, and don’t return”
No in-product next stepS3”Support sees ~6 tickets/week asking “why did my campaign underperform” with no clear next step in-product”
Automation demand (thin)S4”Sales flags two mid-market deals where the buyer asked about “campaign automation / sequences” which we don’t have”
Build windowS5”Eng has ~4 weeks of Campaigns capacity this quarter”
Strategic tie to churnS6”cut 12-month merchant churn 18% to 14% [fictional]”

Inferred (Low confidence) claims: none load-bearing; every effort cites a quote. Evidence gaps: no agreed second-send target (Q4) and no validated read on whether automation demand generalizes beyond two deals; both are flagged, not assumed.

Stakeholder Briefings

Section titled “Stakeholder Briefings”

Storevine B2B ecommerce platform - 8-merchant interview synthesis fanned out to four lenses, driving the template-first scope decision

Full output: Stakeholder Briefings 
# Stakeholder briefings: Campaigns merchant interview synthesis


</details>


---


### Stakeholder Briefings


*Storevine B2B ecommerce platform - templates-vs-blank-canvas first-send A/B result fanned out to four stakeholder lenses for the ship decision*


:::note[Prompt]

/foundation-stakeholder-briefings @campaigns-templates-ab-results.md

Source: Campaigns first-send A/B results. Treatment = pre-built templates, control = blank canvas. Primary metric = first-send rate. Treatment +22% relative on first send vs control; significant. Decision on the table: ship templates as the default first-send experience. Tie-in: this is the activation lever behind the 12% -> 30% first-send target.

Audiences: take the experiment proposal (Data/BI, Executive, PMM, Engineering).

:::


<details>
<summary>Full output: Stakeholder Briefings</summary>


```markdown
# Stakeholder briefings: Campaigns templates A/B result


</details>


---


### Stakeholder Briefings


*Storevine B2B ecommerce platform - Campaigns GA launch checklist fanned out to GTM audiences, demonstrating Custom-lens inference for agency partners*


:::note[Prompt]

/foundation-stakeholder-briefings @campaigns-launch-checklist.md

Source: Campaigns GA launch checklist. GA 2026-07-20. Built-in email/SMS re-engagement, replaces external tools (Klaviyo/Mailchimp) for the ~68% of merchants on an outside tool. v1 template-only. SendGrid dedicated-IP warm-up complete. CAN-SPAM/GDPR signed off. Activation lever: guided template flow (first-send target 12% -> 30%). Paid tier above the free send cap.

Audiences: GTM proposal, plus a custom audience: agency partners (the studios that build and run Storevine stores for merchant clients).

> The skill confirmed the inferred Custom lens before generating: **Agency partners** - decision owned: which client stores to roll Campaigns onto and how to bill the service; cares about client retainer/upsell impact, migration effort off external tools, white-label/multi-store fit; jargon posture: plain partner-business language; length/tone: practical, margin-aware. The PM confirmed `go`.
:::


<details>
<summary>Full output: Stakeholder Briefings</summary>


```markdown
# Stakeholder briefings: Campaigns GA launch


</details>


---


### Stakeholder Briefings


*Storevine B2B ecommerce platform - Campaigns CAN-SPAM PRD projected to five stakeholder lenses ahead of the GA go/no-go review*


:::note[Prompt]

/foundation-stakeholder-briefings @campaigns-prd.md

Source: Campaigns CAN-SPAM PRD (locked, v1.0). Built-in email/SMS re-engagement competing with Klaviyo/Mailchimp. v1 is template-only (no drag-and-drop). Sending on a SendGrid dedicated IP with domain warm-up. CAN-SPAM one-click unsubscribe + GDPR consent in scope. Target: the ~68% of merchants on external email tools today. Activation target: first-send rate 12% -> 30%.

Audiences: take the spec proposal, and add Legal for the CAN-SPAM/GDPR surface. GA go/no-go is at the 2026-07-15 review; beta 2026-06-30, GA target 2026-07-20.

:::


<details>
<summary>Full output: Stakeholder Briefings</summary>


```markdown
# Stakeholder briefings: Campaigns CAN-SPAM PRD (built-in email/SMS)


</details>


---


### Stakeholder Briefings


*Storevine B2B ecommerce platform - Sprint 12 deliverability retro fanned out to three lenses, splitting engineering fixes from support enablement and the exec confidence read*


:::note[Prompt]

/foundation-stakeholder-briefings @campaigns-sprint12-retro.md

Source: Sprint 12 deliverability retrospective. What happened: a batch of merchant sends on the new SendGrid dedicated IP hit spam folders because send volume ran ahead of the warm-up ramp. Inbox-placement dipped before recovering once volume was throttled back to the warmed ceiling. No data loss, no compliance issue. Fixes agreed: enforce a warm-up-aware send-rate cap, add an inbox-placement alert, write a deliverability runbook for support.

Audiences: incident proposal but drop Legal (no regulatory surface) - keep Engineering, CS/Support, Executive.

:::


<details>
<summary>Full output: Stakeholder Briefings</summary>


```markdown
# Stakeholder briefings: Sprint 12 deliverability retro


</details>


---


### Stakeholder Briefings


*Storevine B2B ecommerce platform - Campaigns lean canvas + Q3 OKRs fanned out to strategy audiences, contrasting internal Exec reprioritization with the Board capital narrative*


:::note[Prompt]

/foundation-stakeholder-briefings @campaigns-lean-canvas.md @campaigns-q3-okrs.md

Source: Campaigns lean canvas (embedded re-engagement thesis: capture the ~68% of merchants paying for an external email tool, retention + a new paid send tier) plus the Q3 OKR set. Q3 OKRs: weekly active senders, 90-day retention lift, first-send rate 12% -> 30%, CTR guardrail. Strategic context: persevere decision on Campaigns showed +18% retention for merchants who adopt it.

Audiences: take the strategy proposal (Executive, Board, PMM, Sales). Make the Exec briefing about internal funding/reprioritization and the Board briefing about the company strategy and capital story - they should not read alike.

:::


<details>
<summary>Full output: Stakeholder Briefings</summary>


```markdown
# Stakeholder briefings: Campaigns strategy + Q3 OKRs


</details>


---


### Stakeholder Update


*campaigns-slack-support*


:::note[Prompt]

/meeting-update @2026-04-24_13-00EST_campaigns-pricing-decision_recap.md —channel=slack —audience=customer-facing —cta=“update support playbook with new pricing + grandfathering flow by 2026-05-15”

:::


<details>
<summary>Full output: Stakeholder Update</summary>


```markdown
---
artifact_type: stakeholder-update
version: 1.0
generated_at: 2026-04-25T09:00:00Z
generated_by_skill: foundation-stakeholder-update


meeting_title: "Campaigns Pricing Decision"
meeting_date: 2026-04-24


project: campaigns
topics:
  - pricing-decision


channel: slack
audience_variant: customer-facing
primary_cta: "update support playbook with new pricing + grandfathering flow by 2026-05-15"


thread_continuation_of: null


related_recap: 2026-04-24_13-00EST_campaigns-pricing-decision_recap.md


input_quality: high
confidence: high
visibility: team
status: draft
---


# Stakeholder update: Campaigns Pricing Committed


</details>


---


## Phase: Discover


### Competitive Analysis


*Storevine B2B ecommerce platform . email marketing competitive landscape for Campaigns*


:::note[Prompt]

discover-competitive-analysis

Scope: Email marketing tools available to ecommerce merchants . built-in vs. third-party positioning. Informing Campaigns v1 scope and feature prioritization.

Our product: Storevine . B2B all-in-one ecommerce + web platform, Series A, ~18k active merchants [fictional]. Building Campaigns: native email marketing with audience segmentation and automations.

Competitors: Shopify Email (built-in), Klaviyo (third-party, most-used by merchants), Mailchimp (third-party, SMB standard), Campaign Monitor (third-party, mid-market)

Segment: Small-to-mid-size ecommerce merchants (Storevine core segment). Buyer: merchant owner/operator.

Feature matrix dimensions needed:

  • Drag-and-drop email editor
  • Pre-built templates
  • Audience segmentation (purchase-based)
  • Abandoned cart automation
  • Welcome series automation
  • Analytics (open rate, click rate, revenue attribution)
  • List import (CSV)
  • CAN-SPAM/GDPR compliance tools
  • SMS campaigns

Also need: pricing comparison, positioning map (Platform Integration vs. Feature Depth), deep dives per competitor, gaps and opportunities, and strategic recommendations.

Audience: Growth PM, Eng Lead, Head of Product. References: problem-statement (Q4 discovery), exit survey analysis.

---
:::


<details>
<summary>Full output: Competitive Analysis</summary>


# Competitive Analysis: Email Marketing for Ecommerce Merchants


</details>


---


### Interview Synthesis


*Storevine B2B ecommerce platform . merchant email marketing interviews for Campaigns discovery*


:::note[Prompt]

discover-interview-synthesis

Research topic: Why do Storevine merchants use external email tools instead of Storevine’s built-in email features?

Context: Storevine all-in-one ecommerce + web platform, ~18k active merchants [fictional]. Q4 exit survey: 22% of churned accounts cited “had to use a separate email tool” [fictional]. Competitive analysis filed last week.

We interviewed 8 merchants. Mix of sizes, product categories, and email tool usage. Interview format: 45-min video call, semi-structured.

Key topics: current email tool setup, how they chose it, what they use Storevine’s built-in tools for (if anything), what would need to be true to switch, seasonal patterns.

Date range: Jan 12 - Jan 28, 2026 Interviewer: UX researcher + growth PM

---
:::


<details>
<summary>Full output: Interview Synthesis</summary>


# Interview Synthesis: Why Merchants Use External Email Tools


</details>


---


### Journey Map


*Storevine B2B inventory-forecasting platform - mid-market e-commerce buying group from vendor research to annual renewal*


:::note[Prompt]

discover-journey-map

map the full procure-to-renew journey for storevine (B2B AI inventory forecasting, sold to mid-market e-commerce, 200-2000 employees).

it’s a buying group, not one buyer:

  • Ops manager = champion, lives in the forecasting pain daily
  • Finance = approves the budget, cares about ROI and contract terms
  • IT = owns the data integration and security review, can veto

stages: discovers -> evaluates (RFP + demo) -> pilots -> decides (contract) -> onboards (data integration) -> uses (monthly forecast cycle, recurring) -> renews (annual review, recurring).

the scary transition is pilot -> onboarding: the pilot uses clean sample data and looks great, then real data integration is messy and the accuracy people were promised wobbles. that’s where trust is won or lost.

multi-actor, so use parallel tables per actor. the usage + renewal stages are cyclical.

---
:::


<details>
<summary>Full output: Journey Map</summary>


# Customer Journey Map: Storevine Procure-to-Renew - Multi-Actor Buying Group


> Multi-actor journey. Primary actor: Ops manager (well-researched). Secondary actors: Finance and IT (lighter signal, more Hypothesis entries). Validate the secondary tracks before acting on them.


</details>


---


### Market Sizing


*Storevine B2B platform - sizing the market for AI inventory forecasting for mid-market e-commerce*


:::note[Prompt]

discover-market-sizing

size the market for storevine’s AI inventory forecasting. B2B SaaS, sold to mid-market e-commerce companies (200-2000 employees). ACV around $40k.

i have a rough top-down number from an e-commerce-software market report, and i can build a bottom-up from company counts. i suspect they won’t match - walk me through reconciling them.

---
:::


<details>
<summary>Full output: Market Sizing</summary>


# Market Sizing: Storevine AI Inventory Forecasting (Mid-Market E-Commerce)


> Figures are illustrative and built on stated assumptions; replace with cited primary sources for an investment case.


</details>


---


### Stakeholder Summary


*Storevine B2B ecommerce platform . Campaigns launch stakeholder map*


:::note[Prompt]

discover-stakeholder-summary

Project: Campaigns . native email marketing for Storevine merchants Stage: PRD complete, moving to engineering kickoff

Stakeholders I’ve identified:

Internal:

  • Growth PM (me) . owner
  • Eng Lead (Platform) . aligned, participated in PRD review
  • Design . in progress on Figma specs
  • Legal . needs to review CAN-SPAM + GDPR section; not started yet
  • Merchant Success . launch comms owners; engaged in discovery
  • Storevine Marketing . dog-food use case; interested in using Campaigns for our own merchant communications

External:

  • Power-user merchants (fashion/home segment) . 5-6 who joined discovery interviews; have expectations about the feature
  • Klaviyo integration partner team . active Storevine integration; not sure how they’ll react to a native competing feature

Need: influence/interest map, stakeholder profiles, communication plan, and risk mitigation for Klaviyo and resistant stakeholders.

---
:::


<details>
<summary>Full output: Stakeholder Summary</summary>


# Stakeholder Summary: Campaigns . Native Email Marketing


</details>


---


## Phase: Define


### Hypothesis


*Storevine B2B ecommerce platform . Campaigns v1 first-campaign guided flow hypothesis*


:::note[Prompt]

define-hypothesis

Project: Campaigns . native email marketing for Storevine merchants Stage: Post-discovery, pre-PRD finalization

Hypothesis I want to define:

  • Non-adopter merchants (no active external email tool, <250 customers) are ~38% of our active base [fictional] and represented 3 of 8 merchant interview participants (P3, P6, and P8)
  • Core belief: setup complexity is the barrier . not awareness or price
  • Specific hypothesis: a guided first-campaign flow with product-seeded templates will drive first-send rate from ~12% [fictional] to ≥30% [fictional] within 60 days of GA

Prior work to reference:

  • Merchant interview synthesis (Jan 12 - 28, 2026): P3, P6, and P8 described email as “too overwhelming to start” or perennially “on the list”
  • Competitive analysis (Feb 2026): Shopify Email’s template-first + free tier activation is their primary new-merchant onboarding lever
  • Problem statement: email-related churn estimated at 4.8 pp [fictional] of overall 22% [fictional] annual merchant churn rate

Need: full hypothesis document with success metrics, validation approach, pass/fail criteria, and risks. Will attach to PRD as primary testable belief.

---
:::


<details>
<summary>Full output: Hypothesis</summary>


# Hypothesis: Pre-Populated Templates Drive First Campaign Sends for Non-Adopter Merchants


</details>


---


### JTBD Canvas


*Storevine B2B ecommerce platform . merchant email and tool-stack job-to-be-done for Campaigns*


:::note[Prompt]

define-jtbd-canvas

Project: Campaigns . native email marketing for Storevine merchants Stage: Pre-PRD, grounding feature scope in JTBD framework before engineering handoff

Job I want to map:

  • The core job: merchant owner-operators “hiring” their ecommerce platform to run their business without managing a fragmented external tool stack
  • Specific circumstance: merchant needs email re-engagement for existing customers but every tool they find requires a separate account, API setup, and data sync

Research basis:

  • 8 merchant interviews (Jan 12 - 28, 2026) . direct quotes available
  • Competitive analysis (Feb 2026): Klaviyo used by ~40% of active merchants [fictional]; Mailchimp by ~20% [fictional]
  • Q4 exit survey: 22% churn cited “had to use a separate email tool” [fictional]

Need: full JTBD canvas with functional, emotional, and social job layers, competing solutions, hiring criteria, and product implications. Will inform v1 feature prioritization and GA messaging strategy.

---
:::


<details>
<summary>Full output: JTBD Canvas</summary>


# Jobs to be Done Canvas: Run Email Marketing Without Leaving Storevine


</details>


---


### Opportunity Tree


*Storevine B2B ecommerce platform . churn reduction opportunity tree for Campaigns Q2 sprint planning*


:::note[Prompt]

define-opportunity-tree

Project: Campaigns . and broader platform churn reduction strategy Stage: Pre-Q2 sprint planning . framing the opportunity space before scope lock

Desired outcome: Reduce annual merchant churn from 22% [fictional] to 14% [fictional] by Q4 2026

Opportunities I’ve identified from discovery:

  1. Merchants can’t run email re-engagement without a separate external tool (Q4 exit survey: 22% churn [fictional]; 8 merchant interviews)
  2. Merchants can’t see what’s driving revenue across their store (interview finding: “there’s no way to see what’s working” . P8)
  3. Merchants are paying for Storevine + external tools and beginning to question whether the platform subscription is worth it

Prior work:

  • Competitive analysis (Feb 2026): email is the most-cited capability gap
  • Interview synthesis (Jan 2026): non-adopter segment and Klaviyo lock-in
  • Stakeholder summary: Campaigns PRD moving to engineering kickoff soon

Need: full opportunity-solution tree with visual, solution options per branch, prioritization, and experiments backlog for Q2 planning.

---
:::


<details>
<summary>Full output: Opportunity Tree</summary>


# Opportunity Solution Tree: Reduce Annual Merchant Churn


</details>


---


### Prioritization Framework


*Storevine B2B forecasting platform - reducing a 12-feature MVP wishlist to a shippable 8*


:::note[Prompt]

define-prioritization-framework

we need to cut our storevine MVP from 12 features to 8 to hit the launch date. it’s a B2B inventory forecasting platform. i don’t have reach numbers or solid effort estimates per feature yet - it’s pre-launch.

features: 1. demand forecast core 2. reorder recommendations 3. multi-warehouse 4. CSV data import 5. API integration (Shopify etc) 6. dashboard/reporting 7. low-stock alerts 8. user roles/permissions 9. forecast accuracy tracking 10. seasonal adjustment 11. supplier lead-time modeling 12. mobile view

what should we cut?

---
:::


<details>
<summary>Full output: Prioritization Framework</summary>


# Prioritization: Storevine MVP Scope Reduction (12 to 8)


</details>


---


### Problem Statement


*Storevine B2B ecommerce platform . Campaigns feature problem framing for engineering and design*


:::note[Prompt]

define-problem-statement

Project: Campaigns . native email marketing for Storevine merchants Stage: Define . establishing shared problem framing before PRD draft

Problem I want to articulate:

  • ~68% of active merchants use an external email tool [fictional]
  • Storevine’s built-in email lacks purchase-based segmentation and revenue attribution . the two capabilities merchants cite most
  • Q4 exit survey: 22% of churned merchants cited this as a primary cancellation reason [fictional]
  • Competitive analysis filed last week: Shopify Email has already validated the built-in email model; Campaigns is behind

Prior work to integrate:

  • Competitive analysis (Feb 2026): feature gap matrix vs. Shopify Email, Klaviyo, and Mailchimp; confirmed attribution is the primary v1 differentiator opportunity
  • Q4 exit survey data (internal): 22% churn cited email gaps [fictional]

Need: full problem statement with user impact, business context, success criteria, constraints, and open questions. Audience: engineering lead, design, legal, and head of product before PRD review.

---
:::


<details>
<summary>Full output: Problem Statement</summary>


# Problem Statement: Merchants Require External Email Tools for Capabilities Storevine's Platform Should Provide


</details>


---


## Phase: Develop


### Architecture Decision Record


*Storevine B2B ecommerce platform . email sending infrastructure for Campaigns*


:::note[Prompt]

develop-adr

ADR for email sending infrastructure choice for Campaigns v1. We need to pick the vendor before we start the backend build.

Context: Storevine currently sends transactional emails (order confirm, password reset) through SendGrid on a shared IP. Campaigns will add broadcast marketing email + 3 automated sequences (abandoned cart, welcome, re-engagement) at projected volume of ~2M emails/month at launch [fictional], scaling to ~10M at full merchant adoption [fictional].

Options we evaluated: SendGrid (upgrade to dedicated IP), AWS SES, Postmark, Mailgun.

Key constraints:

  • CAN-SPAM/GDPR compliance is a hard gate before launch
  • Deliverability matters: one spam incident tanks merchant trust
  • We have existing SendGrid integration (transactional)
  • Cost matters but is secondary to deliverability reliability at this stage

Decision: SendGrid dedicated IP. Need this documented for the record. Eng lead and growth PM are the deciders.

---
:::


<details>
<summary>Full output: Architecture Decision Record</summary>


# ADR-007: Email Sending Infrastructure for Campaigns


</details>


---


### Design Rationale


*Storevine B2B ecommerce platform . Campaigns audience selection UX design decision*


:::note[Prompt]

develop-design-rationale

Project: Campaigns . native email marketing for Storevine merchants Decision: Audience selection UX for the campaign creation flow Stage: Pre-sprint design review . finalizing Figma specs before engineering

Decision I need to document:

  • We debated 3 audience selection approaches before the design review: A. Custom filter builder (SQL-like nested conditions, matches Klaviyo) B. Pre-built named segments only (curated list, no customization) C. Pre-built segments as default + custom filter as secondary option
  • We chose Option C after design review with PM, design lead, and eng lead

Context:

  • Primary target segment: non-adopter merchants (no current email tool)
  • Interview data: 3 of 8 merchants cited setup complexity as the barrier
  • Figma link: [internal . Campaigns audience selection v3 spec]

Need: full design rationale document for the engineering handoff package. Decision makers: Design Lead, Growth PM, Engineering Lead.

---
:::


<details>
<summary>Full output: Design Rationale</summary>


# Design Rationale: Campaigns Audience Selection UX


</details>


---


### Solution Brief


*Storevine B2B ecommerce platform . Campaigns one-page solution brief for head of product review*


:::note[Prompt]

develop-solution-brief

Project: Campaigns . native email marketing for Storevine merchants

I need a one-page brief for a head of product review before engineering kickoff. Full PRD already written and reviewed with engineering lead. This brief is for executive context, not the build team.

Problem (3 sentences max):

  • 68% of active merchants use external email tools [fictional]
  • Built-in tools lack segmentation + attribution
  • 22% churn cited email gaps as a top-3 reason [fictional]

Solution: native email within Storevine admin . no separate tool subscription, no sync required

v1 features to include:

  • Purchase-based audience segments (pre-built, seeded from Storevine data)
  • Guided first-campaign flow (product-seeded templates)
  • Revenue attribution (SendGrid webhook → order database)
  • CAN-SPAM/GDPR compliance built in
  • Abandoned cart automation

Success metrics, trade-offs (what we’re NOT building), and top risks.

---
:::


<details>
<summary>Full output: Solution Brief</summary>


# Solution Brief: Campaigns . Native Email Marketing for Storevine Merchants


</details>


---


### Spike Summary


*Storevine B2B ecommerce platform . revenue attribution feasibility spike for Campaigns v1*


:::note[Prompt]

develop-spike-summary

Spike: Revenue attribution feasibility . can SendGrid open/click webhooks be linked to Storevine purchase events within v1 timeline?

Context:

  • Revenue attribution is a launch-gate requirement (confirmed in interview synthesis and opportunity tree)
  • Engineering ADR selected SendGrid for Campaigns email delivery
  • Engineering Lead asked for a 1-week spike before sprint planning

What we investigated:

  • SendGrid Event Webhook payload structure and custom data fields
  • Whether Storevine’s customer_id can survive the email→purchase journey
  • POC: send a test campaign, receive webhook, match to staging order
  • Attribution window design: real-time vs. deferred (7-day)

Need: full spike summary with findings, recommendation, and follow-up items. Will share with PM and Engineering Lead to unblock sprint planning.

---
:::


<details>
<summary>Full output: Spike Summary</summary>


# Spike Summary: Revenue Attribution via SendGrid Event Webhooks


</details>


---


## Phase: Deliver


### Acceptance Criteria


*Storevine B2B ecommerce platform . acceptance criteria for the Campaigns email template builder*


:::note[Prompt]

deliver-acceptance-criteria

Feature: Campaigns . email template builder The template builder lets merchants drag-and-drop content blocks (text, image, button, divider, product card) onto a canvas, customize styling, preview on desktop and mobile, and save templates for reuse across campaigns. Templates are stored per-merchant and can be duplicated.

---
:::


<details>
<summary>Full output: Acceptance Criteria</summary>


---
artifact: acceptance-criteria
version: "1.0"
created: 2026-04-11
status: draft
---


# Acceptance Criteria: Campaigns Email Template Builder


</details>


---


### Edge Cases


*Storevine B2B ecommerce platform . Campaigns campaign send flow edge cases*


:::note[Prompt]

deliver-edge-cases

Feature: Campaigns . campaign creation and send flow Sprint: Q2 2026 Campaigns build (GA Apr 28, 2026)

Key edge cases I want to cover:

  • Input validation: subject line, email body, audience size, physical sender address (CAN-SPAM requirement)
  • Boundary conditions: free tier send volume limit, min/max audience size
  • Error states: network failure during send, SendGrid API errors
  • Concurrency: double-click send, merchant edits in two browser tabs
  • Integration failures: SendGrid unavailable, attribution webhook down

Related docs:

  • User story US-CAM-001 (guided first-campaign flow)
  • Spike summary: SendGrid attribution webhook confirmed
  • Edge cases will be used for QA test plan and engineering handoff

Need: full edge cases document with error messages, recovery paths, and QA test scenarios (P1/P2/P3).

---
:::


<details>
<summary>Full output: Edge Cases</summary>


# Edge Cases: Campaigns Campaign Send Flow


</details>


---


### Launch Checklist


*Storevine B2B ecommerce platform . Campaigns v1 GA launch checklist*


:::note[Prompt]

deliver-launch-checklist

Feature: Campaigns v1.0 . native email marketing for Storevine merchants Launch date: April 28, 2026 Launch type: Major Release Launch owner: Growth PM

Key compliance and infrastructure requirements:

  • Legal sign-off on CAN-SPAM + GDPR required before any production send
  • DMARC/SPF/DKIM sender authentication required for Gmail/Yahoo inbox delivery (enforced by Google and Yahoo since 2024)
  • SendGrid dedicated IP warm-up plan needed before full-volume sends
  • Feature flag rollout: start at 10% of merchants [fictional], scale to 100% over 2 weeks based on send failure rates

Stakeholders:

  • Engineering Lead (Platform Squad)
  • Merchant Success (launch comms + support)
  • Legal (CAN-SPAM/GDPR review)
  • Storevine Marketing (announcement + dog-food)

Key risks from stakeholder summary:

  • Legal review not started; hard gate on compliance sign-off
  • Klaviyo partner team needs 48-hour advance notice before GA announcement
  • Power-user merchant beta cohort expectations may exceed v1 scope

Need: full pre-launch checklist with go/no-go criteria, rollback plan, and check-in schedule.

---
:::


<details>
<summary>Full output: Launch Checklist</summary>


# Launch Checklist: Campaigns v1.0 GA


</details>


---


### PRD


*Storevine B2B ecommerce platform . Campaigns (built-in email marketing)*


:::note[Prompt]

deliver-prd

Feature: Campaigns . native email marketing for Storevine merchants

Context: Storevine all-in-one ecommerce + web builder, ~18k active merchants [fictional]. See: competitive-analysis (filed last week), problem-statement (Q4 discovery doc).

Discovery: Email marketing is a top-3 churn driver. Exit survey: 22% of churned accounts in Q4 cited “had to use a separate email tool” as a primary reason [fictional]. Power merchants patch with Klaviyo or Mailchimp; smaller merchants skip email entirely because setup friction is too high.

Validated solution: Built-in Campaigns . broadcast email + basic audience segmentation. Phase 1 email only, SMS deferred. Pre-built templates, audience builder using order/tag data we already have. No custom HTML editor v1.

Success targets:

  • 40% of active merchants send ≥1 campaign in first 90 days post-launch [fictional]
  • Reduce email-churn contribution by 30% at 6 months [fictional]
  • Campaigns becomes a net-new revenue line (paid tier above free send limit)

Scope locked with eng: v1 = broadcast email + 3 automations (abandoned cart, welcome, re-engagement). No SMS, no A/B testing, no multi-step sequences.

Technical decisions already made:

  • Sending via SendGrid (existing account)
  • Audience builder queries existing customer/order tables . no new pipeline
  • Legal review on CAN-SPAM + GDPR required before launch (not yet started)

Stakeholders: Growth PM (owner), Eng Lead (aligned), Design (in progress), Legal (needs to review compliance section), Marketing (will dog-food).

---
:::


<details>
<summary>Full output: PRD</summary>


# PRD: Storevine Campaigns


</details>


---


### Release Notes


*Storevine B2B ecommerce platform . Campaigns v1.0 GA merchant-facing release notes*


:::note[Prompt]

deliver-release-notes

Product: Storevine Release: Campaigns v1.0 . native email marketing, GA on Apr 28, 2026 Audience: All active Storevine merchants

What’s new:

  • Campaigns: native email marketing, built into the Storevine admin
  • Purchase-based audience segments (pre-built, seeded from Storevine data)
  • Guided first-campaign flow (product-seeded templates, no setup required)
  • Revenue attribution (see which emails drove which purchases)
  • Abandoned cart automation (pre-configured, activates in one click)
  • CAN-SPAM/GDPR compliance automatic in every send

Known issues / limitations to document:

  • A/B testing not in v1 (coming in v2)
  • EU merchant access delayed (GDPR consent flow in v1.1)
  • Klaviyo migration tooling not available (planned v2)

Tone: merchant-benefit-first; plain language; not feature-spec language. Audience is small-business owners, not developers.

---
:::


<details>
<summary>Full output: Release Notes</summary>


# Storevine Campaigns v1.0


**Release Date:** April 28, 2026


</details>


---


### User Stories


*Storevine B2B ecommerce platform . Campaigns guided first-campaign flow user story*


:::note[Prompt]

deliver-user-stories

Project: Campaigns . native email marketing for Storevine merchants Sprint: Q2 2026 Campaigns build (kickoff Mar 3, GA Apr 28)

Story I need: Guided first-campaign flow for non-adopter merchants

Who: Merchant with no active external email tool and no prior Storevine email sends (non-adopter segment, ~38% of active base [fictional]) What: Send their first email campaign using a pre-populated template seeded with their own products and a default audience Why: Start driving repeat purchases without needing to figure out email marketing from scratch

Prior work to reference:

  • Hypothesis: first-send rate target 12% → 30% [fictional] in 60 days
  • Spike summary: SendGrid attribution via unique_args confirmed feasible
  • Design rationale: pre-built named segments as default audience selection
  • PRD: Campaigns v1 scope locked

Need: full user story with acceptance criteria (Given/When/Then), design notes, technical notes, and dependencies. P0 priority.

---
:::


<details>
<summary>Full output: User Stories</summary>


# User Story: Guided First-Campaign Flow for Non-Adopter Merchants


</details>


---


## Phase: Measure


### Dashboard Requirements


*Storevine B2B ecommerce platform . Campaigns adoption and revenue analytics dashboard requirements*


:::note[Prompt]

measure-dashboard-requirements

Dashboard: Campaigns adoption and revenue . post-GA monitoring Audience: Growth PM (daily), Merchant Success (weekly), Head of Product (monthly board prep)

Key questions to answer:

  1. Are non-adopter merchants sending their first campaign? (primary hypothesis metric: first-send rate, 60-day window)
  2. Is Campaigns driving measurable revenue for merchants? (7-day attributed revenue per campaign send)
  3. Is the email-related churn rate declining since GA? (churn cohort analysis: merchants with and without Campaigns sends)

Metrics needed:

  • First-send rate (60-day, non-adopter segment)
  • Campaigns-attributed revenue (7-day window, rolling)
  • Active Campaigns merchants (sent ≥1 campaign in last 30 days)
  • Churn rate by Campaigns usage cohort
  • Send failure rate and unsubscribe rate (guardrails)

Analytics platform: Amplitude (events) + Storevine order DB (revenue)

Need: full dashboard requirements doc with metric definitions, visualizations, filters, data sources, and acceptance criteria.

---
:::


<details>
<summary>Full output: Dashboard Requirements</summary>


# Dashboard Requirements: Campaigns Adoption and Revenue


</details>


---


### Experiment Design


*Storevine B2B ecommerce platform . Campaigns guided first-campaign flow A/B experiment design*


:::note[Prompt]

measure-experiment-design

Project: Campaigns . Campaigns guided first-campaign flow Experiment: Does the guided first-campaign flow increase first-send rate for non-adopter merchants?

Hypothesis (from Define phase doc):

  • We believe pre-populated templates for non-adopter merchants (<250 customers [fictional], no external email tool) will drive first-send rate from 12% [fictional] to ≥30% [fictional] within 60 days of GA

Variants:

  • Control: Standard Campaigns creation flow (blank template editor, named segment library, no pre-population)
  • Treatment: Guided first-campaign flow (product-seeded template, audience defaulted to “Customers who purchased in the last 90 days”)

Sample: ~6,800 eligible non-adopter merchants [fictional]; need enough per variant to detect a 8 pp improvement with 80% power

Run period: April 28 - June 27, 2026 (60 days from GA)

Need: full experiment design with sample size calculation, success criteria, risks, and implementation notes.

---
:::


<details>
<summary>Full output: Experiment Design</summary>


# Experiment Design: Guided First-Campaign Flow for Non-Adopter Merchants


</details>


---


### Experiment Results


*Storevine B2B ecommerce platform . Campaigns guided first-campaign flow A/B test results*


:::note[Prompt]

measure-experiment-results

Experiment: Campaigns guided first-campaign flow A/B test Ran: April 28 - June 27, 2026 (60 days from GA)

Results:

  • Control (blank canvas): 13.4% first-send rate, N=1,204 merchants [fictional]
  • Treatment (guided flow): 31.7% first-send rate, N=1,198 merchants [fictional]
  • p < 0.001, statistically significant

Secondary metrics:

  • Median time to first send: 43 min (control) vs. 12 min (treatment) [fictional]
  • Second campaign rate (90 days): 9.1% control vs. 22.8% treatment [fictional]

Guardrail metrics all within acceptable range.

Segment finding: treatment effect strongest in fashion/home merchants (38.2% vs. 14.6% control) [fictional]; weakest in specialty food (24.1% vs. 11.8% control) [fictional]

Decision: ship the guided flow as default. Need full results document for stakeholder review and decision record.

---
:::


<details>
<summary>Full output: Experiment Results</summary>


# Experiment Results: Campaigns Guided First-Campaign Flow A/B Test


</details>


---


### Instrumentation Spec


*Storevine B2B ecommerce platform . Campaigns send flow and first-campaign flow analytics instrumentation*


:::note[Prompt]

measure-instrumentation-spec

Feature: Campaigns . campaign send flow + guided first-campaign flow Analytics platform: Amplitude

Events I need to instrument:

  1. campaign_created . merchant saves a campaign draft
  2. campaign_sent . merchant sends a campaign
  3. first_send_completed . merchant sends their FIRST campaign ever (milestone event for the non-adopter hypothesis)
  4. attribution_recorded . a purchase is linked to a campaign click within the 7-day attribution window

Prior work:

  • Experiment design: A/B test using first_send_completed as primary metric
  • Spike summary: SendGrid webhook attribution confirmed; unique_args includes campaign_id, merchant_id, recipient_customer_id

PII note: Subscriber email addresses must NOT be sent to Amplitude. Only customer_id (pseudonymous internal identifier).

Need: full instrumentation spec with event definitions, properties, PII handling, implementation notes, and QA testing checklist.

---
:::


<details>
<summary>Full output: Instrumentation Spec</summary>


# Instrumentation Spec: Campaigns Send Flow and First-Campaign Flow


</details>


---


### OKR Grader


*Storevine B2B ecommerce platform. Campaigns team Q3 2026 cycle review at quarter close (October 2026). Scores the OKR set produced in the foundation-okr-writer storevine sample.*


:::note[Prompt]

measure-okr-grader

Original OKR: see sample_foundation-okr-writer_storevine_campaigns-q3.md Cycle: Q3 2026 (July 1 to September 30, 2026) OKR type: aspirational

Final KR values:

  • KR1 (weekly active senders): 26% [fictional] (target was 28%, baseline 14%)
  • KR2 (90-day campaign retention): 60-day cohort interim is 19% [fictional]; full 90-day target was 38% (baseline 22.8%); 90-day final not yet observable
  • KR3 (guardrail, median CTR): 3.6% [fictional] (target was hold at or above 3.4%, baseline 3.4%)

Guardrails:

  • Unsubscribe rate ended cycle at 0.81% [fictional] (baseline 0.72%, threshold 0.95%)
  • Spam complaint rate ended at 0.05% [fictional] (baseline 0.04%, threshold 0.1%)

Initiative status:

  • Initiative 1 (Lifecycle email triggers): shipped July 22 as planned. Open rate on triggered emails 38% [fictional]. Click-through to send action 21% [fictional].
  • Initiative 2 (Templates v2): shipped 8 of 12 templates by Sept 30 [fictional]. Adoption among first-time repeat senders was 31% [fictional], below the 60% [fictional] target. Templates that did get adopted showed no significant retention difference vs. generic templates (Q3 cohort).
  • Initiative 3 (Campaign performance feedback loop): shipped Aug 28. Adoption among repeat senders 64% [fictional]. Self-reported usefulness 4.1 / 5 [fictional].

Cycle context:

  • Onboarding team’s Q3 KR (boost Campaigns activation rate to 50%) hit 47% [fictional]; close enough that we did not rebaseline KR1 mid-cycle.
  • Mid-cycle, the team caught a bug in lifecycle trigger eligibility logic (week 3 of August). Fixed in 4 days but ~120 merchants [fictional] received duplicate triggers. No measurable impact on unsub rate.

Stakeholder interpretation: Campaigns leadership reads the cycle as a clear win on activation-to-recurring-send (KR1) and a learning result on retention-thesis (KR2 + Templates v2). Looking for grader’s independent read.

:::


<details>
<summary>Full output: OKR Grader</summary>


```markdown
# OKR Cycle Review: Storevine Campaigns Team, Q3 2026


</details>


---


### Survey Analysis


*Storevine B2B forecasting platform - feature-prioritization survey of 180 customer admins, segmented by company size*


:::note[Prompt]

measure-survey-analysis

analyze our storevine feature-prioritization survey. 180 customer admins responded. we asked them to rate 5 candidate features by importance and pick their #1.

our hypotheses going in:

  • H1: multi-warehouse support is the top ask
  • H2: seasonal-adjustment accuracy is a close second

segment by company size (we captured it). tell us what to build next.

---
:::


<details>
<summary>Full output: Survey Analysis</summary>


# Survey Analysis: Storevine Next-Feature Validation


</details>


---


## Phase: Iterate


### Lessons Log


*Storevine B2B ecommerce platform . lesson learned from the Campaigns guided first-campaign flow A/B test*


:::note[Prompt]

iterate-lessons-log

Lesson from: Campaigns guided first-campaign flow A/B test Experiment ran: April 28 - June 27, 2026 (60 days from GA) Decision: Ship guided flow as default for all non-adopter merchants

Primary finding:

  • Control: 34.2% opened flow, 39.2% of openers clicked Send [fictional]
  • Treatment: 35.8% opened flow, 88.5% of openers clicked Send [fictional]
  • Flow entry rate was nearly IDENTICAL between variants
  • All of the treatment advantage was in completion rate, not flow entry

What surprised us: We expected the guided UX structure (progress indicator, step sequencing, explicit prompts) to be the mechanism. Funnel analysis shows the treatment advantage is concentrated at the template and subject line step . content pre-population, not UX scaffolding, is doing the work.

Lesson type: Success Pattern / Strategy Need: structured lessons log entry for the team knowledge base.

---
:::


<details>
<summary>Full output: Lessons Log</summary>


# Content Quality, Not UX Scaffolding, Is the Non-Adopter Activation Mechanism


</details>


---


### Pivot Decision


*Storevine B2B ecommerce platform . Campaigns v2.0 persevere decision after guided flow validation*


:::note[Prompt]

iterate-pivot-decision

Product: Campaigns . post-GA persevere/pivot evaluation Evaluation date: July 22, 2026 (12 weeks post-GA)

Situation: Campaigns GA succeeded. Guided flow A/B test: 31.7% vs. 13.4% first-send rate [fictional], shipped as default July 10. BUT: Klaviyo-migrated merchants sending at 23% [fictional] monthly . far below the ~60% [fictional] predicted from their Klaviyo history. Three migrated merchants submitted tickets citing missing advanced segmentation and scheduling. Migrator churn tracking at 18% [fictional].

Question: Should Campaigns v2.0 resources pivot to serve Klaviyo- migrated merchants, or persevere on non-adopter activation?

Options I need evaluated:

  1. Persevere . continue non-adopter activation (77% of segment unconverted [fictional])
  2. Customer Segment Pivot . redirect to Klaviyo-migrated merchants
  3. Platform Pivot . open Campaigns as an API for third-party email tool integration

Need: full pivot decision document with analysis and rationale.

---
:::


<details>
<summary>Full output: Pivot Decision</summary>


# Pivot Decision: Campaigns v2.0 Roadmap Direction


</details>


---


### Refinement Notes


*Storevine B2B ecommerce platform . Campaigns v1.1 sprint refinement session*


:::note[Prompt]

iterate-refinement-notes

Session: Campaigns v1.1 refinement Date: July 22, 2026, 10:00 AM, 60 minutes Sprint preparing for: Sprint 12 . Campaigns v1.1 Facilitator: Growth PM

Stories on the agenda:

  1. CAM-088: EU merchant GDPR consent data model
  2. CAM-089: Per-campaign open rate and click rate analytics
  3. CAM-090: Follow-on experiment . 3 vs. 5 products in guided template
  4. CAM-091: Abandoned cart email trigger

Key constraints:

  • Legal has not yet signed off on the EU consent model (CAM-088)
  • Backend Engineer flagged ambiguity on the open rate denominator (CAM-089): Amplitude delivered-event count vs. SendGrid recipient count
  • CAM-091 may need to be split . scope spans 4 engineering domains

Need: full refinement notes for Sprint 12 planning.

---
:::


<details>
<summary>Full output: Refinement Notes</summary>


# Refinement Notes: July 22, 2026


</details>


---


### Retrospective


*Storevine B2B ecommerce platform . Campaigns v1.0 build sprint retrospective*


:::note[Prompt]

iterate-retrospective

Sprint: Campaigns v1.0 build sprint + GA week Period: February 3 - May 5, 2026 [fictional] Date held: May 7, 2026 Format: Start / Stop / Continue Duration: 90 minutes [fictional]

Team: Growth PM, Engineering Lead, Backend Engineer, Design Lead, Merchant Success Lead, QA Lead

What went well:

  • Beta merchant FAQ (23 questions → 10 FAQ + 15 canned responses) [fictional] . reduced GA-week ticket volume significantly
  • Instrumentation spec process caught subscriber email PII gap before GA
  • Feature flag rollout (10%→100%) worked; zero rollback events

What to improve:

  • Legal review started 3 weeks before GA instead of 6 weeks; created compliance copy crunch that delayed marketing content
  • DMARC/SPF/DKIM setup: estimated 1 day, took 5 business days [fictional]; DNS propagation not in the timeline
  • Klaviyo partner notice email sent 2 days late (no clear owner)

Previous retro actions to review (Sprint 7 retro):

  • Add QA Lead to kickoff sessions . Complete
  • Define escalation path for blocker tickets . In Progress
  • Document infrastructure prerequisites for launches . Not Started

Need: full sprint retrospective with action items.

---
:::


<details>
<summary>Full output: Retrospective</summary>


# Retrospective: Campaigns v1.0 Build Sprint


</details>


---


*49 artifacts generated across the full PM lifecycle.*


---


**Explore other journeys:**


- [Brainshelf (Consumer PKM App)](brainshelf.md)
- [Workbench (Enterprise Collaboration)](workbench.md)