playbook-fundraising

Generates funding-round first lines and list filters for cold email campaigns.

Updated May 28, 2025
One-click install
npx skills add https://github.com/meloShaya/insteltech --skill playbook-fundraising-meloshaya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playbook-fundraising
Source: https://github.com/meloShaya/insteltech/tree/main/crm/library/skills/playbooks/playbook-fundraising
Command: npx skills add https://github.com/meloShaya/insteltech --skill playbook-fundraising-meloshaya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cold email personalization about a prospect's funding round often fails because databases mislabel secondary sales and PE stakes as raises, funding dates lag by months, and spintax gates render broken sentences like "Saw ." on rows with no data. This playbook produces a verified, copy-ready funding sentence per company and the list filters that select funded companies, with every fact decided in code before the model writes a single word. ## Core Features & Use Cases - Copy-ready funding line: Outputs funding_line, a complete sentence including the leading "Saw" and trailing period, so an empty value renders as nothing at all in the email body. - Three-lane source chain: Lane A filters lists to companies that ever raised or raised within 12 months, Lane B generates the per-row copy line via a tested lookup-guard-filter-prompt chain, and Lane C documents the unsolved "raised in the last 30 days" problem honestly. - Deterministic fact guards: Code enforces domain-equality matching, an equity-stage whitelist, and a 12-month recency window, so the model only chooses wording and can never invent a round, date, or amount. - Use Case: Building a Series A prospect list, you filter to equity-stage companies funded in the past year, then push {{funding_line}} as a lead-level variable into your sequencer so each email opens with a verified sentence like "Saw you raised $52M in the Series B." ## Quick Start Ask the assistant to generate a funding-round first line for a list of company domains using the fundraising playbook, then push the resulting funding_line variable into your email sequencer.

Frequently Asked Questions about playbook-fundraising

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a cold email first line about a company's funding round?

Look up the company by domain, verify the returned domain matches exactly, filter funding events to equity stages within 12 months, then have a model phrase only the clause. Code wraps it into a complete sentence like "Saw you raised $52M in the Series B."

How do I build a list of recently funded companies?

Apply a funding-stage filter with equity stages plus a funding_date window of 180 or 365 days when building the list. Note that people-database funding indexes lag 3 to 4 months, so a true last-30-days list has no proven automated path.

Why does my funding personalization render as "Saw ." in some emails?

Spintax is a random chooser with no knowledge of whether a variable is populated, so it renders broken text on abstaining rows. Put the entire sentence in the variable so an empty value renders as nothing, or split the list at upload time.

Can I use total funding or the funding date in email copy?

No. Database totals fold in debt facilities and secondary sales, and raised_at dates were measured off by 15 days to two months. Quote only the round amount and stage, which checked out exactly in testing.

Why does a company lookup return the wrong company for a domain?

Website filters also match other listed websites, so a vendor listing your target as a customer can win the match silently. Always assert the returned company domain equals the requested domain before using any funding data.

What are the limitations of funding-signal feeds for fresh rounds?

Funding feeds have real freshness but often lack domains, mix in acquisitions and VC fund closes, and headline parsing can produce absurd amounts. Cleanup steps must filter on is_closed_round and is_acquisition, and the end-to-end path remains untested.