Follow-up-cadence tracker (low-code -> full-code rung)
Build-along · ~15 min at your own keyboard
Where a business app starts wanting real logic, the rung tilts toward full-code. It reads your leads/contacts sheet, computes days-since-last-touch, and flags who's due. This chains the sheet-pipeline pattern from B11 and previews B12's cron without requiring a deploy: ship the logic first, scheduling is optional stretch. The value is that no lead goes cold because you forgot which day they were on.
Your starter: Follow-up tracker workflow
Workflow stepsMake it yours: Set the cadence to the one you actually keep, name your real CRM or sheet, and change the three touch types to the ones your clients answer.
FOLLOW-UP TRACKER Source: [your CRM export or sheet], one row per person. Each morning: 1. Read the sheet. List everyone whose next-touch date is today or past. 2. For each, draft one touch of the type on their row: [call note / text / mailed card]. 3. Touch text names something true about them from the notes column, never a guess. 4. Show me the list with the drafts. I send; you never do. 5. After I mark sent, write the next-touch date: [your cadence, e.g. 30 days warm, 90 days sphere]. Never add a person I did not add. Never write a message about a property to a person not on that property's row. A fact that is not in the notes column is [CHECK WITH BROKER: fact], never a guess. A message about a listing describes the property, never the people around it.
The coach checks that what you paste back is your own work. The starter pasted back unchanged won't pass.
Do this
0/4Share what happened
Paste your cadence rule, one run's flagged list (names trimmed), and the threshold guard.