Systems

Routine support replies ready to review

Mailroom sorts incoming mail and drafts support replies from each product's documentation. Routine questions can be handled without writing the same answer again, while flagged messages stay in a review queue. An inbox can send automatically when its configured checks pass.

• Each product has its own documentation for drafting replies
• Held drafts show why they need attention and can be edited before sending
• Escalated threads stay with a person until reviewed
• Daily spending limits and phone alerts help keep the inbox manageable

Product updates drafted from the changes already made

Each Monday, marketing-os reads the product changelogs and prepares blog, social and email drafts in a pull request. I review the copy together and merge it when it is ready. Approved content then publishes on schedule, so release changes do not have to be rewritten for each channel.

• Review the proposed copy in one pull request before it publishes
• Weeks without product news do not produce filler posts
• Schedule approved blog posts, email broadcasts and social updates
• Outbound sequences pause and notify me when delivery or complaint thresholds are reached

The week's dinners planned, emailed and ready to shop

Mealdrop plans the week's dinners from our recipe library, around the calendar and meal preferences. The scheduled run emails the plan and adds the groceries to the configured Kroger cart, ready for review and delivery checkout. Planning dinner no longer starts with a blank week and a separate shopping list.

• Set the meals and servings the household needs, with a calendar for busy nights
• Choose from saved recipes while avoiding recent repeats
• Receive the weekly plan and cooking information by email
• Combine the groceries in a Kroger cart for review, checkout and delivery selection

See Mealdrop

Start the day with the schedule and open work in one email

Life-OS brings the day's schedule, open work and household updates into a morning brief. It arrives in the email digest and is saved in Obsidian, so I can see what needs attention without checking each source. Items still waiting keep their age instead of looking new every day.

• Calendar, project and household updates are gathered before the brief is written
• A source that could not be read is named in the brief
• Open items stay visible until a successful read confirms they are closed
• Routine notifications are grouped into digests, with push delivery used where needed