Docs/Projects/Project notes and follow-ups
Projects

Project notes and follow-ups

Notes and follow-ups turn a project from a static record into a working operational tool. They help your team remember context, maintain continuity, and know what action comes next.

Project notes

Project notes are useful for storing:

  • conversation context
  • partner preferences
  • relationship history
  • internal observations
  • blockers
  • reminders for future contact

Notes should help another team member quickly understand the situation.

Follow-ups

Follow-ups help your team track:

  • when to check in next
  • when to send the next message
  • when to review a paused relationship
  • when something needs internal attention

A project with no follow-up often becomes forgotten.

Why these fields matter

Projects are not just about who the target is. They are also about what is happening and what comes next. Notes and follow-ups improve:

  • team memory
  • handoff quality
  • accountability
  • relationship consistency
  • operational clarity

Good note examples

Examples of useful notes:

  • prefers Telegram for communication
  • interested after current mint cycle
  • asked for a revised WL range
  • wants campaign details before moving forward
  • inactive for now, revisit next month

Good follow-up examples

Examples of useful follow-up actions:

  • check reply on Friday
  • send updated offer next week
  • revisit after campaign launch
  • confirm decision with lead tomorrow

πŸ’‘Best practices

  • keep notes short and useful
  • avoid writing vague notes like β€œtalked to them”
  • always leave a next action when possible
  • use follow-ups to prevent projects from going cold
  • update notes right after real interaction, not days later

Deals