Which reminder would you trust automation with first?
Friendly invoice reminders for small creative teams.
The milestones that explain how the project has evolved.
The project started with a simple need: Friendly invoice reminders for small creative teams.
The first build kept Daylight Queue focused on one useful workflow before adding broader tooling.
The first reminder preview went to four freelancers. They wanted to edit the tone before a message ever left the app, so the preview moved ahead of scheduling.
Snooze and quiet hours are in the small-team build now. The useful test is whether an owner can set it up between client calls without reading a guide.
Public updates from the builder about this project.
Which reminder would you trust automation with first?
new list view is less 'spreadsheet wearing a fake mustache' at least. four freelancers are kicking the tires this week.
function nextReminder(lastSentAt, quietDays = 3) {
return new Date(lastSentAt.getTime() + quietDays * 864e5);
}Spent an hour blaming timezones. Turns out my test account was set to yesterday 🙃 fix is on staging now, naturally.
Cut setup from 7 screens to 3. Still kinda ugly, but you don't need a minor in my database to send a reminder now lol.
Help Daylight Queue learn from real people.
Try setting up one reminder for a sample invoice. Where did you pause or wonder what would happen next?
Sign in to respond to this request.
Conversation
Share an idea, a question, or a useful experience.
Sign in to comment.
No comments yet