Fractional Product Manager

• HoneyBook
• DocuSign
• Wave

• Notion
• Linear
• Productboard

• Dovetail
• Maze
• Calendly + Zoom + Google Forms

You are a fractional product manager with 8+ years of experience helping early-stage startups ship faster and avoid costly pivots. Write a cold outreach email to a seed-stage SaaS startup founder.

Context I'll provide: [FOUNDER NAME], [COMPANY NAME], [WHAT THEIR PRODUCT DOES], [ONE SPECIFIC PROBLEM I NOTICED — e.g., 'your onboarding flow has 11 steps before a user sees value']

Requirements:
- Subject line under 8 words, no clickbait
- Opening line references something specific about their product or recent news (not generic flattery)
- One sentence on what I do and who I help
- One concrete, specific observation about a product gap I noticed (use the problem I provided)
- A single low-friction ask (15-min call, not a pitch)
- Total length: under 150 words
- Tone: peer-to-peer, not vendor-to-prospect
- No buzzwords like 'synergy', 'leverage', or 'scale your growth'

Write 3 subject line variants and 1 email body.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

You are a fractional PM helping a startup build their first structured product roadmap. Based on the information I provide, generate a 90-day roadmap broken into three 30-day sprints.

Client context:
- Product: [DESCRIBE THE PRODUCT IN 2-3 SENTENCES]
- Current stage: [PRE-LAUNCH / POST-LAUNCH / GROWTH]
- Team size: [NUMBER OF ENGINEERS, DESIGNERS]
- Top 3 business goals right now: [LIST THEM]
- Known user complaints or drop-off points: [LIST WHAT YOU KNOW]
- Tech debt or known blockers: [LIST OR WRITE 'UNKNOWN']

For each 30-day sprint, provide:
1. Sprint theme (one sentence)
2. 3-5 prioritized initiatives with a one-line rationale for each
3. One success metric to track
4. One risk to watch

Prioritization framework: use RICE scoring logic (Reach, Impact, Confidence, Effort) — explain your reasoning briefly for the top 2 items in each sprint.

Format as a clean table I can paste into Notion or Google Docs.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

I am a fractional product manager. I just completed [NUMBER] user interviews for [CLIENT COMPANY NAME], a [DESCRIBE PRODUCT] used by [TARGET USER TYPE].

Below are my raw interview notes. Analyze them and produce:

1. Top 5 recurring pain points (ranked by frequency and severity)
2. Top 3 unmet needs that the product could address
3. 2-3 surprising or counterintuitive findings
4. Direct quotes (pulled from my notes) that would resonate with the founding team
5. Recommended next steps: what to build, what to kill, what to investigate further

Format for a founder audience — they are not researchers. Use plain language. Flag anything where the sample size is too small to draw conclusions.

Raw notes:
[PASTE YOUR INTERVIEW NOTES HERE]

Do not invent quotes or findings. If the notes are too sparse to support a conclusion, say so explicitly.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

I am a fractional product manager closing a new client engagement. Help me write a clear, professional Scope of Work (SOW) document.

Engagement details:
- Client company: [NAME]
- Product type: [DESCRIBE]
- Engagement length: [e.g., 3 months, rolling monthly]
- Hours per week committed: [NUMBER]
- My hourly or monthly rate: [RATE]
- Deliverables we discussed: [LIST WHAT YOU AGREED TO — e.g., weekly roadmap review, bi-weekly stakeholder syncs, user research synthesis monthly]
- What is explicitly OUT of scope: [LIST]
- Communication norms: [e.g., async Slack, weekly video call]

Generate a SOW that includes:
1. Engagement overview (2-3 sentences)
2. Deliverables with clear acceptance criteria
3. Out-of-scope items (to prevent scope creep)
4. Working hours and communication expectations
5. Change request process (how to add work outside this SOW)
6. Payment terms placeholder

Tone: professional but not stuffy. This is a working document, not a legal contract. I'll have an attorney review before signing.

Review requirements: Separate supplied facts from assumptions. Do not invent market data, customer results, testimonials, or source citations. Flag missing information and suggest a small validation test. Mark numerical examples as scenarios. Keep the final decision with me.

Hard cap at 2 clients when you're starting out. Track your actual hours weekly for the first 90 days. Only add a third client once you have repeatable systems (templates, async communication norms, documented client context) that cut your per-client overhead by at least 30%.

Scope the deliverables tightly, not the hours. Use a SOW with a change-request clause for work outside scope.

No kickoff call, no Slack access, no work until: (1) SOW is signed by both parties, (2) first payment is received or a payment method is on file. Use a tool like DocuSign or HoneyBook to make this frictionless. It takes 10 minutes and protects thousands of dollars.

Define communication norms in your SOW: which channels you'll use, your response time SLA (e.g., 'within 24 hours on business days'), which meetings you attend vs. get a summary for, and how off-scope requests get handled. Enforce this from day one — it's much harder to reset expectations mid-engagement.

Spend the first 2–3 weeks in structured discovery: interview the founding team, review existing data (analytics, support tickets, past user research), and map the current decision-making process. Deliver a 'Current State' document before touching the roadmap. This also protects you — it documents what you inherited.