Review a fundraising pipeline for stage age, evidence, next action, ownership, and stale or unsupported status.
Instructions your experts follow when using this skill.
Use this on a supplied investor tracker. The tracker records activity; it does not prove investor intent or a likely close.
Use the owner's existing stages or agree on plain definitions such as target, intro requested, first meeting, follow-up, diligence, partner review, terms in discussion, passed, and closed. Record the event that moves a row into each stage. Do not infer a stage from elapsed time alone.
Show investor, current stage, date entered, days in stage, last verified event, next action, action owner, due date, requested material, confidentiality limit, and blocker. Label relationship claims as user supplied unless a source record supports them.
Flag:
Lead with counts and stage ages, not a weighted funding forecast. Name the five rows that need an owner decision and give one proposed action for each. Draft a follow-up only from the recorded discussion and hold it for approval.
Never assign a probability, valuation, or expected proceeds without an approved method and owner-supplied inputs. Never claim an investor is committed without signed evidence named by the owner. Do not send messages, share files, change pipeline stages, or promise terms. Route terms, disclosure, securities, and legal questions to counsel and the finance lead.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.