Turn pipeline and relationships into careful manual outreach.

Client Outreach Desk gives you 12 outreach rows, 8 message packs, 4 channel blocks, 5 follow-up steps, and an 8-slot proof log. It prepares context. It does not send.

Simple layer. Outreach is not a volume game here. Pick a real person, observe a real signal, adapt one message, review it, and record the outcome before opening another front.

The generator reads Service Offer Kit, Client Pipeline, Proposal Desk, Relationship Engine, Presence Engine, Cashflow Ledger, Daily Ritual, Proof Ledger, and Weekly CEO Review.

Run the desk

node work/life-os-client-outreach-desk.mjs
# or
node work/life-os.mjs outreach

# then open:
outputs/life-os-command-center/client-outreach-desk.md

Use the 12 outreach rows

PersonReplace every placeholder with a real person or company.

SignalWrite the observed context: post, comment, prior talk, referral, or workflow pain.

ChannelChoose LinkedIn comment, LinkedIn DM, X reply, or email manually.

PackAdapt one of the 8 message packs to the specific signal.

ReviewCheck promise, privacy, name, CTA, and tone before any manual send.

OutcomeRecord sent, replied, call-booked, proposal, nurture, parked, or no-send.

Use message packs without sounding generic

1. Warm reconnect
2. Diagnostic question
3. Proof-first reply
4. Call invite
5. Referral ask
6. Proposal nudge
7. Nurture touch
8. Clean park

Proof from this run: Client Outreach Desk writes 12 outreach rows, 8 message packs, 4 channel blocks, 5 follow-up steps, and 9 cockpit captures.

Close the proof log

outputs/life-os-command-center/client-outreach-import.json

The first useful output is not a sent message. It is a clean proof row: person, signal, chosen channel, adapted line, review decision, and outcome.

Guardrails

The desk does not send DMs, emails, comments, proposals, posts, or follow-ups. It does not scrape LinkedIn, X, email, CRM, or private data. Every message needs human review.