Social Rails

A week, kept.

Built for Macale by Ross Pettitt. Three fictional clients, your real roles, one Monday-to-Friday run the way I'd run it. Pick a day. Change a date. Watch what moves.

1The board

2The tracker

Edit a due date, a status, or an asset box. The board, the nudges, and the flag to Macale recompute.
DeliverableStepOwnerDueStatusAssetFlag

3Nudges, drafted at 11:00

4To Macale, at 2:00

5Monday meeting, turned into action items

6The Friday client note

7How I'd run your accounts

The rhythm

  • Monday meeting becomes action items in the tracker, each with an owner and a date.
  • 9:00 every weekday: the sweep reads every tracker and checks every date.
  • 11:00: one nudge drafted per thing that slipped, addressed to the person who owns it.
  • 2:00: a three-line note to you, only when a client date is at risk, with options attached.
  • 7 PM: I review, send the human parts, and write down any revised timeline.
  • Friday: client notes drafted before you wake up.

What you get

  • A tracker that is true.
  • Nobody chased twice, nobody forgotten.
  • No Friday surprise.
  • A short note when something needs you, and silence when nothing does.
  • Client notes drafted, not written from scratch.

What stays human

  • Tone with clients.
  • What to push and what to hold.
  • Anything with money in it.
  • Every client-facing send during the trial. Drafts by day, sends by me, until you say otherwise.

Week one, I'd need

  • Read access to the trackers and the Dropbox folder list.
  • The team's names and roles.
  • The meeting recording or transcript.
  • One client note you liked, so I match your voice.
The honest part about hours. The checking runs during your business day. The judgment gets my eyes at 7 PM Eastern on weekdays. Anything that can't wait goes to you at 2:00 with options attached, so a decision is never stuck behind my calendar. A small program I wrote does the checking. I do the judgment.