KoltrixTriaging cold pitches in the team inbox without wasting hours
A playbook for handling vendor pitches in a shared inbox: a ten-second look, when to reply or decline, when to block, and keeping pitches out of customer mail.
On this page(11 sections)
Any address you publish attracts pitches: agencies offering leads, developers offering outsourcing, tools offering demos, and "following up on my last email" from someone you've never heard of. Most need no reply. A few are worth reading. The cost is the attention spent telling them apart, multiplied by everyone who sees the shared inbox.
This playbook gets that cost close to zero without accidentally ignoring the partnership email that actually matters.
The goal
Three outcomes, in order of importance:
- Cold pitches don't crowd out customer mail.
- The rare valuable pitch gets noticed.
- Nobody on the team spends more than a few minutes a day on this.
Step 1: Get pitches out of the main view
Pitches are only expensive when they sit between customer emails. Move them somewhere separate first; decide what to do with them second.
Options, from least to most effort:
- Category sorting. In Koltrix, AI sorts incoming mail into categories including Cold pitches, so vendor outreach lands outside Primary without any rules to write.
- Rules for repeat senders. If the same agency writes every month, a rule can label and archive their mail.
- A separate address. Some teams publish partners@ for partnership inquiries and keep it apart from support.
Whichever you use, the main view should contain customers, teammates, and people you're actually doing business with.
Step 2: Do the ten-second look
Once a day, someone scans the pitches pile. The scan is fast because you're only looking at sender, subject, and the first line. You're asking one question: could this matter?
Signals that a pitch deserves a real read:
- It references something specific about your product, not just your company name.
- It comes from a company you already use, recognize, or have considered.
- It proposes a partnership or integration that fits your roadmap.
- It's from a customer or a customer's colleague (pitches sometimes come from people who also use your product).
- It's a journalist, analyst or event organizer, which may be misfiled as a pitch.
Signals it can be ignored:
- Generic flattery ("I love what you're doing at [company]").
- Guarantees or round-number outcomes.
- Multiple follow-ups with no new information.
- Offers to fix problems you don't have.
Step 3: Decide what to do
Every pitch gets one of four outcomes:
| Outcome | When | Effort |
|---|---|---|
| Ignore and archive | Generic, irrelevant, mass outreach | None |
| Polite decline | A real person, plausible offer, not a fit right now | One snippet |
| Forward to an owner | Possibly relevant: partnership, integration, tool you're evaluating | One forward or link |
| Block | Repeat sender after a clear no, or obvious spam patterns | One click |
Most pitches fall into "ignore". That's fine. Not replying to unsolicited sales outreach is normal and widely understood.
Step 4: Keep a decline snippet
For pitches that deserve a response, a short, polite decline closes the loop and often stops the follow-up sequence:
Hi [name],
Thanks for reaching out. This isn't something we need right now, so
I'll pass for the moment. If that changes, we'll get in touch.
[team name]
Don't explain why. Don't invite them to check in later unless you mean it. Explanations invite rebuttals.
Step 5: Route the interesting ones to an owner
When a pitch might matter, don't reply from the shared inbox on the spot. Send it to whoever owns that area:
- Integrations and partnerships: the founder or product lead.
- Tools for a team's workflow: that team's lead.
- Press, events and podcasts: whoever handles communications.
Include one line on why you think it's worth a look. The owner decides whether to reply. This avoids three people replying to the same promising partner with three different answers.
Step 6: Block deliberately
Blocking is useful for persistent senders, but it's permanent and invisible. Block when:
- Someone keeps following up after you declined.
- A sender rotates addresses but keeps the same domain.
- The messages are clearly automated spam rather than a person.
Don't block broad patterns like entire free email providers, and don't block a company domain that customers might also use.
Step 7: Watch for disguised pitches
Some outreach is designed to look like a real conversation:
- "Re:" in the subject of a first message.
- "As discussed" or "following up on our call" when there was no call.
- Fake meeting invitations or calendar holds.
- "Quick question" subjects that lead straight into a sales offer.
These are irritating but harmless to ignore. The real risk is the opposite error: a genuine customer's terse "quick question" being dismissed as a pitch. When in doubt, check whether the sender's domain matches a customer.
Step 8: Assign the daily look
The scan should belong to someone. On a small team, fold it into the person handling daily triage. It takes a couple of minutes if pitches are already in their own pile.
A weekly variant works too: some teams check pitches once a week, on the theory that nothing in that pile is urgent. That's reasonable as long as journalists and event organizers, who do have deadlines, are caught by a rule or reach a different address.
What to avoid
- Replying to every pitch out of politeness. It confirms your address is active and invites more.
- Letting pitches sit in the main view "until someone gets to them". They multiply.
- Deleting immediately without a glance. You'll occasionally lose something useful.
- Engaging with aggressive follow-up sequences. Archive, decline once, or block.
Key takeaways
- Get pitches out of the main view first, with category sorting, rules, or a separate address.
- Scan the pile daily in seconds, looking only for signs it could matter.
- Use four outcomes: ignore, polite decline, route to an owner, or block.
- Keep one short decline snippet, and don't explain or invite follow-ups.
- Watch for real customers and journalists that look like pitches; that's the error that costs you.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
