Internal Comms & Meetings

How to schedule meetings across timezones as Small RevOps Teams

Internal Comms & MeetingsFor Small RevOps Teams3 apps12 steps~24 min to set up

You're two people supporting thirty reps across three or four time zones, and half your scheduling overhead isn't even your own meetings — it's the back-and-forth threads you're mediating when a rep needs to get a prospect, an SE, and a CSM on a call simultaneously. HubSpot shows you the deal stage but not who's already booked who. Google Calendar is a mess of personal events the reps won't share. You're manually checking availability, DMing everyone on Slack, and still ending up with a hold that works for nobody. Every cross-timezone QBR or pipeline review adds another thirty minutes of coordination you don't have.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small RevOps Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A public booking layer connected to your real calendar availability, so reps can share a direct link and kill the back-and-forth entirely

Automated post-meeting summaries with action items extracted and pushed back into HubSpot deal records or a shared Notion doc — no notes lost, no action items orphaned

A simple coordination app that reads Google Calendar across your team, surfaces conflicts by timezone, and drafts the scheduling email or Slack message for you

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Scheduling Meeting Notes Email Agent

Data sources & config

Starch connects directly to Google Calendar via scheduled sync, keeping availability current without any manual refresh. HubSpot is also a scheduled-sync provider — deal and contact data syncs automatically so the meeting-notes app can match summaries to the right deal record. Gmail is wired as a scheduled-sync provider for the email triage layer. Calendly is connected as a scheduled-sync provider to pull booking history if you already have Calendly in place. Any scheduling tool or calendar system without a direct connection — like a customer's proprietary booking portal — is reachable through browser automation with no API needed.

Prompts to copy

Build me a booking page for my team with three meeting types: 30-min pipeline review, 45-min QBR, and 15-min quick sync. Block 10 minutes before each meeting, show availability in EST by default but adjust automatically for bookers in PST and GMT. Connect to my Google Calendar so it stays live.

After every meeting on my calendar tagged 'pipeline' or 'QBR', generate a summary with key decisions, open questions, and action items. Format action items as a table with owner and due date. Push the summary as a note on the matching HubSpot deal if the meeting title includes a company name.

Every morning at 8am, scan my inbox for any scheduling threads older than 24 hours where no meeting has been booked yet. Draft a follow-up reply for each one that includes my booking link and a one-line context refresh. Flag any threads that involve a deal in the final two stages in HubSpot.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Google Calendar as a scheduled-sync provider. Starch pulls 12 months back and 3 months ahead, so availability is always current.

2 Start from the Calendar Management app in the Starch App Store. It ships with booking-page logic pre-built — fork it and add your three meeting types (15-min, 30-min, 45-min), your buffer rules, and your timezone display preference.

3 Tell Starch: 'Create a public booking page that shows my availability in EST but automatically converts slots for visitors in PST and GMT. Block 10 minutes before each meeting.' You get a shareable link in minutes.

4 Connect HubSpot as a scheduled-sync provider. Starch syncs contacts, companies, deals, and owners on a schedule — this is the data the meeting-notes app will use to match summaries to deal records automatically.

5 Set up the Meeting Notes app. Tell Starch: 'After every calendar event tagged pipeline or QBR, generate a structured summary with decisions, open questions, and action items in a table format with owner and due date.'

6 Add the HubSpot write-back step: 'If the meeting title contains a company name that matches a HubSpot company, post the summary as a note on that deal record automatically.' No copy-paste, no tab-switching.

7 Connect Gmail as a scheduled-sync provider to wire the email triage layer. Starch reads incoming messages and surfaces threads by priority, not just recency.

8 Activate the Email Agent and tell it: 'Flag any scheduling thread older than 24 hours where no booking confirmation exists. Draft a follow-up with my booking link and a one-sentence context reminder. Mark as urgent if the related deal is in Commit or Best Case stage in HubSpot.'

9 Build a lightweight coordination view: 'Show me a table of all external meetings my team has booked this week, grouped by rep, with the deal stage and timezone of each external attendee pulled from HubSpot.' This becomes your weekly capacity snapshot without touching a spreadsheet.

10 Share the booking link with your reps via a Slack message Starch drafts for you: 'Draft a Slack message to the #revops channel explaining how to use the new booking link, what the three meeting types are, and what not to book manually anymore.'

11 Each Monday, review the action-item log Starch has assembled from the prior week's meeting summaries. Tell Starch: 'Pull all action items from meetings in the last 7 days where the assigned owner hasn't confirmed completion. Format as a Slack digest I can send to the team.'

12 As the team grows, fork the scheduling app to add new meeting types or add a second calendar owner without rebuilding anything from scratch — describe the change and Starch updates the app.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

March 2026 West Coast QBR Coordination

Sample numbers from a real run

Scheduling threads resolved via booking link (vs. manual)	14
Minutes saved per avoided back-and-forth thread (avg)	22
HubSpot deal notes auto-populated from meeting summaries	11
Action items extracted and assigned across 6 QBR calls	34
Reps who used the booking link vs. Slacked RevOps directly	12

In the first week of March, you had six QBR calls scheduled across EST, PST, and GMT+1 for a UK-based enterprise prospect. Historically this would mean six separate 'when are you free?' chains, each pulling in the rep, the SE, and you as the scheduler-of-last-resort. Instead, the Calendar Management app you forked generated a booking link showing combined availability for the rep and SE automatically. The UK prospect booked the GMT+1-friendly slot without anyone doing the timezone math manually. After each of the six calls, Meeting Notes generated a structured summary — decisions, blockers, action items — and posted it as a note directly on the matching HubSpot deal record. Across those six calls, Starch extracted 34 action items and assigned 28 of them to named owners without you touching a doc. At the Monday standup, you sent the team a Slack digest of the 6 items with no confirmed completion — drafted by the Email Agent in about 40 seconds. Total RevOps time spent on QBR scheduling coordination that week: under 30 minutes, down from roughly 3 hours in February.

Measurement

How you'll know it's working

Time from meeting request to confirmed booking (target: under 4 hours without RevOps involvement)

% of deal-related meetings with a HubSpot note posted automatically within 24 hours

Action item completion rate tracked from meeting summaries week-over-week

Number of scheduling threads that required manual RevOps intervention vs. resolved via booking link

Rep adoption rate of the shared booking link (tracked via Calendly bookings synced to Starch)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Calendly alone

Calendly handles the booking page well but doesn't know your deal stage, doesn't write meeting notes back to HubSpot, and doesn't triage the inbox threads where a rep never used the link in the first place.

HubSpot Meetings

Built into HubSpot so deal association is automatic, but there's no AI triage layer, no action-item extraction, and no way to handle scheduling for reps using a CRM that isn't HubSpot (like Salesforce or Pipedrive reps on the same team).

Notion + manual notes workflow

Cheap and familiar, but someone still has to take the notes, copy them to Notion, tag the deal, and chase action-item owners — which means it's usually you doing it after the call.

Otter.ai or Fireflies for transcription

Good at transcription but siloed — summaries don't route to HubSpot deal records automatically, and there's no connection to your inbox triage or booking layer, so you're still stitching three tools together.

On Starch RECOMMENDED

One platform — scheduling, meeting notes, email agent all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Can Starch actually write meeting notes back to the right HubSpot deal, or do I have to map that manually?

If the meeting title or attendee list includes a company name or contact that matches a HubSpot record, the Meeting Notes app can post the summary as a note on that deal automatically. You describe the matching rule in plain language — for example, 'match on company name in the meeting title' — and Starch handles the lookup. HubSpot is a scheduled-sync provider, so contacts, companies, and deal data are already in Starch and available for matching without a live API call during the meeting.

We have reps on Salesforce, not just HubSpot. Does this still work?

Yes. Salesforce is available from Starch's integration catalog — connect it and the agent queries it live when your app needs deal or contact data. You can build a coordination app that reads from both HubSpot and Salesforce simultaneously, which is useful if your team is mid-migration or running a split stack.

What if a rep's calendar is private and they won't share it?

The booking-page layer only needs the rep's Google Calendar connection to show availability — it doesn't expose the event details or titles to the booker. If a rep genuinely won't connect their calendar, browser automation can interact with calendar-sharing tools that have a web interface, but for best results the Google Calendar scheduled-sync connection is the right path.

Is Starch SOC 2 certified? We handle enterprise deal data.

Not yet — Starch is not SOC 2 Type II certified as of today. That's worth knowing if your security review requires it. It's on the roadmap, but we won't claim it before it's done.

We already use Calendly. Do we have to replace it?

No. Calendly is a scheduled-sync provider in Starch, so your existing booking history and event data syncs into Starch automatically. You can keep Calendly as your public booking layer and use Starch to build the automation on top — routing summaries to HubSpot, triaging inbox threads, extracting action items — without migrating off a tool your reps already know.

How does the email triage layer know which threads are scheduling-related?

You describe the filter in plain language when you set up the Email Agent — for example, 'flag any thread where someone asks about availability or meeting times, where no calendar invite has been created, and the thread is older than 24 hours.' The agent reads your Gmail inbox (connected as a scheduled-sync provider) and applies that logic on its morning scan. You can tune the filter anytime by describing the change.