Outreach
Manual link-building outreach: track prospects and the email send queue per project. Drafts are recorded, never auto-sent.
The outreach lane covers everything the directory checklist doesn't: listicle requests, link insertions, guest posts — any target page you pitch a human about. Prospects carry the article, contact, score and a pipeline status; sends carry the draft (with the specific detail it cites) and the outcome. Humans send the email — the lane records state.
Pipeline
Prospect statuses: prospect → draft_ready → sent → replied → live (or skip). Send statuses: draft → sent → replied → won | lost.
MCP Tool
- Tool name:
startupkit_outreach - Actions:
list(default) — prospects, filterable bystatus, sorted by scoresave— upsert a prospect (urlrequired;title,contact_name,contact_email,notes,score,status;"clear"removes it)sends— the draft/outcome queuelog— queue a draft (prospect_url,subject,body,detail_cited) or update a send (id,status)
- Output: prospects or sends with a per-status
summary
detail_cited is the one specific detail from the target article the draft references — a section name, a competitor called out, the year in the title. It's what keeps pitches non-generic.
CLI
startupkit outreach # prospects + summary
startupkit outreach --add https://a.com/quip-alternatives \
--title "Best Quip alternatives" --email [email protected] --score 8
startupkit outreach --mark <url> --mark-status draft_ready
startupkit outreach --draft <prospect-url> \
--subject "Jot for your list" --body "…" --detail "the offline-editing section"
startupkit outreach --sends # the review queue
startupkit outreach --send-id snd_… --send-status sent # log the human sendSet your startupkit_project first — prospects and sends are tracked per project. For self-serve directory targets, use startupkit_submissions instead.