Lesson 28 - Proposal Desk
ENPT

Turn interested leads into clear proposal decisions.

Proposal Desk sits between pipeline and delivery. It gives you 6 proposal briefs, pricing options, proof assets, 5 follow-up steps, and a close-or-park board.

Simple layer. Do not send a proposal just because a conversation felt promising. First confirm the lead, pain, scope, proof gate, price range, and decision date.
The generator reads Service Offer Kit, Client Pipeline, Cashflow Ledger, Client Delivery OS, Relationship Engine, Presence Engine, Weekly Review, Daily Brief, and Proof Ledger.

Run the desk

node work/life-os-proposal-desk.mjs
# or
node work/life-os.mjs proposal

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

Use the 6 proposal briefs

LeadReplace placeholders with a real person or company.
PainWrite the observed workflow problem in concrete terms.
ScopeChoose diagnostic, sprint, audit, coaching, or advisory.
ProofName the proof gate and the decision date.

Run follow-up without drifting

1. Send manually only after the brief is complete.
2. Ask what criterion is missing.
3. Share one sanitized proof asset if relevant.
4. Ask for yes, no, later, or a concrete criterion.
5. Park cleanly if there is no real decision.

Import into the cockpit

outputs/life-os-command-center/proposal-desk-import.json
Proof from this run: Proposal Desk writes 6 proposal briefs, 3 pricing options, 5 follow-up steps, 6 close-or-park rows, and 8 cockpit captures.

Guardrails

The desk does not send email, DM, invoice, calendar invite, or post. It prepares the decision. You still review privacy, promises, scope, price, and timing before any manual send.