Recurring email examples for web developers and studios — post-launch check-ins, referral asks and client catch-ups that turn one-off projects into ongoing relationships and repeat work.
“Did you publish this week?”
A weekly yes/no checkpoint on whether you published anything — post, email, video, anything.
“Standup — reply with your 3”
A daily prompt that runs your async standup — the team's replies carry the fresh content, not the email.
“Anything blocking you today?”
A one-question daily prompt that surfaces blockers early — reply if you're stuck, silence if you're not.
“Increase your odds to get a new client”
A daily nudge to do one concrete thing toward a new client — then reply with what you did.
“What are you shipping this week?”
Name one thing you'll ship this week to someone who'll notice if you don't.
“Sprint planning tomorrow — prep the top of the backlog”
A reminder that lands the day before planning — groom the top of the backlog, size it, flag dependencies.
“How are things?”
A warm, no-agenda check-in with past clients every six months — the cheapest source of repeat work and referrals there i...
“How's [the site] working out?”
A friendly check-in a few months after delivery that reopens the door for more work and referrals.
“20 minutes on the backlog this week”
A weekly nudge to spend 20 minutes refining the backlog — prune, clarify, re-rank — before it rots.
“Retro: what should we keep, drop, change?”
A Friday prompt that gathers retro input before the meeting — what went well, what didn't, what we change next.
“Quick question”
A low-pressure referral ask, sent to past clients every few months. Most sends get ignored — but it keeps you top of min...
“Show us what you built this week 📸”
A weekly prompt asking everyone to drop a screenshot, clip, or link of what they shipped — async demo day.
“Product update — shipped / next / needs a decision”
A weekly prompt to the product trio and stakeholders — what shipped, what's next, what needs a decision.
