Gmail Reader: GTM weekly planning from your inbox
LoginSign Up
See All Examples
For
FounderGrowthMarketing
Topics
Growth opsWeekly planning
Used with
Product funnel dashboard for founders & teamsMarketing initiative tracker with Slack weekly rollups
Gmail Reader

GTM weekly planning seeded from your inbox

A weekly GTM planning board where this week’s plan items can be seeded automatically from starred or labelled emails — turning inbox commitments into the next week’s plan without re-typing them.

The inbox is a to-do list nobody asked for and nobody planned to keep. Every week starts with promises made in email; most weeks end with a few of them forgotten. Wiring the inbox into the planning surface stops that.

Email is a planning surface in disguise

For founders and operators, most weekly commitments originate in email. “I’ll get you that next week.” “Let’s circle back on this Tuesday.” “Sending the deck Monday morning.” The trouble is the inbox isn’t a planning tool — it’s a queue. Promises arrive, get triaged, and the ones that don’t make it into a separate planning doc usually evaporate.

The standard advice is “move email commitments into your todo list.” The standard outcome is that you don’t. This example removes the manual step: star or label an email, and a plan item appears in next week’s GTM plan automatically.

Weekly Plans + GTM Items on one board

The workspace has two pages. The Weekly Planning page lists every plan you’ve created, organised by week. The Weekly Plan Detail page shows the items in a given week — what you committed to, what’s still open, what closed. Both surfaces also exist outside the inbox-seeding flow: you can add plan items by hand whenever you want.

Star or label, plan item appears

  1. An email arrives in your inbox. The workspace watches your inbox for new messages — drafts and messages added to other labels stay out of the flow.
  2. You star it (or apply a configured label). The flag tells the workspace this email is a planning commitment. The agent watches for the change and picks it up.
  3. A new plan item appears in next week’s plan. The subject becomes the item title; the email snippet becomes the context note. A link back to the email is preserved so you can find the full thread.
  4. Reorder, edit, or close. The workspace doesn’t prescribe a planning style — the plan item is yours to shape. The point is that it’s here, not still floating in the inbox.

Trigger signal, target week, item shape

  • Trigger signal — defaults to the Gmail “starred” flag, which works for most people with no extra setup. If your starring habit is already saturated, configure a dedicated Gmail label (e.g. plan-this) and the workspace will watch for that label instead.
  • Target week — by default, plan items seed into the upcoming week’s plan (the next Monday-to-Sunday window). For teams running rolling two-week plans, target the current week instead.
  • Item shape — title from email subject, context from snippet, link back to the email thread. Tune the snippet length if your emails are typically long.
  • Per-user filtering — each user’s starred or labelled emails seed only their own plan. Shared workspaces stay personal at the planning surface.
  • Manual addition — the inbox flow is opt-in convenience, not the only path. Add plan items by hand from the Weekly Planning page whenever a commitment arrives outside email.

The inbox stops being a place commitments go to die. Star, and the plan item appears where you’ll actually see it next week.

Star this week, planned next week

Inbox-driven workflows are exactly where the spec-driven approach pays off the most. The pieces — watch the inbox for new mail, filter on a flag, write a plan-item entity — are individually small and individually brittle. Maintained as one description, they become a single thing that either works or doesn’t. The spec is what you change when your starring habit moves to a label, or when next week’s plan should accept commitments two weeks out instead of one.

Try it in your Workspace