Skip to main content

​
Tutorial: Paycheck cash flow

Outcome: money is planned against your real pay cycle (not a blank monthly budget). Recurring expenses, debts, and a forecast sit in one app; an optional daily briefing keeps you honest. Domain swap: personal or household; the same pattern works for any period-based cash plan. Keep computed pay dates and installment linking.

​
Step 1 | Prompt in Build mode

Stay in Build mode and send:
Build a paycheck cash flow app for a semi-monthly pay schedule (15th and last business day, skipping weekends and holidays). Roles: owner for now (optional later: viewer who can see but not edit). Track recurring expenses and debts with installment plans mapped to specific paychecks. Show a forecast for the current pay period and the full month. Let me log one-off purchases. Pay dates must be computed, not hard-coded strings. Installments must link to those dates. Optional: a morning briefing that summarizes next pay date, bills due before then, and debt installments due this period. That job must be safe to retry without sending the same digest twice. Optional: receipt photo import that does not hang the chat; I should be able to check progress afterward. Sensitive amounts must stay limited to the right role. No public unauthenticated API.

​
Step 2 | Review the plan by journeys

Approve when these journeys look right:
  1. Schedule: owner sets salary / pay calendar and sees computed upcoming pay dates.
  2. Obligations: owner adds recurring expenses and a debt with a repayment plan tied to those dates.
  3. Forecast: current period and full month show the right deductions for the next paychecks.
  4. Optional digest / receipts: morning briefing and receipt parsing are explicit, retry-safe, and visible under Executions when they run.
Adjust the brief if a journey is missing, then approve.

​
Step 3 | Preview, Access, and Executions

Select a project so Preview uses real project data.
  1. Preview as owner: configure pay dates, add a recurring expense and a debt, open the forecast, confirm the next two paychecks look right.
  2. Log a one-off purchase. If you enabled receipt import, confirm progress under Executions.
  3. If you enabled the morning briefing, run it (or wait for schedule) and confirm under Executions. Retry should not duplicate the digest.
  4. If a partner should view but not edit, ask Build for a viewer role, then Preview as both roles and check App Blueprint → Access.

​
Step 4 | Soft launch

Follow Launch checklist. Keep credit use for daily AI digests in mind under Controlling credits.

​
How to verify (checklist)

  • Pay calendar and recurring items look right for a sample paycheck cycle
  • Preview as owner (and viewer if used): edit rights match the role
  • Morning digest (if enabled) is safe to retry without duplicate emails; check Executions
  • Sensitive amounts are not exposed to the wrong role