ops · $27 · digital download · instant ZIP

Freelance Client Tracker Checklist (SaaS-replacement)

Price: $27 USD · Format: Field system + views + weekly ritual · Delivery: Instant after PayPal

Who this is for

Freelancers who:

• Track clients across Notes, WhatsApp, Sheets, and memory
• Pay $30–$100/mo for CRM tools they barely use
• Need a lightweight system that still catches unpaid invoices

Outcome

One tracker covering Client → Project → Invoice with a 15-minute weekly ritual.

Why this sells

Role-specific freelancer client trackers commonly sell in the $29–$59 range because buyers treat them as a one-time SaaS replacement. $27 hits the impulse sweet spot.

System A — Client record (required fields)

Optional fields: Lifetime value, warmth (1–5), decision-maker, timezone.

System B — Project record

System C — Invoice record

Recommended views

1. Today — next action date = today/overdue
2. Active projects — % done < 100, status active
3. Money risk — invoices overdue
4. Warm leads — status=Lead AND warmth >= 4

Works in Notion, Airtable, Sheets, or paper — fields matter more than the tool.

Weekly ritual (15 minutes, every Friday)

1. Update % done on active projects (3 min)
2. Move next actions that slipped (4 min)
3. Flag overdue invoices + send reminder (5 min)
4. Pick top 3 revenue moves for next week (3 min)

Daily 3-minute open

Open “Today” view → do the first next action before Slack/email rabbit holes.

Setup instructions

1. Create three tables/tabs: Clients, Projects, Invoices
2. Add the fields above
3. Link Projects→Clients and Invoices→Clients
4. Create the four views
5. Import your current 10 hottest clients first (don’t boil the ocean)
6. Run one Friday ritual this week even if incomplete

Common mistakes

• Too many fields on day one → abandon system
• No next action date → tracker becomes a graveyard
• Not reviewing overdue invoices weekly → “surprised” cashflow

ROI

If this prevents one missed follow-up that closes a $500 deal, it pays for itself many times. If it replaces a $29/mo CRM, it pays back in the first month.

Delivery

Full field system + ritual + setup guide after PayPal. Customize naming to your niche.

Bonus deep library (included in your ZIP)

ZIP extras include Sheet/Notion schemas, a filled sample pipeline, weekly ritual print checklist, and install plan.

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###

Pipeline definitions

Lead: no paid work yet

Active: money in motion or delivery in progress

Paused: waiting on client >7 days

Lost: closed lost or 30 days no reply after breakup

Weekly ritual script (read aloud)

1. Sort Today view
2. For each overdue next_action: do it or reschedule with reason
3. For each overdue invoice: send next reminder template
4. Write top 3 revenue moves on a sticky note

Health metrics

• % clients with next_action_date filled
• # overdue invoices
• Avg days invoice→paid
• # stalled projects (no % move in 7 days)

Ultra-detailed appendix

Minimum viable tracker (MVP — week 1 only)

Clients: name, status, next_action, next_action_date

Projects: client, deadline, pct_done, blockers

Invoices: client, amount, due_date, status, link

Add warmth/LTV only after two Friday rituals succeed.

Naming conventions

Clients: Lastname — Company

Projects: YYYY-MM short-slug

Invoices: INV-YYYY-###