palm & pine stopped building every calendar twice

“A client asking to swap two posts used to cost me an afternoon. It costs ten minutes now, and none of them are mine.”Noor Hedlund, founder, palm & pine

The order was backwards

palm & pine used their scheduler the way most agencies do. Build the month in the calendar, screenshot it, send the screenshots, then unpick the calendar when the feedback comes back.

That ordering is invisible until you count it. Every piece of client feedback was two pieces of work: the change itself, and the rescheduling around the change. The creative took ten minutes. The calendar took the afternoon.

What was actually happening

• Nothing was ever approved as a month, so nothing was ever finished as a month. Posts sat in a half-agreed state for weeks.
• Time-sensitive posts forced a manual rebalance of the entire queue, every time.
• Approved assets got exported and re-uploaded. That gap is exactly where a client sees the wrong cut go live, and it happened twice.

What changed

Nothing schedules until it is approved. The client reviews the month as a month, in the calendar and feed views their audience will actually see, and signs off in one sitting.

The moment they do, the posts place themselves inside the hours that client set during onboarding, captions, tags and first comment attached. If a network times out, it retries. If something would be rejected before it is sent, it gets fixed first.

Where they are now

Roughly four hours a week came back, none of it from the creative work. Nothing gets exported. And four people run eleven clients without anyone maintaining a private list of what still needs publishing.