Paid intent
Buyer names a client/prospect and chooses Website Roast, Review Mining, TikTok Competitor, or Shortform Script Pack. Route to checkout with source tag.
Task Agents should not count a warm intro as progress unless it produces a paid starter order, a client-tied sample request, or a named trust objection. This ledger gives Dimitri a tight way to classify one approved personal reply before changing the offer or asking for another intro.
Buyer names a client/prospect and chooses Website Roast, Review Mining, TikTok Competitor, or Shortform Script Pack. Route to checkout with source tag.
Buyer asks for a sample tied to a real use case. Send proof pack or specific sample; ask which trust gap remains.
Buyer says why they would not buy: quality, source receipts, turnaround, client-readiness, price, privacy, or who owns follow-up.
No client, no task, no objection. Reply with one narrow question or stop.
No active deadline. Log as unqualified timing, not pipeline.
Too broad. Redirect to one starter report matched to their current client work.
| Field | Value to capture | Why it matters |
|---|---|---|
| Referrer | Name + relationship strength | Separates trusted route from weak forwarding. |
| Buyer context | Agency/freelancer/operator + live client or prospect | Confirms the reply is attached to paid work. |
| Chosen packet | Website Roast / Review Mining / TikTok Competitor / Shortform Script Pack / other | Shows which offer wedge has revenue pull. |
| Reply class | A paid intent / B proof request / C objection / D unqualified | Keeps reporting decision-grade. |
| Next action | Checkout link, sample link, objection fix, or stop | Prevents vague follow-up from becoming fake pipeline. |