Would you answer two questions before sending a cold request?
I'm building Portunio, an AI-first email experience with the agent on the sender's side. The design question I'm testing is how much clarification is useful before it becomes a barrier to reaching someone.
Here's an illustrative example, not a customer result:
A sender writes: ‘I'd love to collaborate. Can we jump on a call?’
Instead of polishing that sentence, the agent could ask:
- What would you like to work on together?
- What can you offer, and what decision do you need from this person?
The sender might then choose to say: ‘I'm proposing a guest workshop on onboarding for your founder community. I can bring a 20-minute exercise and a sample agenda. Would you like to see the agenda before deciding?’
That last version only helps if the details actually came from the sender. Inventing a convincing offer would make the request worse. The sender needs to review it, and the recipient still decides whether to engage.
The tradeoff: the recipient gets more context, but the sender does more work. Someone with a valuable but half-formed idea might leave. I'm interested in measuring both the time spent clarifying and the follow-up questions still needed afterward. I don't have outcome data proving this works yet.
If you regularly send or receive collaboration requests, would you tolerate those two questions? What would make you abandon the flow?
You can preview a request at https://portunio.com/ramikhalil (please label a hypothetical example ‘pilot test’). The waiting list is at https://portunio.com. Feedback on the tradeoff is welcome even if you don't sign up.
The tradeoff is really send friction vs. less back-and-forth. Have you tested how often senders answer both questions versus abandoning the request?
Not with a reliable completion-versus-abandonment result yet. We also found a gap in our visit tracking today, so I can't honestly use those numbers as evidence. For a small observed pilot, I'd record where each sender stops, time spent, and whether they return; then ask the recipient how many clarifying follow-ups they still need. I'd keep 'decided this wasn't a fit' separate from 'wanted to send but the questions got in the way.' A higher completion rate alone wouldn't prove the questions helped. Have you found a useful way to distinguish those two reasons for stopping?
That distinction is exactly what I’d be interested in digging into. If you’re open to it, what’s the best email to reach you on?
Happy to dig into it. You can reach me through my Portunio page: https://portunio.com/ramikhalil — mention our Indie Hackers discussion so I have the context. If you have an anonymized example, include that too. And if the clarification step itself gets in your way, tell me here; that would be useful feedback for exactly what we're discussing.
I've been on both sides of this — sending outreach and receiving it.
One pattern that works without adding much friction: ask the sender to state (1) the outcome they want and (2) why this person specifically. That filters "can we jump on a call?" spam while still letting a real opportunity through.
Where it gets harmful: if the gate feels like homework before the recipient even knows the topic. Keep it to one breath — a sentence, not a form. Recruiters especially feel this tension: personalization helps, but candidates bounce when every first touch asks them to fill something out.
Curious how you're measuring whether the clarification step increases reply quality vs just reducing volume.
The recruiter example makes the cost of the extra step concrete. I don't have evidence of improved reply quality yet. The test I'd run is whether the recipient can identify the proposed outcome, why it fits them, and the next decision without another clarification message. I'd report that alongside sender time and abandonment, including people who never finish, rather than celebrate fewer messages reaching the inbox. Your 'one breath' suggestion is useful: extract what's already in the first message and only ask about a missing detail. If you're open to trying the preview linked above with an anonymized example, the most useful feedback would be the exact question that feels like unnecessary homework. No need to submit a real request.
The useful guardrail is making the sender state the outcome in one sentence before the rewrite. If they can’t say what they want and why this person, the request probably isn’t ready to send.
I like that as the first thing to clarify. I'd be careful about turning it into a hard gate, though: someone with a useful but half-formed idea might need help finding that sentence. The boundary I'd want is that the sender supplies the substance and confirms the outcome; the agent shouldn't invent a reason this person is a fit. Your suggestion gives us a simple first check before asking anything else.