Make revenue visible before trying to scale it.

The Client Pipeline Tracker turns the acquisition sprint and service offer kit into a visible closing lane: 12 opportunities, 5 stages, follow-up cadence, proposal queue, scorecard, and clear close-or-park decisions.

Simple layer. A lead is not real until it has a signal, a next action, and a proof gate. The tracker prevents sales work from living only in memory.

The generator reads local acquisition and offer artifacts, writes Markdown and JSON, and creates a cockpit import with pipeline rows, capture actions, follow-up rhythm, and no private source paths.

Run the tracker

node work/life-os-client-pipeline-tracker.mjs
# or
node work/life-os.mjs pipeline

# then open:
outputs/life-os-command-center/client-pipeline-tracker.md

The five stages

IdentifyReal name, segment, and observed signal.

DiagnosePain, workflow, cost, and success criteria.

CallAccepted window or clear next date.

ProposalScope, proof gates, price, and decision.

Close or parkYes, no, later, or a reason to pause.

Proof rule

No lead advances without written evidence: observed signal, confirmed pain, next action, proposal, or decision. The system prepares the lane; it does not send DMs, emails, posts, or proposals.

Import into the cockpit

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

Proof from this run: the tracker wrote 12 opportunities, 5 stages, 5 follow-up steps, 4 proposal queue items, and a cockpit import with 12 pipeline rows.