Respond to what the buyer actually said
Interest can mean a request for information, a referral, a question or an active problem. Classify the reply accurately without forcing every response into a booking workflow. A useful follow-up acknowledges the specific point and asks only what is needed to choose the next action.
Attach the conversation to the correct account and contact. Check for an existing opportunity or account owner before sending. Record who follows up if a meeting moves and when the conversation should be reviewed. An enthusiastic response can still be lost if nobody accepts it.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Information or question | Buyer asks about scope, use case or feasibility | Provide a relevant answer and a small clarifying question |
| Referral or timing | Buyer names another role or a later condition | Update ownership or a justified review action |
| Active problem | Buyer describes a current issue and willingness to discuss | Arrange discovery with an accountable seller |
Work through the decision
Illustrative reply: 'Interesting—can this handle per-customer enterprise access?' Send a precise answer within the product's actual capability, then ask about the current access workflow. Do not immediately claim the buyer has a $30,000 project.
If the contact refers you to product leadership, preserve the context and avoid making the new contact repeat everything. If they say the timing depends on a planned migration, record that condition rather than scheduling arbitrary follow-ups. The reply should change the workflow.
The buyer receives another cold sequence after replying
Check suppression across connected tools and active account states. Continuing generic outreach after a relevant response signals that the system is not listening. Route human conversations out of automated sequences unless the next communication is deliberately agreed.
A concrete next step
Trace the last five positive replies and compare the next action with what the buyer asked. Repair unowned or misrouted conversations before increasing send volume.
Sources and research notes
- GitLab sales development handbookCompany operating handbook
- Attio: Sharing and permissionsProduct documentation
Primary sources reviewed October 6, 2026. The operating recommendations and worked scenarios are Daavid’s analysis. Illustrative numbers are assumptions, not measured client results. Company marks identify sources and prior experience; they do not imply a customer relationship or endorsement.
Schematic