Copyable template
Subject: Quick integration idea: [Their Product] + [Your Product] Hi [Founder or Partnerships First Name], I am [Your Name], founder of [Your Product] ([Your URL]). We help [shared audience] [plain description of what your product does]. A few of our users already run [Their Product] alongside [Your Product], and they currently have to [manual glue step between the two tools]. I checked your [API docs / webhook guide / integration directory] and realized we can build a clean [integration type, e.g., webhook sync or one-click export] on our side without taking any engineering time from your team. Here is what that could look like for both of us: - For your users: [concrete problem solved inside their workflow] - Engineering lift on your side: [None / just a sandbox API key and a listing review] - Once it is live: [simple co-marketing step, e.g., a short help doc on both sites or a mutual mention in our release notes] Would you be open to me building a working prototype first and sending you a two-minute video to review? Best, [Your Name] Founder, [Your Product] [Your URL]
When to use this template
Send this email to founders or partner managers at complementary, non-competing products that serve the exact same customer right before or right after your tool in the workflow. Integration partnerships work well for small SaaS products because you piggyback on existing integration directories, help docs, and user searches rather than fighting for cold attention.
Before pitching, verify that their product has a public API, webhook system, or Zapier/app marketplace so you are proposing something realistic. Leading with 'we will do the engineering work first' removes the biggest objection small teams have when evaluating partner requests.
How to fill each placeholder
- [shared audience]: Name the overlap plainly so the other founder sees immediately that you serve the same buyer without competing on core features.
- [manual glue step]: Describe the awkward CSV export, copy-paste, or fragile script mutual customers do right now. Real workflow friction beats abstract talk about 'synergy.'
- Engineering lift on your side: Be explicit that you are not asking their team to pause their roadmap. Asking only for a test account or a directory listing once the integration works dramatically raises the odds of a yes.
- [simple co-marketing step]: Keep the marketing ask proportionate to your size. A mutual help doc, integration directory card, or changelog mention is realistic; asking a much larger company for a dedicated email blast to their whole list is not.
- Prototype-first close: Offering to ship a quick working demo before scheduling a long partnership meeting shows execution speed and saves everyone a premature call.
Filled example (made-up product)
Example using a made-up European VAT invoice tool called PayReceipt: Subject: Quick integration idea: LedgerFlow + PayReceipt Hi Lukas, I am Maya, founder of PayReceipt (https://payreceipt.example). We help European micro-SaaS founders automatically generate localized VAT-compliant receipts and sync them to local bookkeeping software. A few of our users already use your bookkeeping tool LedgerFlow alongside Stripe, and they currently have to download monthly invoice PDFs by hand and re-upload them into LedgerFlow with manual VAT codes. I checked your public REST API docs and realized we can build a clean direct sync on our side that pushes categorized PDF receipts and VAT line items into LedgerFlow automatically, without taking any engineering time from your team. Here is what that could look like for both of us: - For your users: Stripe and Paddle receipts land in LedgerFlow pre-tagged by EU country VAT rate instead of sitting in an uncategorized inbox - Engineering lift on your side: Just a sandbox account so we can test edge cases, plus a review for your Integrations page once it is working - Once it is live: We will publish a step-by-step setup guide linking back to LedgerFlow and include it in our monthly product update Would you be open to me building a working prototype first and sending you a two-minute video to review? Best, Maya Founder, PayReceipt https://payreceipt.example
Mistakes to avoid
- Pitching a vague 'let us explore a strategic partnership' email with zero concrete proposal. Busy founders archive open-ended partnership emails immediately.
- Asking the partner's engineering team to build the integration for you when you are the smaller, newer product. Build on their public API first and bring proof.
- Pitching a direct competitor or an unrelated product just because they have a big audience. Partnerships only convert when the same user naturally uses both tools together.
- Overpromising traffic or user numbers you do not have yet. State your stage honestly and let the practical workflow benefit carry the pitch.
Related tools and guides
Free tool
Cold DM & Early Adopter Outreach GeneratorGenerate high-converting, non-spammy direct outreach templates for X, LinkedIn, and email to land your first 20 beta users.Free tool
Value Proposition & Hero Tagline GeneratorCraft punchy hero headlines, Steve Blank positioning formulas, and tight 60-character directory taglines.Founder guide
Cold Email for Solo Founders: How to Land Your First 10 B2B CustomersA plain outreach framework that doesn't feel pushy, protects your domain and doesn't need expensive lead lists.Founder guide
How to Get Your First 100 SaaS Users Without Paid AdsPractical, unscalable tactics for finding your first users and customers from a cold start, and how to tell which ones are working.More templates
Pritam Ghosh runs Hauntboard and maintains these templates.
Published · Updated
Ready to put your launch in front of real visitors?
A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.