Turn signals, conversations, proposals, proof, and cash into one manual sales week.

Sales Week Sprint is the weekly execution layer after social signals and conversation outcomes. It creates 7 days, 7 lead moves, 5 proposal moves, 7 proof moves, 5 cash moves, 6 closeout questions, and 12 import captures without sending, posting, scraping, touching Gmail, or automating payment.

Simple layer. The goal is not to plan the business again. The goal is to make one real commercial week visible: who to move, what proof to use, what proposal to prepare, what cash move to review, and when to stop.

The operator command calls work/life-os-sales-week-sprint.mjs. It writes sales-week-sprint.md, sales-week-sprint.json, and sales-week-import.json from the existing signal, conversation, pipeline, proposal, proof, presence, relationship, and cashflow artifacts.

Run the sprint

node work/life-os.mjs salesweek

# then open:
outputs/life-os-command-center/sales-week-sprint.md

Use the weekly map

7 daysChoose route, open conversations, create proof, diagnose, propose, move cash, and close the week.

7 lead movesPulls social signals, conversation candidates, and outreach rows into a weekly queue.

5 proposal movesKeeps proposals gated by pain, scope, proof, price review, and next decision.

7 proof movesTurns proof assets into safe conversation, proposal, or content support.

5 cash movesReviews forecast, follow-up, invoice queue, and manual money movement.

6 closeout questionsForces the week to end with proof, follow-up, parked decisions, and next week.

Import into the cockpit

sales-week-import.json contains 12 import captures, 1 project, 7 pipeline rows, 5 content rows, 6 learning rows, and 7 rhythm rows. Export the cockpit state first.

Guardrails

The sprint is local-only, manual-only, real-person-required, no-send, no-post, no-scrape, no-Gmail/OAuth, and no-payment-automation. It organizes the week; it does not contact people, publish posts, scrape platforms, issue invoices, move money, or promise revenue.