Prompts — Product
Recipes for end-to-end product work: position, monetize, activate, launch, and listen to the user.
R1 — Positioning the team will defend
Skills: product-marketing
When: the product exists but everyone explains it differently.
Product: <product>. Audience: <persona>. Main competitor:
<competitor>.
Use product-marketing to generate: one-sentence positioning, 3 key
messages with proof, and the differentiation narrative vs.
<competitor>.
Success: one-pager a dev on the team can defend in a conversation
without asking me anything.
R2 — Monetization funnel
Skills: pricing + paywalls + churn-prevention
When: designing (or reworking) how the product charges, converts, and retains.
Product: <product>, <subscription/usage> model. Design the
monetization funnel: pricing tiers with an anchor, in-app paywall
at value moments <moments>, and a cancellation flow with save
offers and exit survey (churn-prevention).
Success: per-screen spec + tier table + named analytics events for
every step of the funnel.
R3 — Onboarding that activates
Skills: onboarding + signup + emails
When: users sign up and vanish before the aha-moment.
Map with onboarding + signup the flow from signup to the aha-moment
of <product> (aha = <definition>). Cut steps that don't lead to the
aha. Generate with emails the activation sequence for users who get
stuck at each step.
Success: flow with an activation metric per step + email sequence
with trigger, subject, and CTA each.
R4 — Launch plan
Skills: launch + product-marketing + social
When: new feature or product with a date.
Launch of <feature/product> on <date>. Use launch for the timeline
(T-14 to T+7), product-marketing for the core message, and social
for the distribution plan across channels <channels>.
Success: executable checklist by date, with an owner and artifact
per item; base copy ready to adapt.
R5 — Instrument user feedback
Skills: analytics + churn-prevention
When: decisions are being made on opinion; a structured user voice is missing.
Instrument feedback collection for <product>: GA4 tracking plan
(analytics) with named events for flows <flows>, exit survey on
cancellation (churn-prevention), and an NPS trigger after
<value moment>.
Success: tracking plan as a table (event, properties, when it
fires) + survey questions with a defined scale; everything ready
to implement with no pending decision.
See also
offers— sharpen the offer (bonuses, guarantee, value framing) before touching price.aso— if the product is an app: audit the store listing.free-tools/lead-magnets/referrals— acquisition engines outside the paid funnel.