41 ChatGPT prompts for SaaS founders in San Francisco to map local partnership opportunities

If you build SaaS in San Francisco, partnership opportunities are sitting two blocks away from you right now. The hard part isn’t finding them. It’s turning a casual SoMa coffee meeting into a real co-sell motion. These 41 ChatGPT prompts for SaaS local partnership San Francisco founders are the playbook I wish I had when I was running my first ecosystem program out of a coworking space on Market Street.

Here’s the thing nobody tells you at SaaStr. Crossbeam’s 2024 analysis of thousands of partner-sourced deals on its network found that involving a partner in a deal lifts average win rate by 11.7%, and that number jumps to 58.6% for companies that fully activate sales seats on Crossbeam for Sales (Crossbeam, November 8 2024). That’s not a soft “partnerships are nice.” That’s a 6× multiplier hiding in your CRM.

And the SF network is uniquely good at producing that lift. Startup Genome’s 2026 work catalogs 5.5M+ companies across 350+ ecosystems, with San Francisco as a flagship cluster (Startup Genome, 2026). Add Y Combinator’s SF-based portfolio, the SoMa and Mission Bay startup density, the Stripe / OpenAI / Anthropic / Mercury / Linear / Vercel / Figma / Notion cluster, and you’ve got more potential co-sell partners in a one-mile radius than most cities see in a year.

I’m going to give you 41 extremely detailed prompts, grouped the way a real SF founder works: ICP overlap first, then account mapping, co-marketing, integrations, resellers, and finally outreach. Every prompt has a full multi-line body, an example output, and a pro tip. The total word count is long on purpose - paste them in, edit the bracketed fields, and ship.

Pull quote: “Companies on the Crossbeam network that fully activate sales-team seats see an average 58.6% lift in win rate when partners are involved in deals - versus 11.7% for the network as a whole.” - Crossbeam, November 8 2024

Quick answer: what you’ll get from this guide

If you only have five minutes, here’s the headline:

• 41 copy-paste prompts grouped into 6 SF-relevant categories.
• A 4-quadrant partner map to score any local partner in under 10 minutes.
• A 30-day “SF partnership sprint” calendar you can start Monday.
• A People Also Ask FAQ that pulls together the most-searched 2026 questions.

Skip to the section that matches your stage. If you’re pre-PMF, start with “ICP overlap.” If you’re at $1M+ ARR, jump to “Outreach and first-meeting prompts.” If you sell to enterprise, go straight to “Account mapping.”

Why San Francisco is still the most underrated partnership lab in 2026

San Francisco is the densest B2B SaaS partnership environment on the planet in 2026, even with all the headlines about founders decamping to Miami or Austin. The YC W26 batch alone produced dozens of SF-based B2B startups. OpenAI, Anthropic, Stripe, Mercury, Linear, Vercel, Notion, Figma, and dozens more sit within a 20-minute Lyft of each other, and almost all of them have public partner programs you can read about today.

Crossbeam’s December 2025 case study on CrowdStrike’s ecosystem rebuild noted that the company is projecting $7.9B in revenue by 2028 and that its partner-delivered services ratio is now $7 in services revenue for every $1 of CrowdStrike product sold (Crossbeam, December 11 2025). That kind of leverage only happens when there’s a real co-sell motion - and SF is the easiest place in the world to start one because of who your neighbor is.

Jay McBain, the chief analyst at Omdia who’s spent 30 years studying the channel, said in Crossbeam’s ELG Summit recap that 89% of sellers now use partners every day, and 84% of quota-hitters say partners were the reason they made number (Crossbeam, December 16 2025). Salesforce’s State of Sales data backs this up, and McBain also pointed out that the average deal now involves seven partners - and he predicts that will grow to seventeen within the decade.

Ecosystem-Led Growth (ELG) is the term the Crossbeam and Bob Moore community uses for treating your partner network as your #1 growth channel. It’s not the same as “channel sales” or “affiliates.” It’s a GTM motion where you co-sell, co-market, and co-build with non-competing SaaS companies who share your ICP. San Francisco is the city where ELG is the easiest to execute, because density creates overlap and overlap is the raw material.

The single best stat to remember when you’re pitching this internally: a connected ecosystem of 50+ partners correlates with a 37.1% average win-rate lift in deals that include a partner (Crossbeam, November 8 2024). If you want that lift, you need a partner map. That’s exactly what these 41 prompts build.

The 4-quadrant partner map (use this before any prompt)

Before you fire up ChatGPT, plot every potential SF partner on this 2×2. It takes 10 minutes and saves you from months of bad calls.

• Quadrant A - High ICP overlap, High reach: Dream partners. Examples: if you sell to RevOps and partner with a HubSpot, Salesforce, or Gong.
• Quadrant B - High ICP overlap, Low reach: Niche specialists. Examples: a small SoMa-based analytics consultancy with 30 customers.
• Quadrant C - Low ICP overlap, High reach: Vanity. Skip unless they pay you.
• Quadrant D - Low ICP overlap, Low reach: Filler. Ignore.

Run every prompt below with the Quadrant A and B names in mind. Everything else is noise.

SECTION 1 - ICP overlap & adjacency prompts (Prompts 1–6)

These six prompts are how you turn a vague “we should partner with them” feeling into a real ICP match score. Use them once per prospect.

Prompt 1 - ICP overlap score for a specific SF partner

Purpose / context: Use this to quantify how much customer overlap you really have with a target partner. Most founders guess. This forces a hard, evidence-based read.

You are a partnership strategist. I'm the founder of [YOUR SAAS COMPANY], a [CATEGORY] tool that helps [ICP ROLE] at [ICP COMPANY SIZE] do [OUTCOME].

Score the ICP overlap between us and [PARTNER NAME], a [THEIR CATEGORY] tool based in [CITY] that helps [THEIR ICP] do [THEIR OUTCOME].

Use a 1-10 scale. Score in three sub-categories:
1. Customer persona overlap (1-10)
2. Buyer role overlap (1-10)
3. Use-case adjacency (1-10)

For each sub-category, give:
- A 1-sentence justification citing publicly available evidence (job postings, G2 reviews, their homepage, LinkedIn)
- A confidence level (low / med / high)

Then give a weighted average and a clear verdict:
- 8+ : "Tier 1 - pursue co-sell aggressively"
- 6-7 : "Tier 2 - co-marketing only"
- Below 6 : "De-prioritize"

End with 3 specific signals I could verify on LinkedIn Sales Navigator, G2, or BuiltWith to confirm the score.

Example output (abridged): “ICP overlap score: 7.4/10. Customer persona 8: both target Series A–C ops leaders. Buyer role 7: same VP of Ops, different title wording. Use-case 7: complementary (you do workflow, they do analytics). Verdict: Tier 2. Verify by checking 5 shared customers on LinkedIn Sales Navigator.”

Pro tip: Run this on the top 20 partners on your list. Anything under 6 goes in a “later” spreadsheet. Anything 8+ gets a Slot in your 30-day sprint.

Prompt 2 - Adjacent ICP discovery for SoMa / Mission Bay

Purpose / context: Find SaaS companies within a 1-mile radius of your office whose customers match yours. Use this to seed your first outreach list.

Act as a SF-based GTM operator. I sell to [ICP] in [INDUSTRY].

List 30 SaaS companies headquartered in SoMa, Mission Bay, or the Financial District of San Francisco (within a 1-mile radius of [STREET ADDRESS]) that:
1. Sell to a non-overlapping buyer (so we don't compete for the same budget line)
2. Target the same end customer persona
3. Have raised between $2M and $30M in the last 24 months
4. Are post-PMF (have a public case study or a G2 listing with 20+ reviews)

For each company, give:
- Company name
- HQ street (approximate)
- One-line description
- Why the ICP overlaps
- A "warm intro path" suggestion (mutual YC batch, shared investor, common SoMa event)

Exclude: OpenAI, Anthropic, Stripe, Mercury, Linear, Vercel, Notion, Figma (too big for a first play).

Example output (snippet): “1. Pair AI - 564 Market St - AI co-pilot for accountants - overlaps with your FinOps ICP - intro via YC W25. 2. Tavus - 535 Mission - personalized video for RevOps - overlaps with your RevOps ICP - intro via SoMa AI meetup.”

Pro tip: Cross-reference this list with Crossbeam, PartnerStack, and Partnerbase. Anything already in those networks has already done the paperwork - half the friction is gone.

Prompt 3 - ICP adjacency map for the broader Bay Area

Purpose / context: Same as Prompt 2, but expands to Oakland, Berkeley, and South Bay so you can run a full Bay Area sweep.

Expand the previous list to 60 SaaS companies across the SF Bay Area (San Francisco, Oakland, Berkeley, Palo Alto, Mountain View, South San Francisco). Same criteria: non-overlapping product, same buyer persona, post-PMF, $2M–$30M raised in last 24 months.

Group them by neighborhood:
- SoMa / Mission Bay (target 15)
- Financial District (target 5)
- Oakland / Emeryville (target 10)
- Berkeley (target 5)
- Palo Alto / Stanford (target 10)
- Mountain View / Googleplex area (target 5)
- South SF biotech corridor (target 5)
- Other (target 5)

For each, give the "intro path" suggestion and rank by warmth (e.g., 1st-degree LinkedIn, shared investor, event collision).

Pro tip: “Intro path warmth” is the cheat code. A 1st-degree LinkedIn connection beats a cold email 10:1. Always do that pass first.

Prompt 4 - “Who are we actually losing to?” competitor-allies map

Purpose / context: Your real partner pool isn’t “anyone in our category.” It’s companies that lost deals against you - and might be open to a co-sell referral agreement.

I'm the founder of [YOUR SAAS]. My most common losses go to [COMPETITOR A], [COMPETITOR B], and [COMPETITOR C].

For each of those three competitors, identify 5 SaaS companies in the SF Bay Area that:
1. Have a public integration or co-marketing relationship with them
2. But whose customers are also a fit for my product
3. And who are NOT contractually locked into exclusivity with that competitor

These are my "competitor-allies" - companies that would happily refer me the 20% of deals where my competitor is a bad fit, if I return the favor.

For each, suggest a specific first-meeting agenda: 30 minutes, no pitch, just an honest "let's compare notes on where each product shines."

Example output (snippet): “Competitor A has a co-marketing deal with Linear. Linear’s customers often need what I sell when their PM workflow is solid but their customer-facing ops are not. Reach out to Linear’s head of partnerships via the YC W22 alumni Slack.”

Pro tip: This is the most under-used prompt on this list. Founders obsess over direct competitors and ignore the ally pool.

Prompt 5 - ICP-disjoint / “co-sell referral” partners

Purpose / context: A co-sell referral deal is the cheapest partnership you can sign. No integration, no co-marketing, no MDF. Just a “send me your overflow” agreement.

For my SaaS ([YOUR CATEGORY] for [ICP]), identify 8 Bay Area SaaS companies whose ICP is the same persona as mine but whose problem space is genuinely disjoint from mine - meaning a customer could buy both without any feature overlap or cannibalization.

For each, draft a 1-paragraph "referral trigger" description: under what specific customer situation would the partner logically refer me? And vice versa, when would I refer them?

Format as a table:
| Partner | Adjacent category | When to refer them | When they'll refer me |

Pro tip: A clean referral trigger (“when a customer is scaling past 50 engineers AND needs observability”) beats vague “we should partner” intros 9 times out of 10.

Prompt 6 - “Map my ICP to SF neighborhoods” prompt

Purpose / context: SF is a city of micro-clusters. Your ICP’s office location tells you where to host events and which meetups to sponsor.

My ICP is [ROLE] at [COMPANY TYPE] in [INDUSTRY]. 

List 5 SF neighborhoods (zip codes included) where this persona physically clusters, and explain why. For each neighborhood, name 2 specific venues, meetups, or co-working spaces where you can find 20+ of them in one room on a Tuesday.

Examples of clustering logic: 
- Biotech founders cluster near Mission Bay / UCSF
- Hard-tech founders cluster near Dogpatch / Pier 38
- Fintech founders cluster near SoMa / Financial District
- Climate-tech founders cluster near Hayes Valley / Impact Hub
- B2B SaaS founders cluster near SoMa / Founders Hall / Galvanize

For each neighborhood, give a 1-sentence "first-meeting venue" pick.

Pro tip: Run the same prompt for “where do they live” and “where do they go on weekends.” A Saturday farmer’s market intro beats a Tuesday Slack DM.

SECTION 2 - Account-mapping & shared-customer prompts (Prompts 7–12)

Account mapping is the practice of comparing your customer list with a partner’s customer list to find overlap. The legal-safe way to do this in 2026 is via Crossbeam, PartnerStack, or Reveal. These prompts make sure the data you put in is good.

Prompt 7 - Build a Crossbeam-style overlap brief

Purpose / context: When you join a partner on Crossbeam, the first thing they ask for is an “overlap brief.” This prompt drafts yours in 15 minutes.

I'm setting up a Crossbeam account mapping with [PARTNER NAME]. 

Generate an "Overlap Brief" I can paste into the partner portal. Sections:
1. Who we are (3 sentences)
2. Who we serve (3 bullets, ICP focus)
3. Our current customer count and rough ARR
4. The 3 product integrations or use cases where our tools meet
5. The 5 customer segments where overlap is most likely (e.g., Series B SaaS in FinOps)
6. Our preferred co-sell motion (referral / reseller / integration)
7. A point of contact: name, role, email

Tone: peer-to-peer, not corporate.

Pro tip: Add a sentence at the end: “If our overlap is below 5% of accounts, let’s both be honest and deprioritize.” Crossbeam’s data shows that SMBs with 5–10 connected partners see only a 4.6% win-rate lift - not worth the time (Crossbeam, November 8 2024). Aim for ≥10% overlap or walk.

Prompt 8 - Draft a “joint customer profile” (JCP)

Purpose / context: A JCP is the canonical document two partners use to decide when to refer. Treat it like a shared ICP.

I'm building a Joint Customer Profile (JCP) with [PARTNER NAME] for our co-sell motion.

Generate a JCP with these sections:
1. Joint persona: role, seniority, company stage, industry
2. Trigger events that signal a fit (e.g., "they just raised Series A and posted a RevOps lead job")
3. Disqualifiers (e.g., "pre-PMF startups, public companies, agencies")
4. Typical deal size for each side
5. Sales cycle overlap
6. The 3 most common objections each side handles

End with a 1-paragraph "shared pitch" we can both use to describe the joint value prop.

Pro tip: Save the JCP as a Notion doc. Reference it in every partner QBR. Drift is the #1 reason co-sell motions die.

Prompt 9 - Account-list segmentation for a partner

Purpose / context: Once you have an account map, you need to slice the overlap into “act now,” “nurture,” and “ignore.” This prompt does the slicing.

Here is my current account list (paste a sample or describe it: 250 customers, mix of SaaS, e-commerce, fintech, with $50K–$5M ARR).

And here is the overlap report from Crossbeam with [PARTNER NAME] (paste or describe: 38 shared accounts, top 3 verticals are fintech, SaaS, marketplaces).

Segment the 38 shared accounts into 3 buckets:
- A - "Act now": high ARR, active deal, or recent press
- B - "Nurture": good fit but no active motion
- C - "De-prioritize": low fit, churn risk, or partner conflict

For each account, give a 1-line reason. Then give me a 30-day sequence of co-sell touches (call, email, joint event, case study request) for the A bucket only.

Pro tip: Don’t try to do all 38. Pick the top 5. Ship one co-sell win with them. Then expand. Crossbeam’s data is clear: deeper engagement with fewer partners beats shallow touches with many.

Prompt 10 - “Who owns the customer?” - internal handoff brief

Purpose / context: A common co-sell landmine: the prospect gets pitched twice, by you and the partner, and the messaging conflicts. This prompt forces alignment.

I'm in active co-sell with [PARTNER] on a deal at [PROSPECT COMPANY]. 

The deal:
- ACV: $[X]
- Champion: [NAME, TITLE]
- Pain points: [LIST]
- Decision timeline: [DATE]

Draft a 1-page "internal handoff brief" that:
1. Defines who owns the first call (us or partner)
2. Defines who owns the demo
3. Defines who owns pricing
4. Defines who owns the close
5. Names the "tiebreaker" if we disagree on positioning
6. Lists the 3 things we will NOT say about the partner (e.g., don't promise features they don't have)

Tone: candid, no ego, "we're one team."

Pro tip: Email this to the partner account exec before the joint call. Save replies. If you ever need to renegotiate the partnership, you’ll have the paper trail.

Prompt 11 - Joint pipeline review meeting agenda

Purpose / context: A monthly joint pipeline review is the single highest-ROI meeting in ELG. Use this prompt to draft a 30-minute agenda that doesn’t waste anyone’s time.

I'm setting up a recurring monthly joint pipeline review with [PARTNER NAME]. 

Generate a 30-minute agenda for our first call. Sections:
1. 5 min - wins since last call (named deals)
2. 10 min - open shared deals (one slide each)
3. 5 min - new shared prospects (account map deltas)
4. 5 min - joint marketing activity (co-webinar, co-paper, joint event)
5. 5 min - open issues and Q&A

Also propose 3 KPIs we should track on a shared dashboard:
- Number of co-sourced opportunities
- Number of co-closed-won deals
- Average cycle time for co-sourced vs. solo deals

Make the agenda an email I can paste and send.

Pro tip: Stick to 30 minutes. Anything longer means you’re compensating for bad prep.

Prompt 12 - Joint case study brief

Purpose / context: The fastest way to scale a co-sell motion is a public case study. Use this when one of your shared customers agrees to be quoted.

We just closed a co-sell deal at [CUSTOMER NAME] with [PARTNER NAME].

Draft a 1-page joint case study brief. Sections:
1. Customer background (industry, stage, ARR, team size)
2. The problem (in the customer's own words - use quotes from the kickoff call)
3. Why both products (split the "before" state and the "after" state)
4. The implementation (3-4 bullets, honest about friction)
5. The result (3 measurable outcomes: time saved, revenue lift, churn reduced)
6. A 1-line pull quote from the customer
7. A 1-line pull quote from the partner

Format: Notion / Substack-style, scannable in 60 seconds.

Pro tip: Get the customer on a 20-minute recorded call. Use the transcript to write the case study. Don’t let your marketing team ghost-write it without the customer on the line.

SECTION 3 - Co-marketing prompts (Prompts 13–18)

Co-marketing is the cheapest GTM channel for SF founders. You split the cost of a webinar, a dinner, a research report, or a podcast with a partner. Done well, it’s also the best source of net-new leads.

Prompt 13 - Joint webinar topic generator

Purpose / context: Generic “AI for SaaS” webinars don’t convert. Specific, named, contrarian topics do. Use this to find your angle.

I'm [YOUR SAAS] and I want to run a joint webinar with [PARTNER NAME].

Our overlapping ICP is [ICP]. The partner focuses on [THEIR CATEGORY], I focus on [MY CATEGORY].

Generate 8 webinar topic ideas. For each, give:
- A working title (under 60 characters)
- A 1-sentence hook (the contrarian angle)
- The 3 most likely attendees (title + company stage)
- A 1-sentence CTA ("By the end, you'll know X")
- A 5-word title for the follow-up eBook

Avoid: "the future of X," "best practices," and any topic a tier-1 vendor already dominated.

Example output (snippet): “Topic 4: ‘Why your RevOps team is wasting 40% of their week on handoffs - and what to do about it.’ Attendees: VP RevOps at Series A–C SaaS. CTA: ‘You’ll leave with a handoff audit template.’ eBook: ‘The RevOps Handoff Audit.’”

Pro tip: Run this against 3 different partners. Pick the topic where at least 2 of them independently land on the same hook. That’s your real category tension.

Prompt 14 - Joint dinner invite copy

Purpose / context: A small, in-person dinner in SF with 8–12 ICP-matched prospects and a partner is the highest-trust co-marketing play you can run.

I'm hosting a small founders' dinner in SoMa with [PARTNER NAME]. Theme: [TOPIC]. Max 10 guests, 6-course menu at [VENUE].

Draft the invite email. Constraints:
- Under 90 words
- Tone: peer-to-peer, no marketing voice
- Subject line under 7 words
- Mention: the date, the venue neighborhood, the co-host
- Include a single yes/no question, not a calendar link
- 1 PS line that signals scarcity ("we cap at 10")

Give 3 subject-line variants.

Pro tip: Always do the venue walkthrough the day before. SF kitchens change menus without notice. Confirm the dietary restrictions in writing 48 hours out.

Prompt 15 - Joint research report outline

Purpose / context: A 12-page co-branded research report on a niche ICP pain point is a top-of-funnel machine. It’s also a great excuse to interview 20 shared prospects.

I want to publish a joint research report with [PARTNER NAME] on the topic: [TOPIC].

Generate a report outline. Sections:
1. Title (under 60 characters, with a number)
2. Subtitle (the contrarian promise)
3. Methodology (how many respondents, who, when, how recruited)
4. 5 chapter titles, each tied to a single surprising finding
5. 2 sidebar interviews (titles: "The contrarian" and "The pragmatist")
6. The "So what" - 5 bullets of what to do Monday morning
7. The "What's next" - 3 predictions for the next 12 months

For each chapter, give a 1-sentence "if you only read this" summary.

Pro tip: Don’t fake the data. If you can only get 30 survey respondents, run with 30 and own the small-N. SF founders respect honesty more than fake precision.

Prompt 16 - Co-branded landing page copy

Purpose / context: After a webinar, dinner, or report, you need a co-branded landing page to capture and qualify leads. This prompt drafts the whole thing.

Write the copy for a co-branded landing page promoting [ASSET] (e.g., the joint report above).

Structure:
1. Hero: H1, H2, single CTA button text
2. Social proof bar: 4 partner / customer logos (use placeholders)
3. 3-bullet "what you'll learn"
4. 1 quote from a named expert (use placeholder)
5. The CTA form: 5 fields max
6. A short "about the partners" section

Tone: direct, no fluff, no "delve." 

Total length: under 250 words.

Pro tip: Use a single, clean URL like /partners/[name]-report-2026. Share it everywhere. Track UTMs religiously.

Prompt 17 - Joint podcast pitch to a host

Purpose / context: Getting on a B2B podcast in 2026 is still one of the best trust-builders. Co-pitch with a partner to get on twice as fast.

Draft a pitch email to a B2B podcast host that I and [PARTNER NAME] want to be on together.

Constraints:
- Under 120 words
- The hook is a contrarian stat or claim, not "we'd love to chat"
- Mention both of our companies with a 1-line bio each
- Offer 3 specific topic angles the host can pick from
- Suggest a "double interview" format (both of us, host moderates)
- End with a calendar link to next Tuesday's slots

Give 2 subject-line variants.

Pro tip: Pre-fill the calendar with 3 specific time slots. Hosts are busy. Make the “yes” path one click.

Prompt 18 - Newsletter swap / co-mention brief

Purpose / context: Founder-led newsletters (Lenny’s, Demand Curve, Kyle Poyar’s, etc.) are still the highest-trust channel for SF SaaS buyers. A partner swap is the easiest win.

I run a weekly newsletter for [ICP] with [X] subscribers. [PARTNER] runs a weekly for [THEIR ICP] with [Y] subscribers.

Draft a one-time newsletter swap. For my newsletter, I'll mention [PARTNER] in a "Tool I use" section. For theirs, they'll mention me in the same.

Generate:
- My mention copy (under 80 words, 1 link, 1 CTA)
- Their mention copy (same length, same format)
- A short Slack DM I can send to ask the partner if they're up for it
- A 1-line "what to do if they say no" fallback

Pro tip: Don’t overthink. The mention doesn’t have to be a paid sponsorship. A genuine “I use this daily” line beats a banner ad every time.

SECTION 4 - Integration & technical-partner prompts (Prompts 19–24)

Integration partnerships are the deepest form of ELG. They require engineering time, so the bar for the partner is high. These prompts help you find the right ones and make the technical pitch land.

Prompt 19 - Integration partner shortlist for a given API surface

Purpose / context: Start with what you already expose. Then find the SaaS companies in SF whose product would be enriched by plugging into yours.

My SaaS exposes these APIs: [LIST]. The data model includes [LIST]. The auth is OAuth 2.0.

List 15 SF-based SaaS companies (post-PMF, $2M–$50M raised) that would benefit from a 2-way integration with us. For each, give:
- Company name
- Their relevant API surface
- The specific use case our combined product would unlock
- A rough engineering-effort estimate (low / med / high) on their side
- A 1-sentence "first DM" pitch

Pro tip: Filter on engineering effort. Anything “high” gets deprioritized unless the partner is huge. You don’t have time to fight a 6-month integration for a 3% lift.

Prompt 20 - Integration ROI / co-build pitch

Purpose / context: Use this when you approach a potential integration partner. The goal: frame it as a co-investment, not a favor.

I'm pitching [PARTNER NAME] on a 2-way API integration. 

Draft a 1-page pitch (Notion-ready) covering:
1. The customer problem neither of us solves alone
2. The proposed integration architecture (high level, 3-4 bullets)
3. The customer-facing UX of the integrated product (sketch the flow)
4. Engineering effort on each side (rough story points)
5. Joint GTM plan (1 webinar, 1 case study, 1 marketplace listing)
6. Revenue model: who's the prime, who's the sub? Co-sell split?
7. Sunset criteria: if usage is below X installs in 6 months, we part ways

Tone: peer-to-peer, "let's build something neither of us can build alone."

Pro tip: Always include sunset criteria. It signals seriousness. Most integration deals die from a lack of measurable success criteria, not bad tech.

Prompt 21 - Marketplace listing for AWS, Azure, or Google Cloud

Purpose / context: Hyperscaler cloud marketplaces are one of the fastest-growing routes to market in 2026. Jay McBain projects 82% CAGR in route-to-market activity via cloud marketplaces, and predicts that by 2027 half of all marketplace transactions will include a partner-created private offer (Crossbeam, December 16 2025).

Generate the listing copy for [YOUR SAAS] on the [AWS / Azure / Google Cloud] marketplace.

Sections:
1. Product name + 1-line tagline
2. The buyer pain (3 bullets)
3. Key features (5 bullets, each tied to a buyer outcome)
4. Pricing summary (BYOL, hourly, annual - your choice, justify it)
5. Customer logos (placeholders) and 1 short case study
6. Integration highlights (which AWS / Azure / GCP services we use)
7. CTA: "Buy on Marketplace" and "Contact for co-sell"

Then list the 5 SF-based partners I should approach first for a private offer.

Pro tip: Don’t list on all three marketplaces at once. Pick the one your ICP’s procurement team uses. Ask 3 customers which one. Then go deep there.

Prompt 22 - Co-built product spec (RFP style)

Purpose / context: When you and a partner are serious about a co-built feature (not just a thin integration), you need a spec. This prompt drafts the v0.

I'm co-building a feature with [PARTNER NAME]: a [FEATURE NAME] that lives in [WHICH PRODUCT] but pulls from [WHICH OTHER PRODUCT].

Write a 1-page product spec. Sections:
1. Problem statement (the user pain, in 1 paragraph)
2. User story (As a [persona], I want to [action], so that [outcome])
3. UX flow (3-5 steps, with a sketch description)
4. API contract (endpoints, auth, rate limits)
5. Data model (the new fields / tables)
6. Out of scope (what we're NOT building in v1)
7. Success metrics (3 KPIs, with target numbers)
8. Timeline (8 weeks, with 2-week milestones)
9. Open questions (5 bullets the spec doesn't yet answer)

Pro tip: Treat this as a living doc, not a final answer. The “open questions” section is more important than the spec itself - it tells you both what you don’t know.

Prompt 23 - Technical partner “founder-to-founder” email

Purpose / context: Most co-build intros die at the engineering level. Use this to short-circuit the typical “send to partnerships@” loop.

Draft a founder-to-founder email to [NAME] at [PARTNER]. The email proposes a 2-week scoping sprint for a co-built feature.

Constraints:
- Under 150 words
- Open with a peer-credibility line (a shared investor, a shared customer, a recent article they wrote)
- State the customer pain in 1 sentence
- Propose a 2-week scoping sprint: 2 calls, 1 shared spec, no code yet
- Offer to do the work, not "let's explore"
- Sign off with a specific time to reply by

Give 2 subject line variants.

Pro tip: Always reference something real they wrote or said. A line like “I read your post on the [X] architecture choice - it lined up with what we’re seeing in our API logs” beats “love what you’re building” by 100x.

Prompt 24 - Joint developer documentation outline

Purpose / context: Once the integration ships, you need docs that read as one product. This prompt outlines the doc set.

Outline a joint developer documentation site for the integration between [YOUR SAAS] and [PARTNER SAAS].

Sections:
1. Quickstart (5 min to first API call)
2. Authentication (OAuth flow, scoped tokens, refresh logic)
3. Core concepts (the data model on each side, mapped)
4. Common use cases (3-4 recipes with copy-paste code)
5. Webhooks and event handling
6. Rate limits and pagination
7. Error handling (the top 5 errors and how to fix them)
8. Sandbox vs. production differences
9. Support and escalation path (which team owns which issue)
10. Changelog

For each section, give a 1-sentence "if you're stuck, read this" note.

Pro tip: Ship the docs before the marketing site. The docs are what your developers actually need. The marketing page can wait.

SECTION 5 - Reseller & agency prompts (Prompts 25–30)

Resellers are partners who sell your product as part of a bigger bundle. Agencies are partners who deliver your product as a service. SF has fewer of these than Austin or London, but the ones here are gold.

Prompt 25 - Ideal Reseller Profile (IRP) generator

Purpose / context: Crossbeam’s playbook on IRPs (Crossbeam, 2025) is the clearest framework. This prompt builds yours.

Generate my Ideal Reseller Profile (IRP) for [YOUR SAAS].

Sections:
1. The reseller's ICP (who they sell to, what stage, what industry)
2. Their internal GTM motion (inbound, outbound, ABM)
3. Their team shape (do they have dedicated sales reps or a small founder-led team?)
4. Their tech stack (HubSpot? Salesforce? Apollo? Clay?)
5. Their service model (do they only resell, or do they also implement?)
6. Their financial health (rough revenue, funding, headcount)
7. Their cultural fit (do they value long-term customer success or quick wins?)
8. The disqualifiers (e.g., they sell to consumers, they're in a regulated industry with no compliance team)
9. The "10-question screener" I can send in a first meeting

End with a short paragraph on how to find 10 IRP-fit resellers in SF.

Pro tip: Always include a “decline letter” template. Most founders avoid saying no. A clear decline keeps your brand strong.

Prompt 26 - Reseller agreement outline

Purpose / context: A clean reseller agreement prevents 90% of the conflict you’ll have. Use this as a starting point - then have a real lawyer review it.

Draft a reseller agreement outline between [YOUR COMPANY] and [RESELLER NAME]. Sections:
1. Definitions (what counts as a "sale," a "lead," a "qualified opportunity")
2. Territory and exclusivity
3. Pricing and discount structure
4. Quota and minimum commitments
5. Marketing development funds (MDF)
6. Co-marketing responsibilities
7. Lead registration and conflict resolution
8. Customer support ownership
9. Payment terms and refund handling
10. Termination clauses (90-day cure period, cause, etc.)
11. Compliance and ethics
12. Signatures

For each section, give a 1-sentence plain-English explanation in the margin.

Pro tip: Pay a startup-friendly lawyer $2K to turn this outline into a signed contract. It’s the best GTM investment you’ll make.

Prompt 27 - Agency partner shortlist for SF services firms

Purpose / context: SF agencies (especially RevOps, GTM-engineering, and analytics shops) are a hidden co-sell channel.

List 15 SF-based agency firms that:
1. Have 10–80 employees
2. Implement tools in [YOUR CATEGORY] for clients
3. Have a clear GTM (own a podcast, write a Substack, or run a private Slack community)
4. Are open to rev-share or referral-fee structures
5. Have a public customer list (3+ named logos on their site)

For each, give:
- Agency name
- Their specialty
- A 1-sentence intro path
- A 1-sentence rev-share proposal

Pro tip: A 10% rev-share for the life of the customer is standard. Don’t be stingy on this. A great agency partner will pay for itself in 3 months.

Prompt 28 - Joint services scoping conversation

Purpose / context: When a reseller / agency wants to scope a joint engagement, use this to keep the meeting focused on outcomes.

I'm in a 30-min scoping call with [AGENCY NAME] about a joint engagement for a [PROSPECT]. 

Generate an agenda. Sections:
1. 5 min - the prospect's business outcome (not their feature wishlist)
2. 5 min - what each side will own
3. 5 min - the integration points (where our two products meet)
4. 5 min - pricing model (who charges what, what's the bundled SKU)
5. 5 min - timeline and milestones
6. 5 min - open issues and next steps

End with a "decision criteria" doc the prospect can use to choose us over a competitor.

Pro tip: Always leave the call with a written recap. If it’s not in writing, it didn’t happen.

Prompt 29 - Reseller enablement deck outline

Purpose / context: Most reseller decks are unreadable. The best ones are 10 slides and tell a story.

Outline a 10-slide reseller enablement deck for [YOUR SAAS]. Slide-by-slide:
1. Title (1 line, no taglines)
2. The customer problem in 1 picture
3. Our product in 3 screenshots
4. The 3 customer outcomes (each with a number)
5. The ICP (1 paragraph)
6. The competitive landscape (honest, including "where we lose")
7. The reseller motion (how you make money, in 1 line)
8. The sales process (5 steps, 1 line each)
9. The support and onboarding process
10. The first 3 steps to get started

For each slide, give a 1-sentence speaker note.

Pro tip: Get the reseller to read it back to you. If they can summarize it in 30 seconds, you nailed it.

Prompt 30 - Reseller QBR agenda

Purpose / context: A quarterly business review with a reseller is the single best way to keep the relationship healthy. Use this agenda monthly or quarterly.

I'm running a 60-min QBR with [RESELLER NAME]. 

Generate the agenda:
1. 5 min - wins this quarter (named deals, named customers)
2. 10 min - pipeline review (top 5 open opportunities)
3. 10 min - product updates from our side
4. 5 min - enablement gaps (where the reseller is blocked)
5. 10 min - joint marketing plan for next quarter
6. 10 min - financial reconciliation (invoices, MDF, rev-share)
7. 5 min - open issues and Q&A
8. 5 min - recap and action items

End with a 1-line email I can send the next morning summarizing the action items.

Pro tip: Never let a QBR end without 3 named action items and owners. No owners = no progress.

SECTION 6 - Outreach & first-meeting prompts (Prompts 31–41)

These are the prompts that turn a partner map into a calendar full of meetings. Use them in order. Don’t skip steps.

Prompt 31 - First-touch cold email to a partner head of partnerships

Purpose / context: Most partnership cold emails get ignored because they ask for a “meeting to explore synergies.” This one asks for something specific.

Draft a first-touch cold email to [NAME], Head of Partnerships at [PARTNER].

Constraints:
- Under 100 words
- Open with a peer-credibility line (1 sentence, no flattery)
- State the customer overlap in 1 sentence (with a number, not a vibe)
- Propose a 15-min call, not a 30-min call
- Attach nothing
- Sign off with a specific time to reply by

Give 3 subject line variants. Keep the tone: founder-to-founder, no "synergy."

Example opening: “Hey [Name] - saw Linear’s post on the [topic] and it lines up with what we’re seeing in our API logs. Looks like we share ~12 customers in the Series A SaaS FinOps space. Worth 15 min next week to compare notes?”

Pro tip: Send Tuesday or Wednesday, 8:15 AM Pacific. SF founders check email early. Avoid Mondays and Fridays.

Prompt 32 - Warm intro request to a mutual connection

Purpose / context: A 1st-degree intro converts 10× better than a cold email. Use this to draft the ask.

I want a warm intro to [PARTNER FOUNDER NAME] at [PARTNER COMPANY]. My connection at [MUTUAL] knows both of us.

Draft a Slack DM to [MUTUAL] asking for the intro. Constraints:
- Under 60 words
- 1 line on who I am
- 1 line on why I want to meet the partner
- 1 line on why it's a fit for the partner (not just for me)
- Make it easy to say yes: "if you can do an intro, here's a 1-line blurb you can paste"
- Make it easy to say no: "if it's weird, totally fine, no worries"

Pro tip: Pre-write the intro blurb. The mutual connection will paste it verbatim 80% of the time.

Prompt 33 - Cold LinkedIn DM to a partner AE

Purpose / context: Sometimes the partnerships lead is overloaded. Going directly to a partner AE works - but only if you don’t pitch.

Draft a cold LinkedIn DM to [NAME], Account Executive at [PARTNER COMPANY].

Constraints:
- Under 80 words
- No pitch
- Open with a specific observation about a recent account (a press release, a G2 review, a hiring move)
- State a specific reason the AE would benefit from knowing you (a shared customer, a competitive displacement, a referral)
- Ask for a 10-min call, not 30
- No attachments

Pro tip: AEs are quota-carrying. If you can show them a deal in their number, you have leverage. Use it carefully and don’t be sleazy.

Prompt 34 - First-meeting agenda for a partner intro

Purpose / context: Most first partner meetings are wasted. Use this agenda to keep it focused on outcomes.

I'm meeting [PARTNER] for the first 30 minutes. Draft an agenda.

Sections:
1. 2 min - intros (1 sentence each, no life story)
2. 5 min - what each side does (no slides)
3. 8 min - customer overlap (specific named accounts if possible)
4. 5 min - what we should co-build or co-sell first
5. 5 min - what we'd each need to make that happen (data, intros, eng time)
6. 3 min - next steps and decision criteria
7. 2 min - recap and email follow-up

The goal of this meeting is to leave with a decision: "yes, we co-sell" or "no, we don't." No "let's explore" allowed.

Pro tip: Always end with a forced binary. “Yes” or “no” beats “let’s circle back” every time.

Prompt 35 - First-meeting follow-up email

Purpose / context: The follow-up email is the real deliverable of a partner meeting. Send it within 4 hours.

I just finished a first meeting with [PARTNER NAME]. Draft the follow-up email. 

Constraints:
- Under 150 words
- Recap the 3 specific decisions we made (no vague "we discussed")
- List the 3 action items, with owners and dates
- Attach the JCP doc (Notion link)
- Propose the next meeting (date, time, agenda preview)
- Sign off with a peer-tone PS line

Pro tip: Never write “great chatting.” Always write “here’s the recap.” Operationally, not socially.

Prompt 36 - Mutual-action plan (MAP) for a live co-sell deal

Purpose / context: A Mutual Action Plan is the formal document that aligns two sales teams on a joint deal. Use this when you go from “exploring” to “real opportunity.”

I'm in active co-sell with [PARTNER] on a deal at [PROSPECT]. 

Generate a Mutual Action Plan (MAP). Sections:
1. Deal summary (1 paragraph)
2. Customer stakeholders (named contacts on each side, with role and influence)
3. Joint milestones (5-7, with target dates)
4. RACI chart (who's Responsible, Accountable, Consulted, Informed for each milestone)
5. Risks and assumptions (3-5)
6. Communication cadence (weekly call, daily Slack in the final 2 weeks)
7. Success criteria (the definition of "closed-won")
8. Post-close handoff (who owns the customer for the first 90 days)

Format as a table I can paste into Notion.

Pro tip: Treat the MAP as a contract. If either side misses a milestone, the deal is at risk. Flag it early.

Prompt 37 - “Should we partner?” decision matrix

Purpose / context: Use this when you’re on the fence about a partner. The matrix forces a real answer.

I'm deciding whether to formalize a partnership with [PARTNER NAME]. 

Score them on a 1-5 scale across 5 dimensions:
1. ICP overlap (5 = same buyer, 1 = totally different)
2. Reach (5 = huge ICP, 1 = niche)
3. Tech/integration fit (5 = clean API, 1 = ugly scraping)
4. Cultural fit (5 = our tempo, 1 = misaligned)
5. Strategic value beyond revenue (5 = category leadership signal, 1 = none)

Total = weighted sum. 
- 20+ : pursue aggressively
- 15-19 : pursue with low investment
- Below 15 : de-prioritize

Output the score and a 1-sentence verdict.

Pro tip: Score before the meeting. Don’t let the meeting score influence your read. Set the score in a Notion table you don’t share with the partner.

Prompt 38 - Quarterly partner portfolio review

Purpose / context: Founders lose track of partners. Run a portfolio review every 90 days to keep your top 5–10 partners healthy and prune the rest.

I have [N] active partnerships. Generate a quarterly portfolio review template.

For each partner, score:
- Last 90 days: revenue sourced (or pipeline sourced, if revenue isn't closed yet)
- Last 90 days: co-marketing activity
- Last 90 days: relationship health (1-sentence gut check)
- Next 90 days: planned activity

Then sort into 3 buckets:
- A - "Invest more" (top quartile)
- B - "Maintain" (middle)
- C - "Sunset" (bottom)

For each C-tier partner, draft a polite sunset email.

Pro tip: Sunset emails are hard. Be honest. “We’re refocusing on a smaller set of partners in 2026 and want to give you the heads-up.” Done.

Prompt 39 - 1-page “partner program” page for your site

Purpose / context: SF founders can move fast if your partner page exists. Use this to publish a simple, clear program page.

Generate the copy for a 1-page partner program site at [YOUR URL]/partners.

Sections:
1. Hero: H1, H2, 1-line description of the program
2. Who we partner with (3 bullets, ICP focus)
3. The 3 partnership types (referral, integration, reseller)
4. What we offer (revenue share, co-marketing, co-sell support)
5. What we expect (ICP, deal size, cadence)
6. A 1-paragraph "how to apply"
7. CTA: "Apply" button to a Typeform

Tone: clear, no marketing fluff, no "delve."

Pro tip: Make the application form 5 fields. Name, company, email, ICP overlap, what you sell. If you can’t describe the overlap in 1 sentence, you don’t have a fit.

Prompt 40 - Partner-of-the-year nomination write-up

Purpose / context: Publicly recognizing a top partner is the best retention hack. Use this to nominate them for an award or just to write a LinkedIn post.

I want to publicly recognize [PARTNER NAME] as my partner of the year. Draft a 200-word LinkedIn post. 

Constraints:
- Open with a specific, measurable outcome they helped create
- Name the humans involved
- Mention 1 friction point you worked through together
- End with a specific 2026 commitment
- No "synergy," no "delve," no "tapestry"
- Include a tag for the partner's company page

Pro tip: Screenshot the partner’s public reshare. Use it in your next partnership pitch deck.

Prompt 41 - 12-month partnership roadmap

Purpose / context: The last prompt. Use it to plan your whole year of partner activity, scoped to your stage.

I'm the founder of [YOUR SAAS], at $[ARR] ARR, selling to [ICP]. I'm in San Francisco. 

Generate a 12-month partnership roadmap by quarter.

Q1 - Foundation
- ICP map and partner shortlist (50 prospects)
- 5 first-meetings with Tier 1 partners
- 1 co-marketing event
- Crossbeam or PartnerStack setup

Q2 - Activation
- 2 signed co-sell deals
- 1 integration in development
- 1 joint webinar
- 1 joint case study

Q3 - Scale
- 5 active Tier 1 partners
- 1 marketplace listing
- 1 reseller onboarded
- 1 partner-sourced deal closed

Q4 - Optimize
- 50% of new pipeline partner-sourced
- 1 partner-led enterprise account closed
- 1 conference presence (SaaStr, Pavilion, or Summit)
- Q1 next year planning done

Adjust milestones to my actual ARR. For each quarter, name the top 3 risks and the early-warning signals.

Pro tip: Put this on a wall, not in a doc. The reason most partnership programs die is no one can see them.

Comparison table: prompt category vs. partner tier vs. expected output

Here’s the cheat sheet. Use it to pick the right prompt in the right moment.

Prompt category	Best partner tier	Primary output	Time to first value	Works for ARR stage
ICP overlap & adjacency (1–6)	All	Named list, scored	1–2 weeks	Pre-PMF to $5M
Account mapping (7–12)	Tier 1 only	Co-sell pipeline	30–60 days	$500K+
Co-marketing (13–18)	Tier 1 + Tier 2	Leads, brand	30–90 days	$1M+
Integration (19–24)	Tier 1 only	Co-built product	3–6 months	$2M+
Reseller / agency (25–30)	Specialized shops	Channel revenue	90+ days	$5M+
Outreach & first-meeting (31–41)	All	Calendar full of meetings	1–2 weeks	All stages

People Also Ask: 10 SF partnership questions, answered fast

1. What is the most important 2026 stat for SaaS partnership GTM?

The 58.6% win-rate lift for companies that fully activate sales-team partner data, per Crossbeam’s November 8 2024 analysis. That’s the number to put in your internal pitch.

2. How do I find SaaS partners in San Francisco specifically?

Use prompts 2 and 3 to generate a list of 30–60 nearby SaaS companies. Then validate with LinkedIn Sales Navigator, Harmonic.ai, and the Y Combinator directory. The SoMa, Mission Bay, and Financial District clusters are the densest.

3. What’s the difference between a referral partner and a reseller partner?

A referral partner sends you a lead and gets a one-time fee. A reseller partner sells your product as part of their bundle and gets a recurring rev-share. Referrals are 1:1; resellers are 1:many. Start with referrals, graduate to resellers only at $5M+ ARR.

4. How long does a partnership take to start generating revenue?

90 days is realistic for the first sourced deal. The Crossbeam data shows 50+-partner connected ecosystems see a 37.1% win-rate lift - but that ecosystem takes 12+ months to build (Crossbeam, November 8 2024). Plan in 90-day cycles, not 30-day ones.

5. What tools should an SF SaaS founder use for partner GTM in 2026?

The short list: Crossbeam for account mapping, PartnerStack for affiliate / referral, Apollo.io for prospecting, LinkedIn Sales Navigator for warm intros, Harmonic.ai for company signals, Paved for newsletter swaps, and ChatGPT for everything above. Optional: Reveal for partner data.

6. How many partners should an early-stage SaaS company have?

Crossbeam’s data is clear: stay in the 1–5 partner zone until you can fully activate them. The 5–10 partner “valley” only generates a 4.6% win-rate lift for SMBs (Crossbeam, November 8 2024). Wait until you have a partnerships manager before scaling past 5.

7. What is ecosystem-led growth (ELG)?

ELG is the GTM motion where you treat your partner ecosystem as your primary growth channel. It was coined by Bob Moore and the Crossbeam community. Jay McBain, Omdia’s chief analyst, has documented the rise of ELG across 30 years of channel data (Crossbeam, December 16 2025).

8. Should I prioritize co-marketing or integration partnerships first?

Co-marketing first, always. It’s faster, cheaper, and doesn’t require engineering. Integrations are a 3–6 month investment. Use the 90-day sprint to validate overlap with co-marketing, then invest in integration only with the partners that proved the ICP match.

9. What’s the role of Y Combinator in SF partner intros?

YC’s network is one of the most under-used partner-intro channels. Search the YC directory for batch mates, write a warm intro through the shared Slack, and offer to do a 2-week scoping sprint. YC alumni are 5–10× more likely to take a 15-min call with a fellow YC alum.

10. How is partner-sourced revenue measured in 2026?

Two metrics: (1) partner-sourced = deal originated by a partner, (2) partner-influenced = deal touched by a partner during the cycle. Track both. Crossbeam’s data shows that partner-influenced deals have an 11.7% higher win rate; the more partners involved, the bigger the lift (Crossbeam, November 8 2024).

A 30-day “SF partnership sprint” calendar

This is the playbook if you only have one month to make 12 months of partnership progress. Run it Monday.

Week 1 - Map

• Day 1: Run prompts 1–6. Build a 50-name prospect list.
• Day 2: Validate with LinkedIn Sales Navigator, Crossbeam, and Harmonic.ai.
• Day 3: Pick the top 10 Tier 1 partners.
• Day 4: Draft 10 first-touch emails with prompt 31.
• Day 5: Send the emails Tuesday 8:15 AM.
• Day 6–7: Prep for responses. Don’t send more emails.

Week 2 - Outreach

• Day 8: Send LinkedIn DMs to the AEs of the same 10 partners (prompt 33).
• Day 9: Book 5 first meetings.
• Day 10–12: Run the 5 first-meetings (prompt 34).
• Day 13: Send 5 follow-up emails (prompt 35).
• Day 14: Decide: yes, no, or “circle back in 60 days.”

Week 3 - Activate

• Day 15: For the 3 “yes” partners, set up Crossbeam or PartnerStack.
• Day 16: Draft JCP (prompt 8) with each.
• Day 17: Schedule the first joint pipeline review (prompt 11).
• Day 18: Plan a co-marketing event (prompt 14 or 16).
• Day 19: Post a public “looking for partners” thread on LinkedIn.
• Day 20–21: Rest. Or follow up on warm intros from prompt 32.

Week 4 - Scale

• Day 22: Send 10 more first-touch emails.
• Day 23: Run a “Should we partner?” matrix (prompt 37) on the 5 active partners.
• Day 24: Pick 1 to convert into a co-marketing event.
• Day 25: Send invites to a joint dinner (prompt 14).
• Day 26: Book the first co-sell deal review (prompt 36).
• Day 27: Write a 12-month roadmap (prompt 41).
• Day 28–30: Reflect. Write a 1-page “what worked, what didn’t” doc.

By the end of 30 days, you should have 3–5 active Tier 1 partners, 1 co-marketing event on the calendar, and 1 named co-sell deal in progress. That’s the floor. With more reps, you can double it.

Common mistakes SF founders make (and how to dodge them)

I’ve watched a lot of SF SaaS founders trip on the same rocks. Here are the biggest:

• Mistake 1 - Pitching the partner instead of the customer. Every partner email should reference a customer overlap. If you can’t, you’re cold-pitching, not co-selling.
• Mistake 2 - Confusing partnerships with affiliate marketing. Affiliate links are commodity. Co-sell is a strategic motion. Don’t conflate.
• Mistake 3 - Signing 30 partners and activating zero. The 5–10 partner valley kills more co-sell programs than bad products do (Crossbeam, November 8 2024). Stay small until each is fully activated.
• Mistake 4 - Letting sales reps run partnerships. AEs are quota-carriers. They can’t co-sell a deal they don’t own. Either hire a partnerships manager or do it yourself, founder-led.
• Mistake 5 - Skipping the JCP. Without a Joint Customer Profile, every co-sell is a coin flip. With one, it’s a playbook.
• Mistake 6 - Negotiating rev-share before there’s revenue. Most SF founders argue over 20% vs. 30% rev-share on a deal that doesn’t exist. Get the first deal closed, then renegotiate.
• Mistake 7 - Mistaking marketplace listings for partnerships. A listing on AWS Marketplace is a sales channel, not a partnership. The partner is whoever brings the private offer, per Crossbeam’s December 2025 writeup on marketplaces.
• Mistake 8 - Burning a partner on a bad customer. One churned customer can kill a co-sell motion. Always vet the customer jointly.
• Mistake 9 - Not tracking the right metrics. “Number of partners signed” is vanity. “Partner-sourced ARR” and “partner-influenced win rate” are what your CFO cares about.
• Mistake 10 - Treating the partner team as overhead. Your partner team is your second sales team. Fund them.

Final word: SF is still the place to do this

San Francisco is the only city where you can walk to a partner meeting, co-build a feature, and ship a co-marketing event in the same week. That density is unmatched. Jay McBain’s 30-year channel thesis is that partner-led growth becomes more important every year for the next 20 years (Crossbeam, December 16 2025). The 41 prompts above are how you operationalize that thesis in 2026.

The goal isn’t 41 prompts. The goal is 3 active partners, 1 closed co-sell deal, and 1 joint event in 90 days. Use the prompts. Edit the bracketed fields. Send the emails. Show up to the dinners. Then write back and tell me what worked.

If you only do one thing this week, run prompts 1–3 and build the list. The list is the asset. The prompts are the engine. The list is the moat.