The nudge that keeps deals warm
Freelance work dies from silence, not bad proposals. A small workflow over the engagements pipeline that reads the timestamps nobody's watching and pushes the one follow-up about to fall through a crack — rules, not vibes.
Freelance work doesn't die from bad proposals. It dies from silence — the follow-up you meant to send, the proposal that's been sent for nine days, the warm lead you forgot existed. So I built a small nudge workflow over the engagements pipeline: a process whose entire job is to notice the thing about to fall through a crack and put it back in front of me.
The shape of the problem
The freelance surface already has the data — jobs, proposals, and the connector between a lead and the thing I sent them. What it didn't have was time pressure made legible. A proposal row knows when it was sent. Nothing was reading that timestamp and asking the only question that matters: is this one going quiet?
The nudge workflow is the reader. It sweeps the pipeline on a schedule, scores each engagement by how long it's been since the last meaningful touch, and surfaces the ones crossing a threshold — not as a dashboard I have to remember to open, but as a push I can't ignore.
Rules, not vibes
A nudge that fires too often becomes noise you learn to swipe away, so the logic is deliberately conservative:
- Stage-aware timing. A fresh lead gets a 48-hour nudge; a sent proposal gets one at day 5 and again at day 12; a won engagement rolls into a kickoff reminder instead.
- One nudge per engagement per window. No re-pinging the same row daily — that's how people start ignoring the channel.
- Quiet hours and a single digest. Nudges batch into one message rather than trickling in, so the workflow respects attention the same way I'd want a client to respect mine.
Why this is infrastructure, not a feature
Nobody visits a nudge. It has no page. Its success metric is the negative space — proposals that didn't go cold, follow-ups that happened on time — which is exactly the kind of value that's invisible until it's missing. It rides the same pattern as the rest of the plumbing here: read an existing spine, encode a rule about what shouldn't be left to memory, and route the result somewhere I'll actually see it. The pipeline was always the asset. The nudge just makes sure I don't let it rot.
Get the next one
An occasional note when something genuinely new ships here — essays, free tools, projects. No schedule, no filler, easy out.
Need something like this built?
I design and ship AI tools, full-stack apps, and data pipelines — end to end, to production. Tell me the problem in a sentence; I'll give you an honest read on fit within a day.
Work with me →