Path 05 / Cash flow

I did the work. Now I need to get paid.

Set payment terms and run a follow-up routine that does not depend on memory.

Start with the first artifact 4 lessons · about 40 minutes

Do these in order

Small moves. One working result.

Each lesson completes one decision or artifact. Counts and timings are PickBits starter defaults; the finish line is the work, not the clock.

Atomic lesson 01 10 min working session

Put the payment rule in the agreement

Collection gets harder when price, deposit, due date, and late terms were never explicit.

Done when
Your agreement states the amount, deposit, trigger, due date, and late-payment rule.
You leave with
Payment terms block
Build it

Atomic lesson 02 10 min working session

Check the price can carry the delay

Map when project cash leaves and enters using your approved numbers and dates.

Done when
The price and payment schedule cover delivery cost, tools, tax, and margin.
You leave with
Cash-safe price card
Build it

Atomic lesson 03 10 min working session

Schedule the reminder sequence

A due date should trigger the next action without relying on you to remember it.

Done when
The customer receives a clear reminder before, on, and after the due date.
You leave with
Payment reminder schedule
Build it

Atomic lesson 04 10 min working session

Escalate exceptions without hiding from them

Disputes, hardship, and strategic customers need judgment instead of another automated message.

Done when
The routine names when reminders stop and a human conversation begins.
You leave with
Collection exception rule
Build it

Build with us

Get one useful move each Friday.

We are building these paths in public. Reply with the problem you want us to solve next.