For executive assistants

Scheduling email, turned into calendar suggestions.

ZipSched reads your principal’s scheduling mail and proposes the calendar change, with the source email attached. You review it, approve it, and the calendar catches up.

  • Microsoft 365 / Outlook
  • Google Workspace

Illustration: a scheduling email asks for 45 minutes on Thursday afternoon. ZipSched turns it into a suggested hold for Thursday, 2:00 to 2:45 PM, with the email attached as its source. The suggestion is approved, and the hold appears on Thursday’s calendar.

Illustrative example. Names and times are fictional.

The problem

The calendar is only as current as the inbox.

Most scheduling still happens over email. Keeping a principal’s calendar in step with it is careful, manual work.

  1. Requests hide in threads

    A time proposed three replies deep. A forward that says “can you set this up?” A CC you only joined today.

  2. Each one becomes a hold by hand

    Read it, check the calendar, create the event, and hope the context behind it survives.

  3. New meetings land on old ones

    When two commitments collide, someone has to notice, decide what moves, and move it.

How it works

From scheduling email to calendar, in four steps.

  1. 01

    It reads the mail

    ZipSched reads scheduling email and picks out who is asking, when, and for how long.

  2. 02

    It checks the calendar

    The request is checked against your principal’s calendar, including any meeting it would collide with.

  3. 03

    It suggests the change

    A new hold, a move, or a draft reply with times, with the source email attached.

  4. 04

    You approve it

    Review the suggestion beside the email it came from, approve it, and the calendar updates.

What you review

Every suggestion arrives with its source.

The email it came from
Each suggestion is attached to the message that prompted it, so you can check the ask before you act on it.
Collisions come with a proposed move
When a new meeting lands on an existing one, the suggestion names the overlap and proposes where the other meeting could go.
Find-times replies wait as drafts
When someone asks for times, the reply is written as an unsent draft in your principal’s mailbox, waiting for your review.

Illustration of three suggestions. First, a new hold for a board deck review on Thursday at 2:00 PM, approved. Second, a new hold for a site visit on Thursday at 3:30 PM that collides with the weekly ops sync, with a proposed move of the ops sync to Friday at 9:30 AM, awaiting review. Third, a draft reply offering three times, saved unsent in the principal’s Outlook drafts.

Illustrative example. Names and times are fictional.

Fits how you already work

Built around the tools you already use.

What it isn’t

  • A replacement for you. It does the reading and the cross-checking. Knowing your principal is still your job.
  • Every calendar system. Microsoft 365 / Outlook and Google Workspace only.

For principals and chiefs of staff

Why it’s worth it for the person whose calendar it is.

Requests stop waiting in the inbox
Scheduling email becomes a calendar suggestion your EA can act on, with the thread behind it one click away.
Your EA’s time goes to judgment
Less copying from email into the calendar. More time for the calls only they can make.
Text a request between meetings
Text ZipSched to schedule something without opening a laptop.
Tomorrow, the evening before
A 5 pm email with the next day’s calendar.
Portrait of Jacob Cremers

Founder

Jacob Cremers

Jacob Cremers studied computer science at Harvard and worked as a data analyst at Harvard Law School. He has built productivity tools for unicorn startups and top-10 lobbying firms.

ZipSched applies that work to one narrow problem: keeping a principal’s calendar in step with the scheduling email that changes it.

Running a principal’s calendar?

Send a short note about your principal’s calendar and how scheduling reaches you today.