Close every sales conversation with one written outcome.

Conversation Outcome Log records what happened after a real manual conversation: person, channel, outcome, proof, next action, objection, and value note. It gives you 8 outcome options, 6 follow-up rows, 6 proposal triggers, 6 learning prompts, 8 scorecard metrics, and 12 import captures.

Simple layer. A conversation is not progress until it has a result, evidence, and a next step. This log turns a reply into follow-up, diagnostic, proposal, delivery intake, referral, nurture, parked, or discarded.

The operator command calls work/life-os-conversation-outcome-log.mjs. It writes conversation-outcome-log.md, conversation-outcome-log.json, conversation-outcome-events.json, and conversation-outcome-import.json. The event file is mutable and sanitized.

Run the log

node work/life-os.mjs converse-log --person "Real Person" --channel "LinkedIn" --outcome "follow-up" --proof "Reply logged" --next "Manual follow-up tomorrow"

# then open:
outputs/life-os-command-center/conversation-outcome-log.md

Use the map

8 outcome optionsfollow-up, diagnostic, proposal, delivery-intake, referral, nurture, parked, or discarded.

6 follow-up rowsRecent events come first; empty space falls back to conversation candidates.

6 proposal triggersPain, urgency, decision maker, scope, proof fit, and commercial next step.

12 import capturesCurrent closeout, follow-ups, and outcome options can move into the cockpit after export.

mutable event fileconversation-outcome-events.json grows locally as you append real outcomes.

manual-onlyThe tool logs; it never sends, posts, scrapes, or opens Gmail/OAuth.

Import into the cockpit

conversation-outcome-import.json contains 12 import captures, 1 project, 6 pipeline rows, 6 content rows, 6 learning rows, and 8 rhythm rows. Export the cockpit state first.

Guardrails

The log is local-only, mutable, manual-only, no-send, no-post, no-scrape, and no-Gmail/OAuth. Store sanitized summaries only. Do not copy full DMs, emails, phone numbers, private client data, tokens, local paths, or revenue guarantees.