Example project

Software Retainer Example

A retainer project where monthly delivery, unresolved bugs, and payment follow-up need careful separation.

Source records

What the workspace reviews.

retainer.pdfMonthly support blockAgreement
github-issues.csvTwo open issuesDelivery context
invoice-204.pdfNet 15Billing
email.emlPayment promised FridayPayment promise

Decision path

The next action comes after context.

1

Collect records

Agreement, approval, delivery, invoice, and open questions are reviewed together.

2

Mark uncertainty

Missing approval, scope changes, or delivery concerns are visible before action.

3

Prepare the message

The user reviews and decides whether to send, confirm, invoice, or wait.

Early access

Help shape a clearer way to run client work.

We are inviting independent professionals and small teams to test with real or anonymized client projects.